About Server Request Broker (SRBroker)

Server Request Broker (alias SRBroker) is an interactive-mode Siebel Server component that belongs in the System Management component group. By default, one SRBroker is started for each Siebel Server. SRBroker handles client component requests by acting as a request router. For example, if a client makes a request to a Siebel Server for a component that is not running on that Siebel Server, then the request is routed to another Siebel Server that is running the requested component.

Siebel Server requests from clients that have no end point get stored in the database until the request is completed. The SRBroker works with the Server Request Processor (alias SRProc). For more information about this component, see "About Server Request Processor (SRProc)".

SRBroker also controls how many component requests by clients can be serviced by a Siebel Server at one time. Each client connection and component connection counts as one task. The number of tasks that can be handled by a single SRBroker is determined by the Maximum Tasks (alias MaxTasks), Maximum MT Servers (alias MaxMTServers), and Minimum MT Servers (alias MinMTServers) component parameters. Keep MaxMTServers and MinMTServers at their default value of 1 for SRBroker. For more information about these parameters, see Siebel Performance Tuning Guide. For information about how to set the number of tasks for SRBroker, see "Configuring Tasks for Server Request Broker".

Do not configure run-time parameters for SRBroker. If you have to support more client and component connections, then increase the number of tasks that can be handled by the SRBroker component.