Extract migration overview
You can use the ibmint extract server and ibmint extract node commands to migrate the configuration and resources of integration servers and integration nodes from your source system to your IBM® App Connect Enterprise 13.0 system. The commands extract the configuration and resources from your source system and re-create them in a directory structure on your target system. You can extract the configuration and resources from an integration node, including the configuration and resources from all of the integration servers that are associated with the integration node, or from individual integration servers on your source system.
The following information describes the folder structure that is created when you use extract migration on an integration node or an integration server.
Extract migration of an integration node
The extract migration of the configuration of an integration server or integration node from an earlier version results in the re-creation of the integration server or integration node on your IBM App Connect Enterprise 13.0 system. A node folder is created in the installation directory, or in the directory in which you have your registry. The resources that comprise the integration node configuration on your source system are put into the node folder. The configuration of all the integration servers that are associated with the integration node is also extracted, resulting in the re-creation of these integration servers on your Version 13.0 system. A server sub-folder is created in the node folder for each integration server. The resources that comprise each integration server configuration on your source system are put into the corresponding server sub-folder.
| Folder | Sub-folder | Sub-folder | Sub-folder | Contents/description |
|---|---|---|---|---|
| <node name> | node.conf.yaml file. This file contains the settings for your migrated integration node. You can override the settings in the node.conf.yaml file by using the mqsichangeproperties command. | |||
| servers | Sub-folders for every integration server that is server associated with the integration node. One sub-folder exists for each integration server. | |||
| <server name> | Sub-folders containing the integration server configuration and resources. The name of the sub-folder is the same as the name of the integration server. | |||
| run | Deployed resources. | |||
| overrides | server.conf.yaml file. This file contains the settings for the integration server. You can override the settings in the server.conf.yaml file by using the mqsichangeproperties command. | |||
| policies | Sub-folders for every policy that is created from a configurable service on the integration node on the source system. | |||
| NodePolicies | ||||
| policy_name.policy.xml | One policy file per migrated configurable service. The file contains the policy information. |
Extraction of configuration and resources of an integration server
The extract migration of the configuration of an integration server from an earlier version results in the re-creation of an independent integration server on your IBM App Connect Enterprise 13.0 system. You might want to migrate an integration server in this way if you are operating in a container-based environment. The resources that comprise the integration server configuration are put into a work directory on your Version 13.0 system. You specify the work directory when you use the ibmint extract server command.
| Folder | Sub-folder | Contents/description |
|---|---|---|
| <work_directory_name> | server.conf.yaml file. This file contains the settings for your migrated integration server. You can override the settings in the server.conf.yaml file by using the mqsichangeproperties command. | |
| run | Deployed resources, including policy projects, libraries, and applications. | |
| overrides | server.conf.yaml file. This file exists if you dynamically override settings in the integration server server.conf.yaml by using the mqsichangeproperties command. | |
| log | Files containing event log and syslog entries. By default, file names are of the format integration_server.integration_server_name.entries.txt.n where n is an integer in the range 1 through 9. When the integration server generates log entries, the most recent log data is held in a file that does not have the n suffix. As the data ages, it is held in files with the n suffix where the value of n increments with the age of the log data: the oldest data is held in the file that is suffixed 9. The files fill in an incremental fashion; when one file becomes full, entries are written to the next consecutive file. | |
| config | Files containing other configuration information such as security configuration. |