server.conf.yaml configuration

In an on-premises installation, the server.conf.yaml file is created in the root of the specified work directory: workDirectory/server.conf.yaml. If you use any commands that modify the integration server, an overrides subdirectory is created under the working directory for the integration server. This overrides subdirectory contains an additional server.conf.yaml configuration file (for example, workDirectory/overrides/server.conf.yaml), which contains property values that are set by commands. The values of properties in this overrides/server.conf.yaml file override any values that you have set in the integration server's server.conf.yaml file at /server.conf.yaml.

When you create an integration server in a containerized environment, you get a predefined set of values for server.conf.yaml. Using the server.conf.yaml configuration type, you can override these values with your own settings from your workDirectory/server.conf.yaml or workDirectory/overrides/server.conf.yaml files by combining them into a single server.conf.yaml file. The file needs to contain only the settings that you want to set and does not need to contain everything in workDirectory/server.conf.yaml.

You can provide only one server.conf.yaml configuration type per integration server, although multiple integration servers can reuse the same configuration.

• If you are creating the configuration object by using the Red Hat® OpenShift® web console or CLI, you will need to run a Base64 encoder against your server.conf.yaml file and use the output as the value of the spec.data parameter in the configuration custom resource. For more information, see Creating a configuration object.
• If you are using the App Connect Dashboard, you can create the configuration object from the Configuration page or while creating the integration server, as described in Configuration types for integration servers.

For more information about this configuration type, see server.conf.yaml type.