Deployment Planning Guide > Load Balancing and Resilient Processing Planning >

About Server Request Broker

Server Request Broker (SRBroker) processes synchronous server requests—requests that must be run immediately, and which the calling process waits for completion. Server Request Broker (SRBroker) in Siebel 7 replaces Server Request Manager (SRMSynch) in previous versions.

Whereas SRMSynch could only run server requests on a local Siebel Server (that is, the same Siebel Server that SRMSynch was running on), SRBroker can run server requests on any server in the Enterprise. For example, if SRBroker is unable to run a server request on the local Siebel Server because the required component is not enabled, SRBroker will locate another Siebel Server that is hosting the required component and run it there. Server Request Broker runs by default on all Siebel Servers.

SRBroker decides where to run a server request using the following criteria:

• If the required component is available locally then SRBroker will run the task locally.
• If the required component is not available locally then SRBroker will identify any Siebel Servers in the same Enterprise that have the component online. Server requests will be submitted to each of these Siebel Servers in turn (a round-robin algorithm).
• If the required component is not available anywhere in the Enterprise, then the server request will fail.

This provides resilient processing. As long as the required component is running on a Siebel Server somewhere in the Enterprise, then the server request can be processed. For more information on resilient processing, see About Resilient Processing.