Deploying the IVT application in JBoss with a custom IBM WebSphere MQ environment

When installing the IBM® WebSphere® MQ resource adapter in JBoss®, if you want to use a different queue, queue manager, port, host, channel, or use bindings mode instead of client mode, you must first modify the IVT application and associated scripts in JBoss before deploying the resource adapter or IVT application.

About this task

Important: These instructions are only applicable for Java EE Versions 6 and 5, not for Java EE Version 7. The use of these instructions for JBoss Version 8 (WildFly) is therefore not supported.

If you want to deploy to a different configuration from that specified in Installing and testing the resource adapter in JBoss AS 5.1 and 6, that is, if you want to use a different queue manager, queue, port, host, channel, or use bindings mode instead of client mode, then complete the following steps before deploying the resource adapter or IVT application.

Procedure

  1. If you want to specify a different queue manager and queue to use for the IVT application, set values for the queue manager and queue.
    1. For the jms/ivt/IVTCF connection definition:
      1. Set the value of the queueManager config-property to be the name of your queue manager.
      2. If you are using a client connection, set the value of the various client connection elements to be appropriate for a connection to your queue manager.
      3. If you are using a bindings connection, set the value of the transportType element to be BINDINGS, and then comment out or delete the various client connection elements.
    2. For the jms/ivt/IVTQueue mbean, set the value of the baseQueueName element to be the name of the queue you have created for the IVT application.
    3. Save your changes.
  2. If you want to specify a different queue manager and queue in the configuration for the message-driven bean (MDB), modify the configuration of the MDB to connect to the queue manager and queue.
    1. Open the wmq.jmsra.ivt.ear file.
    2. Open the WMQ_IVT_MDB.jar within it.
    3. Edit META-INF/ejb-jar.xml:
      1. Set the value of the queueManager activation-config-property to be the name of your queue manager.
      2. If you are using a client connection, set the value of the various client connection activation-config-properties to be appropriate for a connection to your queue manager.
      3. If you are using a bindings connection, set the value of the transportType activation-config-property to be BINDINGS, and then comment out or delete the various client connection elements.
    4. Save the changes and update the file within the WMQ_IVT_MDB.jar file.
    5. Update the wmq.jmsra.ivt.ear file with the modified WMQ_IVT_MDB.jar.
  3. If you are configuring the resource adapter to connect to IBM WebSphere MQ in bindings mode, ensure that the JNI libraries are on the system path, or the path for JBoss. For details, see Configuring the Java Native Interface (JNI) libraries.

What to do next

Continue deploying the resource adapter as described in Installing and testing the resource adapter in JBoss AS 5.1 and 6.

.