MDM PI Adapter Error

[Former Member]

I deployed the MDM PI Adapter for PI 7.1 with the JSPM tool. Everything worked fine.

In the integration directory i created the needed objects for the communication with MDM (Comm.channel etc.).

Now i`m trying to send IDOCS from an ERP system to SAP MDM without success.

SXMB_MONI says that everything fine.

RWB(Message-Monitoring->Adapter Engine) shows up an error:

2009-08-26 16:58:41 Information: Using connection MDM_http://sap.com/xi/MDMAdapter. Trying to put the message into the receive queue.

2009-08-26 16:58:42 Information: The message status was set to DLNG.

2009-08-26 16:58:42 Information: Message successfully put into the queue.

2009-08-26 16:58:42 Information: The message was successfully retrieved from the receive queue.

2009-08-26 16:58:42 Information: Delivering to channel: MdmAdapterReceiver

2009-08-26 16:58:42 Information: Message entered AF MP exit bean and will be passed to the JCA adapter now.

2009-08-26 16:58:42 Fehler: Adapter Framework caught exception: JNDI name of the ra connectionFactory is not configured. Go to the directory and create a value with name 'JNDIName' and value 'deployedAdapters/<ra name>/shareable/<ra name>' as module configuration data of the module 'ModuleProcessorExitBean'

2009-08-26 16:58:42 Fehler: Delivering the message to the application using connection MDM_http://sap.com/xi/MDMAdapter failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: JNDI name of the ra connectionFactory is not configured. Go to the directory and create a value with name 'JNDIName' and value 'deployedAdapters/<ra name>/shareable/<ra name>' as module configuration data of the module 'ModuleProcessorExitBean'.

2009-08-26 16:58:42 Information: The message status was set to WAIT.

Does anyone has an idea how to fix this?

Best regards

serdar

[Former Member · Accepted solution]

Same error been discussed here

Hope it is relevant for your case

[Former Member · Accepted solution]

Hello,

at first thanks for your answers.

Where can i change the JNDI name and whats the value i need to change? The JNDI Browser just gives an overview, no chance to change the parameter.

regards

serdar

[former_member91687 · Accepted solution]

Hi,

You need to make the entry in the Receiver MDM adapter, module configuration tab.

For the exit bean add the below

Parameter Name : JNDIName

Parameter Value: deployedAdapters/sap.com_tcmdm_adapterjca/shareable/sap.com_tcmdm_adapterjca

You can find also get the parameter value(mentioned above) in the MDM adapter metadata in the IR.

Thanks,

Chandra

[Former Member · Accepted solution]

Hi,

i finally found the place to insert the data. There`s a Note for my problem.

https://websmp230.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1336552

--> Just switch from comm.channel type receiver to sender and back.

But there`s another problem with the JNDIname. There`s no entry under the given path: deployedAdapters/sap.com_tcmdm_adapterjca/shareable/sap.com_tcmdm_adapterjca

And i get an error message in the rwb:

Adapter Framework caught exception: Cannot lookup the ra connectionFactory. Reason: Path to object does not exist at sap.com_tcmdm_adapterjca, the whole lookup name is deployedAdapters/sap.com_tcmdm_adapterjca/shareable/sap.com_tcmdm_adapterjca.

The value in the module conf. is: deployedAdapters/sap.com_tcmdm_adapterjca/shareable/sap.com_tcmdm_adapterjca

regards

serdar

[former_member91687 · Accepted solution]

Can you check in MDM adapter metadata in the IR what is the value shown corresponding to JNDI name?

Thanks,

Chandra

[Former Member · Accepted solution]

ModuleConfig:

ModuleConfigItem:

Key: exit

Name: JNDIName

Value: deployedAdapters/sap.com_tcmdm_adapterjca/shareable/sap.com_tcmdm_adapterjca

But somehow there`s nothing in the NWA->JNDI Browser -> deployedAdapters. There`s no sap.com->tc_mdmadapter....

Thx and regards

serdar

[former_member91687 · Accepted solution]

Go to the integration repository and there in adapter metadata for MDM adapter you will find an entry for JNDI name, check what is the value shown here(this is not something you would have entered manually).

[Former Member · Accepted solution]

Enterprise Services Builder -> MDM Adapter Metadata:

Value for the JNDIName is : deployedAdapters/sap.com_tcmdm_adapterjca/shareable/sap.com_tcmdm_adapterjca

I just checked the running applications on NWA. The application tc_mdmadapter~svc has a "implicit_stopped" stauts. Maybe something went wrong with the deployment of the adapter?

greetz

Edited by: Serdar Yalcinkaya on Aug 27, 2009 3:33 PM

[Former Member · Accepted solution]

The Log says during the start of the service:

ERROR CODE DPL.DS.5029] Exception in operation startApp with application sap.com/tc_mdmadapter~svc.

Reason : [ERROR CODE DPL.DS.5029] Exception in operation startApp with application sap.com/tc_mdmadapter~svc.

[EXCEPTION]

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

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:520)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:412)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:495)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:169)

at com.sap.engine.services.deploy.server.application.ParallelAdapter$2.run(ParallelAdapter.java:365)

at com.sap.engine.frame.core.thread.Task.run(Task.java:73)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:144)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:242)

Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application sap.com/tc_mdmadapter~svc cannot be started. Reason: it has hard reference to resource com.sap.mdm.tech.mdm4j with type library, which is not active on the server.

at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToLibrary(ReferenceResolver.java:739)

at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:574)

at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:496)

at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:166)

at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:410)

... 7 more

[Former Member]

serdar,

Have you arrived at a solution? We are experiencing the same issue when trying to implement the PI MDM Adapter. Any help you could provide would be greatly appreciated.

Thanks,

Chris

[Former Member]

Hi,

we resolved the problem. You need to deploy the JAVA API for MDM Adapter.

https://websmp205.sap-ag.de/swdc -> Support by packages.. -> Entry by App group -> Netweaver -> MDM -> MDM 7.1 ->Entry by component -> JAVA API.

The MDM-Adapter is not startet until you deploy the JAVA API. You can check the status of the Adapter in the NWA -> Start & Stop Application -> Search for "MDM".

Best regards

serdar

[Former Member]

First you should configure the JNDI name using NWA for reference of the deployed module

after that your entry in Communication Channel -Module should be like below

Processing Sequence -

1 localejbs/ModuleProcessorExitBean Local Enterprise Bean exit

Module Configuration -

exit JNDIName Your JNDI name/path.