+

Search Tips   |   Advanced Search

Configuring JMS resources for the WebSphere MQ messaging provider

Use the WAS console to configure activation specifications, connection factories and destinations for the WebSphere MQ JMS provider.

This task assumes that you are working in a mixed WebSphere Application Server and WebSphere MQ environment, and that we have decided to use the WebSphere MQ messaging provider to handle JMS messaging between the two systems. If wer business uses WebSphere MQ, and to integrate WebSphere Application Server messaging applications into a predominately WebSphere MQ network, the WebSphere MQ messaging provider is the natural choice. However, there can be benefits in using another provider. If we are not sure which provider combination is best suited to the needs, see Choose messaging providers for a mixed environment.

We can configure JMS resources for the WebSphere MQ messaging provider through the console as described in this task, or we can configure JMS resources for the WebSphere MQ messaging provider through the WebSphere MQ administrative commands.

Using the console, we can set the scope of the WebSphere MQ messaging provider to restrict the range of resources that are displayed:

There are two ways of specifying the information needed by WebSphere MQ messaging provider messaging resources so that they can connect to a WebSphere MQ queue manager. It can either be specified manually, or by providing the WebSphere MQ messaging provider resource with a uniform resource locator (URL) that points to a client channel definition table (CCDT).

A CCDT is a binary file containing information about how to create a client connection channel to one or more queue managers. The file contains information such as the hostname, port, and name of the target queue manager, as well as more advanced configuration information like the SSL attributes that should be used.

Create WebSphere MQ messaging provider resources using CCDTs provides the following benefits:

For further information about generating a CCDT, see the WebSphere MQ information center.

Maintenance note: The WebSphere MQ messaging provider uses code provided by the WebSphere MQ resource adapter, which is automatically installed as part of the product.


Subtopics


Related concepts

  • Interoperation using the WebSphere MQ messaging provider