Migrate from WAS V 5 embedded messaging

This set of topics describes the migration of JMS applications from the embedded messaging in WAS V5.1 to the default messaging provider in later versions.

You can temporarily use JMS resources developed for WAS V5.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 V5 embedded messaging.

When migrating a V5.1 node to a later version, you do not have to modify the JMS applications; they can continue to use most of the existing V5.1 JMS deployment, installation, and settings. However, when migrating a V5.1 message-driven bean (MDB) application, 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.

See about migrating from WAS V5 embedded messaging, see the following links:

 

What to do next