Siebel CRM Performance Tuning Guide Siebel 2018 E24801-01 |
|
![]() Previous |
![]() Next |
View PDF |
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 to the SRBroker component to determine what to do with the request:
If the destination component is running on the same Siebel Server, then SRBroker passes the request to this component. If multiple instances of the destination component are running, then SRBroker passes the request to each component instance in a round-robin fashion.
If the destination component is not running on the same Siebel Server, then SRBroker passes the request to SRBroker running on another computer. If the destination component runs on multiple Siebel Servers, then SRBroker passes the request to each server in round-robin fashion.
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: SettingMaxTasks parameter values for SRBroker components in such a way that does not meet the above guidelines might result in request failures. |
For more information about the SRBroker and SRProc components, see Siebel System Administration Guide.