Network Deployment (Distributed operating systems), v8.0 > Migration and coexistence > Migrate Messaging resources
Migrate from WAS Version 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.
We 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 your JMS applications; they can continue to use most of the existing v5.1 JMS deployment, installation, and configuration 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.
For more information about migrating from WAS v5 embedded messaging, see the following links:
- Migrate a stand-alone application server from v5 embedded messaging
- Migrate a network deployment configuration from v5 embedded messaging
- Example: Migrating a message-driven bean from v5 embedded messaging - stage 1
- Example: Migrating a message-driven bean from v5 embedded messaging - stage 2
- Migration from v5 embedded messaging
- Migrate v5.1 messages using the message migration utility
- Migration from v5 embedded messaging
When you migrate from WAS Version 5 embedded messaging to the default messaging provider, you do not have to change v5.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 v5.1 and later versions.
- Migrate v5.1 messages using the message migration utility
This set of topics describes the migration of WAS v5.1 messages to later version messages, using the WAS message migration utility.
- Migrate a stand-alone application server from v5 embedded messaging
Migrate a stand-alone application server from WAS v5 embedded messaging for use with the default messaging provider in later versions.
- Migrate a network deployment configuration from v5 embedded messaging
Migrate a WAS Network Deployment environment from the embedded messaging in WAS v5.1 to the default messaging provider in later versions.
- Example: Migrating a message-driven bean from v5 embedded messaging - stage 1
We can migrate a message-driven bean application from the embedded messaging in WAS v5.1 to the default messaging provider in later versions.
- Example: Migrating a message-driven bean from v5 embedded messaging - stage 2
By following this example, you can migrate a message-driven bean application on a v6 or later node from using v5.1 default messaging JMS resources and listener port to using default messaging provider JMS resources.
Maintain v5 default messaging resources