Use the mqsimigratecomponents command to migrate a component from one version of the product to another version on the same computer.
Migrate components to IBM® Integration Bus Version 10.0 from a previous version:
You must run this command from the later version of the product, regardless of whether it is the source version or the target version.
You must have an installation of the product at both target and source versions, with the required component code installed, to issue this command successfully.
Before you start migration, stop the integration node and all active debug sessions in the IBM Integration Toolkit. You cannot migrate message flows that are being debugged.
If you specified a data source user ID and password on the mqsicreatebroker command for the integration node that you are migrating, the values of these parameters are also migrated and saved in the format that is used by the mqsisetdbparms command. The values are used by the integration node to access databases for which you did not set alternative values by using the mqsisetdbparms command. After migration, if you want to change the user IDs or passwords that the integration node uses to access databases, you can use only the mqsisetdbparms command.
If you update the user ID and password values, and you migrate the integration node back to the previous version, the new values are also migrated back to the original integration node.
.-| Move |---. >>-mqsimigratecomponents--+-| Check |--+----ComponentName-------> +-| Undo |---+ '-| Verify |-' >--+-----+----------------------------------------------------->< '- -q-' Check |-- -c --+--------------------+--+--------------------+---------| '- -s--SourceVersion-' '- -t--TargetVersion-' Move |--+--------------------+--+--------------------+---------------| '- -s--SourceVersion-' '- -t--TargetVersion-' Undo |-- -u-- -s--SourceVersion-- -t--TargetVersion------------------| Verify |-- -v--+--------------------+----------------------------------| '- -t--TargetVersion-'
You can check a running component. The check does not affect the component, apart from a slight degradation of performance.
The check command either succeeds or fails, and prints a message about whether the migration will succeed, but no modifications are made during the process.
The -c and -v parameters are mutually exclusive. Additionally, if you specify either of these parameters, you cannot specify any other parameter when you run this command.
The -c and -v parameters are mutually exclusive. Additionally, if you specify either of these parameters, you cannot specify any other parameter when you run this command.
(Optional) Print fewer status messages during the operation.
(Required) The name of the component to migrate.
The mqsimigratecomponents command updates your registry, file system, and WebSphere MQ definitions.
This command can produce many possible responses, depending on the results of the various operations. This command differs from other commands in the way it produces messages: they are displayed when they are generated, rather than being reported in a batch at the end of the program.
The following example shows a migration from Version 10.0 back to Version 8.0:
mqsimigratecomponents MYBROKER -t 8.0.0.2