Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SOAVIRT_9.10.6_CTP_3.1.2

...

For

For the WebSphere MQ JMS provider

Minimum Required jars

For MQ 9

You can find these under [WebSphere MQ installation directory]/java/lib:

  • com.ibm.mq.allclient.jar.

For MQ 8

You can find these under [WebSphere MQ installation directory]/java/lib:

  • com.ibm.mq.allclient.jar.

For MQ 7.0

You can find these under [WebSphere MQ installation directory]/java/lib:

  • com.ibm.mq.jar
  • com.ibm.mqjms.jar
  • com.ibm.mq.commonservices.jar 
  • com.ibm.mq.headers.jar
  • com.ibm.mq.jmqi.jar
  • connector.jar
  • dhbcore.jar
  • com.ibm.mq.pcf.jar

You also need to download the following jar:

  • ME01: WebSphere MQ - Initial Context Factory — mqcontext.jar

For MQ 6.0

You can find these under [WebSphere MQ installation directory]/java/lib:

  • com.ibm.mq.jar
  • com.ibm.mqjms.jar - connector.jar
  • dhbcore.jar
  • jta.jar

You also need to download the following jars:

  • MS0B: WebSphere MQ Java classes for PCF — com.ibm.mq.pcf.jar
  • ME01: WebSphere MQ - Initial Context Factory — mqcontext.jar

MQ Client Download

The jars from [WebSphere MQ installation directory]/java/lib are also included in the MQ Client. The MQ 6 Client is no longer available from IBM. The MQ 7 Client is available at http://www-01.ibm.com/support/docview.wss?uid=swg24019253


Typical Provider URL Pattern

yourhostname:1414/SYSTEM.DEF.SVRCONN

Factory class

WebSphere MQ JNDI Initial Context factory class - com.ibm.mq.jms.context.WMQInitialContextFactory

SSL Configuration

WebSphere JMS clients can achieve SSL connections by setting the appropriate properties in the initial context. Both WebSphere MQ and WebSphere JMS clients will set the same properties for SSL connectivity.

JMS messaging without JNDI

Under the properties tab, define the following properties:
Name: Value
provider:  WebSphere MQ
queue.manager: [your queue manager name]
channel: [your channel name]
port: [port number, the default WebSphere MQ port is 1414]
With this configuration, SOAtest/Virtualize will create the connection factory using the provided parameters as follows:

Code Block
  import com.ibm.mq.jms.*;
  ...
  MQConnectionFactory cf = new MQConnectionFactory();
  cf.setHostName(hostname);
  cf.setPort(port);
  cf.setQueueManager(queuemanager);
  cf.setChannel(channel);
  cf.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP);   
  cf.setFailIfQuiesce(JMSC.MQJMS_FIQ_YES);
  cf.setUseConnectionPooling(true);
 Additional Notes
 

IBM's JNDI provider authenticates itself with the Websphere MQ server by sending the user's login name. This is typically the user name that was provided when logging into the workstation before starting SOAtest/Virtualize.

If the MQ server does not recognize the user name, then your tool will fail with the error "javax.jms.JMSSecurityException: MQJMS2013: invalid security authentication supplied for MQQueueManager".

This error can be resolved by adding a Windows user account on the Websphere MQ server machine. This account should 1) have the same user name as the account on the local machine whereVirtualizeis running and 2)  be a member of the "mqm" IBM WebSphere MQ Administration Group.

Alternatively, use a different user name by changing the value of the  user.name Java System property. This system property can be configured by startingVirtualizeusing virtualize.exe -J-Duser.name=username where username is the user name you want to use. In some configurations using an empty username via soatest/virtualize.exe -J-Duser.name= will work. Using SYSTEM for the user.name property may also work in some configurations. 

For more details on this error, see http://www.mqseries.net/phpBB/view-topic.php?t=40640.
 

Learn more at

http://www-01.ibm.com/software/integration/wmq/library/

http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzaw.doc/jm10320_.htm

...