Migrating an integration node with configurable services

Migrate an IBM® Integration Bus Version 10.0 or Version 9.0 integration node that has configurable services for external resources, and a specific user ID and password that is associated with one or more resources by using the mqsisetdbparms command.

About this task

In this scenario, a simple flow that contains a FileInput node and a FileOutput node is deployed to an IBM Integration Bus Version 10.0 or Version 9.0 integration server, then to an integration node. An FtpServer configurable server 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.

The following steps describe how to migrate the flow to IBM App Connect Enterprise Version 11.0.

Procedure

  1. Back up the IBM Integration Bus Version 10.0 or Version 9.0 integration node by using the mqsibackupbroker command. 
    mqsibackupbroker IntegrationNode -d  directory
    A file with a name in the format intNodeName_yyMMdd_HHmmss.zip is created in the specified directory.
  2. In IBM App Connect Enterprise Version 11.0, use the mqsicreatebroker command to create a new integration node.
    mqsicreatebroker IntegrationNode
  3. Start the integration node by running the command mqsistart IntegrationNode.
  4. Create the directory structure servers\IntegrationServer under the integration node work path ($MQSI_WORKPATH).
    For example, on Windows: C:\ProgramData\IBM\MQSI\components\IntegrationNode\servers\IntegrationServer.
  5. Stop the integration node by running the command mqsistop IntegrationNode.
  6. Use the mqsiextractcomponents command to migrate the IBM Integration Bus Version 10.0 or Version 9.0 integration server and resources to IBM App Connect Enterprise Version 11.0.

    All deployed resources are migrated under the /run directory: C:\ProgramData\IBM\MQSI\components\IntegrationNode\servers\IntegrationServer\run.

    During migration, the IBM Integration Bus Version 10.0 or Version 9.0 configurable services are converted to policies in IBM App Connect Enterprise Version 11.0. The policy project is in the /run subfolder in the work directory. No value was specified for the policy_project_name; therefore, policies are created in a policy project called DefaultPolicies. For example, if the FTPServer configurable service name is ftpbroker, a policy file with name ftpbroker.policyxml is created under the run\DefaultPolicies folder in the work path.

  7. Start the integration node by running the command mqsistart V11BRK.
    You might see the following error message in the event viewer:
    File node "File Output" in message flow "FileInOutFlow". The remote user identifier supplied as "myftp" is invalid.
The user identifier supplied by a securityIdentity is not valid. Either the user identifier is missing, or no securityIdentity definition exists, or the securityIdentity registry information could not be read due to a permissions problem. FTP processing for this node has been disabled.
Ensure that the securityIdentity is correctly defined using the mqsisetdbparms command.
    Currently, the mqsiextractcomponents command does not migrate the credentials that are set by using the mqsisetdbparms command in IBM Integration Bus Version 10.0 or Version 9.0. Therefore, you need to set the security identity and other credentials by running the mqsisetdbparms again in IBM App Connect Enterprise Version 11.0: 
    mqsisetdbparms V11BRK -n ftp::myftp -u user -p password
  8. Restart the IBM App Connect Enterprise Version 11.0 integration node by running the mqsistop command, followed by the mqsistart command.