Configuration types

You can create configuration objects of various types, which can be used to configure integration servers, integration runtimes, the App Connect Dashboard, or App Connect Designer.


Configuration types for integration servers and integration runtimes

Integration servers and integration runtimes require two types of resources to run and provide an integration that you develop: one or more BAR files that contain development resources, and configuration files for setting up the integration server or integration runtime.

The BAR file contains authored integration artifacts that include message flows, message sets, ESQL files, Java™ code, stylesheets, and maps. The configuration files can define any environment-specific settings, or contain secrets or data that cannot be checked into a source control system. Separating the BAR file artifacts from the configuration files in this way eliminates the need to edit a BAR file before you deploy it to different environments such as development and production. When you create an integration server or integration runtime to run the integration that is packaged in the BAR file, you can select or create your preferred configurations to apply to the BAR file.

Before you deploy your integration to an environment, you can customize the BAR file to configure properties or requirements that define how the integration server or integration runtime should run and how it should connect to external systems. You configure such customizations by creating configuration objects that can be applied to one or more integration servers or integration runtimes, and which are shared by all users with access to the namespace where the configuration objects and integration servers or integration runtimes are deployed. The defined configuration objects are stored in files that will be processed before your deployed integration server or integration runtime starts.

Note: Although the same configuration files are used in a containerized environment and in App Connect Enterprise on premises, there is a difference in how the files are set up on the integration server or integration runtime. In App Connect Enterprise, users need to create and add configuration objects to the file system. When working in a containerized environment, configuration objects, which contain the configuration files, must be created in the namespace by users who can then associate the configuration objects to an integration server or integration runtime. When the integration server or integration runtime container starts, it pulls these configuration files from the Red Hat® OpenShift® or Kubernetes cluster, and configures the file system with the correct files. The integration server or integration runtime container also executes some commands to set up secrets that the integrations use. The running integration server or integration runtime then uses these files in the same way as when they are configured directly by a user that adds the files to the file system.

Configuration types for App Connect Dashboard and App Connect Designer

You can use a bucket in an object storage service as an alternative location for storing the following artifacts:

  • BAR files that are uploaded or imported to your App Connect Dashboard instance
  • The AI model for the Mapping Assist incremental learning feature that is available in App Connect Designer

A configuration of type s3Configuration is required to store the credentials for connecting to the bucket that is used with the Dashboard or Designer instance.

Learn more about the configuration types

Use the following links to learn about each configuration type and how to create its required configuration file: