Siebel System Administration Guide > Siebel Server Infrastructure Administration >

About Server Request Processor (SRProc)

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

• Assignment Manager
• Communications Manager
• Enterprise Application Integration
• EIM
• Field Service (all components)
• Interactive Assignment
• Workflow Management

If either SRBroker or SRProc become unavailable for any reason, then the ability to execute intercomponent requests is severely affected. The request mechanism (component jobs) of the Server Manager GUI relies on a functioning SRBroker and SRProc 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 SRBroker or SRProc components are unavailable (or, alternatively, restarting the SRBroker or SRProc components). For more information about using the server manager command-line interface program, see Using the Siebel Server Manager Command-Line Interface.

Several parameters are available that ensure that these components automatically restart in the event of a failure, so the components experience as little downtime as possible. For information about the parameters Default Tasks (alias DfltTasks), Default Processes (alias DfltProcs), and Auto-Restart (alias AutoRestart), see Siebel Server Components and Parameters.