Bookshelf Home | Contents | Index | PDF |
Siebel Performance Tuning Guide > Tuning the Siebel Server Infrastructure > Tuning Server Request Broker (SRBroker)The Server Request Broker (SRBroker) component routes requests between Siebel Server components, such as from a Siebel Application Object Manager to a batch component. SRBroker also handles requests between batch components. SRBroker is used whether the components run on the same computer or on different computers. Server requests originating with a Siebel Application Object Manager component always go the SRBroker component to determine what to do with the request:
The default parameter values for SRBroker work well for most deployments. If necessary, adjust the value of the MaxTasks parameter (the default value is 100). MaxTasks determines the maximum number of SRBroker threads (tasks) that can run on the Siebel Server. As necessary, set MaxTasks to a value equal to the number of batch components running on the Siebel Server, plus the number of Siebel Servers in the enterprise, plus 10 (for overhead). MaxMTServers and MinMTServers determine the maximum and minimum number of SRBroker multithreaded processes that can run on the Siebel Server. Each multithreaded process can run a maximum of MaxTasks divided by MaxMTServers threads. Default values for MaxMTServers and MinMTServers must be set to 1. Increasing this value will not increase performance, and will not have any benefit. CAUTION: Setting MaxTasks parameter values for SRBroker components in such a way that does not meet these guidelines might result in request failures. (HonorMaxTasks has no effect when set on the Server Request Broker (SRBroker) or Server Request Processor (SRProc) components.) For more information about SRBroker and SRProc components, see Siebel System Administration Guide. About HonorMaxTasks Parameter for Batch ComponentsBy default, the HonorMaxTasks parameter for batch components, such as Workflow Process Manager, is set to FALSE (this setting is recommended). With this setting, if requests are routed by SRBroker to a batch component that has reached the maximum task capacity, then the requests will be queued in memory, and processed when tasks become available. Queuing such tasks minimizes the potential of request failure on the batch component due to the MaxTasks value having been reached. You might consider setting HonorMaxTasks to TRUE for batch components in the following scenarios:
|
Siebel Performance Tuning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |