Migrating a message set

This task topic describes how to migrate a message set into WebSphere Message Broker Version 6.0.

Before you start:

Before you attempt this task, read the following information:

Note: This task topic only applies to migrating a message set from WebSphere MQ Integrator Version 2.1 or WebSphere MQ Integrator Broker Version 2.1 to WebSphere Message Broker Version 6.0.

It is possible to use message sets in WebSphere Message Broker Version 6.0 that were created using WebSphere MQ Integrator Version 2.1 or WebSphere MQ Integrator Broker Version 2.1. If the *.mrp file is modified by hand between the export from WebSphere MQ Integrator Version 2.1 or WebSphere MQ Integrator Broker Version 2.1, and then imported into WebSphere Message Broker Version 6.0, the results are not guaranteed and errors could occur.

To migrate a message set:

  1. Export the message set or sets from WebSphere MQ Integrator Broker Version 2.1. For more detailed information on this task refer to the WebSphere MQ Integrator Broker Version 2.1 documentation library.
  2. Transfer the exported *.mrp file or files to the system on which you are running the WebSphere Message Broker Version 6.0 workbench. Check that the directory in which you store these files contains only the files that you want to import.
  3. Close the workbench. This must not be running when you invoke the mqsimigratemsgsets command.
  4. From a command line, invoke the mqsimigratemsgsets command, specifying the parameters that you require.
  5. Check the report file mqsimigratemsgsets.report.txt that is written to the directory from which you invoked the command. The command provides the following information:
    • The parameters specified when the mqsimigratemsgsets command was invoked
    • The name of each message set file (*.mrp file) that has been migrated
    • Any warnings that have been generated
    • Details of the objects created
    • The time taken to process the message set
    • The number of warnings produced for the message set
    • The number of objects created for the message set
    • The number of exported files that were processed
  6. Start the workbench and switch to the Broker Application Development perspective.
  7. You can now examine and manipulate the newly created message set project or projects. The created projects are closed in the Broker Application Development perspective and must be opened (right-click the project then click Open Project).
When you have migrated your resources, see the Version 2.1 post-migration tasks or Version 5.0 post-migration tasks for information about tasks that you might want to perform after migration.
Related concepts
Message sets overview
Related tasks
Working with a message set
Generating information from message sets
Related reference
mqsimigratemsgsets command
Migrating Message Sets from Version 2.1