8.6.3 Configuring the WebSphere MQ JMS provider

The WebSphere MQ JMS provider can be configured to communicate with WebSphere MQ using a bindings or client connection. These two connectivity options are described below:

When used in bindings mode, the WebSphere MQ JMS provider uses the Java Native Interface (JNI) to call directly into the existing queue manager API, rather than communicating through a network. This provides better performance when connecting to WebSphere MQ than using a client connection.

However, to use a bindings connection, WebSphere MQ and WAS must be installed on the same machine.

If it is not possible to collocate WAS and WebSphere MQ on the same machine, the WebSphere MQ JMS provider must be configured to connect to WebSphere MQ using TCP/IP. Using a client connection allows you to perform authorization checks.

Additional considerations must be taken into account when configuring the WebSphere MQ JMS provider to use a client connection, for example:

Whether the connection needs to be secured by encrypting the data that flows over the connection

Whether the connection will go through a firewall

The sections that follow describe the properties exposed by WebSphere MQ connection factories and destinations, and also how to configure connection factories and destinations for the WebSphere MQ JMS provider.

As discussed in 8.5.2, Managing the WebSphere MQ JMS provider, WebSphere MQ resources, such as queue managers, channels, and queues, must be created using the tools provided with WebSphere MQ.