Configuring InfoSphere MDM Collaboration Server for WebSphere MQ

You must configure connectivity with WebSphere® MQ to integrate IBM® InfoSphere® Master Data Management Collaboration Server with WebSphere MQ. You use the common.properties file of InfoSphere MDM Collaboration Server for configuring the default settings for connecting to WebSphere MQ.

About this task

In WebSphere MQ 7.1 and 7.5, channel authentication is enabled by default. If you migrate the queue manager from previous versions to these versions, channel authentication is still disabled; therefore no action is required. However, if you create a queue manager with WebSphere MQ 7.5, you must explicitly disable channel authentication with the following command:

ALTER QMGR CHLAUTH(DISABLED)

For more information, see Channel authentication.

Procedure

  1. Create the wanted WebSphere MQ topology, including queue managers, queues, and channels. For more information, see: WebSphere MQ product documentation. If your WebSphere MQ topology requires the WebSphere MQ Server to be installed on a remote computer, (not on the same computer as InfoSphere MDM Collaboration Server), or if you are using the Script APIs to integrate with WebSphere MQ, then you must correctly configure the WebSphere MQ for client connectivity and define the relevant server connection (SVRCONN) channel and listeners.
    Note: When you use WebSphere MQ with the Script API, WebSphere MQ client connectivity is used. The Script API provides a reduced set of capabilities and does not support transactions.
  2. When you connect to WebSphere MQ through the Script API, default configuration information must be provided.
    1. Configure the following properties in the common.properties file for connecting and controlling the way messages are directed to WebSphere MQ. 
      mq_port=1414
mq_channel=WPC.SVRCONN
mq_hostname=wpc.ibm.com
mq_queuemanager=WPC_QMGR
mq_username=
mq_password=
mq_inbound_queue=WPC.IN.QUEUE
mq_outbound_queue=WPC.OUT.QUEUE
mq_queue_put_open_options=
mq_message_put_options=
mq_queue_get_open_options=
mq_message_get_options=
mq_use_utf=false
mq_charset=819
    2. Set the JMS-specific default settings: 
      jms_provider=IBM WebSphere MQ
jms_receive_timeout=1000
jms_inbound_queue=WPC.IN.QUEUE
jms_outbound_queue=WPC.OUT.QUEUE
  3. If you are developing the InfoSphere MDM Collaboration Server solution with the Java™ API, then direct access to the WebSphere MQ APIs must be used. Both client mode and bindings mode connectivity can be used. However, the design of the WebSphere MQ deployment topology is the deciding factor.

Last updated: 23 October 2014