Previous	Next		Contents	Index	Glossary

You can use the License Manager AD utility to review which products you currently have licensed. See: License Manager, Oracle Applications AD Utilies Reference Guide.

To ensure that the license status of the seeded events and subscriptions in the Business Event System is updated according to the status of the products you currently have licensed, you can run the Synchronize Product License and Workflow BES License concurrent program. Use the Submit Requests form in Oracle Applications to submit this concurrent program.

If you upgrade from an Oracle Applications release earlier than Release 11.5.9, you should run the Synchronize Product License and Workflow BES License concurrent program once after the upgrade to update the license status of the existing events and subscriptions in your Event Manager. Otherwise, subscriptions may not be correctly processed after the upgrade. Subsequently, when you license a product, Oracle Workflow automatically updates the license status for all the events and subscriptions owned by that product.

Note: Any events and subscriptions that you define with a customization level of User are always treated as being licensed.

   To submit the Synchronize Product License and Workflow BES License concurrent program:

1. Navigate to the Submit Requests form in Oracle Applications to submit the Synchronize Product License and Workflow BES License concurrent program. When you install and set up Oracle Applications and Oracle Workflow, your system administrator needs to add this concurrent program to a request security group for the responsibility that you want to run this program from. The executable name for this concurrent program is "Synchronize Product License and Workflow BES License" and its short name is FNDWFLIC. See: Overview of Concurrent Programs and Requests, Oracle Applications System Administrator's Guide.

2. Select the Synchronize Product License and Workflow BES License concurrent program as the request to run. This program does not require any parameters. See: Running Reports and Programs, Oracle Applications User's Guide.

3. When you finish modifying the print and run options to define the schedule for this request, choose Submit to submit the request.

See Also

Event Subscriptions (for Oracle Applications), Oracle Workflow Developer's Guide

Cleaning Up the Workflow Control Queue

The Generic Service Component Framework uses WF_CONTROL to handle control events for containers and service components, such as notification mailer or agent listener service components. In Oracle Applications, WF_CONTROL is also used for other Oracle Applications internal processing.

You do not need to schedule propagation for the WF_CONTROL agent, because the middle tier processes that use WF_CONTROL dequeue messages directly from its queue.

However, the subscribers to the WF_CONTROL queue need to be cleaned up periodically.

• In the standalone version of Oracle Workflow, you can use an API called WF_BES_CLEANUP.Cleanup_Subscribers() to perform this cleanup.

• In Oracle Applications, a concurrent program named Workflow Control Queue Cleanup is automatically scheduled to perform this cleanup for you.

The WF_BES_CLEANUP.Cleanup_Subscribers() procedure sends an event named oracle.apps.wf.bes.control.ping to check the status of each subscriber to the WF_CONTROL queue. If the corresponding middle tier process is still alive, it sends back a response. The next time the cleanup procedure runs, it checks whether responses have been received for each ping event sent during the previous run. If no response was received from a particular subscriber, that subscriber is removed. See: Cleanup_Subscribers, Oracle Workflow API Reference.

The recommended frequency for performing cleanup is every twelve hours. In order to allow enough time for subscribers to respond to the ping event, the minimum wait time between two cleanup runs is thirty minutes. If you run the procedure again less than thirty minutes after the previous run, it will not perform any processing.

Standalone Oracle Workflow If you are using the standalone version of Oracle Workflow, then use the WF_BES_CLEANUP.Cleanup_Subscribers() API to clean up the WF_CONTROL queue. You can use the Oracle Workflow Manager component available through Oracle Enterprise Manager to submit and manage Workflow control queue cleanup database jobs. You can also use the procedures in the DBMS_JOB or DBMS_SCHEDULER packages to schedule and manage the WF_BES_CLEANUP.Cleanup_subscribers() procedure as a database job. See the Oracle Workflow Manager online help and Managing Job Queues, Oracle Database Administrator's Guide or Using the Scheduler, Oracle Database Administrator's Guide.

Oracle Workflow Embedded in Oracle Applications If you are using the version of Oracle Workflow embedded in Oracle Applications, Oracle Workflow provides a concurrent program named Workflow Control Queue Cleanup, which uses the WF_BES_CLEANUP.Cleanup_Subscribers() API to perform the necessary cleanup. This concurrent program is scheduled to run every twelve hours by default, which is the recommended frequency for performing cleanup. You can optionally run this program with a different schedule if you want to perform cleanup at a different frequency.

   To submit the Workflow Control Queue Cleanup concurrent program:

1. Navigate to the Submit Requests form in Oracle Applications to submit the Workflow Control Queue Cleanup concurrent program. When you install and set up Oracle Applications and Oracle Workflow, your system administrator needs to add this concurrent program to a request security group for the responsibility that you want to run this program from. The executable name for this concurrent program is "Workflow Control Queue Cleanup" and its short name is FNDWFBES_CONTROL_QUEUE_CLEANUP. See: Overview of Concurrent Programs and Requests, Oracle Applications System Administrator's Guide.

2. Select the Workflow Control Queue Cleanup concurrent program as the request to run. This program does not require any parameters. See: Running Reports and Programs, Oracle Applications User's Guide.

3. When you finish modifying the print and run options to define the schedule for this request, choose Submit to submit the request.

See Also

Standard Agents, Oracle Workflow Developer's Guide

Business Event System Cleanup API, Oracle Workflow API Reference