Previous  Next          Contents  Index  Glossary  Library

To Schedule Background Engines

If you are using the version of Oracle Workflow embedded in Oracle Applications, you can submit the background engine procedure as a concurrent program to schedule different background engines to run at different times. Use the Submit Requests window in Oracle Applications to submit the Workflow Background Process.

   To Run a Workflow Background Process as a Concurrent Program:

Item Type Specify an item type to restrict this engine to activities associated with that item type. If you do not specify an item type, the engine processes any deferred activity regardless of its item type.
Minimum Threshold Specify the minimum cost that an activity must have for this background engine to execute it, in hundredths of a second.
Maximum Threshold Specify the maximum cost an activity can have for this background engine to execute it, in hundredths of a second.
By using Minimum Threshold and Maximum Threshold you can create multiple background engines to handle very specific types of activities. The default values for these arguments are 0 and 100 so that the background engine runs activities regardless of cost.
Process Deferred Specify whether this background engine checks for deferred activities. Setting this parameter to 'Yes' allows the engine to check for deferred activities.
Process Timeout Specify whether this background engine checks for activities that have timed out. Setting this parameter to 'Yes' allows the engine to check for timed out activities.
Note: Make sure you have a least one background engine that can check for timed out activities and one that can process deferred activities. At a minimum, you need to set up one background engine that can handle both timed out and deferred activities.

See Also

To Start a Background Engine

To Set Engine Thresholds

         Previous  Next          Contents  Index  Glossary  Library