Optional: Customizing runtime server properties

You can add custom configuration for the Business Automation Workflow runtime configuration, such as modifying the Workflow Server connection properties.

About this task

In a Business Automation Workflow on-premises installation, you customize the server configuration using the WebSphere® administrative console and the 100custom.xml file. In containers, you can customize the following properties:
  • baw_configuration[x].liberty_custom_xml to customize the Liberty server. If the customization does not contain sensitive information, you can use this property to put the customization directly into the custom resource.
  • baw_configuration[x].custom_xml_secret_name to customize the Liberty server if the customization contains sensitive information
  • baw_configuration[x].lombardi_custom_xml_secret_name to customize the Workflow Server

Procedure

  1. To customize baw_configuration[x].liberty_custom_xml, add a plain XML snippet in the custom resource configuration file.
    The following example shows what your input might look like:
    liberty_custom_xml: |+
  <server>
    <!-- custom properties here -->
  </server>
  2. To customize baw_configuration[x].custom_xml_secret_name, do the following steps.
    1. Create a customized XML file, such as custom.xml.
    2. Create a customized secret using the following command: 
      kubectl create secret generic custom-xml-secret-name --from-file=sensitiveCustomConfig=./custom.xml
    3. Set the baw_configuration[x].custom_xml_secret_name property to the secret name in the custom resource file.
  3. To customize baw_configuration[x].lombardi_custom_xml_secret_name, do the following steps.
    1. Create a customized XML file, such as 100custom.xml.
    2. Create a customized secret using the following command: 
      kubectl create secret generic custom-xml-secret-name --from-file=sensitiveCustomConfig=./100custom.xml
    3. Set the baw_configuration[x].lombardi_custom_xml_secret_name property to the secret name in the custom resource file.
  4. After you modify the custom resource file, you must update your deployment to have it take effect.
    Follow the instructions in Updating deployments.