Essentials (Siebel 7.

7)

Module 5: Exploring the

Siebel Architecture
Module Objectives

 After completing this module you will be able to:

 Identify the pieces that make up the Siebel Web
architecture
 Identify the process by which Siebel requests are
processed and sent to the Web Client
 Identify the role of each component of the architecture

 Why you need to know:

 Enables you to understand the relationship between
Siebel software components

Module 5: Exploring the Siebel Architecture 2 of 31

Siebel Web Architecture Overview
 At a high level, the Siebel architecture consists of:
 Web clients that access the business data
 A Web server that handles interactions with the Web clients
 Servers that manage the business data and provide batch and
interactive services for clients
 A relational database and file system that store business data
Siebel Gateway
Siebel Web Client Web Server
Name Server

Enterprise

Siebel File
Siebel Server(s)
System

Database
Server

Module 5: Exploring the Siebel Architecture 3 of 31

Siebel Web Client
 Displays the interactive Siebel application used to manage the
Siebel data
 Runs in a variety of environments
 Web browsers, WML devices, and PDAs (Windows CE and Palm)
Siebel Web
Client
Siebel Gateway
Web Server
Name Server

Enterprise

Siebel File
Siebel Server(s)
System

Database
Server

Module 5: Exploring the Siebel Architecture 4 of 31

Web Server
 Identifies and passes Siebel requests from Web clients to the
Siebel servers
 Passes completed HTML application pages back to Web clients

Siebel Gateway
Siebel Web Client Web Server
Name Server

Enterprise

Siebel File
Siebel Server(s)
System

Database
Server

Module 5: Exploring the Siebel Architecture 5 of 31

Siebel Web Server Architecture
 Consists of a third-party Web server with the following additional
Siebel components
 Virtual directories
 Siebel Web Server Extensions (SWSE)
 Configuration file (.CFG)

Web Server Siebel Gateway

Siebel Web Client
Name Server
Virtual Directories
SWSE
Eapps.cfg

Module 5: Exploring the Siebel Architecture 6 of 31

Virtual Directory
 Exists on the Web server to receive inbound Web client
requests for each installed Siebel eBusiness application, and
forwards these requests to SWSE

Web Server Siebel Gateway

Siebel Web Client
Name Server
Virtual Directories
SWSE
Eapps.cfg

Module 5: Exploring the Siebel Architecture 7 of 31

Siebel Web Server Extension (SWSE)
 Receives and parses inbound HTTP requests from Web clients
 Creates and manages TCP connections to the Siebel Servers or
Load Balancer (if implemented)
 Routes requests to the appropriate Siebel Server components

Web Server Siebel Gateway

Siebel Web Client
Name Server
Virtual Directories
SWSE
Eapps.cfg

Module 5: Exploring the Siebel Architecture 8 of 31

Eapps.cfg
 Is the single configuration file for all the Siebel applications
 Contains configuration information, including: connectivity
information, login, and security settings
 Allows the SWSE to communicate with the Siebel Server
 Contains a connect string for each Siebel application

Web Server Siebel Gateway

Siebel Web Client
Name Server
Virtual Directories
SWSE
Eapps.cfg

Module 5: Exploring the Siebel Architecture 9 of 31

Siebel Gateway Name Server
 Is a Windows service or Unix daemon process
 Dynamically registers Siebel Server and component availability
 Stores component definitions and assignments, operational
parameters, and connectivity information
 Stored in siebns.dat file located in \\sea77\gtwysrvr\ADMIN

Siebel Gateway
Siebel Web Client Web Server
Name Server

Enterprise

Siebel Server(s)

Module 5: Exploring the Siebel Architecture 10 of 31

Server Load Balancing
 Evenly distributes the workload across available servers
 Web Server load balancing supported by third-party HTTP load
balancer
 Siebel Server load balancing supports two mechanisms
 Siebel SISNAPI/SSL load balancer built in to the SWSE
 Third-party HTTP load balancer
Siebel Gateway
Siebel Web Client Web Server
Name Server
HTTP load SISNAPI
balancer /SSL Enterprise

