Deployment Planning Guide > Load Balancing and Resilient Processing Planning >

About Server Request Processor

The Server Request Processor (SRProc) processes asynchronous, server-initiated requests. These are requests that are submitted for later execution and do not require the calling process to wait for the request to complete.

The Server Request Processor runs by default on all Siebel Servers. When asynchronous requests are submitted, they are stored in the Siebel Database in the S_SRM_REQUEST table. SRProc periodically checks this table for any requests that are eligible to be run. For a request to be eligible, it must meet all the following criteria:

  • Be the correct state (Submitted)
  • Its start time must have passed
  • The target Siebel Server must either not be specified, or must be the Siebel Server on which the SRProc instance is running

If a request is eligible, SRProc will invoke Server Request Broker (SRBroker) to run the request. Therefore, as long as a target Siebel Server is not specified, asynchronous requests will be read by any SRProc task on any Siebel Server.

This provides resilient processing for server-initiated tasks. As long as a SRProc task is running somewhere in the Siebel Enterprise Server, the request will be processed. For more information on resilient processing, see About Resilient Processing.

Deployment Planning Guide