Performing an in-place migration of an integration node

You can use the ibmint extract node command with the --overwrite-existing parameter to migrate an integration node from IBM® Integration Bus 10.0, IBM App Connect Enterprise 11.0, or IBM App Connect Enterprise 12.0 to IBM App Connect Enterprise 13.0 with the same name on the same machine.

Before you begin

  • Plan your migration by reading the topics in Preparing for migration.
  • Complete pre-migration tasks by following the instructions in Performing pre-migration tasks.
  • If your deployment uses functions that integrate with 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 more information, see Installing IBM MQ.
    • If you are reusing an existing IBM MQ deployment, migrate your queue managers and other resources to a supported version of IBM MQ by following the instructions in the IBM MQ product documentation.
    • If you are reusing an existing IBM MQ deployment, you can configure the new IBM App Connect Enterprise 13.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 necessary configuration for your IBM App Connect Enterprise 13.0 integration nodes.
    • Check that you have no aggregations in progress on this integration node. When you migrate an integration node to Version 13.0, all live data that is being stored for aggregations in progress is lost.

About this task

If you want to migrate an IBM Integration Bus 10.0, IBM App Connect Enterprise 11.0, or IBM App Connect Enterprise 12.0 integration node to IBM App Connect Enterprise 13.0, with the same name on the same machine, you must create a backup file by running the mqsibackupbroker command. Then, you can use the ibmint extract node command with the --overwrite-existing parameter. This option deletes an existing node before it creates the new node with the same name, by writing the extracted configuration and resources. This option is required if the value of the --output-integration-node parameter is the name of an existing integration node.

If you want to put the integration node back to its original state, you can run the mqsirestorebroker command to restore the integration node from the backup file, which you created when you ran the mqsibackupbroker command.

Procedure

The following example uses an IBM Integration Bus 10.0, IBM App Connect Enterprise 11.0, or IBM App Connect Enterprise 12.0 integration node that is named INODE, which retains the same name when it is migrated to IBM App Connect Enterprise 13.0 on the same machine.

  1. Install IBM App Connect Enterprise 13.0 on the same computer as your existing version, but in a different location.
    For more information, see Installing IBM App Connect Enterprise software.
  2. From the IBM Integration Bus 10.0, IBM App Connect Enterprise 11.0, or IBM App Connect Enterprise 12.0 command environment for your operating system, stop your existing integration node by running the mqsistop command: 
    mqsistop INODE

    For more information, see mqsistop command - Windows, Linux, and AIX systems.

  3. From the IBM Integration Bus 10.0, IBM App Connect Enterprise 11.0, or IBM App Connect Enterprise 12.0 command environment for your operating system, create a backup of your existing integration node by running the mqsibackupbroker command, specifying the name of the existing integration node that you intend to migrate to IBM App Connect Enterprise 13.0:
    The following example backs up integration node INODE on Windows, and saves it in the archive file C:\MQSI\BACKUP\INODE.zip:
    mqsibackupbroker INODE -d C:\MQSI\BACKUP -a INODE.zip
    For more information, see mqsibackupbroker command.
  4. In your newly installed Version 13.0 environment, set up the command environment for your operating system:
    • Linux platformUNIX platformOn Linux® and UNIX systems, open a new shell and run the environment profile mqsiprofile for your Version 13.0 installation. For more information, see Are the Linux and UNIX environment variables set correctly?
    • Windows platformOn Windows, click Start, and open the Command Console that is associated with your Version 13.0 installation.
  5. Migrate your existing integration node by running the ibmint extract node command with the --overwrite-existing parameter: 
    ibmintextractnode --backup-file "C:\temp\INODE.zip" --input-integration-node INODE --output-integration-node INODE --overwrite-existing

    For more information, see ibmint extract node command.

  6. Start your migrated integration node by running the mqsistart command: 
    mqsistart INODE

    For more information, see mqsistart command - Windows, Linux, and AIX platforms.

What to do next

When you complete migration, check whether you need to complete any post-migration tasks in Performing post-migration tasks.

Restoring a migrated integration node

About this task

If you want to put the integration node back to its original state, you can run the mqsirestorebroker command to restore the integration node from the backup file, which you created when you ran the mqsibackupbroker command: 

mqsirestorebroker INODE -d C:\MQSI\BACKUP -a INODE.zip

For more information, see mqsirestorebroker command.