Adapter Module Deployment in PI 7.3

[Former Member]

Hello all,

I had created an adapter module which needs to be used on SOAP adapter.I am facing some issues with it please share your inputs in this....

1. We had deployed .ear file in visual admin is this correct? or .ear file needs to be converted to .sda or .sca before deployment.?

2. Once after deployment , in CC module configuaration which name we need to give ? does it should start with sap.com/modulename or AF_Modules/modulename .

3. Modulename : is this the name of the java class name or the whole file ear file name.

4. I do not need any module configuaration can I leave that section blank and leave module key field with either 0 or 1.??

Please share you inputs.

Thanks in advance.

[Former Member · Accepted solution]

Hi,

>>We had deployed .ear file in visual admin is this correct? or .ear file needs to be converted to .sda or .sca before deployment.?

You can deploy .ear file directly from NWDS and in case you are deploying using JSPM then you have to convert the .ear file into .sda file. Search SDN there are few articles/wiki availbale on the same.

>>Once after deployment , in CC module configuaration which name we need to give ? does it should start with sap.com/modulename or AF_Modules/modulename .

localejbs/JNDI NAME

>> I do not need any module configuaration can I leave that section blank and leave module key field with either 0 or 1.??

You can leave module configuration section as blank if u are not passing anything to ur adapter module.

>>Modulename : is this the name of the java class name or the whole file ear file name.

Its the ejb java class name.

Thanks

Amit Srivastava

[Former Member · Accepted solution]

Thanks Amit for your response.

Basis team deployed it using Hotfixes in JPSM 7.3

However when tried to run end to end SOAP channel showing error as "exception caught with cause com.sap.engine.services.jndi.persistent.exceptions720.NameNotFoundException: Object not found in lookup of 'XXXXXXX'

BUt in JNDI registry entries in NWA there is no "localejbs root"- and I can not see the module any where.

But from HotFixes screen shot it is shwoing as success.

Few doubts:

1. Do we need to restart the server after deploying modules inorder they are visibile in NWA.

2. is there a way to check that module is deployed successfully ?

3. if .ear file is not formed well, still we need to see it in localejbs root node in JNDI registry..is this correct?

If possible please share document which shows step by step how to deploy module and check in PI 7.3

Thanks in advance.

[Former Member · Accepted solution]

Hi,

I think you need to convert .ear to .sda file and then deploy it using JSPM (if i am not wrong u can only deploy .sda file using JSPM). Cross check with ur basis team. You error description clearly suggest that module is not deployed correctly.

>>Do we need to restart the server after deploying modules inorder they are visibile in NWA.

Generally it is not required but u can take a java restart. I remember doing it once because my new deployed module was not getting reflected but never done after that (deployed many adapter modules).

>>is there a way to check that module is deployed successfully ?

Under NWA -> you can check under JNDI browser -> under localejbs

You can also check the java trace file under NWA

Thanks

Amit Srivastava

[Former Member · Accepted solution]

HI Amit...Thanks for the response....i could not able to find where I give points for this...

I had still issue with this:

Basis team tried converting to .sda and deployed it but i can not find the localejbs root node in JNDI registry.... where can I check? I believe the deployment is not success but Basis team saying its success.

Is there any other way where we can look at the deployed modules and and use them in communication channels?

Thanks.

[Former Member · Accepted solution]

Hi,

>> i can not find the localejbs root node in

Under JNDI browser -> select "Context Name" and serach for  "localejbs".

As stated above, please check the java trace file logs under NWA. Also, check below artricle for converting .ear to .sda file (below article is for PI7.1 but u can refer it for PI7.3 also, i dont think the steps will change)

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20a221c6-3943-2e10-5198-dada408de...

Thanks

Amit Srivastava

[anand_solanki]

Hi Amit,

We are facing a similar issue in my project ?

we are using PI7.31 .

Basis team is using only the jar file for deployment ( not sure if that is ok).

You can refer my thread http://scn.sap.com/thread/3408662

Please provide your mobile number if possible, so that i can directly get in touch wth you.

Getting the follwoing error

Error occurred while trying to load com.sap.adaptermodule.MMTKToXML_ConversionBean

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:250)

