Siebel CRM – Workflow Debugging through Logs.

When we talk about Siebel, I think Workflows are the most common term that we come across after Object Manager. We can achive really complex functionality through worklfows but what it means is that debugging them is equally complex. We generally test workflows through Simulation but if we were debug workflows in real time it can be quite painful and time consuming.

A simple method to debug workflow is to increase the log level for Workflow Process Manager (WPM) component. But if somebody has ever tried that he can vouch that it can be quite a headache to go through that log (believe me it is a lot and it can go up in MB’s even if the workflow is of moderate complexity). And what’s more is that most of the information that is contained in that log is useless and not realted to workflow functionality.

So here in this article I am going to present a pretty simple technique which can help you to get just the right amount of information that you need to debug a workflow.
Instead of increasing the log level of complete WPM component if you just increase the log level of just selective sub-components that should do the trick. I will list down the Sub-Components that you need to increase the log level to get just the appropirate information that you need.

  • Workflow Definition Loading
  • Workflow Engine Invoked
  • Workflow Process Execution
  • Workflow Step Execution
  • SQL Tracing

Just increase the log level of the above said components from 1 to 4 and you are done !!!!!
To get logs from dedicated client you need set the Environmental Variable on your system. To understand the process of doing that Please go through my Old Post where I have explained about siebel logs.

Hope this post has helped you.
If the answer is “YES”!! Please leave your comments and visit again.

7 Responses to Siebel CRM – Workflow Debugging through Logs.

  1. Workflows are complicated and as neel said debugging thru logs is tedious and most of the timethe siebel logs contains generic erros which are harmless in nature.
    Another way of monitoring the workflows is increasing the monitoring level in the UI.
    Go to Administrator-Business Process – Workflow Deployment and query for the worflow which needs to be monitored and in the bottom applet of the queired wkfl, there is a column called “Monitoring Level” change it to max 4(debug).

    This captures the process as it goes thru ever step and makes our live easy 🙂 in fixing the issue.

    Another issue I found is with failure to execute a schedule job setup (Under Administrator-Server Management-JOBS)with error (SBL-OMS-00203: Error (null) invoking method “(null)” for Business Service “(null)”) – is in regards to TYPO for the Value in the “JOB PARAMETERS” – All care should be taken while typing in the value.
    IF youtry to look up the erro in the siebel supportweb, it will take you thru everything and still wont tell you what the issue is. – frustrating.

    cheers
    dpfromcanberra

  2. Workflows are complicated and as neel said debugging thru logs is tedious and most of the timethe siebel logs contains generic erros which are harmless in nature.Another way of monitoring the workflows is increasing the monitoring level in the UI.Go to Administrator-Business Process – Workflow Deployment and query for the worflow which needs to be monitored and in the bottom applet of the queired wkfl, there is a column called “Monitoring Level” change it to max 4(debug).This captures the process as it goes thru ever step and makes our live easy 🙂 in fixing the issue.Another issue I found is with failure to execute a schedule job setup (Under Administrator-Server Management-JOBS)with error (SBL-OMS-00203: Error (null) invoking method “(null)” for Business Service “(null)”) – is in regards to TYPO for the Value in the “JOB PARAMETERS” – All care should be taken while typing in the value.IF youtry to look up the erro in the siebel supportweb, it will take you thru everything and still wont tell you what the issue is. – frustrating.cheersdpfromcanberra


  3. Another way of monitoring the workflows is increasing the monitoring level in the UI.
    Go to Administrator-Business Process – Workflow Deployment and query for the worflow which needs to be monitored and in the bottom applet of the queired wkfl, there is a column called “Monitoring Level” change it to max 4(debug).


    That is great information. I have deployed lot of workflows but never payed attention to that coloumn. That will surely make our life easy 🙂

    Thanks for sharing!!!
    and may I know your name please.

  4. Another way of monitoring the workflows is increasing the monitoring level in the UI.Go to Administrator-Business Process – Workflow Deployment and query for the worflow which needs to be monitored and in the bottom applet of the queired wkfl, there is a column called “Monitoring Level” change it to max 4(debug).That is great information. I have deployed lot of workflows but never payed attention to that coloumn. That will surely make our life easy :)Thanks for sharing!!!and may I know your name please.

Leave a Reply

Contribute