Use this task to create a link that enables a messaging engine to handle message requests from Version 5 JMS applications.
The WebSphere MQ client link enables WebSphere Application Server Version 5 J2EE applications to use messaging resources of the WebSphere Application Server Version 6 default messaging provider that are backed by destinations on the service integration bus.
Each WebSphere MQ client link presents itself as a queue manager and transforms between the WebSphere MQ client protocols used by Version 51 JMS applications and the WebSphere Application Server Version 6 protocols used by messaging engines.
If you migrate a Version 5 node to Version 6, a default WebSphere MQ link, with the name Default.MQClientLink, is created for the application servers on that node. You only need to create another WebSphere MQ client link if you want some Version 5 JMS applications to use a different channel to connect to the messaging engine, or want to present a messaging engine as a non-default queue manager name.
If you create a WebSphere MQ client link, you only need to manually specify values for a subset of the available properties. You can choose to specify values for other optional properties in this task, or if wanted at a later time by changing the configuration of the client link.
To create a WebSphere MQ client link, use the administrative console to complete the following steps.
In this information ... | IBM Redbooks, demos, education, and more(Index) |