Performing parallel migration for an integration node

You can use parallel migration to perform a staged migration process by creating a new Version 11.0 integration node to run in parallel with your existing integration node. You can then migrate your application logic from your existing integration node to your new integration node.

Before you begin

Complete the following tasks:
  • Plan your migration; see Preparing for migration.
  • Perform pre-migration tasks; see Performing pre-migration tasks.
  • If your deployment uses functions that integrate with IBM MQ (or IBM MQ), or requires that the integration node has a specified queue manager, make sure that you have a supported version of IBM MQ. For information about IBM App Connect Enterprise functions that require IBM MQ, see Installing IBM MQ.
    • If you are reusing an existing IBM MQ (orIBM MQ) deployment, migrate your queue managers and other resources to a supported version of IBM MQ by following the instructions that are provided in the IBM MQ product documentation.
      Note: If you are reusing an existing IBM MQ (or IBM MQ) deployment, you can configure the new IBM App Connect Enterprise Version 11.0 integration nodes to use the same queue managers as the existing integration nodes. You do not have to create new queue managers for the new integration nodes.
    • If you are installing a new IBM MQ deployment, create one or more queue managers to support the required configuration for your IBM App Connect Enterprise Version 11.0 integration nodes.
  • Check that you have no aggregations in progress on this integration node. When you migrate an integration node to Version 11.0, all live data that is being stored for aggregations in progress is lost.

About this task

To migrate application logic from an integration node on a distributed operating system to a different Version 11.0 integration node on the same computer, or on a different computer, complete the following steps:

Procedure

  1. Install IBM App Connect Enterprise Version 11.0 on the same computer as your existing version, or on a different computer.
    If you are installing on the same computer, you must specify a different location.
  2. Migrate your development resources to the IBM App Connect Enterprise Toolkit Version 11.0; see Migrating development resources to IBM App Connect Enterprise Version 11.0.
  3. Set up the correct Version 11.0 command environment:
    • Linux platformOn Linux® systems, open a new shell and run the environment profile mqsiprofile for this Version 11.0 installation.
    • Windows platformOn Windows, click Start, and open the Command Console that is associated with this Version 11.0 installation.
  4. Create a Version 11.0 integration node by using the mqsicreatebroker command or the IBM App Connect Enterprise Toolkit. Give the integration node a name that is different from the name of the existing integration node.
    If any of the resources on the existing integration node require IBM MQ, specify an appropriately configured queue manager for the new integration node; see Installing IBM MQ.
  5. Start the Version 11.0 integration node by using the mqsistart command.
    You can also start a local integration node by using the IBM App Connect Enterprise Toolkit.
  6. Write a list of the integration servers that you have on the existing integration node, and create these same integration servers on the Version 11.0 integration node.
    Use the web user interface, the IBM App Connect Enterprise Toolkit Version 11.0, or the mqsicreateexecutiongroup command to complete this step.
  7. Deploy the message flows, applications, and libraries that are in use by the existing integration node to the Version 11.0 integration node from the Version 11.0 IBM App Connect Enterprise Toolkit.
  8. Configure all other relevant properties of the existing integration node on the Version 11.0 integration node.
  9. If you want to delete your existing integration node, complete the following steps:
    1. In a command environment for your previous version, stop the original integration node by using the mqsistop command.
    2. Remove the original integration node from the IBM App Connect Enterprise Toolkit.
    3. In a command environment for your previous version, delete the original integration node by using the mqsideletebroker command.

What to do next

When you have completed migration, see the tasks in Performing post-migration tasks for information about tasks that you might want to complete after migration.