Adapter Module Problems in SAP PI 711

[socrates_socratous2]

Hi,

  we recently update SAP PI to & 711 and I had to migrate the custome module adapter! I perform all stepa necessary but when I deploy the EAR file I get a warning:

1. Exception has been returned while the [sap.com/EPA_NewDias_EAR] was starting. Warning/Exception :[

][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/EPA_NewDias_EAR].]

And in the communication channel I get ana error:

  Error:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception
during lookup operation of object with name
localejbs/DiasParseFile_DXreosis_NEW, cannot resolve object reference. [Root
exception is javax.naming.NamingException: Error occurs while the EJB Object
Factory trying to resolve JNDI reference Reference Class Name: Type:
clientAppName Content: sap.com/EPA_NewDias_EAR Type: interfaceType Content:
local Type: ejb-link Content: DiasParseFile_DXreosis_NEW Type: jndi-name
Content: DiasParseFile_DXreosis_NEW Type: local-home Content:
com.sap.aii.af.lib.mp.module.ModuleLocalHome Type: local Content:
com.sap.aii.af.lib.mp.module.ModuleLocal
com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException:
Cannot start applicationsap.com/EPA_NewDias_EAR; nested exception is:
java.rmi.RemoteException: [ERROR CODE DPL.DS.6125] Error occurred while starting
application locally and wait.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE
DPL.DS.5029] Exception in operation [startApp] with application
[sap.com/EPA_NewDias_EAR]. at
com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:315)
at
com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:106)
at
com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55)
at
com.sap.engine.services.ejb3.runtime.impl.EJBObjectFactory.getObjectInstance(EJBObjectFactory.java:144)
at
com.sap.engine.services.ejb3.runtime.impl.EJBObjectFactory.getObjectInstance(EJBObjectFactory.java:63)
at
com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:77)
at
com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:33)
at
com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:228)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:283) at
com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:434)
at
com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:223)
at
com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:242)
at javax.naming.InitialContext.lookup(InitialContext.java:351) at
javax.naming.InitialContext.lookup(InitialContext.java:351) at
com.sap.aii.af.lib.util.ejb.FastEjbFactory.createEjbInstance(FastEjbFactory.java:69)
at
com.sap.aii.af.lib.util.ejb.FastEjbFactory.createEjbInstance(FastEjbFactory.java:50)
at
com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.getModuleLocal(ModuleProcessorBean.java:419)
at
com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:287)
at sun.reflect.GeneratedMethodAccessor319.invoke(Unknown Source) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592) at
com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:74)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at
com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at
com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sun.proxy.$Proxy258.process(Unknown Source) at
com.sap.aii.adapter.file.File2XI.send(File2XI.java:3519) at
com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1345) at
com.sap.aii.adapter.file.File2XI.invoke(File2XI.java:630) at
com.sap.aii.af.lib.scheduler.JobBroker$Worker.run(JobBroker.java:534) at
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at
java.security.AccessController.doPrivileged(Native Method) at
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:182) at
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:280)
]

----------------------------------------------------

In the reference in application-j2ee-engine.xml I have:

-------------------------------------------------

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<application-j2ee-engine  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="application-j2ee-engine.xsd">

<reference reference-type="hard">

<reference-target provider-name="sap.com" target-type="service">engine.security.facade</reference-target>

</reference>

<reference reference-type="hard">

   <reference-target provider-name="sap.com" target-type="library">engine.j2ee14.facade</reference-target>

</reference>
<reference reference-type="hard">

  <reference-target provider-name="sap.com" target-type="service">com.sap.aii.af.svc.facade</reference-target>

</reference>

<reference reference-type="hard">

   <reference-target provider-name="sap.com" target-type="interface">com.sap.aii.af.ifc.facade</reference-target>

</reference>

<reference reference-type="hard">

   <reference-target provider-name="sap.com" target-type="library">com.sap.aii.af.lib.facade</reference-target>

</reference>

<reference reference-type="hard">

   <reference-target  provider-name="sap.com" target-type="library">com.sap.base.technology.facade</reference-target>

</reference>

<fail-over-enable mode="disable" xsi:type="fail-over-enableType_disable"/>

</application-j2ee-engine>

---------------------------------------------------------------

And in ejb-j2ee-engine.xml the jndi names are correct (same in Communication channel)

------------------------------------

...

<enterprise-bean>

   <ejb-name>DiasParseFile_DXreosis_NEW</ejb-name>

   <jndi-name>DiasParseFile_DXreosis_NEW</jndi-name>

</enterprise-bean>

...

-----------------------------------

and in ejb-jar.xml

--------------------------------

<session>

            <icon/>

            <ejb-name>DiasParseFile_DXreosis_NEW</ejb-name>

            <home>com.sap.aii.af.lib.mp.module.ModuleHome</home>

            <remote>com.sap.aii.af.lib.mp.module.ModuleRemote</remote>

            <local-home>com.sap.aii.af.lib.mp.module.ModuleLocalHome</local-home>

            <local>com.sap.aii.af.lib.mp.module.ModuleLocal</local>

            <ejb-class>com.sap.adaptermodule.DiasParseFile_DXreosis_NEWBean</ejb-class>

            <session-type>Stateless</session-type>

            <transaction-type>Container</transaction-type>

</session>

---------------------------------

Any Ideas?

Thanks,

S.Socratous

[Former Member]

Socrates, have you resolved this? I'm getting the same error using the NWDS 7.3 deploying to PI 7.1.

Can you please share the cause and solution?

Thanks!

Alberto'

[former_member795473]

Alberto,

  the solution was to install SAP Netweaver Dev Studio 7.1 and recompile and deploy a new ear.

I hope this will help you.

S.Socratous

[Former Member]

Did you do something after the NDWS 7.1 update? I've installed NWDS 7.1 and updated to the last patch. Although when I try to create a new EJB projetc the "target runtime" doesn't show the option SAP Libraries and either the "Configuration" doesn't show the standard options. I don't know what to do... Do you have any idea?

PS: all the update itens were succesfully installed.

Thanks!

Alberto

[Former Member]

Hi Alberto,

Where you able to add the SAP Libraries as Target Runtime ?

I am having the same issue.

Regards

Rick

[Former Member]

Hey Ricardo!

I couldn't resolve this issue in NWDS 7.1. There is a kind if bug that prevents the NWDS to update.

So, I resolved the problem by using the NWDS 7.3 latest SP.

It was veeeeery dificulty to solve, I'm even thinking on building a wiki for that.

So, here it goes what I did:

- I installed the NWDS 7.3.

- Downloaded from the instalation the Libraries for PI. The necessary libraries you can find here, on page 2: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0667f56-96c7-2b10-0e9a-c40fbd523...

- Here it goes the Magic: NWDS 7.3 works only with JDK 1.6. But PI 7.1 works with JDK 1.5. So, any adapter that you compile using JDK 1.6 will fail to start. So, install both JDK on your machine. After that, in NWDS, go to Window >> Preferences >> Java >> Installed JREs. Here, uncheck the JDK 1.6 and check the JDK 1.5.

- After that you can develop your adapter (using the libraries from PI 7.1) and deploy it directly to PI via NWDS. For more details about that, you can find here: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e674...

Feel free to get in touch with me if this procedure fails.

Best regards!

Alberto

[Former Member]

Hi Alberto

Thank you very much, i was already trying with NWDS 731 exactly like you describe it, also folowing the guide you shared, it is good to know i was going in the right path.

I think the root problem with NWDS 711 is that they move all the content from sdn downloads and now when you try and install the server runtime from SAP it end up in error.

Again Thanks

Best Regards

Rick