Siebel Workflow Process Runtime Architecture
A Workflow Process can run as a business service or as a server component in the runtime environment. You can invoke a Workflow Process either synchronously or asynchronously.
-
In a synchronous scenario, everything is carried out in process (for example, in the Application Object Manager that the user is currently interacting with) and the Workflow Process will run to completion before returning control to the calling process.
-
In an asynchronous scenario, the Server Request Broker and Server Request Manager are invoked to run operations in the background (out-of-process). For more information, see Server Request Broker Server Component, Workflow Process Manager Server Component, and Server Requests Business Service.
The following figure shows the components in the runtime architecture that Siebel Workflow Process uses.
As shown in this figure, the components in Siebel Workflow Process runtime architecture are as follows:
-
Application Object Manager. Siebel business objects, runtime events (local and remote, synchronous and asynchronous) and the Workflow Process Manager (Business Service) reside on the Application Object Manager.
-
Server Request Broker Server Component. The Server Request Broker brokers the request to the appropriate server component. For more information, see Server Request Broker Server Component.
-
Workflow Process Manager (Server Component). The Workflow Process Manager server component runs the Workflow Process as a business service. For more informaiton, see Workflow Process Manager Server Component and Components of the Workflow Management Server Component Group.
Workflow Process Manager (Business Service). For more information, see the following: