Pages

Wednesday, June 5, 2013

Error : workflow background engines is down


schedule the concurrent request WorkFlow Background Process as follows

WorkFlow Development recommends that users run the he Workflow Background Engine with these basic settings:
==========================================================================================

A. Schedule one concurrent request to process deferred activities:

1. Item Type :
2. Min Threshold :
3. Max Threshold :
4. Process Deferred : Yes
5. Process Timeout : No
6. Process Stuck : No

B. Schedule one concurrent request to process timeout activities:

1. Item Type :
2. Min Threshold :
3. Max Threshold :
4. Process Deferred : No
5. Process Timeout : Yes
6. Process Stuck : No

C. Run for stuck activities periodically (monthly or weekly):


1. Item Type :
2. Min Threshold :
3. Max Threshold :
4. Process Deferred : No
5. Process Timeout : No
6. Process Stuck : Yes

Instructions to run the request.

1. Log into the Application as System Administrator Responsibility.

2. Navigation: Concurrent -> Request -> View Concurrent Request

3. Query WorkFlow Background Process in the Name field,
and verify it has run and how it was scheduled.


How do you start the Workflow Background Process if it is not running?

1. Sign onto the Oracle Application using the System Administrator 
Responsibility.

2. Navigation: Concurrent -> Request -> (B) Run, click OK for Single Request.

3. Open the Submit Request form. Click on the Pick List and choose 
Workflow Background Process

4. In the parameters window, enter the following parameters then click OK:

a. Item Type: 
If you want to restrict workflow engine to a specific Item Type, 
specify the same here. Else, the engine will process all/any 
deferred activity regardless of the Item Type.

b. Minimum Threshold: 
If you want to restrict this engine to activities with specific minimum 
cost, define it here. Otherwise the Workflow engine will process any 
deferred activity regardless of cost.

c. Maximum Threshold: 
If you want to restrict this engine to activies with specific maximum 
cost, define it here. Otherwise the workflow engine will process any 
deferred activities regardless of cost.

d. Process Deferred:
Specify whether the workflow engine should run deferred. Set it to Yes or
No. If this set to yes, the Workflow Background Process will run the 
workflow activities as a deferred process.

e. Process Time out: 
Specify whether the workflow engine should check for activities that have 
been timed out. Set it to Yes or No.

5. When you have finished the above steps, define Scheduling for the background 
process engine (as per the specific business needs) and click the submit 
button.

No comments:

Post a Comment