Migrating an integration node with configurable services

You can use the mqsiextractcomponents command to migrate an integration node from IBM® Integration Bus 10.0 to IBM App Connect Enterprise 12.0. This scenario involves an integration node with a configurable service and a security identity. The configurable service provides connection information for communications with an FTP Server. The security identity (created by using the mqsisetdbparms command) defines the user ID and password that are required when communicating with the FTP Server.

About this task

In this scenario, a simple flow containing a FileInput node and a FileOutput node is deployed to an IBM Integration Bus 10.0 integration server that is managed by the integration node. An FtpServer configurable service has been created by using the following command:

mqsicreateconfigurableservice MigrationNode -c FtpServer -o FtpServer01 
-n serverName,scanDelay,transferMode,connectionType,securityIdentity 
-v one.hursley.abc.com:123,20,Binary,ACTIVE,myftp

Screenshot that shows a message flow that contains a FileInput node and a FileOutput node.

Procedure

The following steps describe how to migrate the integration node to IBM App Connect Enterprise 12.0:

Back up the IBM Integration Bus 10.0 integration node by using the mqsibackupbroker command. For example:
```
mqsibackupbroker MigrationNode -d  C:\temp
```
where MigrationNode is the name of the integration node to be backed up.
A file with a name in the format MigrationNode_yyMMdd_HHmmss.zip is created in the specified directory, which in this example is C:\temp.
Use the mqsiextractcomponents command to migrate the IBM Integration Bus 10.0 integration node to IBM App Connect Enterprise 12.0.
For example:
```
mqsiextractcomponents --backup-file C:\temp\MigrationNode_220317_150351.zip 
--source-integration-node MigrationNode --target-integration-node MigrationNodeV12
```
In this example, the Version 10 integration node called MigrationNode is migrated to a Version 12 integration node called MigrationNodeV12. The deployed resources are migrated into the run directory of the integration server that is managed by the integration node. For example, if the original integration node (MigrationNode) contained a single integration server called MyServer, all the deployed resources are migrated into the run directory of the MyServer integration server on the target integration node (MigrationNodeV12):
```
C:\ProgramData\IBM\MQSI\components\MigrationNodeV12\servers\MyServer\run
```
During migration, the IBM Integration Bus 10.0 configurable services are converted to policies in IBM App Connect Enterprise 12.0. The policy project resides in the migrate_config_servs subfolder in the work directory. No value was specified for the policy_project_name as part of the mqsiextractcomponents command, so policies are created in a policy project called DefaultPolicies. In this example, the FTPServer configurable service was named FtpServer01, so a policy file called FtpServer01.policyxml is created under the run\DefaultPolicies folder in the work directory.
Start the integration node by running the mqsistart command:
```
mqsistart MigrationNodeV12
```