Siebel File
Siebel Server(s)
System

Database
Server

Module 5: Exploring the Siebel Architecture 11 of 31

Enterprise Server
 Is a logical collection of Siebel Servers that support users
accessing a single database server and a single file system
 Logically groups Siebel Servers for common administration via
Siebel Server Manager
 Supports sharing of common configuration information

Siebel Gateway
Siebel Web Client Web Server
Name Server

Enterprise

Siebel File
Siebel Server(s)
System

Database
Server

Module 5: Exploring the Siebel Architecture 12 of 31

Siebel Servers
 Execute tasks to manage the business data
 Interactive processing (for example: supports the Web client
running Siebel Call Center)
 Background processing (for example: workflow and business
process automation)
 Batch processing (for example: volume data importing)
Siebel Gateway
Siebel Web Client Web Server
Name Server

Enterprise

Siebel File
Siebel Server
System

Database
Server

Module 5: Exploring the Siebel Architecture 13 of 31

Siebel Server Architecture
 Consists of the following entities:
 Siebel Server
 Siebel Repository File (.SRF)
 Configuration File (.CFG) and Component Parameters
 Siebel Web Templates (.SWT)
 Server components

Siebel Gateway
Siebel Web Client Web Server
Name Server

Enterprise

Siebel Server
.SRF
.CFG
Database
.SWT
Server
Server Components

Module 5: Exploring the Siebel Architecture 14 of 31

Siebel Server
 Is a Windows service or Unix daemon process
 Is the platform that supports interactive, batch, and background
processing for all Siebel clients
 Controls server components running on a machine

Siebel Gateway
Siebel Web Client Web Server
Name Server

Enterprise

Siebel Server
.SRF
.CFG
.SWT
Server Components

Module 5: Exploring the Siebel Architecture 15 of 31

Siebel Repository File (.SRF)
 Separate binary file which defines one or more Siebel
applications
 Specifies the:
 Data presentation
 Business rules and processes
 Data organization and storage
Enterprise

Siebel Server
.SRF
.CFG
.SWT
Server Components

Module 5: Exploring the Siebel Architecture 16 of 31

 Siebel Configuration File (.CFG) and Component
Parameters
 Specify initialization settings of the application at run time, for
example:
 Application parameters
 Security settings
 Siebel Gateway Name Server
 Enterprise Server
Enterprise

Siebel Server
.SRF
.CFG
.SWT
Server Components

Module 5: Exploring the Siebel Architecture 17 of 31

Siebel Web Templates (.SWT)
 Set of template files that specify how to render the UI in the
user’s browser
 HTML files with embedded Siebel tags defining content

Enterprise

Siebel Server
.SRF
.CFG
.SWT
Server Components

Module 5: Exploring the Siebel Architecture 18 of 31

Server Component
 Is a program that executes on a Siebel Server
 Performs a specific function or job
 Examples include:
 Importing and exporting data
 Configuring the database to monitor for user-defined conditions
 Processing of client requests
Enterprise

Siebel Server Examples:

.SRF • Application Object Manager
.CFG • File System Manager
• Synchronization Manager
.SWT
• Assignment Manager
Server Components • Enterprise Integration Mgr

Module 5: Exploring the Siebel Architecture 19 of 31

Application Object Manager
 Is a server component that creates and processes data at
multiple levels
 UI layer
 Business layer
 Data layer
 Provides the environment in which Siebel applications run
Enterprise

Siebel Server
Server Components Within the AOM, UI
layer is supported by
AOM the Siebel Web Engine.
File System Manager Data layer is supported
by the Data Manager.

Module 5: Exploring the Siebel Architecture 20 of 31

Database Server
 Stores data used by Siebel eBusiness Applications in a
predefined database schema
 Supports a variety of third-party relational database
management system (RDBMS)

Enterprise

Siebel Server
Server Components
Database AOM
Server File System Manager

The Data Manager, within

the AOM, controls access
to the Database Server

Module 5: Exploring the Siebel Architecture 21 of 31

