WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

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:

Why and when to perform 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 Figure 1.
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 WebSphere Application Server Version 6. The JMS application is supported by an application server. The JMS application could 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.

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:

Steps for this task

  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.

After migrating the application server, the basic stand-alone application server scenario becomes as shown in the following figure Figure 2.
Figure 2. WebSphere Application Server 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 6. The JMS resources are now managed as Version 5 default messaging JMS resources implemented by the Version 6 default messaging provider. Also, a WebSphere MQ client link and bus queue have been created and assigned to the messaging engine, to enable Version 5 JMS applications to use the JMS resources.
This figure shows an example single-node scenario after migrating the node to WebSphere Application Server Version 6.

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.

Related tasks
Migrating Version 5 messages using the WebSphere message migration utility
Migrating a network deployment from Version 5 embedded messaging
Example: Migrating an MDB application from Version 5 embedded messaging - stage 1
Example: Migrating an MDB application from Version 5 embedded messaging - stage 2
Related reference
General considerations for migrating from Version 5 embedded messaging

Task topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjn0041_.html

© Copyright IBM Corporation 2004, 2007. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)