Siebel Components

Siebel Architecture

Siebel Architecture Consist of the Followings:

1-Siebel Gateway Name Server

2-Siebel Enterprise Servers & Siebel Server

3-Siebel Web Server [SWSE]

4-Siebel Database Server [RDBMS]

5-Siebel File System [Shared folder]

6-Web Clients

1.    Siebel Gateway Name Server:

·         The Siebel Gateway Name Server coordinates the Siebel Enterprise Server and Siebel Servers. A single Siebel Gateway Name Server can support multiple Siebel Enterprise Servers. The Siebel Gateway Name Server also provides the backing of Siebel Enterprise Server configuration information, including:

   -- Definitions and assignments of component groups and components

   -- Operation Parameters

   -- Connectivity information

·         Siebel Gateway Name Server maintains all this information in the [siebns.dat] file which is present on the Gateway Name Server Installation Directory/ADMIN/ folder. Gateway Name Server acts as Registry for the Siebel Servers and components availability information.

·         In a Windows environment, the Siebel Gateway Name Server runs as a Windows service. In a UNIX environment, the Siebel Gateway Name Server runs as a daemon process. The system process associated with the Siebel Gateway Name Server is [siebsvc.exe] on Windows and [siebsvc] on UNIX. Each running Siebel Server has a corresponding Siebel Gateway Name Server system process.

·         Impact of Failure - When the Siebel Gateway Name Server goes down, service to active user connections is not immediately interrupted. All Siebel Server components and object managers currently running continue to do so. However, no new Siebel Server components can be started or added. Server administration functions become limited.

2.    Siebel Enterprise Server & Siebel Servers:

·         The Siebel Enterprise Server is a logical grouping of Siebel Servers that connect to one Siebel database. The Siebel Servers in a Siebel Enterprise Server are configured, managed, and monitored as a single logical group, allowing the Siebel administrator to start, stop, monitor, or set server parameters for all Siebel Servers within the Siebel Enterprise Server.

·         Siebel Server - The Siebel Enterprise Server is composed of one or more Siebel Servers. Siebel Servers function as application servers and are composed of server components. Each server component performs a defined function. Server components or groups of components determine what applications and services a Siebel Server supports. Components run in one of several modes:

o        Interactive mode Interactive components start tasks automatically in response to user requests. The tasks end when the user ends the session. Examples of interactive mode tasks are the Synchronization Manager and all Application Object Managers (AOMs).

o        Background mode Background components handle background processing tasks. Typically, background tasks are called by interactive mode tasks. Background tasks run until explicitly shut down. Examples of background tasks are Transaction Router and Workflow Monitor Agent.

o        Batch mode Batch mode components handle processing of asynchronous work requests. Batch mode components handle processing of asynchronous work requests. Examples of batch mode components are Database Extract and Enterprise Integration Manager (EIM).

·         Many of the Siebel Server components can operate on multiple Siebel Servers simultaneously. This allows Siebel applications to scale across many Siebel Servers to support large numbers of users. Other Siebel Server components provide additional functionality besides application support. This includes the following:

o        Siebel Mobile Web Client synchronization

o        Integration with legacy or third-party data

o        Automatic assignment of new accounts, opportunities, service requests, and other records

o        Workflow management

o        Document generation

·         Siebel Connection Broker (SCBroker) The Siebel Connection Broker (alias SCBroker) is a background-mode server component that provides intraserver load balancing. By default, it is always enabled and online. At least one instance of SCBroker must be running on the Siebel Server hosting interactive components.

o        SCBroker listens on a configurable, static port for new connection requests from the Web server or a third-party load balancer. The parameter, Static Port Number (alias Port Number), defines the port that SCBroker monitors. The default value for this parameter is 2321. After a request is received, SCBroker distributes it to the appropriate instance of an Application Object Manager (AOM) running on the Siebel Server.

o        SC Broker uses the Connection Forward algorithm (ConnForwardAlgorithm) to forward the socket to the Object Manager processes. This parameter has two possible settings: Least Loaded (LL) and Round-Robin (RR). Least Loaded is the default value. The Least Loaded algorithm balances incoming Object Manager login requests and identifies which Object Manager process is handling the least number of tasks and assigns that process to handle the session. The Round-Robin algorithm distributes all Object Manager login requests to the Object Manager process in a round-robin fashion, that is, equal loads distributed in order and without priority. The algorithm that SCBroker uses to forward the socket to the OM processes. (LL, RR)

·         Application Object Manager (AOM)

o        An Application Object Manager (AOM) server component is implemented as a multithreaded process on the Siebel Server. One of the most important types of server components is the Application Object Manager (AOM). These server components run in interactive mode. They process user requests and are application- or service-specific. For example, the Siebel Employee Relationship Management component group contains the Employee Relationship Object Manager. This AOM provides the session environment in which this application runs. AOMs also contain a [DATA MANAGER] and the Siebel Web Engine. When an AOM receives a user request to start an application, the AOM follows this procedure:

§         The Business object layer start an application user session, process any required business logic, and sends a data request to the data manager.

§         The data manager creates an SQL query and forwards it the database server.

§         The data manager receives the data from the database and forwards it to the business object layer for additional processing.

§         The business object layer forwards the result to the Siebel Web Engine, which helps create the UI for the data. The Siebel Web Engine then forwards the Web pages to the Siebel Web Server Extension on the Web server.

3.    Siebel Web Server Extension [SWSE]:

·         Siebel Web Server Extension (SWSE) enables communication between Siebel Web Clients and Siebel Servers. The Siebel Business Applications are a family of Web-based applications that users access through a standard Web browser. plug-in extension that runs within the Web server and that communicates with the Siebel Web Engine (which is part of an Application Object Manager component, such as Call Center Object Manager) on the Siebel Server. This chapter describes installing and configuring the SWSE on the Web server machine.

·         Siebel Web Engine (Application Object Manager/Siebel Server) The Siebel Web Engine is part of the Application Object Manager (AOM) component on the Siebel Server, such as Call Center Object Manager. The AOM provides access to Siebel applications data and logic.

Siebel FAQ's

Siebel FAQ's

1.what happens when u have search spec set in bc level and applet level?
2.will it be over written in applet level or will it be appended?
3.what is the difference between string reference and string override properties? these will be there for most of the objects
4.how many types of applets are there?
5.what is the difference between control and list child object types in Applet?
6.in control or list column how do you associate a field in applet from bc?
7.how do you configure dynamic drill down ?
8.how do you configure static drill down ?
    -- example for both of them
9.what is application object?
10.what is the difference between page tab and screen menu item child object types in Application object type?
11.what is Buscomp view mode child object type in BC?
12.what does field child object type has in BC?
13.where can you see implicit joins?
14.what is the difference between implicit join and explicit join?
15.what is Multi Value Field?
16.what is Multi Value Link?
17.what is single value field object type in bc?
18.what is link and tell me important properties that you used?
19.can you give different name in alias of join?
20.why do you set outer join flag?
21.what is join constraint?
22.what is join specification?
23.what mvc pickmap?
24.why do you use project object in tools?
25.what is admin mode flag?
26.what is visibility applet property in view?
27.what is the difference between string reference and string override?
28.what is add to history property in view?
29.what is item identifier in view web template item child object type?
30.what is applet mode property signifies in view web template item child object type of view?
31.what bounded property in pick list?
32.what long list property in pick list?