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

Migrating from Version 5 embedded messaging

This set of topics describe the migration of JMS applications from the embedded messaging in WebSphere Application Server Version 5 to the default messaging provider in WebSphere Application Server version 6.

For general migration considerations, see 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 61, 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 given in the general considerations and related tasks). However, after migrating a Version 5 MDB application, you should change the configuration to use a JMS activation specification instead of a listener port, then redeploy or reinstall the MDB application.

Migrating from Version 5 embedded messaging is described in more detail in the following topics:

Related tasks
Maintaining Version 5 default messaging resources
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: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjn0040_.html

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