Siebel Deployment Planning Guide > Siebel Architecture Overview >

About the Server Request Processor

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

SRProc runs by default on all of the 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 of the following criteria:

• The request must be in the correct state (Queued)
• Its start time must have passed
• The target Siebel Server must not be specified or must be the Siebel Server where the requested component is running

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

The SRProc component helps provide resilient processing for server-initiated tasks. As long as an SRProc task is running somewhere in the Siebel Enterprise, the request is processed. For more information about resilient processing, see About Resilient Processing.