Contents	Index	Glossary	Master Index	Feedback

When you display the Process window for the Workflow Event Protocol process, you see that the process consists of eight unique activities, some of which are reused to make up the ten activity nodes that appear in the workflow diagram. To examine the activities of the process in more detail, we have numbered each node for easy referencing below. The numbers themselves are not part of the process diagram.

The Workflow Send Protocol workflow begins when the Event Manager sends an event message to the Workflow Event Protocol process. For example, when you raise the Workflow Send Protocol event locally or receive that event from an external source, predefined subscriptions send the event message to the Workflow Event Protocol process. See: Workflow Send Protocol Events.

The workflow begins at node 1 with the Receive message activity. At node 2, the process attempts to retrieve the agent details for the intended outbound and inbound agents from the subscription.

If no inbound agent is specified, the process continues immediately to node 6 to determine whether to send an acknowledgement message.

If the subscription does specify a To Agent, the process sends the event message to that agent. Then the process determines whether the event message requires an acknowledgement from the recipient, based on a subscription parameter. If an acknowledgement is required, the Workflow Engine waits to receive the acknowledgement message. Otherwise, the process continues immediately to node 6 to determine whether to send an acknowledgement message.

At node 6, the process determines whether it should send an acknowledgement of the original message that it received. If no acknowledgement needs to be sent, the process ends at this point. Otherwise, the process retrieves the agent details for the inbound agent where the acknowledgement must be sent and sends the acknowledgement message to that agent. Then the process ends.

Copyright © 1996, 2002 Oracle Corporation.
All Rights Reserved.