Siebel Server Administration Guide > Siebel Server Infrastructure Administration >

Administering Server Request Broker


Server Request Broker is an interactive-mode Siebel Server component that belongs in the System Management Siebel Server component group. By default, one Server Request Broker will be started for each Siebel Server. Server Request Broker 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 will be routed to another Siebel Server that is running the requested component.

Siebel Server requests to clients that have no end point get stored in the database until the request is completed. The Server Request Broker works with the Server Request Processor (see 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 will be in the database and sent to the client when the user logs on. Server Request Broker 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 Server Request Broker is determined by the Maximum Tasks component parameter.

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

To change the number of tasks that can be handled by Server Request Broker

  1. Navigate to the Components screen.
  2. Click the Component Parameters view tab.
  3. In the Server Components list, select the Server Request Broker you want to configure.
  4. In the Component Parameters list, select the Maximum Tasks parameter.
  5. In the Value on Restart field, type in the number of tasks.
  6. The default value is 100.

  7. Click the menu button and then Save Record
  8. For changes to take effect, restart the Siebel Server System Service.
  9. For more information on restarting the Siebel Server System Service, see Administering the Siebel Server System Service.

Figure 32 shows an example of changing the number of tasks that can be handled by Server Request Broker to 200.

Figure 32. Changing Number of Tasks Handled by Server Request Broker

Click for full size image

Server Request Processor

The Server Request Processor and the Server Request Broker are jointly responsible for the processing of both synchronous and asynchronous requests from a variety of Siebel Server components. The Server Request Processor (SRProc) is a background-mode component that handles requests between the Siebel Server and the database. There can only be one instance of the Server Request Processor for each Siebel Server. The following components rely on a functioning Server Request Processor and Server Request Broker:

If either of the Server Request Broker or Server Request Processor components become unavailable for any reason, the ability to process requests from other components is severely affected. This situation is due to the request mechanism (Component Requests) of the Server Manager GUI, which relies on a functioning Server Request Broker and Server Request Processor to schedule and process requests. However, the server manager command-line interface program bypasses this request mechanism permitting the user to start (but not schedule) a component task by using the command-line interface if either or both the Server Request Broker or Server Request Processor are unavailable (or, alternatively, restarting the Server Request Broker or Server Request Processor). For more information on using the server manager command-line interface program, see Using the Siebel Server Manager Command-Line Interface.

In order to make sure that these components experience as little downtime as possible, there are a number of parameters available against the components that make sure they are automatically restarted in the event of a failure. See information in Siebel Server Components and Parameters on the Default Tasks, Default Processes, and Auto-Restart parameters.


 Siebel Server Administration Guide, Version 7.5, Rev. C 
 Published: 18 April 2003