Siebel Web Architecture

Siebel Web ArchitectureSiebel Web Architecture

Upgrading from Siebel 2000 to 7Upgrading from Siebel 2000 to 7

Module 5: Exploring the Siebel Architecture 2 of 33

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 ServerSiebel Gateway

Name Server

Database Server

Enterprise

Siebel File System

Siebel Server(s)


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 Siebel Web ClientClient

Web ServerSiebel Gateway

Name Server

Database Server

Enterprise

Siebel File System

Siebel Server(s)


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 ServerWeb ServerSiebel Gateway

Name Server

Database Server

Enterprise

Siebel File System

Siebel Server(s)


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

Virtual Directories

SWSE

Eapps.cfg

Siebel Web ClientSiebel Gateway

Name Server


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


Virtual Directories

SWSE

Eapps.cfg


Name Server


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


Virtual Directories

SWSE

Eapps.cfg


Name Server


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


Virtual Directories

SWSE

Eapps.cfg


Name Server


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 ServerSiebel Gateway Siebel Gateway

Name ServerName Server

Enterprise

Siebel Server(s)


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


Name Server

Database Server

EnterpriseEnterprise

Siebel File System

Siebel Server(s)


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)


Name Server

Database Server

Enterprise

Siebel File SystemSiebel ServerSiebel Server


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


Name Server

Database Server

Enterprise

Siebel ServerSiebel Server

.SRF

.CFG

.SWT

Server Components


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


Name Server

Enterprise


.SRF

.CFG

.SWT

Server Components


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


.SRF

.CFG

.SWT

Server Components


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


.SRF

.CFG

.SWT

Server Components


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


.SRF

.CFG

.SWT

Server Components


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


.SRF

.CFG

.SWT

Server Components

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


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 ComponentsServer Components

AOM

File System Manager

Within the AOM, UI layer is supported by the Siebel Web Engine. Data layer is supported by the Data Manager.


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)

Database Server

Enterprise

Siebel Server


AOM

File System Manager

The Data Manager, within the AOM, controls access to the Database Server


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


AOM

File System Manager Siebel File Siebel File SystemSystem

Files System Manager controls access to the Siebel File System

0/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

Enterprise

Siebel Server


AOM



Name Server

File

File

2. FSM compresses and renames file

1. File uploaded from local machine

3. File stored in the File System

1/3

Database Server


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

Enterprise

Siebel Server


AOM



Name Server

File

File

2. FSM decompresses and renames file

3. File downloaded to local machine

1. File retrieved from File System

2/3

Database Server


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

[ServerDataSrc]FileSystem = \\ORBMBFS01\siebfile\att

[ServerDataSrc]FileSystem = *FSM*

Directly access the file system

Access the file system using the

FSM

3/3


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

1. Browser sends URL to Web server

Siebel Web Client <browser>

Web Server

<websrvr1>

Virtual Directory [/callcenter_enu]

http://websrvr1/callcenter_enu

2. Connects to the virtual directory on the specified Web server


Web Server

<websrvr1>

Virtual Directory [/callcenter_enu]

SWSE Eapps.cfg

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

4. SWSE locates the requested section in eapps.cfg

Siebel Web Client <browser> 3. Virtual directory

specifies to use SWSE



Siebel Server <SS1>

Enterprise – <Siebel>

Application Object ManagerSCCObjMgr_enu

Web Server

<websrvr>

Siebel Gateway

Name Server

<gtwysrvr>

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



Application Object Manager reads configuration file and component parameters, which specify SRF location, application, and so forth

Siebel Server

Enterprise <Siebel>


.CFG .SRF

Database Server

Database Server

6. Application Object Manager reads CFG file

(or component parameters)



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

Siebel Server

Application Object Manager

SWE

.SWT

Database Server

Database Server

7. SWE reads Web Templates

and creates HTML pages

Enterprise <Siebel>

.CFG .SRF

HTML login page


Web Server

<websrvr1>


Siebel Server <SS1>

Enterprise – <Siebel>


HTML login page

Siebel Call Center

Application Object Manager sends the completed Web page to the Web server, which passes it back to the Web client


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

Enterprise Server

FirewallFirewall

High-speed LAN

Web Server

SWSE Siebel Server

Siebel File System

Database Server

Siebel Server

Date post:	19-Oct-2014
Category:	Technology
View:	35,390 times
Download:	3 times

Siebel Web Architecture

Technology