Workflows in Siebel can be run in the below ways:
- Server Component: Workflow Policy, Repeating component request, srvrmgr, submitting a task for the component, eScript (submitting request for the component), Runtime events (submitting request for the component). In all the above ways, the request for the Workflow process execution is done by the Workflow Process Manager component (WfProcMgr) or the Workflow Process Batch Manager (WfProcBatchMgr) component.
- Application Object Manager: Runtime event, Scripting and simulation in the Thin Client.
- Client: Runtime event, Scripting and simulation in the mobile web Client or the Dedicated Client.
Tracing on Server:
Increase the Log level for the below events for the Workflow Process Manager component (WfProcMgr) or the Workflow Process Batch Manager (WfProcBatchMgr) component.
Event Type | Log Level |
Task Configuration | 5 |
Object Manager SQL Log | 5 |
Workflow Definition Loading | 5 |
Workflow Engine Invoked | 5 |
Workflow Process Execution | 5 |
Workflow Step Execution | 5 |
Object Manager Business Component Operation and SetErrorMsg Log | 5 |
Object Manager Extension Language SetErrorMsg Log | 5 |
Object Manager Business Service Operation and SetErrorMsg Log | 5 |
SQL Tracing | 5 |
The changes will take effect immediately and does not need a server bounce.The Workflow Process Batch Manager log file (WfProcBatchMgr_xxx.log) and the Workflow Process Manager log file (WfProcMgr_xxx.log) are located in the SIEBSRVR_ROOT\log directory.
Tracing on the Application Object Manager:
Increase the log level for the below for the Application Object Manager component like the Callcenter Object Manager.
Event Type | Log Level |
Task Configuration | 5 |
Object Manager SQL Log | 5 |
Workflow Definition Loading | 5 |
Workflow Engine Invoked | 5 |
Workflow Process Execution | 5 |
Workflow Step Execution | 5 |
Object Manager Business Component Operation and SetErrorMsg Log | 5 |
Object Manager Extension Language SetErrorMsg Log | 5 |
Object Manager Business Service Operation and SetErrorMsg Log | 5 |
SQL Tracing | 5 |
The changes do not need a server bounce and the log for the application Object manager is generated at SIEBSRVR_ROOT\log directory.
Tracing on the Client:
Set the below environment variable and the siebel.log will be generated in <ClientRootDir>\log directory
SIEBEL_LOG_EVENTS = 5
