Migrating a network deployment from version 5 embedded messaging

This topic describes the migration of a network deployment environment from the embedded messaging in WebSphere Application Server version 5 to the default messaging provider in WebSphere Application Server version 6.

Before you begin

• Stop all message-producing JMS applications in the WebSphere Application Server version 5 environment. For example, you can use the administrative console to stop the applications, as described in Starting and stopping applications.

• Allow all message-consuming JMS applications (including those consuming publications as a result of durable subscriptions) to continue until all the JMS queues are drained, then stop those applications.

Why and when to perform this task

This topic provides the main steps, which are based on the general considerations given in General considerations for migrating from version 5 embedded messaging, and link to tasks that provide the detailed steps involved.

The main consideration is that when migrating a WebSphere Application Server version 5 node to version 6¹, you do not need to make any changes to JMS applications; they can continue to use their same deployment and installation, and their same configurations of version 5 JMS resources (with one exception below). Consider the basic network deployment scenario before migration, as shown in the following figure Figure 1.

• The JMS application uses JNDI to look up the JMS resources in the WebSphere Application Server name space.

• The JMS resources, in this example a JMS queue connection factory (shown as JMS QCF) and a JMS queue (shown as JMS Q), can be configured as server resources or in the client container . The JMS resources are migrated without change except that if a topic connection factory has the Port property set to DIRECT, change it to QUEUED before use with the default messaging provider.

• The JMS queue connection factory creates connections to the JMS server on nodeA, as defined by the Node property of the connection factory. The connection factory could be configured to connect to a JMS server on any node in the deployment manager cell, and by default connects to the JMS server on the same node as the JMS application.

• WebSphere Application Server version 5 embedded messaging uses WebSphere MQ technology, and is implemented through a JMS server that runs as a separate server on the node. The administrator has defined the name of the JMS queue, Q, to the JMS server. The JMS application uses WebSphere MQ client protocols to communicate with the JMS server.

Figure 1. WebSphere Application Server 5 network deployment JMS application scenario before migration .

This figure shows the example network deployment scenario before migrating any nodes to WebSphere Application Server version 6. The JMS application is supported by an application server running on nodeB, and uses JMS resources configured to use a JMS server on nodeA. The cell is managed by the deployment manager on nodeC. The JMS application could be running within the application server or as a JMS client application.
nodes to WebSphere Application Server version 6. For more information about this scenario, see the text that accompanies this figure.">

To migrate a WebSphere Application Server network deployment environment from version 5 embedded messaging to the version 6 default messaging provider, complete the following steps:

Steps for this task

1. Use the migration wizard to migrate the deployment manager node to version 6. See Migration for more information. At this point, you have a WebSphere Application Server version 6 cell, which is managed by a version 6 deployment Manager, with 2 version 5 nodes (and their node agents).

   The version 5 embedded messaging JMS resources in the deployment manager cell are renamed to

   "V5 Default Messaging" JMS resources in WebSphere Application Server version 6. For example, on the WebSphere administrative console,

   WebSphere JMS Provider >

   WebSphere queue connection factories as shown in version 5 is renamed to

   V5 Default Messaging >

   WebSphere queue connection factories in version 6.

