Documente Academic
Documente Profesional
Documente Cultură
7)
Module Objectives
After
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
2 of 31
Siebel Server(s)
Database Server
3 of 31
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 Web Server Enterprise Siebel File System Siebel Gateway Name Server
Siebel Server(s)
Database Server
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 Server(s)
Database Server
5 of 31
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 Virtual Directories SWSE Eapps.cfg Siebel Gateway Name Server
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
7 of 31
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
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
Siebel Web Client Web Server Virtual Directories SWSE Eapps.cfg Siebel Gateway Name Server
9 of 31
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 Enterprise Siebel Gateway Name Server
Siebel Server(s)
10 of 31
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 Web Client HTTP load balancer
Siebel Server(s)
Database Server
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 Web Client Web Server Enterprise Siebel File System Siebel Gateway Name Server
Siebel Server(s)
Database Server
12 of 31
Siebel Servers
Siebel Server
Database Server
13 of 31
Siebel Repository File (.SRF) Configuration File (.CFG) and Component Parameters Siebel Web Templates (.SWT) Server components
Siebel Web Client Web Server Enterprise Siebel Server .SRF .CFG Database .SWT Server Server Components Siebel Gateway Name Server
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
Server Components
15 of 31
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
16 of 31
17 of 31
Set of template files that specify how to render the UI in the users browser
HTML files with embedded Siebel tags defining content
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 .SRF .CFG .SWT Server Components
Examples: Application Object Manager File System Manager Synchronization Manager Assignment Manager Enterprise Integration Mgr
19 of 31
Within the AOM, UI layer is supported by the Siebel Web Engine. Data layer is supported by the Data Manager.
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
The Data Manager, within the AOM, controls access to the Database Server
Module 5: Exploring the Siebel Architecture
21 of 31
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
http://websrvr1/callcenter_enu
Web Server Virtual Directory
[/callcenter_enu]
<websrvr1>
23 of 31
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>
Virtual Directory
[/callcenter_enu]
SWSE <websrvr1>
Eapps.cfg
24 of 31
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 Siebel Gateway Name Server <gtwysrvr> Siebel Server <SS1> Application Object Manager SCCObjMgr_enu
<websrvr>
25 of 31
Application Object Manager reads configuration file and component parameters, which specify SRF location, application, and so forth
26 of 31
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 HTML login page .CFG Database Database Server Server
SWE
.SRF
.SWT
27 of 31
Application Object Manager sends the completed Web page to the Web server, which passes it back to the Web client
Enterprise <Siebel> Web Server Siebel Server <SS1> Application Object Manager SCCObjMgr_enu
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 Name Server
High-speed LAN
Enterprise Server
Siebel Server
Siebel File System Siebel Server Database Server
29 of 31
Firewall
Firewall
Summary
This
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
30 of 31
Lab
31 of 31