ibmint extract node command

• Windows
• Linux®
• AIX®
• IBM z/OS® Container Extensions (zCX). Run this command by modifying and submitting the supplied JCL or by using an IBM z/OS console command.

Extract configuration and resources for integration nodes to IBM App Connect Enterprise 13.0 from IBM Integration Bus 10.0, IBM App Connect Enterprise 11.0, or IBM App Connect Enterprise 12.0.

You must have an installation of the product at both target and source versions, with the required component code installed, and you must run this command from the later version of the product.

You can use this command to extract configuration and resources from your IBM Integration Bus 10.0, IBM App Connect Enterprise 11.0, or IBM App Connect Enterprise 12.0 system that is running on any previously supported platform to your IBM App Connect Enterprise 13.0 system that is running on Windows, Linux, or AIX.

Before you start to extract configuration and resources, stop the integration server and all active debug sessions in the IBM App Connect Enterprise Toolkit. You cannot extract message flows that are being debugged.

You can use this command to extract components to an integration node. Extracting the configuration and resources from an integration node also extracts the configuration and resources of all the integration servers that are associated with the integration node. Ensure that you run the mqsibackupbroker command on the source system and then transfer the backup file that is created to the computer to which you are extracting the configuration and resources.

If the integration node is then deployed or configured to use IBM App Connect Enterprise 13.0 features, it can no longer be run with IBM Integration Bus 10.0, IBM App Connect Enterprise 11.0, or IBM App Connect Enterprise 12.0.

--input-integration-node input_integration_node_name

(Required) The name of the integration node to extract from the backup file.

If you are extracting configuration and resources from an integration server only, you must also specify the name of the integration node with which the integration server is associated.

--output-integration-node output_integration_node_name

(Required) The name of the integration node to which the extracted configuration and resources will be written. If the integration node already exists, the ibmint extract node command fails unless you specify the --overwrite-existing parameter.

If you are extracting configuration and resources from an integration server only, you must also specify the name of the integration node with which the integration server is associated.

--input-integration-server integration_server_name

(Optional) The name in the backup file of the integration server from which you are extracting configuration and resources.

--backup-file backup_file_name

(Required) The file path of the backup file that is created by running the mqsibackupbroker command on the source system prior to running the ibmint extract node on the target system.

--work-path workpath_directory_path

(Optional) The directory into which internal data, such as installation logs, component details, and trace output is written for the output integration node.

--shared-work-path shared_workpath_directory_path

(Optional) The directory in which registry and configuration data is shared between multiple instances of the target integration node.

--overwrite-existing

(Optional) Deletes the integration node if it already exists on your IBM App Connect Enterprise 13.0 system, before the ibmint extract node command extracts the configuration and resources from the input system and creates a new integration node with the same name as the one that was deleted.

--service-user-id userid

(Optional) The user ID that is used when creating the Windows service definition. Defaults to 'LocalSystem'. This parameter only applies on Windows platforms.

--service-password password

(Optional) The password that is used when creating the Windows service definition. Defaults to a blank string because a password is not required by the default user ID of 'LocalSystem'. This parameter applies only on Windows platforms.

--prompt

(Optional) Use a prompt to enter the service password without displaying it. This parameter applies only on Windows platforms.

--input-platform platform-type

(Optional) The platform type where the backup was taken. This parameter is required only if the auto-detection fails. You can specify one of the following values: WinX64, LinuxX64, AIXPPC64, zOS, Linuxz64, LinuxPPC64, LinuxPPCLE64, SolarisSparc64, SolarisX64, HPUXIA64, MacOSX.

--input-platform-ccsid ccsid

(Optional) The default CCSID of the platform where the backup was taken. This parameter is required only if the auto-detection fails.

--do-not-rename-record-replay-source-topics

(Optional) This parameter prevents the updating of topic strings to reference the new integration node or server. By default, when extracting DataCaptureSource configurable service definitions and creating record and replay source configuration, the topic strings for any topics that reference the source integration node (and source integration server when extracting a single server) are updated to reference the name of the new integration node or integration server. This parameter prevents the update from taking place.

--ignore-compiled-resource-types resourceTypes

(Optional) This parameter specifies a comma-separated list of compiled resource types that are ignored when they are found in the backup, so they are not extracted. You can specify any of the following resource types: ALL, MAP, BIR, and DPIF. This option is not supported with backups from IBM Integration Bus 10.0 or earlier, because compiled resources in backups from these versions are always ignored.

--integration-node-domain-group domainGroup

(Optional) The Windows domain group that is used to secure files in the shared workpath of a multi-instance integration node. This parameter is used only in conjunction with the --shared-workpath parameter, and applies only on Windows platforms.

--java-version javaVersion

(Optional) Override the major version of Java that will be used by any integration servers. Valid values are 17 and 8.

--trace traceFileName

(Optional) Send verbose internal trace to the specified file.