XI JMS error MQJMS2005 : failled to create MQQueuemanager for ....

[Former Member]

I'm new in XI.

We want to establish a connection to Websphere MQ 5.3 and we receive the message MQJMS2005 ... .

The java drivers are installed.

On MQ server we created a local user in group mqm and we use it in Configuration panel.

On MQ server, the listener listens on port 1414 which is defined on Configuration panel.

Everything looks good bud we receive the error message.

We need more information about the error and I'd like to know how to access to the linked error of MQ .

Is there anybody who can tell me how to see that, what are the setting to activate this log?

Many regards.

[Former Member]

Peter ,

How can I check the drivers are correctly deployed?

All the parameter You give are correctly defined.

Regards

Eric.

[Former Member]

Hi Eric,

Did you follow the how-to guide available at SAP Marketplace to deploy the JMS Adapter. If so, i believe the information given in that guide is incomplete.

Once you have installed the JMS Driver, you must deploy the Java libraries on the J2EE server so that the JMS adapter can access the required Java classes at runtime.

If you use MQSeries 53x.xxx, you must enter the following JAR files in aii_af_jmsproviderlib.sda.

com.ibm.mq.jar

com.ibm.mqbind.jar

com.ibm.mqjms.jar

connector.jar (use the JAR file from the J2EE client directory)

and if ur question is, "Where do I get the Java Library from "

The required Java libraries are product-specific and can be obtained from either the product vendor or other providers.

And i guess the 4 jar files should be enough. Just remember to add these 4 jar files to 'provider.xml' file inbetween the <jars>..</jars> tag.

Follow the instructions as per the guide,

https://websmp205.sap-ag.de/~sapdownload/011000358700003994312004E/HowTo_ConfigExtAdapters.pdf

But just remember to have all the 4 jar files in aii_af_jmsproviderlib.sda

Also go through these threads and see if it helps...

Regards,

Abhy

[Former Member]

Have you checked the entry for Queue Manager Name and Channel Name. I once had this problem when I specified an incorrect (or inactive) Queue manager name.

If the drivers are deployed correctly, these settings should be sufficient to connect to the Queue:

Transport Protocol: WebSphere MQ (MQSeries) JMS Provider
IP Address or Server Name
Server Port (default 1414, or another one if you have set up your listener to another port)
Queue Manager Name
Channel Name
JMS Queue (the MQ Local Queue)
Transport Protocol: TCP/IP

All the rest is just for special configuration...

regards,

Peter