Running the WebSphere message migration utility

This topic describes how to run the WebSphere® message migration utility.

Before you begin

  1. Ensure that you have a WebSphere Application Server Version 5, which contains an embedded messaging server.

    You do not need to start the WebSphere Application Server Version 5.

  2. Ensure that no applications are reading from the WebSphere Application Server Version 5 queue manager when you run the message migration utility.
  3. Ensure that you have not modified or deleted the message queues on the WebSphere Application Server Version 5.
  4. Ensure that you have a running WebSphere Application Server Version 6 that fulfills the following conditions.
    1. The WebSphere Application Server Version 6 is on the same host as the WebSphere Application Server Version 5.
    2. The WebSphere Application Server Version 6 contains a messaging engine on the bus to which the messages will migrate (this is automatically included for you if you upgrade your server from Version 5 to Version 6).
    Note: These conditions are met if you run the message migration utility at the correct point in the WebSphere Application Server migration sequence. The correct point is after you have run the WASPostUpgrade command and restarted the Version 6 node.

About this task

Messages are migrated from the WebSphere Application Server Version 5 to the WebSphere Application Server Version 6 under an XA (globally coordinated) transaction. For further information about the XA transaction refer to XA recovery.

For further information about the reversal of message migration, using the message migration utility, refer to Reversing the migration of messages using the WebSphere message migration utility.

During successful migration, messages are moved from the WebSphere Application Server Version 5 to the WebSphere Application Server Version 6, no copy is left on the Version 5 server's queue.

Note:
  1. You run the message migration utility only once for a particular queue, unless a failure occurs.
  2. If a failure occurs during message migration, it is safe to run the message migration utility again in the same direction because messages are moved rather than copied. Whether you successfully try a failing message migration again, or delete the message, the message ordering of the remaining messages is preserved on the WebSphere Application Server Version 6 queue.

Procedure

  1. Follow the actions indicated by the message migration utility.
  2. On the panel called "Select the direction of migration" select Migrate messages from Version 5 to Version 6.
  3. Select a message reliability to apply to messages that are to be migrated. More details on the choice of reliabilities can be found in the Message Reliability Levels topic.
  4. It is possible to migrate multiple queues during a single execution of the utility.

Results

  1. You will need to run the migration utility more than once if the first message migration attempt failed.
  2. If a queue has a failing message then perform one of the following operations:
    1. Try the failing message again, in case there is a transient error.
    2. Delete the failing message and go on to the next message.
    3. Stop the queue that has the failing message and move on to the next queue.



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=tjnmmurun
File name: tjnmmurun.html