Scribd
Upload
7 views2 pages

Siebel Server Architecture

Uploaded by

abhishek040599
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
7 views2 pages

Siebel Server Architecture

Uploaded by

abhishek040599
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Explain the Siebel server architecture:

---------------------------------------

The Siebel Server architecture is a multi-tiered design that enables scalability,


flexibility, and integration for enterprise applications. Below is an explanation
of its primary components and their roles:

---

### **1. Client Tier**


- **Components:** Web browsers, Siebel Mobile clients, or dedicated Siebel clients.
- **Functionality:**
- Acts as the user interface (UI) layer where end-users interact with the Siebel
application.
- Communicates with the Siebel Web Server through HTTP/HTTPS.

---

### **2. Web Server Tier**


- **Components:** Siebel Web Server Extension (SWSE).
- **Functionality:**
- Acts as the intermediary between the client tier and the Siebel Server.
- Handles incoming HTTP requests from clients, interprets them, and forwards them
to the appropriate Siebel Server.
- Provides session management and load balancing across multiple Siebel Servers.

---

### **3. Siebel Gateway Server**


- **Functionality:**
- Acts as the central configuration manager for the Siebel enterprise.
- Maintains metadata about the Siebel environment, including server
configurations, components, and connectivity.
- Used for communication and coordination between multiple Siebel Servers.

---

### **4. Siebel Server Tier**


- **Components:** Siebel Application Server processes and components.
- **Functionality:**
- Executes business logic and handles core functionalities like workflow
processing, data manipulation, and batch operations.
- Includes a variety of server components categorized into:
- **Background Components:** Handle asynchronous tasks (e.g., workflows,
reports).
- **Interactive Components:** Process user interactions in real time (e.g.,
EAI, EIM).
- **Infrastructure Components:** Manage system-level processes like task
routing and load balancing.
- Allows component-based modular deployment for scalability and resource
optimization.

---

### **5. Database Server Tier**


- **Components:** Oracle, Microsoft SQL Server, or IBM Db2 databases.
- **Functionality:**
- Stores all application data, including user data, metadata, and configuration
settings.
- Siebel Servers interact with the database for CRUD (Create, Read, Update,
Delete) operations.

---

### **6. External Systems**


- **Examples:** LDAP servers, email servers, third-party applications, and legacy
systems.
- **Functionality:**
- Facilitates integration with external systems using Siebel’s integration
capabilities like Siebel EAI (Enterprise Application Integration) and Siebel
Workflow.
- LDAP provides authentication and user directory services.
- Email servers handle notifications and communications.

---

### **Data Flow Overview**


1. **User Interaction:** The client sends a request via the web browser or
dedicated client.
2. **Request Processing:** The SWSE receives the request, validates it, and
forwards it to the Siebel Server.
3. **Business Logic Execution:** The Siebel Server processes the request using its
components and accesses the database server if necessary.
4. **Response Delivery:** The result is sent back to the SWSE, which then delivers
it to the client.

---

### **Key Features**


- **Scalability:** Supports horizontal scaling by adding more servers to each tier.
- **Fault Tolerance:** Redundancy in components ensures high availability.
- **Flexibility:** Modular architecture allows for tailored deployments to meet
specific business needs.
- **Integration:** Built-in tools and APIs facilitate interaction with external
systems.

This architecture ensures efficient handling of enterprise applications while


maintaining performance and reliability.

You might also like