This set of topics describes the migration of JMS applications from the embedded messaging in WebSphere® Application Server Version 5.1 to the default messaging provider in later versions.
You can temporarily use JMS resources developed for WebSphere Application Server Version 5.1 with service integration in later versions, however you should ideally migrate all resources to the later versions as soon as possible.
For migration strategies, see Migration from Version 5 embedded messaging.
When migrating a Version 5.1 node to a later version, you do not have to modify your JMS applications; they can continue to use most of the existing Version 5.1 JMS deployment, installation, and configuration settings. However, when migrating a Version 5.1 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:
When you migrate from WebSphere Application Server Version 5 embedded messaging to the default messaging provider, you do not have to change Version 5.1 JMS applications, JMS resource definitions, or client JMS resource definitions. Use of bus resources is enabled by a WebSphere MQ client link, and the wildcard syntax is converted automatically for interoperation between Version 5.1 and later versions.
This set of topics describes the migration of WebSphere Application Server Version 5.1 messages to later version messages, using the WebSphere Application Server message migration utility.
Migrate a stand-alone application server from WebSphere Application Server Version 5 embedded messaging for use with the default messaging provider in later versions.
Migrate a WebSphere Application Server Network Deployment environment from the embedded messaging in WebSphere Application Server Version 5.1 to the default messaging provider in later versions.
You can migrate a message-driven bean application from the embedded messaging in WebSphere Application Server Version 5.1 to the default messaging provider in later versions.
By following this example, you can migrate a message-driven bean application on a Version 6 or later node from using Version 5.1 default messaging JMS resources and listener port to using default messaging provider JMS resources.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) |