Bookshelf Home | Contents | Index | PDF |
Siebel Business Process Framework: Workflow Guide > Architecture That Siebel Workflow Uses > About the Architecture of a Workflow Process > Run-Time Architecture That Siebel Workflow UsesA workflow process can run as a business service or as a server component in the run-time environment. The Workflow Engine interacts with other server components through the Server Request Broker. The Workflow Engine works as a business service that calls a server component. To call a server component that Siebel CRM:
Figure 6 describes the run-time architecture that Siebel Workflow uses. Explanation of CalloutsThe run-time architecture that Siebel Workflow uses includes the following items:
Server Request Broker Server ComponentThe Workflow Engine sends a request to the Server Request Broker synchronously or asynchronously, and then the Server Request Broker brokers the request to the appropriate server component. It does the following work:
The Server Request Broker also does load balancing. If it receives a request, then it routes this request to a server component that resides in the current server. If this server component is not available in the current server, then the Server Request Broker sends it to other servers where the Workflow Process Manager is active. It does this on a round robin basis. A workflow process also uses the Server Request Broker to resume a workflow process that is waiting. The Server Request Broker periodically queries a database table to identify server tasks that it must resume. For more information, see Server Requests Business Service and Siebel System Administration Guide. Workflow Process Manager Server ComponentThe Workflow Process Manager (WfProcMgr) is a server component that uses the Siebel Object Manager. It runs a workflow process as a business service. It hosts the business object layer and the data object layer that allows Siebel CRM to run multiple object managers and multiple server tasks for each object manager. The term Workflow Process Manager refers to the Workflow Engine and the workflow server components. The Workflow Process Manager can be in one of the following states:
For more information, see Starting a Workflow Process from the Workflow Process Manager. How the Business Service Determines Where the Workflow Process RunsThe Workflow Engine includes the Workflow Process Manager business service and the Workflow Process Manager (Server Request) business service. To run Siebel Workflow in an Application Object Manager, Siebel CRM starts the workflow process as a business service. The Workflow Engine uses output arguments to send information to this business service and it uses input arguments get information from this business service. Table 3 describes how the business service determines where the workflow process runs. How Siebel Workflow Runs in the Workflow Process Manager Server ComponentA Workflow Process Manager server component that Siebel CRM configures and optimizes to run the Workflow Process Manager business service can run a workflow process in the background. The Workflow Process Manager server component works as the object manager that runs the workflow process, including any application logic that the workflow process uses. The Workflow Process Manager accepts the workflow process name in the following ways:
If a workflow policy starts a workflow process, then the Workflow Monitor Agent typically uses the Encoded Input Arguments parameter to send input arguments to the Workflow Process Manager. However, setting Encoded Input Arguments in the Component Request Parameters applet fails because it is not in a format that the Workflow Process Manager server component can recognize. Components of the Workflow Management Server Component GroupTable 4 describes server components that the Workflow Management server component group contains.
|
Siebel Business Process Framework: Workflow Guide | Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |