This set of topics describes 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.
You can temporarily use Application Server Version 5 JMS resources with service integration in WebSphere Application Server Version 6, however you should ideally migrate all resources to Version 6 as soon as possible.
For general migration considerations, see General considerations for migrating from Version 5 embedded messaging.
When migrating a Version 5 node to Version 6, you do not have to modify your JMS applications; they can continue to use most of the existing Version 5 JMS deployment, installation, and configuration settings. However, when migrating a Version 5 message-driven bean (MDB) application, you must modify the configuration to provide a JMS activation specification, not a listener port (MDBs do not use listener ports), then redeploy or reinstall the MDB application.
For more information about migrating from WebSphere Application Server Version 5 embedded messaging, see the following links:
In this information ...Subtopics
| IBM Redbooks, demos, education, and more(Index) |