cancel
Showing results for 
Search instead for 
Did you mean: 

Calling adapter module in PI7.1

Former Member
0 Kudos

Hello,

I have migrated an adpater module from XI3.0 and deployed it successfully, but I get an error ("Object not found") at runtime. I have the suspicion that the expression I use in the com channel for referencing the module is wrong.

The module shall be used in a communication channel of type file adapter.

What exactly do I have to enter on the module tab?

My EJB is called ProcessingInstructionModule, it's in a package called com.sapcons.xi.af.conversion, the provider is sap.com.

So I tried

localejbs/sap.com/com.sapcons.xi.af.conversion/ProcessingInstructionModule

com.sapcons.xi.af.conversion/ProcessingInstructionModule

and several other combinations but always got

"Object not found in lookup of com.sapcons.xi.af.conversion"

or

"exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at com.sapcons.xi.af.conversion, the whole lookup name is localejbs/sap.com/com.sapcons.xi.af.conversion/ProcessingInstructionModule"

Any idea?

Thank in advance

Rainer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

check this blog:

/people/udo.paltzer/blog/2007/04/26/new-sap-netweaver-process-integration-release-planned-for-2007

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00838345-708c-2a10-1199-9514c0b0...

Note: reward points if solution found helpfull

Regards

Chandrakanth.k

Former Member

Answers (4)

Answers (4)

Former Member
0 Kudos

I am also facing same problem......my probblem in PI7.0 only.....any solution for this....

stefan_grube
Active Contributor
0 Kudos

> and several other combinations but always got

> "Object not found in lookup of com.sapcons.xi.af.conversion"

> or

> "exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at com.sapcons.xi.af.conversion, the whole lookup name is localejbs/sap.com/com.sapcons.xi.af.conversion/ProcessingInstructionModule"

Hi Rainer,

first of all go to the NWA and check, if your module is active. Then check the JNDI name.

In the module chain you just enter the JNDI name, nothing else.

Regards

Stefan

vijay_b4
Active Contributor
0 Kudos
Former Member
0 Kudos

Hello,

migrating an adpater module..needs

Steps in the SAP NetWeaver Developer Studio:

1. Create an EJB J2EE 1.4 module project

2. Apply the libraries (at least com.sap.aii.af.lib.mod.jar and

com.sap.aii.af.ms.ifc_api.jar)

3. Create a package

4. Create a stateless session bean

5. Apply the code of the adapter module

6. Modify the Java code of the adapter module

7. Adjust the ejb-jar.xml

8. Adjust the ejb-j2ee-engine.xml

Steps to be preformed for migration to SAP NetWeaver 7.1

u2013 In principle, these are the same steps as for a new deployment

u2013 First: Create an EJB 1.4 module project. New adapter modules are still based on EJB 2.0, not the

new EJB 3.0

u2013 Next: Apply the new libraries

u2013 Create a package

u2013 Create a stateless session bean

u2013 Apply the code of the old adapter module

u2013 Modify the Java code of the adapter module

u2013 You have to adjust the two library deployment descriptor files

Libraries for AF 3.0/7.0

aii_af_mp.jar

aii_af_ms_api.jar

aii_af_trace.jar

aii_af_svc.jar

aii_af_cpa.jar

Libraries for AF 7.1

com.sap.aii.af.lib.mod.jar

com.sap.aii.af.ms.ifc_api.jar

sap.comtcloggingjavaimpl.jar

com.sap.aii.af.svc_api.jar

com.sap.aii.af.cpa.svc_api.jar

+++++++++++++++++++++++++++

The interface module

com.sap.aii.af.mp.module -> com.sap.aii.af.lib.mp.module

Dealing with payload and attachments

com.sap.aii.af.ra.ms.api -> com.sap.engine.interfaces.messaging.api

Writing in audit log

com.sap.aii.af.service.auditlog ->

com.sap.engine.interfaces.messaging.api.auditlog

Writing in J2EE server log

com.sap.aii.af.service.trace -> com.sap.tc.logging

Accessing communication channel data

com.sap.aii.af.service.cpa -> com.sap.aii.af.service.administration.api.cpa or

com.sap.aii.af.service.cpa

For the module migration, you have to adjust the

import statements in your Java code.

􀂄 As the package names changed in PI 7.1, you have to adjust the import statements

in your adapter code.

􀂄 A lot of class names did not change, so you have to adjust the code of adapter

development only for special cases, which are described on the following slides

*************rEWARD POINTS,IF FOUND USEFUL