Migrate JMS applications

Migrate JMS applications

Both WebSphere Application Server Version 4.0.x and Version 5 support the Java Message Service (JMS) V1.0.2 specification. Version 4.0.x applications written to this specification do not require modification in order to run in Version 5.

Version 5 JMS migration involves migrating the JMS resources such as connection factories, queues, and topics used by such applications. Three different JMS providers are available in Version 5:

Generic JMS provider

Embedded WebSphere JMS provider

WebSphere MQ JMS provider

See Administer JMS resources in the Administration topic for more information on these Version 5 JMS providers.

By default, all JMS resources from Version 4.0.x are mapped to generic JMS provider resources by the Version 5 migration tools. For more information on generic JMS providers, see Administer generic JMS providers in the Administration topic. If the WebSphere MQ or MQSeries products were used as your back-end message server in Version 4.0.x, then ensure that you have the versions supported by Version 5 before you migrate:

WebSphere MQ for iSeries V5.3 (5724B41)

WebSphere MQ classes for Java and JMS (5639C34)
Note: Earlier versions of these products (e.g. MQSeries for iSeries V5.2) are not supported by Version 5. Additionally, possess a full license for these products if you plan to continue using these products with the generic JMS provider in Version 5.

The WebSphere MQ JMS provider provides better integration with the WebSphere MQ product. If you are using this product as your back-end message server, then consider remapping your JMS resources from the generic JMS provider to the WebSphere MQ JMS provider. For more information on the WebSphere MQ JMS provider and how to configure resources for it, see Administer resources for the WebSphere MQ JMS provider in the Administration topic.

For new JMS applications which use WebSphere MQ that is installed on the same machine where WAS Version 5 in running, also consider using the embedded WebSphere JMS provider. For more information, see Administer resources for the embedded WebSphere JMS provider in the Administration topic.

Enterprise applications that use message beans with the JMS Listener in WebSphere Application Server Enterprise Edition Version 4.0.x must be migrated to use EJB 2.0 message-driven beans. See Migrate a JMS listener application to use message-driven beans in the Application development topic for more information.

Note: WebSphere Application Server Enterprise Edition Version 4.0.x is not available on iSeries. These instructions are provided for customers who are migrating such applications from Enterprise Edition Version 4.0.x running on a workstation platform to Version 5 running on iSeries.