WAS v8.5 > Administer applications and their environment > Administer web services - Invocation framework (WSIF) > Administer WSIF > Enable a WSIF client to invoke a web service through JMS

Configure JMS resources for the WebSphere MQ messaging provider

Use the WebSphere Application Server dmgr 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 WAS 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 WAS 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 your needs, see Choose messaging providers for a mixed environment.

We can configure JMS resources for the WebSphere MQ messaging provider through the dmgr 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 dmgr console, we can set the scope of the WebSphere MQ messaging provider to restrict the range of resources that are displayed:

• If we set the scope to contain only WAS v6 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 v5 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 WebSphere MQ messaging provider messaging resources so 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.

Creating WebSphere 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 WebSphere MQ queue manager resides, only the CCDT needs to be updated. When it is updated, all WebSphere 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 a WebSphere MQ messaging provider resource manually, much more information is required -- especially if you are configuring SSL.

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.

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

Subtopics

• Create an activation specification for the WebSphere MQ messaging provider
  Use this task to create an activation specification for use with the WebSphere MQ messaging provider.
• Configure an activation specification for the WebSphere MQ messaging provider
  Configure a JMS activation specification to enable a message-driven bean (MDB) to communicate with the WebSphere MQ messaging provider.
• Migrating a listener port to an activation specification for use with the WebSphere MQ messaging provider
  For WAS v7 and later, listener ports are stabilized. You must therefore plan to migrate your WebSphere MQ message-driven bean deployment configurations from using listener ports to using activation specifications.
• Create a connection factory for the WebSphere MQ messaging provider
  Use this task to create a connection factory, a queue connection factory, or a topic connection factory for use with the WebSphere MQ messaging provider.
• Configure a unified connection factory for the WebSphere MQ messaging provider
  Use this task to view or change the configuration of an existing domain-independent connection factory for the WebSphere MQ messaging provider on a WAS node.
• Configure a queue connection factory for the WebSphere MQ messaging provider
  Use this task to view or change the configuration of an existing JMS queue connection factory for point-to-point messaging with the WebSphere MQ messaging provider.
• Configure a topic connection factory for the WebSphere MQ messaging provider
  Use this task to view or change the configuration of a JMS topic connection factory for publish/subscribe messaging with the WebSphere MQ messaging provider.
• Configure a queue for the WebSphere MQ messaging provider
  Use this task to view or change the configuration of a JMS queue destination for point-to-point messaging with the WebSphere MQ messaging provider. This task contains an optional step for you to create a new JMS queue destination.
• Configure a topic for the WebSphere MQ messaging provider
  Use this task to view or change the configuration of a JMS topic destination for publish/subscribe messaging with the WebSphere MQ messaging provider. This task contains an optional step for you to create a new JMS topic destination.
• Configure custom properties for WebSphere MQ messaging provider JMS resources
  In addition to the standard properties that we can define for WebSphere MQ messaging provider JMS resources, we can configure further WebSphere MQ properties as custom properties. We can configure custom properties for activation specifications, connection factories, and JMS destinations for the WebSphere MQ messaging provider.

Related concepts:

Interoperation using the WebSphere MQ messaging provider

+

Search Tips   |   Advanced Search