Siebel File System
 Is a shared directory that stores compressed files used by
Siebel applications
 Examples: Product literature, sales tools, presentations
 Read/write access is controlled by the File System Manager
server component

Enterprise

Siebel Server
Server Components
AOM
Siebel File
File System Manager
System

Files System Manager

controls access to the
Siebel File System
Module 5: Exploring the Siebel Architecture 22 of 31
Web Usage Login Scenario
 Siebel Web Client (browser) sends the URL to the Web server
 URL specifies:
 Either http or https protocol
 Web server machine name
 Application and language

 URL initially connects to the virtual directory on the Web server

Siebel Web Client http://websrvr1/callcenter_enu

<browser>

Web Server
Virtual Directory
[/callcenter_enu]
1. Browser sends <websrvr1>
URL to Web server
2. Connects to the virtual directory
on the specified Web server

Module 5: Exploring the Siebel Architecture 23 of 31

Web Usage Login Scenario Continued
 Virtual directory forwards request to the Siebel Web Server
Extension (SWSE) installed on the Web server
 SWSE uses the eapps.cfg file to obtain connection parameters

Siebel Web Client

<browser> 3. Virtual directory
specifies to use SWSE

Web Server
Virtual Directory
SWSE Eapps.cfg
[/callcenter_enu]
<websrvr1>

4. SWSE locates the requested

section in eapps.cfg

Module 5: Exploring the Siebel Architecture 24 of 31

Web Usage Login Scenario Continued
 Eapps.cfg specifies the location of the Gateway, Gateway port
number, Enterprise, Application Object Manager, and load
balancer information for initial connection
 Contains Siebel Server information in the case of no load
balancing

5. eapps.cfg specifies
connect string values

Enterprise – <Siebel>

Siebel Siebel Server <SS1>

Web Server
Gateway
Name Application
Server Object Manager
<websrvr> SCCObjMgr_enu
<gtwysrvr>

Module 5: Exploring the Siebel Architecture 25 of 31

Web Usage Login Scenario Continued
 Application Object Manager reads configuration file and
component parameters, which specify SRF location, application,
and so forth

Enterprise <Siebel>

Siebel Server

6. Application Object Application

Database
Object Manager Database
Manager reads CFG file SCCObjMgr_enu
Server
Server
(or component
parameters)
.CFG .SRF

Module 5: Exploring the Siebel Architecture 26 of 31

Web Usage Login Scenario Continued
 The SWE, as part of the Application Object Manager, reads a
set of Web templates that are stored on the Siebel Server and
creates HTML pages for the data requested

Enterprise <Siebel>

Siebel Server
Application
Object Manager Database
Database
Server
HTML login
SWE Server
page

7. SWE reads
.CFG .SRF
Web Templates
and creates
.SWT HTML pages

Module 5: Exploring the Siebel Architecture 27 of 31

Web Usage Login Scenario Continued
 Application Object Manager sends the completed Web page to
the Web server, which passes it back to the Web client

Siebel Call Center

Enterprise – <Siebel>

Web Server Siebel Server <SS1>

HTML login Application
page Object Manager
<websrvr1> SCCObjMgr_enu

Module 5: Exploring the Siebel Architecture 28 of 31

Physical Architecture

 The Siebel Gateway Name Server, Siebel Server, Database

Server, and File System can be implemented on one machine
or spread across multiple machines
 The Siebel Server(s) should have a high-speed LAN
connection to the Database Server

Siebel Gateway
High-speed LAN
Name Server

Web Server Enterprise Server

SWSE Siebel Server

Siebel File
System

Firewall Siebel Server

Firewall
Database
Server

Module 5: Exploring the Siebel Architecture 29 of 31

Summary

 This module showed you how to:

 Identify the pieces that make up the Siebel Web
architecture
 Identify the process by which Siebel requests are
processed and sent to the Web Client
 Identify the role of each component of the architecture

Module 5: Exploring the Siebel Architecture 30 of 31

Lab
 In the lab you will:
 Verify the architecture components

Module 5: Exploring the Siebel Architecture 31 of 31