XI to IBM Websphere Default JMS Provider with JNDI

[Former Member]

Hello everybody!

We face a problem with connecting SAP XI to IBM WebSphere Default JMS Provider (need to send a message from XI to WebSphere JMS and receive the response).

We have the following versions installed:

SAP XI: 7.0 SP8 , Sun JDK 1.4.2

IBM WebSphere: IBM WebSphere Application Server ND, 6.0.2.17, J2RE 1.4.2 IBM

We cannot set the JMS adapter of SAP XI for conecting with IBM WebSphere Default JMS Provider. The Communication Channel has erroneous state (at runtime) and the Communication Channel Monitoring tool displays the error message as described below (under "Variant 1" and "Variant 2" sub-headings) depending on the settings performed.

For connecting, the following JMS-provider settings were used at IBM WebSphere side:

JMS Providers: Default Messaging Provider

Queue Connection Factories: name:QueueConnectionFactory, jndi:jms/QueueConnectionFactory, provider: Default Messaging Provider

Queues: name Queue, jndi: jms/Queue, provider: Default Messaging Provider

The XI communication channel (and associated JMS-adapter) was set as Variants 1 and 2 show. Settings for both cases and received error messages were the following:

<b>Variant 1.</b>

Adapter type: JMS

Type: Receiver

JMS Provider: Access JMS Provider with JNDI (Java Naming and Directory Interface)

JNDI Lookup Name of QueueConnectionFactory: jms/QueueConnectionFactory

JNDI Lookup Name of JMS Queue: jms/Queue

Name of JNDI Initial Context Factory: com.sap.engine.services.jndi.InitialContextFactoryImpl

JNDI Server Address: iiop://WEBSPHERE.HOST:2809/

As the result, the Communication Channel Monitoring displays that the channel has erroneous state and the following error message is written:

"Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of jms/QueueConnectionFactory.

at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)"

<b>Variant 2</b>

The same settings as in Variant 1 above, were used and additionally the following settings were done:

- Name of JNDI Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory

- The archive aii_af_jmsproviderlib.sda containing libraries required by WsInitialContextFactory, was deployed to the SAP WebAS where the XI is running. Those libraries were taken from WebSphere Application Server Pluggable Application Client installation package (described in the article "WebSphere Application Server Pluggable Application Client" located at http://www-128.ibm.com/developerworks/websphere/library/techarticles/0409_bhogal/0409_bhogal.html)

- Also, as it is recommended in the referred article, the files required by IBM's iiop protocol (ibmext.jar ibmorb.jar ibmorbapi.jar) were put to the folder jre/lib/endorsed of the server(Sun JVM 1.4.2 is used by SAP WebAS / XI).

As the result, the Communication Channel Monitoring displays that the channel has erroneous state as well and the following error message is written:

"No adapter registered for this channel"

We have not found the recommended solution either in SDN forums or in Internet in general. Is it yet possible to connect SAP XI to IBM WebSphere Default JMS Provider having mentioned product versioning? If yes, what settings have to be performed?

[Former Member · Accepted solution]

IBM Websphere Default JMS Provider which is installed alongwith the application server is nothing but a scaled down version of the IBM WebSphere MQSeries. you should be able to connect to it with the same settings that can be used for a separate MQSeries server connectivity from XI.

[Former Member · Accepted solution]

Did this work?

Is there any Licencing issue?

Or did you have to Buy MQ?