2. Company confidential 2 Objective Types of Implementation
Cutover Management SIEBEL Maximum Availability Optimizing SIEBEL
Deployment Real Life Experiences
3. Company confidential 3 Implementation Types Types of
Implementation New Implementation (Green field) Upgrade
Implementation
4. Company confidential 4 Cutover Management cutover will be
managed in the same manner as any other project stage cutover will
be governed by the following 5 stages
5. Company confidential 5 Cutover Strategy Types of Cutover
strategies Big Bang approach A Phased approach
6. Company confidential 6 Cutover Phases Cutover will be done
on the following three phases Pre - Cutover Cutover Post -
Cutover
7. Company confidential 7 Cutover Phases
8. Company confidential 8 Phased Approach
9. Company confidential 9 Maximum Availability Architecture
(MAA) Group of computers that support server applications that can
be reliably utilize with a minimum down-time
10. Company confidential 10 MAA Deployment Options Load
Balancing Client Initiated workload is distributed across multiple
component instances running on multiple servers Distributed
Services Siebel Server initiated workload is distributed across
multiple component instances running on multiple servers Clustering
Server clusters consists of two or more physical servers linked
together so that if one server fails, resources such as disks,
network addresses, Seibel Servers, Siebel gateway can be switched
over to another server
11. Company confidential 11 MAA Deployment options Available
Siebel Component Deployment Options Component Clustering Load
Balancing Distributed Services Gateway Name Server Preferred
Application Object Managers Supported Preferred EAI Object Manager
Supported Preferred Interactive Assignment Supported Preferred
Siebel File System Preferred Siebel Marketing Supported Preferred
Siebel Remote Preferred Workflow Process Manager Supported
Preferred
12. Company confidential 12 SIEBEL Deployment Case Study -1
Upgrading SIEBEL from 7.7.2.8 to 8.1.1.2 The Cutover time is 2 days
(week end) The Market Statistics 100,000+ Outlets/Customers 440
Remote Clients 80+ Web Clients
13. Company confidential 13 SIEBEL Deployment Case Study -1
SIEBEL Gateway Cluster Two clustered sets of SIEBEL Remote Servers
One SIEBEL Server on passive node of the gateway cluster Two SIEBEL
Servers on passive nodes, one on each Remote cluster Three SIEBEL
Web servers
14. Company confidential 14 MA Environment Case -1
15. Company confidential 15 SIEBEL Deployment Case Study -2
Upgrading SIEBEL from 7.7.2.5 to 8.1.1.2 The Cutover time is 3 days
The Market Statistics 400,000+ Outlets/Customers 900 Remote Clients
50+ Web Clients SIEBEL Gateway Cluster (Active Passive) Two
clustered SIEBEL Remote Servers (Active Active) Two SIEBEL Web
Servers on two nodes
16. Company confidential 16 MA Environment Case -2
17. Company confidential 17 SIEBEL Deployment Case Study -3 New
SIEBEL 8.1.1 Implementation (Phased Approach) The Cutover time is 2
days (week end) The Market Statistics 80,000+ Outlets/Customers 400
HH Clients 80+ Web Clients SIEBEL Gateway Cluster (Active Passive)
Two Native Load Balanced SIEBEL Servers One SIEBEL Web Server
18. Company confidential 18 MA Environment Case -3
