The Action Interval parameter of Workflow Monitor Agent is always controls, how the Action should be executed.
1) Just Navigate to Sitemap-> Administration->Server Configuration->Enterprises->Component Definitions->Choose Workflow Monitor Agent Component.
In the Component Parameters List choose Action Interval and check the default value is “3600” seconds (This is the default value to Action Interval Parameter).
2) Change the default value to 60. It means depending on the value of the Action Interval parameter for Workflow Monitor Agent, the action is taken.
3) Once Workflow Monitor Agent performs an action on the record in violation, an entry is logged into the S_ESCL_LOG table. If the same record comes into violation again within the Action Interval time, the Workflow Monitor Agent will not perform the action again on the same record. It will only remove the row from S_ESCL_REQ table. As a result, it is possible that Workflow Monitor Agent clears many records from the S_ESCL_REQ table for which no actions have been performed.
4) Setting the Action Interval = 0 is not recommended by Siebel Systems because the following behaviors have been observed to occur with this setting:
-> Actions performed for rows in S_ESCL_REQ without checking if conditions are met or not.
-> Actions do not get executed at all at times.
-> Duplicate actions occur for the same record.
-> Performance issues occurs because this setting causes Workflow Monitor Agent to be busy all the time. Thus, Workflow can cause resource crunch in terms of CPU utilization and memory, etc.
1) Just Navigate to Sitemap-> Administration->Server Configuration->Enterprises->Component Definitions->Choose Workflow Monitor Agent Component.
In the Component Parameters List choose Action Interval and check the default value is “3600” seconds (This is the default value to Action Interval Parameter).
2) Change the default value to 60. It means depending on the value of the Action Interval parameter for Workflow Monitor Agent, the action is taken.
3) Once Workflow Monitor Agent performs an action on the record in violation, an entry is logged into the S_ESCL_LOG table. If the same record comes into violation again within the Action Interval time, the Workflow Monitor Agent will not perform the action again on the same record. It will only remove the row from S_ESCL_REQ table. As a result, it is possible that Workflow Monitor Agent clears many records from the S_ESCL_REQ table for which no actions have been performed.
4) Setting the Action Interval = 0 is not recommended by Siebel Systems because the following behaviors have been observed to occur with this setting:
-> Actions performed for rows in S_ESCL_REQ without checking if conditions are met or not.
-> Actions do not get executed at all at times.
-> Duplicate actions occur for the same record.
-> Performance issues occurs because this setting causes Workflow Monitor Agent to be busy all the time. Thus, Workflow can cause resource crunch in terms of CPU utilization and memory, etc.
No comments:
Post a Comment