Upgrading from Siebel 2000 to 7

Siebel Web Architecture

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 Web Client

Web Server

Siebel Gateway
Name Server

Enterprise
Siebel Server(s)

Siebel File
System

Database
Server

Module 5: Exploring the Siebel Architecture

2 of 33

Siebel Clients
Display 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
Web Server

Siebel Gateway
Name Server

Enterprise
Siebel Server(s)

Siebel File
System

Database
Server

Module 5: Exploring the Siebel Architecture

3 of 33

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

Siebel Web Client

Web Server

Siebel Gateway
Name Server

Enterprise
Siebel Server(s)

Siebel File
System

Database
Server

Module 5: Exploring the Siebel Architecture

4 of 33

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)
Siebel Web Client

Web Server

Siebel Gateway
Name Server

Virtual Directories
SWSE
Eapps.cfg

Module 5: Exploring the Siebel Architecture

5 of 33

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

Siebel Web Client

Web Server

Siebel Gateway
Name Server

Virtual Directories
SWSE
Eapps.cfg

Module 5: Exploring the Siebel Architecture

6 of 33

Siebel Web Server Extension (SWSE)

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

Siebel Web Client

Web Server

Siebel Gateway
Name Server

Virtual Directories
SWSE
Eapps.cfg

Module 5: Exploring the Siebel Architecture

7 of 33

Eapps.cfg

Used by the SWSE

Is a single configuration file for all Siebel applications

Contains configuration information, including: connectivity

information, login, and security settings
Contains a connect string for each Siebel application

Siebel Web Client

Web Server

Siebel Gateway
Name Server

Virtual Directories
SWSE
Eapps.cfg

Module 5: Exploring the Siebel Architecture

8 of 33

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 Web Client

Web Server

Siebel Gateway
Name Server

Enterprise
Siebel Server(s)

Module 5: Exploring the Siebel Architecture

9 of 33

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 Web Client

Web Server

Siebel Gateway
Name Server

Enterprise
Siebel Server(s)

Siebel File
System

Database
Server

Module 5: Exploring the Siebel Architecture

10 of 33

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 Web Client

Web Server

Siebel Gateway
Name Server

Enterprise
Siebel Server

Siebel File
System

Database
Server

Module 5: Exploring the Siebel Architecture

11 of 33

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 Web Client

Web Server

Siebel Gateway
Name Server

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

Module 5: Exploring the Siebel Architecture

12 of 33

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 Web Client

Web Server

Siebel Gateway
Name Server

Enterprise
Siebel Server
.SRF
.CFG
.SWT
Server Components

Module 5: Exploring the Siebel Architecture

13 of 33

Siebel Repository File (.SRF)

Separate binary file that 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

14 of 33

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

15 of 33

Siebel Web Templates (.SWT)

Set of template files that specify how to render the UI in the

users browser
HTML files with embedded Siebel tags defining content

Enterprise
Siebel Server
.SRF
.CFG
.SWT
Server Components

Module 5: Exploring the Siebel Architecture

16 of 33

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
.SRF
.CFG
.SWT
Server Components

Module 5: Exploring the Siebel Architecture

Examples:
Application Object Manager
File System Manager
Synchronization Manager
Assignment Manager
Enterprise Integration Mgr

17 of 33

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

Used by thin clients (Mobile client uses Siebel.exe)
Enterprise

Siebel Server
Server Components
AOM
File System Manager

Module 5: Exploring the Siebel Architecture

Within the AOM, UI

layer is supported by
the Siebel Web Engine.
Data layer is supported
by the Data Manager.

18 of 33

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
Database
Server

Server Components
AOM
File System Manager

The Data Manager, within

the AOM, controls access
to the Database Server
Module 5: Exploring the Siebel Architecture

19 of 33

0/3

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
Easier security administration

Only the user with administrative privileges for the Siebel Server needs
access privileges to the file system directories
Enterprise

Siebel Server
Server Components
AOM
File System Manager

Module 5: Exploring the Siebel Architecture

Files System Manager

controls access to the
Siebel File System

Siebel File
System
20 of 33

1/3

Uploading an Attachment Using the FSM

Attachments are copied from the user's hard drive and
transferred to the Siebel Server
The FSM component compresses the file, and then stores the
compressed file in the Siebel File System

Compression and renaming of the files is automated by the FSM

Siebel Gateway
Name Server

Web Server

Siebel Web Client

Enterprise
File

Siebel Server
1. File uploaded
from local machine

Server Components
AOM
File System Manager

2. FSM compresses
and renames file

Siebel File
System

3. File stored in
the File System

File

Database
Server
Module 5: Exploring the Siebel Architecture

21 of 33

2/3

Downloading an Attachment Using the FSM

The attachment download request is received by the FSM,
which retrieves the requested file

Decompresses the file and restores its original name

The file is sent back to the user's Web browser

Siebel Gateway
Name Server

Web Server

Siebel Web Client

Enterprise
File

Siebel Server
3. File downloaded
to local machine

Server Components
AOM
File System Manager

2. FSM decompresses
and renames file

Siebel File
System

1. File retrieved
from File System

File

Database
Server
Module 5: Exploring the Siebel Architecture

22 of 33

3/3

Configuring File System Connectivity

Web Clients always connect using the FSM
Mobile Web Clients connect directly to their local file system and
synchronise files using the Synchronisation Manager
Dedicated Web Clients can connect directly to the file system or
use the FSM

Modify the FileSystem parameter in the .cfg file

Directly access
the file system

[ServerDataSrc]
FileSystem

= \\ORBMBFS01\siebfile\att

[ServerDataSrc]
FileSystem

= *FSM*

Module 5: Exploring the Siebel Architecture

Access the file

system using the
FSM

23 of 33

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
<browser>

http://websrvr1/callcenter_enu
Web Server
Virtual Directory

1. Browser sends
URL to Web server

[/callcenter_enu]
<websrvr1>

2. Connects to the virtual directory

on the specified Web server

Module 5: Exploring the Siebel Architecture

24 of 33

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

[/callcenter_enu]

Eapps.cfg

<websrvr1>

4. SWSE locates the requested

section in eapps.cfg

Module 5: Exploring the Siebel Architecture

25 of 33

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>
Web Server
<websrvr>

Siebel
Gateway
Name
Server
<gtwysrvr>

Module 5: Exploring the Siebel Architecture

Siebel Server <SS1>

Application
Object Manager
SCCObjMgr_enu

26 of 33

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
Manager reads CFG file
(or component
parameters)

Module 5: Exploring the Siebel Architecture

Application
Object Manager
SCCObjMgr_enu
.CFG

Database
Database
Server
Server

.SRF

27 of 33

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

HTML login
page

Application
Object Manager

SWE
.SRF

.CFG

.SWT

Module 5: Exploring the Siebel Architecture

Database
Database
Server
Server

7. SWE reads
Web Templates
and creates
HTML pages

28 of 33

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
page

Application
Object Manager
SCCObjMgr_enu

<websrvr1>

Module 5: Exploring the Siebel Architecture

29 of 33

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
Name Server

Web Server

High-speed LAN

Enterprise Server
Siebel Server

SWSE

Siebel File
System
Firewall

Firewall

Module 5: Exploring the Siebel Architecture

Siebel Server
Database
Server
30 of 33