Today, I will discuss about Siebel Enterprise. Just for a quick refresh, Siebel Enterprise Environment contains:-
1.Siebel Gateway Server
2.Siebel Server
3.Siebel Native Load Balancer
4.3rd Party HTTP Load Balancer
5.Siebel Web Server/SWSE/SWE
6.Siebel File System
7.Siebel Database
8.Siebel Report Server
9.Web Client
10.Mobile Web Client
11.Dedicated Web Client
1. Gateway Server
-Serves as a single entry point for accessing Siebel Servers and provides enhanced scalability, load balancing, and high availability across the Enterprise Server.
-Name Server
-Siebel Gateway Server does not function as a resource intensive server. With clustering technologies and powerful CPU(s), it usually scales up very well.
2. Siebel Server
§The Siebel Server is the middle-tier platform that supports both back end and interactive processes for every Siebel client. These processes are component within the Siebel Server architecture, and support functions such as:
§Mobile web client synchronization
§Operation of business logic for Siebel web clients, as well as connectivity and access to the database server and file system
§Integration with legacy or third-party data
§Automatic assignment of new accounts, opportunities, service requests, and other records
§Workflow management
§And more…
§Siebel server runs as a service on Microsoft NT/Windows 2000 platform and runs as background daemon processes on Unix platforms.
§Unlike Siebel Gateway Name Server, Siebel server is a heavy-duty constituent of Siebel Enterprise. This is particularly true in Siebel7, as it needs even more processing power than in prior releases due to the fact that Siebel7 fully supports the three-tiers architecture.
§With proper load balancing, Siebel Server can scale up with more powerful CPU(s) and scale out with more servers.
3. Server Component
§The various programs that operate on the Siebel Server are implemented as components. A component represents only a specific type of program; a component is executed or operated as a task, or instantiation of a component, on a specific Siebel Server.
§Server Request Broker
§Server Request Processor
§Server Connection Broker
§File System Manager
4. Server Component Group
§ A collection of components that provide related Siebel Server functionality and are grouped together for ease of administration.
§For Example:
§ Assignment Management
Made up of the following components: Assignment Manager, Batch Assignment
§ Siebel Call Center
Made up of the following components: Call Center Object Manager, Service OM
§ Siebel Remote
Made up of the following components: Database Extract, Generate New Database, Parallel Database Extract, Replication Agent, Synchronization Manager, Transaction Merger, Transaction Processor, Transaction Router
§Call Center Object Manager
§Assignment Manager
§Workflow Manager
§Communication Manager
§EAI Object Manager
5. Siebel Object Manager
§ A Siebel component that runs on Siebel server
§Instantiates and processes UI, Business Objects, and Data Object layers
§Handles communications with the Siebel Web Server Extension and the database.
§Manages user connections
§Multi-Process
§Multiple SOM processes per Server Component
§Dynamic load balancing allows Siebel Object Manager to run across multiple machines
§Multi-Threaded
§Process overhead spreads across all threads in a process, reducing server CPU and RAM requirements
6. Siebel Native Load Balancer
§New in Siebel 7.7
§A software component that provides load balancing
Scalability
-Allows Siebel to easily support very large numbers of concurrent users
-Can easily add additional servers
Utilization
-By distributing load to unused resources makes optimal use of available hardware
Performance
-By distributing load to unused resources minimizes hardware bottlenecks
Without the maintenance overhead of Resonate
-Resonate Central Dispatch is no longer supported as of Siebel 7.7
§Availability
If a load-balanced component becomes unavailable on one server, it can still be accessed through other load-balanced servers
§Security
Simple firewall configuration – 1 VIP/Vport only
Allows change of port used (I.e. HTTP Tunneling)
Round-robin through SWSE naming directory
Load balance by number of running tasks of OM instances
Listen to both static and configurable port
Support SISNAPI reconnect out of box
§When to Use
When all destination servers are of the same capacity
When customer does not want to purchase a HTTP 3rd Party load balancer
7. 3rd Party HTTP Load Balancer
§New in Siebel 7.7
§A hardware component that provides load balancing
Scalability
Allows Siebel to easily support very large numbers of concurrent users
Can easily add additional servers
Utilization
By distributing load to unused resources makes optimal use of available hardware
Performance
By distributing load to unused resources minimizes hardware bottlenecks
Availability
If a load-balanced component becomes unavailable on one server, it can still be accessed through other load-balanced servers
Security
Simple firewall configuration – 1 VIP/Vport only
Allows change of port used (I.e. HTTP Tunneling)
Supports complex network technologies (I.e. NAT)
§Provides Network Switching Capabilities
§Provides Flexible Configuration Options
Allow customer to segment load-balanced Siebel servers
§Can Be Integrated With Other 3rd Party Monitoring And Management Tools
§Integrates Load Balancing With High Availability Solutions (Veritas)
§Currently Certified
F5 Big-IP
CISCO CSS
§When to Use
Different capacity across Siebel servers (CPUs, heterogeneous OS, etc)
When NAT is required
8. Siebel Connection Broker (SCBroker)
§Siebel Connection Broker is a server component
At least one instance of it must be running
By default is on
§Load balance is by least # of running tasks for all processes belong to a particular component
§Load balancing scheme is not configurable
§By default listens on static port 2321
9. Siebel Web Server Extension (SWSE)
§Siebel Web Server Extension (SWSE) is a plug-in that runs within the Siebel Web Server Interacts with Web server for all incoming and outgoing Web requests
Direct requests via the Siebel Object Manager to the Siebel Web Engine. It handles all files with .SWE extension in the URL.
Manages network connections to the application servers
Requests a new network connection for each new user session
Connection is generally persistent, until processes terminated at either end points or SISNAPI connection timeout
§Contains two layers
Web framework layer –interacts with web client infrastructure
Session manager layer – manages SISNAPI connections to the application server
Siebel-Provided load balancing logic resides in the Session Manager layer
9. Siebel File System
§The Siebel File System consists of a shared directory that is network-accessible to the Siebel Server and contains the physical files used by Siebel clients. To gain access to files, web clients connect directly to the appropriate Siebel Server to request file uploads or downloads. The Siebel Server then accesses the Siebel File System using the File System Manager (FSM) server component. File System Manager will process these requests through interaction with the Siebel File System directory.
§When using Siebel Mobile Web Client in connected mode (also known as the Dedicated Web Client), you may want to connect directly to the Siebel File System without going through the File System Manager
10. Siebel Database
§The backend data store for Siebel Enterprise
§Customer Data
§Seed Data
11. Siebel Report Server
§Actuate Report Server
§Generates and manages reports
§Contains the Report Encyclopedia, which is a shared repository that stores report items along with related data, such as access privileges and request queues
§Actuate Active Portal
§Provides access to the Siebel Reports Server from the World Wide Web
§Allows users to access and work with reports through any web browser
§Actuate Management Console
§Offers the capability to manage one or more Actuate Report Server and Encyclopedia
§Siebel Report Server Access
§A Siebel integration component that includes Siebel Report executables, templates, and other Siebel-specific library files.
§Communication between Siebel Object Manager and Reports Server
§Pre Siebel 7.7: Report Server API
§Siebel 7.7: SOAP
§Clustering support in Siebel 7.7
§Siebel Repository
§No Business Logic
§Multiple RDBMS vendors
§Oracle
§DB2
§MS SQL Server
In my subsequent posts I will try to put detailed working of how each components work. Till then goodbye! (Do share your knowledge - clicking in the comments link below the post)
Posts
