Activation Specification Setup using Websphere MQ Resource Adapter

This post explains the steps to create an Activation Specification for a MDB to listen using Websphere MQ resource adapter.

We need to first install the Websphere MQ Resource adapter RAR file. The RAR file can be found at the path /usr/mqm/java/lib/jca. RAR file name is wmq.jmsra.rar

Please note that i might have whitened out certain parts of images to avoid sensitive information to be revealed.

1. Login to WAS admin console and click on the Resource Adapters section under the Resources menu item

2. Click in the ‘Install RAR’ button. You will get the below screen

3. Select the RAR file and node and click Next

4. Enter only the name for the Resource Adapter installation. Leave other fields blank and click OK

5. You will see the installed resource adapter listed in the Resource Adapters section

6. Save the changes to the Master configuration

7. Now open the installed Resource Adapter. You will see the below screen.

8. Click the J2C Activation specifications link. You will be taken to the below screen

9. Click the New button and fill the details as below to create the Active spec

10. Save the work to the Master configuration.

11. Now open the newly created active specification

12. Click the link under Additional Properties

13. In the resultant screen, modify all relevant properties. Most important would be destination, destinationType, queueManager, port, channel, hostname

Finally save the work to the master configuration

14. We have created the Activation Specification. Now we need to create the configuration for the queue which we specified as destination in the above steps. To do that click the ‘J2C administered objects’ link in the MQ resource adapter page.

15. Click ‘New’ and enter the below details and click OK.

16. Now open the created queue and click the link under the Additional Properties

17. Enter the values as shown in the below screen and save the work

NOTE:

Make sure that the mqm installation directory is mentioned correctly in the Websphere Variables section