Configuration of the WebSphere MQ resource adapter

To configure the WebSphere® MQ resource adapter, you define various JCA resources and system properties.

Define JCA resources in the following categories:

The properties of the ResourceAdapter object, which represent the global properties of the resource adapter, such as the level of diagnostic tracing. These properties are described in Configuration of the ResourceAdapter object.
The properties of an ActivationSpec object, which determine how an MDB is activated for inbound communication. These properties are described in Configuring the resource adapter for inbound communication.
The properties of a ConnectionFactory object, which the application server uses to create a JMS ConnectionFactory object for outbound communication. These properties are described in Configuring the resource adapter for outbound communication.
The properties of an administered destination object, which the application server uses to create a JMS Queue object or JMS Topic object for outbound communication. These properties are also described in Configuring the resource adapter for outbound communication.

The WebSphere MQ resource adapter RAR file contains a file called META-INF/ra.xml, which contains a deployment descriptor for the resource adapter. This deployment descriptor is defined by the XML schema at https://java.sun.com/xml/ns/j2ee/connector_1_5.xsd and contains information about the resource adapter and the services that it provides. An application server might also require a deployment plan for the resource adapter. This deployment plan is specific to the application server. For example, WebSphere Application Server Community Edition requires a deployment plan called geronimo-ra.xml.

If you are using Secure Sockets Layer (SSL), specify the locations of the keystore file and truststore file as JVM system properties, as in the following example:

java ... -Djavax.net.ssl.keyStore=
key_store_location
         -Djavax.net.ssl.trustStore=trust_store_location
         -Djavax.net.ssl.keyStorePassword=key_store_password

These properties cannot be properties of an ActivationSpec or ConnectionFactory object, and you cannot specify more than one keystore for an application server. The properties apply to the whole JVM, and might therefore affect the application server if other applications, running in the application server, are using SSL connections. The application server might also reset these properties to different values. For more information about using SSL with WebSphere MQ classes for JMS, see Using Secure Sockets Layer (SSL) with WebSphere MQ classes for JMS.

An installation verification test (IVT) program is supplied with the WebSphere MQ resource adapter, but you must configure the resource adapter before you can run the program. For information about what you need to configure in order to run the IVT program, see The installation verification test program for the WebSphere MQ resource adapter.

The resource adapter logs, warning, and error messages use the same mechanism as the IBM® WebSphere MQ classes for JMS, for details, see Logging and IBM WebSphere MQ classes for JMS. For WebSphere Application Server, these messages are automatically redirected to the application server output log. For other application servers, such as WAS CE and JBoss®, these will, by default, go to a file called mqjms.log. To configure the resource adapter to additionally log warning messages to your application servers standard output log, set the following JVM system property for your application server:


-Dcom.ibm.msg.client.commonservices.log.outputName=mqjms.log,stdout

For details on how to set a JVM system property, see your application server documentation.