WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Migrating a single node from Version 5 embedded messaging

This topic describes the migration of a single-node environment from the embedded messaging in WebSphere Application Server Version 5 to the default messaging provider in WebSphere Application Server version 6.

Before migrating a WebSphere Application Server Version 5 node, you need to stop Version 5 JMS applications using the JMS queues that are to be migrated.

This topic provides the main steps, which are based on the general considerations given in General considerations for migrating from Version 5 embedded messaging.

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).

Note: 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 provided by WebSphere Application Server Version 5.
Consider the basic single-node scenario shown, before migration, in the following figure Figure 1.
Figure 1. WebSphere Application Server 5 single-node JMS application scenario before migration. This figure shows the example single-node scenario before migrating the node to WebSphere Application Server version 6. The JMS application is supported by an application server. The JMS application could be running within the application server or as a JMS client application.
This figure shows the example single-node scenario before migrating the node to WebSphere Application Server version 6. For more information about this scenario, see the text that accompanies this figure.

To migrate a single-node WebSphere Application Server environment from Version 5 embedded messaging to the version 6 default messaging provider, complete the following steps:

  1. Migrate the WebSphere Application Server node to Version 6. Use the procedure described in Migrating product configurations. The Version 5 embedded messaging JMS resources have been migrated to Version 5 default messaging JMS resources.
  2. If any V5 default messaging JMS topic connection factory has the Port property set to DIRECT, you must change it to QUEUED before use with the version 6 default messaging provider. For example, after migrating the node 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_tcf_name.
    2. For the Port field, select the QUEUED option
    3. Click OK.
    4. Save any changes to the master configuration.
After migrating the node, the basic single-node scenario becomes as shown in the following figure Figure 2.
  • 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.
  • The JMS application communicates with the Version 5 JMS resources through the WebSphere MQ client link and the messaging engine. This is invisible to the JMS application.
  • The JMS resources, a JMS queue connection factory, shown as JMS QCF(V5), and a JMS queue, shown as JMS Q(V5), are managed as Version 5 default messaging JMS resources.
  • The new bus queue, shown as Bus Q, is managed as a resource of the service integration bus. Messages for JMS Q(V5) are stored and processed by the message point for the associated bus destination, a queue point shown as BusQ@ME.
  • The WebSphere MQ client link presents itself as a queue manager and transforms between the WebSphere MQ client protocols used by Version 5 JMS applications and the WebSphere Application Server version 6 protocols used by messaging engines.
Figure 2. WebSphere Application Server 5 JMS application scenario after migration. This figure shows an example single-node scenario after migrating the node to WebSphere Application Server version 6. The JMS resources are now managed as V5 default messaging JMS resources implemented by the version 6 default messaging provider. 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.
This figure shows an example single-node scenario after migrating the node to WebSphere Application Server version 6. For more information about this scenario, see the text that accompanies this figure.

You should replace the Version 5 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; for example, as described in Configuring resources for the default messaging provider.

Related tasks
Migrating Version 5.x messages using the WebSphere message migration utility
Migrating a network deployment from Version 5 embedded messaging
Example: Migrating an MDB application from Version 5 embedded messaging - stage 1
Example: Migrating an MDB application from Version 5 embedded messaging - stage 2
Related reference
General considerations for migrating from Version 5 embedded messaging

Task topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjn0041_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)