This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Enabling tracing for Business Process Choreographer

Edit online
You can configure trace settings for Business Process Choreographer to help diagnose problems with the processing of BPEL processes and human tasks.

Trace settings

Business Process Choreographer tracing uses the standard application server tracing mechanism. This must be enabled in the normal way.
You can specify the following trace settings for Business Process Choreographer.
Table 1. Trace settings for Business Process Choreographer
Trace string What is logged
com.ibm.bpe.* All available trace information for BPEL processes
com.ibm.bpe.basic.navigation.* Major navigation steps and state changes for BPEL processes
com.ibm.bpe.basic.api* Time and sequence of methods called by the Business Flow Manager API
com.ibm.task.* All available trace information for human tasks
com.ibm.task.basic.api* Time and sequence of methods called by the Human Task Manager API
com.ibm.task.basic.core* Major steps in the processing of human tasks, state changes, and calls to SPIs
com.ibm.ws.staffsupport.* All available trace information for the people directory providers
To get a complete set of trace information for Business Process Choreographer, specify the following trace settings:
com.ibm.bpe.*=all:com.ibm.task.*=all:com.ibm.ws.staffsupport.*=all

What to send to support

After enabling tracing, re-create your problem, then provide the following files:
  • The WebSphere® Application Server FFDC log, located in the ffdc folder
  • The following log files:
    • SystemOut.log
    • SystemErr.log
    • trace.log
    • For Linux operating systemFor UNIX operating systemOn Linux® and UNIX systems, these files are located in the profile_root/logs/server_name directory.
    • For Windows operating systemOn Windows platforms they are located in the profile_root\logs\server_name directory.

    If your problem scenario causes a lot of logging, backup files for the logs might be created with names, such as SystemOut_07.10.01_11.00.51.log. You can use the administrative console to change the number of backup files that are created and the size of the log files. It might be good to increase both of these values to ensure that you capture all of the data.