Section 2: Architecture and Installation

Module 9: Exploring the Siebel Architecture

1
 Module Objectives
After completing this module you will be able to:
Identify the pieces that make up the Siebel architecture
Identify how clients access Siebel Servers

Why you need to know:

Enables you to successfully install Siebel software

2
 Logical Server Architecture

Gateway Server:
Provides access to and
availability of Siebel Gateway Server
Servers

Enterprise Server: Enterprise Server Siebel Server:

Group of Siebel Siebel Server Siebel Server Runs one or more
Servers that access Component Component components that
the same Database supply services to
Server clients

Database Server: Database File System: Shared

Server
Predefined tables Siebel directory that stores
and columns that File System compressed files
store Siebel data used by Siebel
applications

3
 Open Database Connectivity (ODBC)
A standard application programming interface (API) for accessing
databases
An ODBC driver (piece of software) converts ODBC (generic) calls
into native or database-specific calls
An ODBC data source specifies the driver to use and the database to
connect to
Gateway Server

Enterprise Server
Siebel Server Siebel Server
Component Component

ODBC

Database
Server
Siebel
File System
4
 Gateway Server: Name Server
Serves as a single entry point for accessing Enterprise Server(s)
Dynamically registers Siebel Server and component availability
Stores component definitions and assignments, operational
parameters, and connectivity information
Persistent storage provided by siebns.dat file in shared directory
Runs as a Windows NT Service or Unix daemon process
Gateway Server

Enterprise Server
Siebel Server Siebel Server
Component Component

Database
Server
Siebel

5 File System
 Gateway Server: Connection Brokering
Directs client requests to the least-laden Siebel Server running the
desired component
Does not apply to database connections or mobile client connections
Uses Resonate Central Dispatch (optional third-party software)

Gateway Server

Enterprise Server
Siebel Server Siebel Server
Component Component

Database
Server
Siebel
File System

6
 Server Component
A type of program that executes on a Siebel Server to perform a
specific function or job
Importing and exporting data
Configuring the database to monitor for user-defined conditions
Processing to support thin or mobile clients
Enforcing business rules
Gateway Server

Enterprise Server
Siebel Server Siebel Server
Component Component

Database
Server
Siebel
File System

7
 Siebel Server
Runs one or more server components
Obtains configuration information from the Gateway Server
Uses ODBC to access a single Database Server
Runs as a Windows NT Service or Unix daemon process

Gateway Server

Enterprise Server
Siebel Server Siebel Server
Component Component

Database
Server
Siebel
File System

8
 Enterprise Server
Supports groups of users accessing a single database server
Logically groups Siebel Servers for common administration via
Server Manager
Installed and configured as part of the first Siebel Server install

Gateway Server

Enterprise Server
Siebel Server Siebel Server
Component Component

Database
Server
Siebel
File System

9
 Database Server
Stores Siebel data within a predefined database schema on a third-
party relational database management system (RDBMS)
Supports dedicated client access using native drivers
Supports Siebel Server access through ODBC

Gateway Server

Dedicated
Client Enterprise Server
Siebel Server Siebel Server
Component Component

ODBC

Database
Native Driver Server
Siebel
File System

1
 Siebel File System
Shared directory that stores compressed files used by Siebel
applications
Supports direct read/write access by dedicated and mobile clients
Supports access through Siebel Servers for thin clients

Gateway Server

Enterprise Server
Siebel Server Siebel Server
Component Component

Database
Server
Siebel
File System

1
 Siebel Repository (.srf) File
Compressed object definitions that define the application look,
behavior, and data
Interpreted by the application engine at run time

.srf Application
Engine

1
 Configuration (.cfg) File
Contains initialization settings for the application engine such as:
Gateway Server
Enterprise Server
Application or server component
Repository (.srf) file
Database Server (DataSource)

1
 Dedicated Clients
Access local .cfg and .srf files
Directly access the Database Server and Siebel File system using
native drivers
Access the Gateway Server to determine the correct Siebel Server to
access if a component is desired
Gateway Server

Enterprise Server
Siebel Server
Component

Dedicated
Client
Database
Server
.cfg Siebel
File System

.srf

1
 Dedicated Clients Continued
Launch siebel.exe from program group or startup icon
Startup switch identifies .cfg
.cfg identifies .srf, application, DataSources, Gateway Server, and
Enterprise Server

Dedicated
Client

1
 Mobile Clients
Access local .cfg and .srf files
Directly access a local database and Siebel File System
Directly connect to their designated Siebel Server for synchronization

Mobile Gateway Server

Client
Enterprise Server

.cfg Siebel Server

Component

.srf

Database
Server
Siebel
File System

1
 Mobile Clients Continued
Launch siebel.exe from program group or startup icon
Startup switch identifies .cfg
.cfg identifies .srf, application, local database, and Siebel Server

Mobile
Client

1
 Windows and Java Thin Clients
Access the Gateway Server to determine the Siebel Server that is
running the desired object manager component
Access server-stored .cfg and .srf files
Access the Database Server through the object manager component

Windows /
Gateway Server
Java Thin
Client
Enterprise Server
Siebel Server
Component

Database .cfg .srf

Server
Siebel
File System

1
 Windows and Java Thin Clients Continued
Launch tclient.htm on the Siebel Server from a Web browser
tclient.htm identifies the Gateway Server, Enterprise Server, object
manager component, and Siebel Server
Object manager component parameters identify the .cfg and .srf

Windows /
Java Thin
Client

1
 HTML Clients
Access a Web server that has the Siebel Web Server Extension
installed to access the Gateway Server and Siebel Servers
All access to Siebel data is through the object manager component
Results are transformed by the object manager and returned as HTML
pages
Gateway Server

Enterprise Server Siebel Web

Server
Siebel Server
Extension
Component
Web Server

HTTP
Database .cfg .srf HTML
Server Thin Client
Siebel
File System

2
 HTML Clients Continued
Launch an HTML page from a Web browser that specifies a .swe page
.swe page invokes the Siebel Web Server Extension (SWSE)
SWSE parameters identify the .cfg
.cfg specifies the Gateway Server, Enterprise Server, object manager
component, and Siebel Server

HTML
Thin Client

.swe (SWSE)

2
 All Clients
Siebel architecture is designed to be scaleable to support all clients

Mobile Windows /
Client Java Thin
Gateway Server
Client
.cfg Enterprise Server
Siebel Server
.srf Component

Database .cfg .srf Siebel Web

Dedicated Server Server
Client Siebel Extension
File System
Web Server
.cfg

HTML
.srf Thin Client
(TC)

2
 Physical Architecture
The Gateway 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
Enterprise Server

High-speed LAN
Gateway Server
Siebel Server

Dedicated
Client
Siebel
File System

Siebel Server
Database
Server

2
 You Decide
Consult the documentation to determine which software to install on
which machine(s) given your environment and requirements

2
 Summary
This module showed you how to:
Identify the pieces that make up the Siebel Server architecture
Identify how clients access Siebel Servers