Preparing to migrate from WebSphere MQ Event Broker Version 2.1

This topic describes what you must do before you start to migrate a WebSphere MQ Event Broker Version 2.1 broker domain in any of the following tasks:

You must complete the steps in this topic before you perform the task Migrating from WebSphere MQ Event Broker Version 2.1 to WebSphere Event Broker Version 6.0.

  1. Make sure that Control Center users have checked in all WebSphere MQ Event Broker resources.
  2. Back up all configuration repository and broker database tables.
  3. Decide which message flows you want to migrate and use in the WebSphere Event Broker Version 6.0 broker domain. Using a Control Center session, in which all the required message flows are visible in the workspace, export the message flows. Save the export files in a directory other than the one in which WebSphere MQ Event Broker is installed.
  4. Decide which brokers you want to migrate, and which assignments, topology, and topics configuration data you want to preserve.
    For each broker that you want to migrate, and for the associated assignments configuration data that you want to preserve, record the following information (view this information in a Control Center session and record it manually):
    • The name of the broker
    • The name of each execution group within the broker
    • For each execution group within the broker, the name of each message flow that is assigned to the execution group
    • For each message flow assigned to an execution group, the following properties:
      • Additional instances
      • Commit count
      • Commit interval
      • Coordinated transaction
    For the topology configuration data that you want to preserve, record the following information:
    • The name of each collective and the names of the brokers that are in the collective
    • All direct connections between brokers
    For the topics configuration data that you want to preserve, record the following information:
    • The hierarchy of topics, including the name of each topic
    • The access control list for each topic
  5. Decide which databases and queue managers you want to preserve.

    When you migrate, you delete all the components of WebSphere MQ Event Broker and drop all the database tables used by the Configuration Manager and the brokers. However, to simplify the task of configuring the new broker domain, preserve the databases and queue managers used by the brokers that you want to migrate. If you are migrating a single broker domain from WebSphere MQ Event Broker to WebSphere Event Broker, also preserve the database and queue manager used by the Configuration Manager, and the queue manager used by a User Name Server.

    You do not need to change the configuration of a queue manager that is preserved during migration. You might, however, need to ensure that the WebSphere MQ product code is at the required release and service level to support WebSphere Event Broker. At the same time, ensure that you have installed the other software prerequisites.

  6. Decide where you are going to store the development data that is created and maintained in the workbench. Store the data in the local file system, on a shared drive, or in a shared repository that is supported by Eclipse. The instructions for the individual migration tasks assume that you are using the local file system or a shared drive.
  7. When you are ready to migrate, run the mqsimigratecomponents command with the -c parameter. This performs a pre-migration check against the Version 2.1 components to ensure that they can be migrated. The pre-migration check identifies potential problems and allows you to correct them before proceeding with migration.
Related tasks
Migrating from WebSphere MQ Event Broker Version 2.1 to WebSphere Event Broker Version 6.0
Related reference
mqsimigratecomponents command