Optional: Customizing Business Automation Studio properties

You can make Liberty and 100custom configuration changes to Business Automation Studio deployment. The settings can impact the designers and playback engines running inside the deployment, such as Application Designer, Workflow Authoring, and the playback server.

About this task

This task provides the generic methods for modifying Liberty and 100Custom configuration settings for Business Automation Studio deployment. The usage is generally paired with other documentation pages which might describe a specific Liberty or 100Custom configuration setting that needs to be modified.

You can customize the following properties:
  • bastudio_configuration.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.
  • bastudio_configuration.custom_secret_name to customize the Liberty server if the customization contains sensitive information
  • bastudio_configuration.bastudio_custom_xml to customize Workflow Authoring
Important: Put your configuration settings either in bastudio_configuration.custom_xml or in bastudio_configuration.custom_secret_name. Don't specify the same configuration value in both places.

Procedure

  1. To customize Liberty properties:
    • To use XML, add a plain XML snippet in the custom resource file in the bastudio_configuration.custom_xml parameter. The settings will be merged into the Liberty settings for the component.
      The XML snippet must be in the <server> element, as shown in the following example.
      custom_xml: |+
        <server>
          <!-- custom properties here -->
        </server>
      
      For more information about Liberty customization, see Administering Liberty manually.
    • To use a secret, 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-secret-name --from-file=sensitiveCustom.xml=./custom.xml
      3. Set the bastudio_configuration.custom_secret_name parameter to the secret name in the custom resource file.
  2. You can also modify Workflow configuration properties in a 100Custom.xml file. To modify 100Custom.xml configuration properties, add an XML snippet in the custom resource file in the bastudio_configuration.bastudio_custom_xml property similar to the following example. For details about creating a valid 100Custom.xml structure, see Creating a 100Custom.xml configuration file.
    bastudio_custom_xml: |+
        <properties>
                ……
                <common>
      	       <!-- General IBM Business Automation Workflow settings -->
                </common>
                ……
        </properties>
  3. After you modify the custom resource file, you must update your deployment to have it take effect. Follow the instructions in Updating script-installed deployments.
    To verify the 100Custom.xml settings, check for the files on the server pods. For more information, see Location of 100Custom configuration files.