Configuring 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.
Before you begin
This task assumes that you are working in a mixed WebSphere Application Server and IBM MQ environment, and that you have decided to use the IBM MQ messaging provider to handle JMS messaging between the two systems. If your business uses IBM MQ, and you want to integrate WebSphere Application Server 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 you are not sure which provider combination is best suited to your needs, see Choosing messaging providers for a mixed environment.
You can configure JMS resources for the IBM 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.
About this task
- If you set the scope to contain only WebSphere Application Server Version 6 or 7.0 版或更新版本 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 WebSphere Application Server 7.0 版或更新版本 nodes, you can also configure JMS activation specifications.
- If you set the scope to a WebSphere Application Server Version 5 node, you can only configure domain-specific JMS resources, and the subset of properties that apply to WebSphere Application Server Version 5.
There are two ways of specifying the information needed by IBM MQ messaging provider messaging resources so that they can connect to a 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 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.
- 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 that is required are the CCDT URL and an optional queue manager name. If you configure a IBM 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 IBM MQ information center.
Procedure
- Creating an activation specification for the IBM MQ messaging provider
- Configuring an activation specification for the IBM MQ messaging provider
- Migrating a listener port to an activation specification for use with the IBM MQ messaging provider
- Creating a connection factory for the IBM MQ messaging provider
- Configuring a unified connection factory for the IBM MQ messaging provider
- Configuring a queue connection factory for the IBM MQ messaging provider
- Configuring a topic connection factory for the IBM MQ messaging provider
- Configuring a queue for the IBM MQ messaging provider
- Configuring a topic for the IBM MQ messaging provider
- Configuring custom properties for IBM MQ messaging provider JMS resources