cancel
Showing results for 
Search instead for 
Did you mean: 

configuration of JMS adapter Using WebSphereMQ

Former Member
0 Kudos

Hi All

I am trying Http to JMS scenario.

I configured my JMS adapter as receiver

Trasport protocol: Web sphereMQ JMS provider.

Queue Connection Factory : com.ibm.mq.jms.MQQueueConnectionFactory

Queue Java class : com.ibm.mq.jms.MQQueue

IP address : 172.17.50.150Where I installed Web Sphere MQ

In SXMB_MONI my http client sends msg without any error

But In runtime work bench whn I observe Adapter monitoring I got error as

Receiver channel. Details: MQJMS2005: failed to create MQQueueManager for '172.17.50.150:QM_APPEL'

PLZ ell me d coz

Thanks

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

Is QM_APPEL the name of the Queue Manager that you want to connect to? The initial entry when you create a JMS Channel suggests QM_hostname, but the queue manager name can be anything - check with the MQ admin.

Also the Listener on the MQ side can be running on another than the default port 1414 (this is often the case, when you have more than one queue manager configured).

Finally, check the Channel - whether it's a SVRCONN channel, got the name correct and the authority settings (see the answer below).

good luck, regards,

Peter

Former Member
0 Kudos

Some possible reasons could be :

A. You are trying to access the QM and its objects with credentials which are not configured to access the same. An example setting for this could be add the network user on a windows machine to the MQM group on the machine where MQ is.

for e.g. user domain/user1 makes a connection to MQ over network then this user needs to be added to MQM group.

B. Your MQSeries listener program is not running.

Hope this helps.

former_member187339
Active Contributor
0 Kudos

Hi,

Refer these thread :

Regards

Suraj

bhavesh_kantilal
Active Contributor
0 Kudos

Hi,

for the configuration of a Websphere MQ JMS adapter, you will have to also give details like, Queue Manager Name, channel name, etc.

Just check this link for the same,

http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm

Provide all the correect details and it will hopefully work.

Regards,

Bhavesh