SRBroker and SRProc in a gist

Server Request Broker (SRBroker)

1.Used to start synchronous Siebel Server tasks
2.Server Request Broker & Server Manager are the only components which directly start tasks.
3.Introduced in in Siebel 7
4.Background component
5.Multi-threaded component
6.Need to set MaxTasks as per the needs.

Server Request Processor (SRProc)

1.Used to start asynchronous Siebel Server tasks
2.Manages queued requests
3.Calls SRBroker to manage task execution
4.Background component

This is a high level explanation which would be very helpful when you sit next time to debug logs;cheers

How to enable Customize Button

Enabling the Customize Button

---

The user can select a configurable product and click the Customize button to customize the product. However, the Customize button is only enabled when the user's responsibilities include one of the appropriate views that allows users to customize products. The following views of the Quotes screen are examples of views that enable the customize button:

• Complex Product Runtime Instance View
• Complex Product Runtime Instance View - Order
• Complex Product Runtime Instance View - Shopping Cart

Within these views, the Customize button is enabled only when the type of the product is Customizable.

To find a complete list of the views that enable the Customize button

1. Open Oracle's Siebel Tools.
2. In the Views tab, search for views that match the following:
   Complex Product Runtime Instance View*

Did you Know these personalities in Siebel:)

Demo Users for Siebel Call Center

Username / Password	Name / Title	Application	Primary Responsibility	Role
CCHENG	Casey Cheng / Universal Agent	Siebel Call Center	Universal Agent	Cheng handles service requests of all types: emails, inbound calls, and Web collaboration session requests. In addition, he executes outbound call campaigns.
TARNOLD	Ted Arnold / Telesales Representative	Siebel Call Center	Telesales Representative	Arnold primarily executes inbound and outbound telemarketing and telesales calls.
VTAYLOR	Vic Taylor / VP Call Center	Siebel Call Center	Call Center Manager	Taylor's responsibilities for the day-to-day operations of a Call Center make him a regular user of Siebel Call Center Administration functions. He uses the Siebel Analytics function to evaluate performance and ROI and to make strategic decisions based on the analyses.
EMODI	Emily Modi /Engagement Manager	Siebel Call Center	Consulting Manager	Modi is responsible for managing a consulting practice business, including opportunity management, client relationships, contracts and agreements, and financial reporting and management.
GABBO	Glen Abboline / Information Technologist	Siebel Professional Services	Consultant	Abboline is responsible for day-to-day project management, including staffing requests.
GCLARK	Gary Clark / Consultant	Siebel Professional Services	Consulting Manager	Clark is responsible for managing a consulting practice business.

How Siebel Workflow Interacts with Siebel Server Components..

Siebel Server Components

The Workflow Engine interacts with other server components through the Server Request Broker. Working as a business service, the Workflow Engine calls server components. To call a server component that is exposed as a specialized service, the Workflow Engine calls the signature for the service. For example, to send an email, the Workflow Engine calls the Communications Server as the Outbound Communications Manager business service. To assign an object to a user, it calls the Assignment Manager component as the Synchronous Assignment Manager Requests business service.
To call a server component that is not exposed as a specialized service, the Workflow Engine uses the predefined Server Requests Business Service. This business service sends a generic request to the Server Request Broker.

Server Request Broker
The Workflow Engine sends a request to the Server Request Broker, synchronously or asynchronously, and the Server Request Broker brokers the request to the appropriate component. The following work is performed:

1.Sending asynchronous messages from an interactive server component to the Workflow Engine

2.Communicating, synchronously and asynchronously, between the Workflow Engine and batch components

3.Scheduling repeated server tasks that are executed periodically in the Workflow Engine The Server Request Broker also performs load balancing. If the Server Request Broker receives a request, then it routes the request to the server component in the current server. For a workflow process, if the component is not available in the current server, then the Server Request Broker sends it to other servers on a round robin basis where the Workflow Process Manager component is activated.
A workflow process also uses Server Request Broker to resume a waiting workflow process. The Server Request Broker queries a database table on a regular basis in order to identify server tasks that must be resumed.

Personalization Engine

The Personalization engine handles run-time events, such as application events, applet events, and business component events. A workflow process handles run-time events through integration with the Personalization engine. A workflow started or resumed by a run-time event registers itself with the Personalization engine when the process is activated. If a run-time event occurs in a user session, then the Personalization engine calls Siebel Workflow in the local object manager.