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.

Why and when to perform this task

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 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 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:

• General considerations for migrating from version 5 embedded messaging
  This topic describes the general considerations for migrating from version 5 embedded messaging to the version 6 default messaging provider. These general considerations apply to the related migration tasks.

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

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

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

• Example: Migrating an MDB application from version 5 embedded messaging - stage 2
  This topic provides an example of the migration of an MDB (message-driven bean) application on a version 6 node, from using version 5 default messaging JMS resources and listener port to version 6 default messaging provider JMS resources including JMS activation specification.

Related tasks

"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