+

Search Tips   |   Advanced Search

Set a connection for V5 default messaging


Use this task to configure a connection to V5 default messaging. This task is provided to help you manually migrate nodes from V 5 to V6. If we use the supplied tools to migrate existing Version 5 nodes to V6, the jmsserver, appserver and port created with this task are defined automatically.

To configure a connection for V5 default messaging, use the admin console to complete the following steps:

 

  1. Create an appserver with the name jmsserver (only one of these can exist on each node). In the navigation pane, expand Servers > Server Types > WebSphere application servers .

  2. 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 that is a member of the bus. The appserver called jmsserver does not actually have to be started; it is only used for looking up the port address.

  3. Define a queue connection factory and queue at the Node or Cell scope. In the navigation pane, click Resources > JMS > JMS providers .

  4. In the content pane, click the name of the V5 default messaging provider.

  5. Define a queue destination on the bus with the same name as the queue defined for the V5 default messaging provider.

  6. Define an alias destination on the bus with the same name as the queue defined for the V5 default messaging provider but with WQ_ appended to the front the name. For example, if the queue has the name MyV5Queue, the alias should have the name WQ_MyV5Queue.

  7. Point the alias at the 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.

  8. 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 the node name. For example, if the 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.

  9. Restart the server so that the new JNDI definitions bind correctly. Your V5 client should now be able to connect to Version 6 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.

  10. If we open the Client connections view and click the refresh icon, the host name of the connecting system is visible when the client is connected. In the navigation pane, expand Buses > [bus name] > Messaging engines > [messaging engine name] > WebSphere MQ client links > [client link name] > Runtime > Client connections view.

  11. Click OK.

  12. Save any changes to the master configuration.

  13. To have the changed configuration take effect, stop then restart the appserver.

 

Related tasks


Set a queue for V5 default messaging
Set V5 default messaging resources
Manage WAS V5 JMS use of messaging resources in later versions of WAS ND

 

Related


Version 5 default messaging queue connection factory settings