Understanding SRProc and SRBroker in Siebel

Overview

In Siebel CRM, SRProc (Server Request Processor) and SRBroker (Server Request Broker) are crucial components of the Siebel Server architecture. These components manage server requests, ensuring efficient processing and routing across various services and systems.

SRProc (Server Request Processor)

SRProc is responsible for processing asynchronous server requests. It handles tasks queued for execution, enabling users or other components to continue working without waiting for completion.

Key Functions

• Processes asynchronous requests from the S_SRM_REQUEST database table.
• Executes background jobs such as workflows, EIM tasks, and batch operations.
• Includes a retry mechanism for failed requests based on configuration.

How It Works

1. Requests are queued in the S_SRM_REQUEST table.
2. SRProc polls the queue at configured intervals.
3. It processes each request by invoking the appropriate server component or business service.

SRBroker (Server Request Broker)

SRBroker routes incoming requests to the appropriate Siebel Server components, ensuring efficient distribution and execution.

Key Functions

• Routes synchronous and asynchronous requests to the appropriate components.
• Performs dynamic load balancing using algorithms like round-robin.
• Maintains a registry of available components and their states.

How It Works

1. Receives incoming requests (e.g., from users or integration systems).
2. Identifies the target server component based on the request type.
3. Routes the request to an available instance or queues it until a component is free.

Comparison of SRProc and SRBroker

Feature	SRProc	SRBroker
Primary Role	Processes asynchronous requests.	Routes requests to appropriate components.
Request Type	Asynchronous (background tasks).	Synchronous and asynchronous.
Request Queue	Uses S_SRM_REQUEST table.	Routes requests in real-time.
Load Balancing	Not applicable.	Performs dynamic load balancing.
Usage Example	Workflow processing, EIM jobs.	Routing user session requests or web services.

Interview Questions and Answers

What is SRProc, and what is its role?

SRProc (Server Request Processor) handles asynchronous server requests. It retrieves requests from the queue and processes them in the background.

What is SRBroker, and what is its role?

SRBroker (Server Request Broker) routes incoming requests to appropriate Siebel Server components, ensuring efficient load distribution.

What type of requests does SRProc handle?

SRProc handles asynchronous tasks like workflows, EIM jobs, and scheduled tasks stored in the S_SRM_REQUEST table.

How does SRBroker achieve load balancing?

SRBroker uses algorithms like round-robin to distribute requests evenly among available component instances.

How can you monitor SRProc and SRBroker?

Use the Siebel Server Manager (srvrmgr) to monitor and manage logs for both components. Ensure they are functioning as expected.

Can SRBroker handle asynchronous requests?

Yes, SRBroker routes both synchronous and asynchronous requests to appropriate components.

What is the relationship between SRProc and the S_SRM_REQUEST table?

SRProc polls the S_SRM_REQUEST table for queued asynchronous requests and processes them.

Useful Resources

Here are some links to deepen your understanding of SRProc and SRBroker in Siebel:

• Oracle Siebel Documentation Library
• Siebel Hub - Tutorials and Insights
• Oracle Support Knowledge Base
• Stack Overflow - Siebel Questions
• YouTube Tutorials on Siebel