server.conf.yaml type
Use the server.conf.yaml type to create
configurations that use the server.conf.yaml file to configure the operation of
the integration runtime and its associated resources.
Summary of key details for the configuration type
| File name or type | Contains secrets | Path extracted/imported to | Maximum allowed per integration runtime |
|---|---|---|---|
| server.conf.yaml | No | /home/aceuser/ace-server/overrides/server.conf.yaml | 1 |
Creating the file for a configuration object of type
server.conf.yaml
The server.conf.yaml type requires a server.conf.yaml file
that the integration runtime can use.
The file is placed in the overrides directory for the running runtime, so any default values that are set for the integration runtime container are overridden by the values that are set in this file. The server.conf.yaml file contents are identical to the contents of the file that is used in IBM® App Connect Enterprise software and no enforced limit exists on what properties can be set.
In the server.conf.yaml file, you can use the Log section to configure logging for BIP messages. For an independent integration server in App Connect Enterprise, the eventLog property, which controls outputting BIP messages to event log files, uses a default location of $workdir/log, where $workdir is the integration server work directory. In the server.conf.yaml file, this default location is depicted as [iib.system-work-dir]/log, as shown in the following example.
Log:
eventLog: '[iib.system-work-dir]/log/[iib.system-node-label].[iib.system-server-label].events.txt' # Control writing
BIP messages to file. Set to '' to disable, default is as shown.In App Connect Enterprise, you can set the eventLog
property to any log directory of your choice. However, if you are using a
server.conf.yaml file to create a configuration object in your containerized
environment, and you want to use the eventLog property to set a log directory,
only the following substitutions can be specified as the starting
location:
[iib.system-work-dir](defaultstarting
location that resolves to /home/aceuser/ace-server in the container file system)[iib.system-node-label][iib.system-server-label][iib.system-common-log-dir]
Only one server.conf.yaml file can be specified per integration runtime.
You can obtain a copy of the server.conf.yaml configuration file from the /home/aceuser/ace-server directory in the pod, or from the local directory installDir/server/sample/configuration where IBM App Connect Enterprise Toolkit is installed. For example, on Windows, the path is C:\Program Files\IBM\ACE\12.0.7.0\server\sample\configuration. A sample file is provided in the attached .zip archive for reference (server.conf.zip).
For more information about how to modify the server.conf.yaml file, see Configuring an integration server by modifying the server.conf.yaml file.
After you create the file, you can use it to create a configuration object as described in Configuration reference: Creating an instance from the Red Hat OpenShift web console and Creating an instance from the Red Hat OpenShift or Kubernetes CLI.