at com.sap.engine.services.ejb3.runtime.impl.Actions_BeanClassesInitialization.loadApplicationClass(Actions_BeanClassesInitialization.java:54)

at com.sap.engine.services.ejb3.runtime.impl.Actions_BeanClassesInitialization.loadApplicationClasses(Actions_BeanClassesInitialization.java:41)

at com.sap.engine.services.ejb3.runtime.impl.Actions_ComponentInterfacesProviderClassesInitialization.loadApplicationClasses(Actions_ComponentInterfacesProviderClassesInitialization.java:20)

at com.sap.engine.services.ejb3.runtime.impl.Actions_SessionBeanClassesInitialization.loadApplicationClasses(Actions_SessionBeanClassesInitialization.java:20)

at com.sap.engine.services.ejb3.runtime.impl.Actions_StatelessBeanClassesInitialization.loadApplicationClasses(Actions_StatelessBeanClassesInitialization.java:18)

at com.sap.engine.services.ejb3.runtime.impl.Actions_BeanClassesInitialization.perform(Actions_BeanClassesInitialization.java:27)

at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:84)

at com.sap.engine.services.ejb3.container.ApplicationStarter.perform(ApplicationStarter.java:213)

at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:957)

at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.prepareStart(ContainerInterfaceImpl.java:462)

at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:508)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:393)

... 24 more

Caused by: java.lang.NoClassDefFoundError: com/sap/aii/af/lib/mp/module/Module

at java.lang.ClassLoader.defineClass1(Native Method)

at java.lang.ClassLoader.defineClassCond(ClassLoader.java:724)

at java.lang.ClassLoader.defineClass(ClassLoader.java:705)

at com.sap.engine.boot.loader.ResourceMultiParentClassLoader.loadClassLocal(ResourceMultiParentClassLoader.java:189)

at com.sap.engine.boot.loader.MultiParentClassLoader.findClassInLoaderGraph(MultiParentClassLoader.java:316)

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:275)

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:247)

... 36 more

Caused by: java.lang.ClassNotFoundException: com.sap.aii.af.lib.mp.module.Module

------------------------- Loader Info -------------------------

ClassLoader name: [JavaEE/MMTKToXML_Conversion]

Loader hash code: ef8b912

Living status: alive

Direct parent loaders:

   [system:Frame]

   [interface:webservices]

   [interface:cross]

   [interface:security]

   [interface:transactionext]

   [library:webservices_lib]

   [library:opensql]

   [library:jms]

   [library:ejb20]

   [service:p4]

   [service:ejb]

   [service:servlet_jsp]

Resources:

   /usr/sap/X70/DVEBMGS00/j2ee/cluster/apps/JavaEE/MMTKToXML_Conversion/EJBContainer/applicationjars/MMTKToXML_Conversion.jar

Your friend,

Anand Solanki

[Former Member]

Anand... did you ever resolve this issue? I'm facing exactly the same... Thx.

[sugata_bagchi2]

Hi Anand,

If you have developed the EJB using NWDS, you can deploy the same from NWDS it self. For this you just need to have the proper J2EE admin authorization.

you have to select the target J2EE as your AS Java host in NWDS and from NWDS you can deploy the same using "Run on Server" feature. But you must have your EAR created for this,
You can even deploy your adapter module as an external EAR from NWDS  while you are in Deploy View.

You can refer this document.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90c937e8-9e91-2d10-59a5-8994a98c3...

Thanks

Sugata B

[Former Member]

Hello all,

Deployed user module in PI 7.3 , while deploying logs shows warning message as:

status="SUCCESS" dplorder="0" description="1. Warning occurred on server 5146550 during deploy of XXXXXXXXX : EJB Model Builder: ASJ.ejb.004101 stateless bean "XXXXXXXX" should have at least one of the following interface pairs: "local" and "local-home", "home" and "remote" or service endpoint interface (Location:META-INF/ejb-jar.xml)[message resource bundle missing], severity: warning CSN component of deployment item is not available" vendor="sap.com"

While constructing ear file I had removed the local,local-home,remote home.java as suggested in the  How to guide for adapter module in PI 7.1

I am still facing this error.

In communication channel also errored as Object Not found.

I can see the module in JNDI>localejbs...

Please share inputs.

Thnaks.