Oracle Workflow Components
Oracle Workflow Components
Oracle Workflow Components
Components
Overview
Distribution
Job Title*
Ownership
The Job Title [[email protected]?Subject=EDUxxxxx] is responsible for ensuring that
this document is necessary and that it reflects actual practice.
Workflow Processes
• A workflow process definition must be saved to the same database as the Workflow
Engine.
• A process definition is composed of activities and the transitions between them.
• A completed application transaction or event can initiate a workflow process by raising an
event or by calling a series of Workflow Engine APIs.
• The Workflow Engine locates the ‘Start’ activity in the process definition.
• The Workflow Engine drives through the process, performing all automated steps such as
function activities and Raise and Send event activities, until an asynchronous activity such
as a notification, Receive event activity, or blocking activity occurs.
- The Workflow Engine calls the Notification System to deliver a notification message to
an appropriate role. Once a user of that role completes the notification response, the
Workflow Engine continues to drive through the remaining activities in the process.
- If a blocking activity is encountered, the Workflow Engine waits for an external
program to complete and call the appropriate Workflow Engine API before proceeding
to the next activity.
Messaging Gateway, while available with AQ in Oracle9i Database Release 1 (9.0.1), was
not yet documented in the Oracle9i Application Developer’s Guide - Advanced Queuing
for that release. Messaging Gateway documentation is available in the Oracle9i
Application Developer’s Guide - Advanced Queuing for Oracle9i Release 2 (9.2) and
higher versions of the AQ documentation.
Notification System
The Notification System:
• Routes notifications to a role, which can be a single user or group of users
• Enables users to receive and respond to notifications using an e-mail application or Web
browser of choice
• Sends e-mail notifications and processes e-mail responses using the JavaMail API
• Allows any users with access to the Internet to be included in a workflow process
• Provides access to the Worklist from Oracle E-Business Suite through the Worklist web
pages
• Enables users to drill down from a notification in the Worklist web pages to any URL or
Oracle E-Business Suite form to respond to the notification
Instructor Note
The Developer 2000 Notifications form is not supported in Oracle Workflow 2.5 and higher.
Instead, users view notifications with the Worklist web pages or an e-mail client. However,
users can still drill down from a Workflow notification to an attached form (Oracle E-Business
Suite screen).
Directory Services
Users can be associated with more than one role, and a role may contain more than one user.
The Workflow Engine and Notification System use the directory service to determine who
should receive notifications and in what format. Notifications can be delivered to an individual
user or to all members of a particular role.
Note: In the Oracle E-Business Suite, Oracle Workflow uses a directory service model in
which denormalized information is maintained in the Workflow local tables for performance
gain. You should maintain synchronization between the user and role information stored in
application tables by the source modules and the information stored in the Workflow local
tables.
Workflow Monitor
The standalone version of Oracle Workflow includes the Workflow Monitor in the standalone
format. The version of Oracle Workflow embedded in the Oracle E-Business Suite includes the
administrator and self-service versions of the Status Monitor in the Oracle Applications
Framework user interface format.
Workflow Manager
Administrators can use Workflow Manager to perform the following tasks:
• Run Workflow service components, such as notification mailers and agent listeners.
• Control other Workflow system services, including background engines, purging obsolete
Workflow data, and cleanup of the Workflow control queue.
• Monitor work item processing by viewing the distribution of all work items by status and
drilling down to additional information.
• Monitor event message processing for local Business Event System agents by viewing the
distribution of event messages by status and drilling down to additional agent information
and individual event messages, as well as by viewing queue propagation details.
With this ability to monitor work items and event messages, a system administrator can
identify possible bottlenecks easily.
Service Components
Oracle Workflow uses the Generic Service Component Framework (GSCF) to simplify and
automate the management of background Java services. A service component is an instance of
a Java program which has been defined according to the GSCF standards so that it can be
managed through this framework.
Use Oracle Workflow Manager to configure and run service components.
Note: In Oracle E-Business Suite, Oracle Workflow Manager also lets you manage Web
services outbound components, which process outbound Web service messages for Oracle
XML Gateway. For more information, see the Oracle XML Gateway User’s Guide.
Refer to Guided Demonstration – Loading and Running a Workflow Process
[LAB23B9Y]