|
|
|
|
|
||
| Previous | Next | Contents | Index | Glossary |
Note: If you require a larger rollback segment for the Workflow Background Process than the default, you can use the Concurrent Programs window in the System Administrator responsibility to specify the rollback segment that you want. This rollback segment will be used instead of the default and will be used up until the first commit.
Query the Workflow Background Process concurrent program (FNDWFBG) in the Concurrent Programs window, and choose the Session Control button. Then in the Session Control window, enter the rollback segment you want in the Rollback Segment field, and save your work. See: Concurrent Programs Window, Oracle Applications System Administrator's Guide.
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. |
| Process Stuck | Specify whether this background engine checks for stuck processes. Setting this parameter to 'Yes' allows the engine to check for stuck processes. |
Note: Make sure you have a least one background engine that can check for timed out activities, one that can process deferred activities, and one that can handle stuck processes. At a minimum, you need to set up one background engine that can handle both timed out and deferred activities as well as stuck processes.
See: Overview of Concurrent Programs and Requests, Oracle Applications System Administrator's Guide
| Previous | Next | Contents | Index | Glossary |