Previous	Next		Contents	Index	Glossary

If you are using the standalone version of Oracle Workflow, then use the WF_ENGINE.BACKGROUND

() API to start up a background engine. Sample scripts that repeatedly run the background engine are provided with the standalone version of Oracle Workflow. You can use the procedures in the DBMS_JOB package to schedule and manage the background engine as a database job. See: Background, Oracle Workflow API Reference and Managing Job Queues, Oracle Administrator's Guide.

If you are using the version of Oracle Workflow embedded in Oracle Applications, you can start a background engine by submitting the Background Process concurrent program using the Submit Requests form. See: To Schedule Background Engines

Note: If you are using the version of Oracle Workflow embedded in Oracle Applications and you have implemented Oracle Applications Manager, you can use Oracle Workflow Manager to submit and manage the Workflow Background Process concurrent program. For more information, please refer to the Oracle Applications Manager online help.

If you are using the standalone version of Oracle Workflow, you can use the standalone Oracle Workflow Manager component available through Oracle Enterprise Manager to submit and manage Workflow background engine database jobs. For more information, please refer to the Oracle Workflow Manager online help.

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: Setting Up Background Engines

See: To Set Engine Thresholds

Copyright © 2003 Oracle Corporation.
All rights reserved.