2. Use the migration wizard to migrate the JMS server node to version 6. See Migration for more information.

   The JMS server is migrated to an application server, called jmsserver, and added as a member of a service integration bus that has the same name. A messaging engine is created automatically on that bus for the application server. There is only one such application server and bus for each version 5 node.

   A default WebSphere MQ client link , called Default.MQClientLink, is created automatically for the node and assigned to the messaging engine for the application server called jmsserver.

   For each JMS queue defined on the JMS server, the migration process automatically creates a new bus queue with the same name as the version 5 JMS queue, and creates a message point assigned to the messaging engine. Messages sent to the JMS queues are stored and processed at the message point. After migrating the deployment manager and JMS server nodes, the network deployment scenario becomes one of interoperation between version 5 and version 6 nodes within a version 6 deployment manager cell as shown in the following figure Figure 2.

   • The JMS resources, a JMS queue connection factory (shown as V5 JMS QCF) and a JMS queue (shown as V5 JMS Q), are managed by the version 6 deployment manager as V5 Default Messaging JMS resources.

   • The JMS application communicates with the version 5 JMS resources through the WebSphere MQ client link and the messaging engine in the application server created from the JMS server. This is all invisible to the JMS application.

   Figure 2. WebSphere Application Server 5 network deployment JMS application scenario after migration stage 1 .

   This figure shows the example network deployment scenario after migrating the deployment manager nodeC and the JMS server nodeA to WebSphere Application Server version 6. The version 5 JMS server has been recreated as a version 6 application server with a messaging engine in its own service integration bus, shown as bus nodeA. Also, a WebSphere MQ client link and bus queue have been created and assigned to the messaging engine, to enable version 5 JMS applications to use the JMS resources.
   
   

   The interoperation between version 5 and version 6 nodes within a version 6 deployment manager cell is intended only as an intermediary stage toward a complete version 6 cell. In this scenario, to complete the migration you migrate the remaining application server nodeB.

3. Use the migration wizard to migrate the version 5 application server
   nodes to version 6. See Migration for more information.

4. If any V5 default messaging JMS topic connection factory has the Port property set to DIRECT, change it to QUEUED before use with the default messaging provider. For example, use the version 6 WebSphere
   administrative console to complete the following steps:
   1. Display the version 5 default messaging JMS topic connection factory Click

      Resources >

      JMS Providers >

      V5 Default Messaging >

      WebSphere Topic Connection Factories >

      jms_qcf_name.

   2. For the

      Port field, select the QUEUED option

   3. Click

      OK .

   4. Save any changes to the master configuration.

After migrating all the nodes in the cell, the scenario then becomes as shown in the following figure Figure 3.

Figure 3. WebSphere Application Server version 5 network deployment JMS application scenario after migration stage 2 .

This figure shows the example network deployment scenario after migrating all the nodes to WebSphere Application Server version 6, but before replacing version 5 JMS resources with equivalent version 6 JMS resources. The WebSphere MQ client link for the messaging engine on bus B enables JMS applications to use the version 5 JMS resources implemented by the version 6 default messaging provider.
nodes to WebSphere Application Server version 6, but before replacing version 5 JMS resources with equivalent version 6 JMS resources. For more information about this scenario, see the text that accompanies this figure.">

The JMS application can continue to access the version 5 JMS resources, which are now managed as V5 default messaging JMS resources implemented by the WebSphere Application Server version 6 default messaging provider. You can use the version 6 administrative console to manage the JMS resources as V5 default messaging JMS resources. There are two variants on this migration:

• If the application server and JMS server were on the same host, the migration creates the same pair of service integration buses on the one version 6 host, as shown in the following figure Figure 4.

• If JMS applications on a version 6 node need to use JMS resources provided by a JMS server on a version 5 node in the cell, they can do so through the version 5 default messaging JMS resource definitions.

Figure 4. WebSphere Application Server version 5 network deployment JMS application scenario after migration of a combined JMS server - application server node .

This figure shows an example network deployment scenario after migrating the deployment manager nodeC and a server node that hosts both a JMS server and application server. The version 5 JMS server has been recreated as a version 6 application server with a messaging engine in its own service integration bus, shown as bus nodeB. Also, a WebSphere MQ client link has been created for the messaging engine on bus nodeB, to enable version 5 JMS applications to use the JMS resources implemented by the version 6 default messaging provider.

You should replace the V5 default messaging JMS resources with equivalent version 6 default messaging provider JMS resources as soon as is conveniently possible (after all JMS applications using those resources have been moved onto WebSphere Application Server version 6).

You should define any new JMS resources as version 6 resources.

Parent topic: Migrating from version 5 embedded messaging

Related tasks

Related reference

General considerations for migrating from version 5 embedded messaging ¹ To make reading easier in this topic, the abbreviation

"version 5" is sometimes used to refer to

"WebSphere Application Server version 5" and

"version 6" is used to refer to

"WebSphere Application Server version 6" . For example,

"version 5 JMS resources" refers to JMS resources