Migrate IBM App Connect Enterprise configuration from an on-premises to a containerized environment
This migration scenario describes how to migrate configuration for integration servers from an IBM App Connect Enterprise on-premises system to an IBM Cloud Pak for Integration containerized environment in which the IBM App Connect Operator is installed.
Alongside a BAR file, an integration server might require a number of configuration files for its setup. The configuration files can define environment-specific settings, or contain secrets or data that should not be checked into a source control system. This method of separating BAR file artifacts from configuration files eliminates the need to edit a BAR file before its deployment to different environments such as development and production.
An integration server that you deploy to a containerized environment by using the IBM App Connect Operator uses the same configuration files that are used in App Connect Enterprise on premises, but there is a difference in how the files are set up. In an on-premises installation, you are required to create and add configuration objects to the file system, but in a containerized environment, you create configuration objects (which contain the configuration files) and then associate them with an integration server. When the integration server container starts, it pulls these configuration files from the cluster and configures the file system with the correct files. The integration server container also runs some commands to set up secrets that the integrations use. The resulting running integration server then uses these files in the same way as an on-premises installation in which files are added directly to the file system.
Migrating configuration object types
The App Connect integration component in IBM Cloud Pak for Integration supports a number of configuration object types that represent the different configurations that can be applied to integration servers in an IBM App Connect Enterprise on-premises system.
In the containerized environment, you can create configuration objects from an App Connect Dashboard instance, or by using the Red Hat® OpenShift® web console or CLI. When you create an integration server from the App Connect Dashboard, you can select or create your preferred configurations to associate with your integration. When you create an integration server by using the Red Hat OpenShift web console or CLI, you need to first create the configuration objects in the web console or CLI, and then reference these objects in the spec.configurations parameter.
For more information about creating configuration objects and integration servers that reference configuration objects, see:
The following examples identify some configuration object types that you might currently be using on your on-premises environment, and describe how these configuration objects could be migrated for use in a containerized environment.