Configuring WebSphere Application Server logging for Case Builder and the Business Automation Workflow API application

Draft comment:
This topic is shared by BAW, CP4BA. Last updated on 2025-03-13 12:15

Case Builder and the workflow API application log information to the WebSphere Application Server main log and trace log. You can redirect the WebSphere Application Server log to record information for these components in the Business Automation Workflow log location. You can also change the logging levels in WebSphere Application Server.

About this task

You can use the logging settings in the WebSphere Application Server administrative console to redirect the logs to the Business Automation Workflow log location.

To access the settings in the administrative console, click Troubleshooting > Logs and trace, and select your server name.

Procedure

To configure logging options for Case Builder and the Business Automation Workflow API application:

Redirect the log:
1. Click Diagnostic Trace and click the Runtime tab.
2. In the File Name field, change the value to installation_path/IBM/CaseManagement/logs.
Redirect the main application server logs:
1. Click JVM logs and click the Runtime tab.
2. In the File Name fields, change the path before the /SystemOut.log and /SystemErr.log file names to the Business Automation Workflow log location.
  For example, use installation_path/IBM/CaseManagement/logs/SystemOut.log and installation_path/IBM/CaseManagement/logs/SystemErr.log.
Change the logging level:
1. From the WebSphere Application Server administrative console, click Logging and Tracing > server > Change log detail levels.
2. Change the logging levels as needed.
Case Builder components have the Message and Trace Levels set to info by default. Reset these components to audit or warning to prevent filling log files too quickly. Under the com.ibm.acm.* component, select the com.ibm.acm.sold.* node to set the Message and Trace Levels settings for all the Case Builder components.