Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Deployment Planning Guide > Application-Level Deployment Planning > Siebel Workflow Deployment PlanningSiebel Workflow lets you define, manage, and enforce your business processes or workflows. It allows you to design complex workflow processes and automate the enforcement of business policies and procedures. This module includes the following:
For information about using and administering Siebel Workflow, see Siebel Business Process Framework: Workflow Guide. Each user request to the Workflow Process Manager starts a new thread. However, sessions for Object Manager components (such as EAI Object Manager or Application Object Manager) that might invoke workflow processes are cached and reused for subsequent requests. When you size a deployment of Siebel Business Applications, the maximum number of workflow tasks that you expect to have active at a given time helps determine the maximum number of Object Manager sessions created for Siebel applications. The exact CPU and memory consumption of each task depends on the actions performed in your workflow processes. To estimate CPU and memory consumption in your production environment, run a single task, measure its resource consumption, and make an estimation based on your maximum concurrent sessions. Take session caching into account when making these measurements. If you need a large number of sessions, then you might want to run Workflow Process Manager on multiple Siebel Server computers. You can then load-balance requests across the Siebel Servers. If you plan to run a significant number of tasks per server (such as 100 or more), then you might also want to run multiple multithreaded processes. If you are going to run several different types of workflows, then run each type in a separate process. Doing so makes it easier to monitor the overall CPU and memory usage of each process type. The number of multithreaded processes and the number of tasks for each process are controlled through the parameters MaxMTServers (Maximum MT Servers), MinMTServers (Minimum MT Servers), and MaxTasks (Maximum Tasks). These parameters are for each Siebel Server. For example, MaxMTServers refers to how many multithreaded processes to run on each Siebel Server computer. Business Integration Manager and Business Integration Batch Manager have been deprecated. If you were using either one of these components in your business processes, then replace them with Workflow Process Manager or Workflow Process Batch Manager, respectively. If a workflow policy action is set up to use the Run Integration Process workflow policy program, which invokes the Business Integration Manager (BusIntMgr) component, then create a new workflow policy action using the Run Workflow Process workflow policy program. The new workflow policy action instead invokes Workflow Process Manager. Delete the old workflow policy action from the workflow policy, add the new workflow policy action to the workflow policy, and restart Workflow Monitor Agent tasks. For more information about server components, see Siebel System Administration Guide. |
![]() |
![]() ![]() |
Siebel Deployment Planning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |