Which step is required to enable a trace specification for Business Automation Workflow?

To enable a custom trace specification in a containerized IBM Business Automation Workflow (BAW) environment, the administrator must first define the trace settings in a logging.xml file. This file is then packaged into a Kubernetes ConfigMap. The ConfigMap acts as a vehicle to inject this custom configuration into the BAW pods. Finally, the Custom Resource (CR) is updated to reference this ConfigMap, triggering the operator to apply the changes. Creating the ConfigMap is the pivotal step that makes the trace configuration a manageable and deployable resource within the Kubernetes cluster.

A. Updating the Custom Resource YAML is a necessary step to apply the configuration, but it only references the ConfigMap. The ConfigMap containing the trace specification must be created first.

B. Creating a logging.xml file is a prerequisite for defining the trace string, but this file is not used directly by the pods; it must be embedded within a ConfigMap.

D. Restarting the Business Automation Workflow pods is a consequence of applying the configuration change via the CR, not the direct administrative action taken to enable the trace.

1. IBM. (2022). Configuring logging for Business Automation Workflow. IBM Cloud Pak for Business Automation v21.0.3 Documentation. Retrieved from https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/21.0.3?topic=containers-configuring-logging-business-automation-workflow.

Reference Details: The section "Configuring logging for Business Automation Workflow" explicitly states the procedure: "To enable tracing in Business Automation Workflow

you create a custom logging.xml file and then use it to create a configmap. You then apply the configmap to your Business Automation Workflow deployment by updating the custom resource (CR)." This highlights that creating the ConfigMap is a required

central step.