Migrating a stand-alone application server from Version 5 embedded messaging

Migrate a stand-alone application server from WebSphere® Application Server Version 5 embedded messaging for use with the default messaging provider in later versions.

Before you begin

Before starting this task you must stop all Version 5.1 JMS applications that are using the JMS queues you want to migrate:

About this task

When migrating a WebSphere Application Server Version 5.1 stand-alone application server to later versions, you do not have to make any changes to JMS applications that can continue to use their same deployment and installation, and their same configurations of Version 5.1 JMS resources, apart from one exception which is described below. For a more detailed explanation, see Migration from Version 5 embedded messaging.

Before migrating, consider the stand-alone application server scenario shown in the following figure Stand-alone WebSphere Application Server 5 JMS application scenario before migration.
  • The JMS application uses JNDI to look up the JMS resources in the WebSphere Application Server namespace.
  • The JMS resources in this example are a JMS queue connection factory (shown as JMS QCF) and a JMS queue (shown as JMS Q).
  • WebSphere Application Server Version 5 embedded messaging uses WebSphere MQ technology, and is implemented through a JMS server that runs as the jmsserver service of the application server. The JMS application uses WebSphere MQ client protocols to communicate with the JMS server.
Figure 1. Stand-alone WebSphere Application Server 5 JMS application scenario before migration. This figure shows the example stand-alone application server scenario before migrating the stand-alone application server to a later version. The JMS application is supported by an application server. The JMS application can be running within the application server or as a JMS client application.
This figure shows the example stand-alone application server scenario before migrating the node to WebSphere Application Server Version 6 or later.

To migrate a stand-alone WebSphere Application Server environment from Version 5 embedded messaging to the default messaging provider in later versions, complete the following steps:

Procedure

  1. Migrate the stand-alone WebSphere Application Server to the later version. See the documentation about migrating product configurations. The Version 5 embedded messaging JMS resources have been migrated to V5 default messaging JMS resources.
  2. If any Version 5.1 default messaging JMS topic connection factory has the Port property set to DIRECT, you must change it to QUEUED before use with the default messaging provider. For example, after migrating the application server, use the administrative console in the later version to complete the following steps:
    1. Display the Version 5.1 default messaging JMS topic connection factory Click Resources -> JMS -> JMS providers -> V5 default messaging provider -> [Additional Properties] Topic connection factories > factory_name.
    2. For the Port field, select the QUEUED option.
    3. Click OK.
    4. Save your changes to the master configuration.

Results

After migrating the application server, the basic stand-alone application server scenario becomes as shown in the following figure WebSphere Application Server Version 5 JMS application scenario after migration.
  • The JMS application can continue to access the Version 5.1 JMS resources, which are now managed as Version 5.1 default messaging JMS resources implemented by the default messaging provider in the later version.
  • The JMS application communicates with the Version 5.1 JMS resources through the WebSphere MQ client link and the messaging engine. This is invisible to the JMS application.
  • The JMS resources, a JMS queue connection factory, shown as JMS QCF(V5), and a JMS queue, shown as JMS Q(V5), are managed as Version 5.1 default messaging JMS resources.
  • The new bus queue, shown as Bus Q, is managed as a resource of the service integration bus. Messages for JMS Q(V5) are stored and processed by the message point for the associated bus destination, a queue point shown as BusQ@ME.
  • The WebSphere MQ client link presents itself as a queue manager and transforms between the WebSphere MQ client protocols used by Version 5.1 JMS applications and the protocols used by the messaging engines in the later version of the product.
Figure 2. WebSphere Application Server Version 5 JMS application scenario after migration. This figure shows an example stand-alone application server scenario after migrating the application server to WebSphere Application Server Version 7.0. The JMS resources are now managed as Version 5 default messaging JMS resources implemented by the Version 7.0 default messaging provider. Also, a WebSphere MQ client link and bus queue have been created and assigned to the messaging engine, to enable JMS applications developed for WebSphere Application Server Version 5.1 to use the JMS resources.
This figure shows an example of a single-node scenario after migrating the node  to WebSphere Application Server Version 6 or later.

What to do next

Security tip: If you have configured authorization level security on Version 5.1 it cannot be migrated to the later version. The migration tool cannot migrate authorization security for you and manual configuration is needed.

You should replace the Version 5.1 default messaging JMS resources with equivalent default messaging provider JMS resources as soon as is conveniently possible (after all JMS applications that use those resources have been moved onto the later version of the product).

You should define any new JMS resources as resources in the later version; for example, as described in Configuring resources for the default messaging provider.

Task topic Task topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 5:16:49 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-base-iseries&topic=tjn0041_
File name: tjn0041_.html