Bookshelf Home | Contents | Index | PDF |
Siebel Business Process Framework: Workflow Guide > Administering a Workflow Process > Diagnosing a Workflow Process That Has Failed > Diagnosing a Workflow Process That Has Failed in a Production EnvironmentThis topic describes how to diagnose problems that occur in the production environment. For more information about some of the tools described in this topic, see Monitoring a Workflow Process. Using Tracing to Diagnose a Workflow ProcessYou can use tracing to diagnose a workflow process that has failed. To use tracing to diagnose a workflow process
For details on how to turn on tracing, see Setting Monitoring Levels for Tracing and the Event Log. Using Instance Monitoring to Diagnose a Workflow ProcessYou can use instance monitoring to diagnose a workflow process that has failed. To use instance monitoring to diagnose a workflow process
Using the Business Service Simulator to Diagnose a Workflow ProcessYou can use the business service simulator to diagnose a workflow process that has failed. To use the business service simulator to diagnose a workflow process
TIP: To increase the data that is available to you for troubleshooting, you can set the monitoring level to 4-Debug, as described in Step 3, start the workflow process with the Business Service Simulator, and then view information about the workflow process in the Workflow Instance Monitor views. For more information, see Business Service Simulator and Removing a Workflow Process from the Run-Time Environment. Avoiding Excessive Records in the S_WF_PROP_VAL TableThe S_WF_PROP_VAL table stores values of process properties for a workflow process. When a workflow process runs, Siebel CRM creates records in the S_WF_PROP_VAL table along with a new S_WF_STEP_INST record. The S_WF_PROP_VAL table might become very large over time because a workflow process typically contains five or more process properties. Siebel CRM might add five records to the S_WF_PROP_VAL table for each workflow process instance. If you enable Persistence on a large number of workflow processes, then the S_WF_PROP_VAL table might become very large. To avoid this situation, you can disable persistence on your custom workflow processes. To avoid excessive records in the S_WF_PROP_VAL table
How to Get Help with an Error of a Workflow ProcessTo get help with a workflow process error, you can create a service request on My Oracle Support. Alternatively, you can phone Global Customer Support directly to create a service request or get a status update on your current service request. Support phone numbers are listed on My Oracle Support. Be prepared to do the following:
|
Siebel Business Process Framework: Workflow Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |