Configure JMS resources for the IBM messaging provider

Use the WebSphere Application Server administrative console to configure activation specifications, connection factories and destinations for the IBM MQ JMS provider.

This task assumes that we are working in a mixed WAS and IBM MQ environment, and that we have decided to use the IBM MQ messaging provider to handle JMS messaging between the two systems. If our business uses IBM MQ, and we want to integrate WAS messaging applications into a predominately IBM MQ network, the IBM 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 our needs, see Choosing messaging providers for a mixed environment.

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

Use the administrative console, we can set the scope of the IBM MQ messaging provider to restrict the range of resources displayed:

• If we set the scope to contain only WAS Version 6 or v7.0 or later nodes, we can configure JMS 1.1 resources and properties. This includes unified JMS connection factories for use by both point-to-point and publish/subscribe JMS 1.1 applications. With JMS 1.1, this approach is preferred to the domain-specific queue connection factory and topic connection factory.

• If we set the scope to contain only WAS v7.0 or later nodes, we can also configure JMS activation specifications.

• If we set the scope to a WAS Version 5 node, we can only configure domain-specific JMS resources, and the subset of properties that apply to WAS v5.

There are two ways of specifying the information needed by IBM MQ messaging provider messaging resources so that they can connect to an IBM MQ queue manager. It can either be specified manually, or by providing the IBM 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 IBM MQ messaging provider resources using CCDTs provides the following benefits:

• Flexibility, because client connection channel information is contained in a single place. If any of the information changes, such as the host name of the machine on which the IBM MQ queue manager resides, only the CCDT needs to be updated. When it is updated, all IBM MQ messaging provider resources that make use of the CCDT pick up the change.

• Reliability, because less information is needed for a CCDT there is a reduced chance of configuration errors. When using a CCDT to enter connection information, all required are the CCDT URL and an optional queue manager name. If we configure an IBM MQ messaging provider resource manually, more information is required -- especially if we are configuring SSL.

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

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

Subtopics

• Create an activation specification for the IBM MQ messaging provider
  
• Configure an activation specification for the IBM MQ messaging provider
  
• Migrate a listener port to an activation specification for use with the IBM MQ messaging provider
  
• Create a connection factory for the IBM MQ messaging provider
  
• Configure a unified connection factory for the IBM MQ messaging provider
  
• Configure a queue connection factory for the IBM MQ messaging provider
  
• Configure a topic connection factory for the IBM MQ messaging provider
  
• Configure a queue for the IBM MQ messaging provider
  
• Configure a topic for the IBM MQ messaging provider
  
• Configure custom properties for IBM MQ messaging provider JMS resources
  

Related:

Interoperation using the IBM MQ messaging provider