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

Example: Migrating an MDB application from Version 5 embedded messaging - stage 1

This topic provides an example of the migration of an MDB (message-driven bean) application from the embedded messaging in WebSphere Application Server Version 5 to the default messaging provider in WebSphere Application Server Version 6.

Before you begin

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.

Why and when to perform this task

This topic provides a contextual description of the migration, then a summary of the steps involved.

The migration of the MDB application is part of the migration of the Version 51 node, called wasA, on which it runs. When migrating the WebSphere Application Server Version 5 node to version 6, you do not need to make any changes to the MDB application; it can continue to use the same deployment and installation, and the same configurations of Version 5 JMS resources. However, to complete the migration, you should replace the listener port used by the MDB application with a JMS activation specification.

Consider the example scenario shown, before migration, in the following figure.
Figure 1. WebSphere Application Server Version 5 single-node MDB application scenario before migration
This figure shows a WebSphere Application Server Version 5 single-node MDB application scenario before migration.
After migrating the node, the basic single-node scenario becomes as shown in the following figure, Figure 2.

You should then replace the Version 5 default messaging JMS resources with equivalent Version 6 default messaging provider JMS resources as soon as is conveniently possible (for example, after any Version 5 JMS client applications have been migrated onto WebSphere Application Server Version 6).

To migrate the MDB application from Version 5 embedded messaging to the version 6 default messaging provider, complete the following steps:

Steps for this task

  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 JMS application uses the Version 5 embedded messaging provider's DIRECT port for publish/subscribe messaging, as set on the WebSphere topic connection factory, change the Port property of the connection factory to QUEUED before use with the Version 6 default messaging provider.

After migrating the Version 5 node, the MDB application scenario becomes as shown in the following figure:
Figure 2. WebSphere Application Server Version 5 node after migration
This figure shows a WebSphere Application Server Version 5 single-node MDB application scenario after migration.

The MDB application can continue to access the JMS resources, which are now implemented through the WebSphere Application Server Version 6 default messaging provider. You can use the Version 6 administrative console to manage the JMS resources as Version 5 Default Messaging JMS resources.

The MDB application can continue to receive messages through the listener port.

After migrating a Version 5 MDB application, you should complete the following steps:
  1. You should replace 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).
  2. Change the configuration of the MDB application to use a JMS activation specification instead of the listener port.
  3. Re-deploy or re-install (with the Deploy EJB option selected) the MDB application.

These steps enable you to benefit from the better performance of the Version 6 default messaging provider, and to exploit the use of multiple messaging engines in a service integration bus, and other default messaging functions enabled by service integration technologies.

You can replace JMS resources manually, for example by using the WebSphere Application Server administrative console. Alternatively, you could replace the resources by writing some scripting that retrieves the Version 5 property values then creates Version 6 JMS resources with values appropriate to your Version 6 environment and your use of the Version 5 properties.

For an example of migrating the MDB application from Version 5 default messaging JMS resources and listener port to Version 6 default messaging provider JMS resources including JMS activation specification, see Example: Migrating an MDB application from Version 5 embedded messaging - stage 2

Related tasks
Migrating Version 5 messages using the WebSphere message migration utility
Migrating a stand-alone application server from Version 5 embedded messaging
Migrating a network deployment from Version 5 embedded messaging
Example: Migrating an MDB application from Version 5 embedded messaging - stage 2
Related reference
General considerations for migrating from Version 5 embedded messaging
1 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.

Task topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjn0043_.html

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