Network Deployment (Distributed operating systems), v8.0 > 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 WAS administrative 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 your business uses WebSphere MQ, and you want 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 you are not sure which provider combination is best suited to your needs, see Choosing messaging providers for a mixed environment.
We can configure JMS resources for the WebSphere MQ messaging provider through the administrative console as described in this task, or you can configure JMS resources for the WebSphere MQ messaging provider through the WebSphere MQ administrative commands.
Use the administrative console, you can set the scope of the WebSphere MQ messaging provider to restrict the range of resources that are displayed:
- If you set the scope to contain only WAS v6 or v7.0 or later nodes, you 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 you set the scope to contain only WAS v7.0 or later nodes, you can also configure JMS activation specifications.
- If you set the scope to a WAS v5 node, you 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 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 that contains 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:
- 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 that is required are the CCDT URL and an optional queue manager name. If you 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.
Procedure
- Create an activation specification for the WebSphere MQ messaging provider
- Configure an activation specification for the WebSphere MQ messaging provider
- Migrate 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
Related
Create an activation specification for the WebSphere MQ messaging provider
Configure an activation specification for the WebSphere MQ messaging provider
Migrate 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
Interoperation using the WebSphere MQ messaging provider
Manage messaging with the WebSphere MQ messaging provider