Migrating from WebSphere Application Server Version 5 embedded messaging

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.

About this task

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:

What to do next

Task topic    

Terms of Use | Feedback

Last updated: Oct 20, 2010 7:53:43 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-dist&topic=tjn0040_
File name: tjn0040_.html