Siebel Architecture and Servers – An Overview

This article will help to understand the Siebel architecture and servers; we will also discuss the physical architecture of Siebel setup and the basic understanding of Siebel clients, Web Server, Siebel Web Server Extensions (SWSE), .cfg, Siebel Enterprise Server, Siebel Gateway Name Server, Siebel Database Server.

 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 Architecture

 Further drilling down on the Siebel environment we have

The Siebel Business Applications environment consists of the following entities:

Siebel Clients :

  • Includes Siebel Web client, Siebel Developer Web Client, Wireless Client, Mobile Web Client, handheld client, and Siebel Tools Client
  • Displays the interactive Siebel application used to manage the Siebel data Runs in a variety of environments
    • Web browsers
    • WML devices
    • PDAs (Windows CE and Palm)

Siebel Web Server:

  • Identifies and passes Siebel requests from Web clients to the Siebel servers Passes completed HTML application pages back to Web clients
  • Consists of a third-party Web server with the following additional Siebel components
    • Virtual directories
    • Siebel Web Server Extensions (SWSE)
    • Configuration file (.CFG)

 Siebel Enterprise Server:

  • 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 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 \\sea**\gtwysrvr\ADMIN
  • Includes the connection broker and name server for a single server deployment. (The name server is a separate entity for multiple server deployments.).

Siebel Database Server:

  • Includes the RDBMS client software and Siebel tables, indexes, and seed data.
  • Stores data used by Siebel eBusiness Applications in a predefined database schema
  • Supports a variety of third-party relational database management system (RDBMS)

 Siebel File System:

  • Stores the data and physical files used by Siebel clients and Siebel Enterprise Server.
  • Read/write access is controlled by the File System Manager server component
  • Is a shared directory that stores compressed files used by Siebel applications
    • Examples: Product literature, sales tools, presentations


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 Physical Architecture

4 comments on “Siebel Architecture and Servers – An Overview”

  1. Kishor M Reply

    It is good post!!!
    If you include the siebel components that resides in the siebel server, it would be really good.

  2. Vivek Reply

    The above picture is only correct for Wen client . however for dedicated mobile client the access path is different. For Remote client again Sync comp come into picture

  3. Ganesh Reply

    Indeed it is good post!!!!!!!!!!!!!!!!!!
    Also we need OpenUI architecture!!!!!!!!!!!!!!!!

Leave A Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!