Use this task to configure a connection to Version 5 default messaging.
This task is provided to help you manually migrate nodes from v5 to v6; If
you use the supplied tools to migrate existing v5 nodes to v6, the jmsserver,
appserver and port that you create with this task are defined automatically.
About this task
To configure a connection for Version 5 default messaging, use
the administrative console to complete the following steps:
Procedure
- Create an application server with the name jmsserver (only one
of these can exist on each node). In the navigation pane, expand .
- On the new server, define a new JMSSERVER_QUEUED_ADDRESS port with
the host set to the v6 server host, and the port set to the same as the SIB_MQ_ENDPOINT_ADDRESS
of the server which is a member of your bus. The appserver called jmsserver
does not actually have to be started; it is only used for looking up the port
address.
- Define a queue connection factory and queue at the Node or Cell
scope. In the navigation pane, expand .
- Define a queue destination on your bus with the same name as your
queue defined under v5 default messaging.
- Define an alias destination on your bus with the same name as your
queue defined under v5 default messaging but with WQ_ appended to the front
the name. For example, if your queue has the name MyV5Queue, your alias should
have the name WQ_MyV5Queue.
- Point the alias at your queue destination with the correct name.
The migration process targets the queue with the WQ_ prefix; defining the
alias to point to the real queue helps migration.
- Define the WebSphere MQ Client Link on your messaging engine on
the bus. Keep the WebSphere MQ channel name WAS.JMS.SVRCONN and set the queue
manager name so that it contains your node name. For example, if your node
name is MyNode, you would set the queue manager name to WAS_<MyNode>_jmsserver. Now
set the queue manager name to the same; in this example it would be WAS_MyNode_jmsserver.
The WebSphere MQ Client Link will show a status of inactive, this is normal.
- Restart your server so that the new JNDI definitions bind correctly.
Your v5 client should now be able to connect to v6 using the host and bootstrap
address of the v6 system in the provider url component of the initial context.
Your client should now also be able to send messages to the destination on
the bus.
- If you open the Client connections view and click the refresh icon,
the hostname of the connecting system is visible whilst the client is connected.
In the navigation pane, expand.
- Click OK.
- Save any changes to the master configuration.
- To have the changed configuration take effect, stop
then restart the application server.