Siebel System Administration Guide > Siebel Server Infrastructure Administration >

About Server Request Broker (SRBroker)

Server Request Broker (alias SRBroker) is an interactive-mode Siebel Server component that belongs in the System Management Siebel Server 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, 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) (see About Server Request Processor for further information on this component) on this process. For example, if the Siebel Server sends an email to a user who is not connected, the email remains in the database and is sent to the client when the user logs on.

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 (MinMTServers) component parameters. MaxMTServers and MinMTServers should be kept at their default value of 1 for SRBroker. For more information on these parameters, see Siebel Performance Tuning Guide. See Configuring Tasks for Server Request Broker for information on how to set the number of tasks for SRBroker.

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

Siebel System Administration Guide Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices.