Configuring IBM WebSphere to work with IBM MQ - Middleware News

Part 1.  Creating your Queues in IBM MQ Explorer

1. Once you launch your MQ Explorer, the first thing we want to do is create a new queue Manager.  Right click on the Queue Manager folder and choose 'New Queue Manager'. Enter your your 'Queue Manager Name' then proceed through the pages accepting the defaults until the last screen. Here you can leave the port at 1414 or define another port for your Queue Manager to listen on. (we used 9001 for this example)

2. Next we will create our queues. Right click on the 'Queues' folder and a new 'Local Queue'. Give this queue a name of 'CQINDB' then click next and Finish.

3. Once your CQINBD is created it should show on the queues view. You will want to follow step 2 for SQINBD, CQINBD, SQOUTBD and CQINBDERR. Once done the Queue view should look as follows.

4. Our last step in the MQ explorer is to create the servers connection channel. We can do this by right clicking on the Channels folder then creating a new 'Server-connection Channel'. Give your channel a name and proceed through the screens to finish. Ensure the transmission protocol is set to TCP. In this example we called it 'MAXCHAN'

Part 2: Configuring WebSphere to work with MQ.

1. The first thing we need to do on the WebSphere side is define the MQ Library Path for the messaging provider. Expand 'Resources' - > 'JMS' and click on 'JMS providers'. Select the scope on which you want this configuration defined (use cell to allow for other configurations to utilize) and choose 'WebSphere MQ messaging provider' In the 'Native library path' set the path to your WebSphere MQ Lib folder as seen below for a Windows environment.

2. The next step in WebSphere is to define the queues and point them back to your Queue Manager.  Click on 'Queues' and set the scope to the same as above. Then click on new. Choose 'WebSphere MQ messaging provider'. Based off our previous configuration set the following values.

Name: CQIN

JNDI name: jms/maximo/int/queues/cqin

Queue name: CQINBD

Queue Manager: MAXIMO

Repeat the above steps for the following

Name: SQIN

JNDI name: jms/maximo/int/queues/sqin

Queue name: SQINBD

Queue Manager: MAXIMO

Name: SQOUT

JNDI name: jms/maximo/int/queues/sqout

Queue name: SQOUTBD

Queue Manager: MAXIMO

Name: CQINERR

JNDI name: jms/maximo/int/queues/cqinerr

Queue name: CQINBDERR

Queue Manager: MAXIMO

You should now have the following configuration.

3. Now we will create our Queue connection factory, again under 'Resources' - > 'JMS' click on 'Queue connection factories'. Set your scope, click on new and choose ' WebSphere MQ messaging provider'. Set the following values in the panels, you can test your connection to ensure it is correct.

Name: intconfact

JNDI name: jms/maximo/int/cf/intcf

Queue Manager: MAXIMO

Hostname: maximo.local  (This will be the hostname of MQ Server)

Port: 9001 ( port defined for the TCP listener when creating the queue manager  )

Server connection channel: MAXCHAN

Transport: Client

4. On the connection factory you just created click on 'Custom Properties' and add the following properties.

Name: CLIENTRECONNECTOPTIONS
Value: QMGR

Name: CLIENTRECONNECTTIMEOUT
ValueL 900

5. Now lets create the Activation Specifications

Under 'Resources' - > 'JMS' -> 'Activation Specification', choose your scope and click on new. Enter the following values:.

WebSphere MQ Provider
Name: intjmsact
JNDI name: intjmsact
Queue manager: Maximo
Transport: Client
Hostname: MQ Hostname
Port: MQ Listener Port
Server connection channel: MAXCHAN
Destination JNDI name:jms/maximo/int/queues/cqin

Now repeat the above steps for intjmsacterr

WebSphere MQ Provider
Name: intjmsact
JNDI name: intjmsact
Queue manager: Maximo
Transport: Client
Hostname: MQ Hostname
Port: MQ Listener Port
Server connection channel: MAXCHAN
Destination JNDI name:jms/maximo/int/queues/cqinerr

Now that's about it for the MQ\WebSphere\Maximo configuration.  You can now define your queues on the external system as you would of previously when using JMS queues. Your transactions will send outbound and inbound via MQ.  I hope this blog helps with any configuration obstacles you may of run in to, as always feel free to comment and ask questions