Performing extract migration of an integration node or integration server

You can use the ibmint extract node and ibmint extract server commands to migrate 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. Use these commands to migrate the configuration and resources of an integration node or integration server.

Before you begin

About this task

Use the ibmint extract node command to migrate integration nodes. Use the ibmint extract server command to migrate managed integration servers. Independent integration servers that were created in IBM App Connect Enterprise 11.0 or IBM App Connect Enterprise 12.0 can be started in IBM App Connect Enterprise 13.0 without the need to migrate them or their resources. However, integration server work directories are typically created as transient rather than long-term artifacts, and many users prefer to rebuild them when they move from one version to another.

Procedure

To complete extract migration for an integration node or a managed integration server, follow the appropriate set of steps:

Performing extract migration of an integration node

Procedure

  1. On your source system, run the mqsibackupbroker command, specifying the name of the 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.
  2. Transfer the backup file that is created by the mqsibackupbroker command to an appropriate location.
    You can transfer the backup file to a location on the same system as the existing integration node, or to a location on a different system.
  3. Run the ibmint extract node command on the system to which you transferred the backup file.
    On the ibmint extract node command, you must specify the following values:
    • The name of the backup file that is created when you run the mqsibackupbroker command on the source system.
    • The name in the backup file of the integration node from which you are migrating.
    • The name of the integration node to which to write the extracted configuration and resources.
    You can also specify one or more optional parameters on the ibmint extract node command. For more information, see ibmint extract node command.
  4. Optional: If you plan to run the migrated integration node on the same system as the existing integration node, stop the existing integration node by running the mqsistop command before you start the migrated integration node. For more information, see mqsistop command.
  5. Optional: If you plan to run the migrated integration node on the same system as the existing integration node, and with the same name as the existing integration node, delete the existing integration node by running the mqsideletebroker command before you start the migrated integration node. For more information, see mqsideletebroker command.
  6. Start the migrated integration node by using the mqsistart command. For more information, see mqsistart command.
  7. After the mqsistart command completes, check the syslog, or the Windows Event log to confirm that the integration node started successfully with no errors.

Performing extract migration of a managed integration server

Procedure

  1. On your source system, run the mqsibackupbroker command, specifying the name of the integration node that is associated with the integration server that you intend to migrate to IBM App Connect Enterprise 13.0.
  2. Transfer the backup file that is created by the mqsibackupbroker command to an appropriate location on your Version 13.0 system.
  3. Run the ibmint extract server command on your Version 13.0 system.
    On the ibmint extract server, you must specify the following values:
    • The name of the backup file that is created when you run the mqsibackupbroker command on the source system.
    • The name of the integration node with which the integration server that you are migrating is associated.
    • The name of the integration server that you are migrating.
    • The work directory to which the integration server components are to be extracted.
    You can also specify one or more optional parameters on the ibmint extract server command. For more information, see ibmint extract server command.
  4. When the ibmint extract server command completes successfully, start the integration server on your Version 13.0 system by using the IntegrationServer command.

What to do next

For more information about tasks that you might want to complete after migration, see Performing post-migration tasks.