Sunday, 15 December 2013

Siebel Web Architecture - Overview

The Siebel Web Architecture

At a high level, the Siebel Web architecture consists of:


  •  Siebel Web Clients that access and display the business data
  • A Gateway Name Server that stores configuration information
  • A Web server that handles interactions with the Web Clients and distributes requests to the Siebel Servers
  • Servers that manage the business data and provide batch and interactive services for clients
  • A relational database and file system that store business data

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 a Siebel-specific virtual directory on the Web server
·         Virtual directories are created as part of the Siebel installation

·         Virtual directory forwards request to the Siebel Web Server Extension (SWSE) installed on the Web server
·         SWSE uses the eapps.cfg configuration file to obtain connection parameters

Eapps.cfg specifies the location of the server, server connection broker port, Enterprise, and Object Manager information for initial connection
  •  For multi-server installations provides load balancing information
  • Also provides generic login information for initial “anonymous” access to database



Siebel Gateway Name Server
Stores component definitions and assignments, operational parameters, and connectivity information
  •  For example, connect strings to query servers for server/component availability
  •  Information stored in siebns.dat file on Gateway Name Server
Siebel Enterprise
  • Is a logical collection of Siebel Servers that support users and access a single database server and the Siebel file system
  • Logically groups Siebel Servers for common administration via Siebel Server Manager
  • Supports sharing of common configuration information
Siebel Servers
Execute tasks to manage the business data
  • Programs known as server components perform specific functions or jobs for the server
  •  For example:
    •  Importing and exporting data
    • Configuring the database to monitor for user-defined conditions
    •  Processing of client requests
  •  Tasks may run interactively, in the background, or as batch jobs
Siebel File System
Is one or more shared directories that store files used by Siebel applications

  •  Files are compressed in a proprietary format to save space and provide security
  •  Examples: Product literature, sales tools, presentations, user profiles
Database Server
  • Stores data used by Siebel applications in a predefined database schema
    • Single database for Enterprise provides data consistency for users
    •  Data is accessed by components through a data manager layer
  • Supports a variety of third-party relational database management systems (RDBMS)


No comments:

Post a Comment