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 WebSphere Application Server Version 6 default messaging provider.

Before you begin

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

About this task

For related information, see General considerations for migrating from Version 5 embedded messaging.

When migrating a WebSphere Application Server Version 5 stand-alone application server to Version 6, you do not need to make any changes to JMS applications which can continue to use their same deployment and installation, and their same configurations of Version 5 JMS resources, apart from one exception which is described below.

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 node to WebSphere Application Server Version 6.

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

Procedure

  1. Migrate the stand-alone WebSphere Application Server to Version 6.

    Use the procedure described in Migrating product configurations.

    The Version 5 embedded messaging JMS resources have been migrated to Version 5 default messaging JMS resources.
  2. If any Version 5 default messaging JMS topic connection factory has the Port property set to DIRECT, you must change it to QUEUED before use with the Version 6 default messaging provider. For example, after migrating the application server use the Version 6 WebSphere Application Server administrative console to complete the following steps:
    1. Display the Version 5 default messaging JMS topic connection factory Click Resources > JMS > JMS Providers . All currently configured JMS providers (default, Version 5 default, and WebSphere MQ) are listed.
    2. From the list view, select the required provider.
    3. In the content pane, under Additional properties, click Topic connection factories All topic connection factories for the selected provider are displayed.
    4. For the Port field, select the QUEUED option
    5. Click OK.
    6. Save any 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 5 JMS application scenario after migration.
  • The JMS application can continue to access the Version 5 JMS resources, which are now managed as Version 5 default messaging JMS resources implemented by the WebSphere Application Server Version 6 default messaging provider.
  • The JMS application communicates with the Version 5 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 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 JMS applications and the WebSphere Application Server Version 6 protocols used by messaging engines.
Figure 2. WebSphere Application Server 5 JMS application scenario after migration
This figure shows an example single-node scenario after migrating the node to WebSphere Application Server Version 6.

What to do next

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

You should replace the Version 5 default messaging JMS resources with equivalent Version 6 default messaging provider JMS resources as soon as is conveniently possible (after all JMS applications using those resources have been moved onto WebSphere Application Server Version 6).

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




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 6:22:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-express-dist&topic=tjn0041_
File name: tjn0041_.html