Implementing High-Availability (HA) Solutions for Siebel ebusiness Applications

Transcription

1 Implementing High-Availability (HA) Solutions for Siebel ebusiness Applications

2 Agenda Overview of High Availability for Siebel Web Servers Application Object Manager Servers Gateway NS & Non-Object Manager Servers Database Servers Operational Guidance Summary

3 Agenda Overview of High Availability for Siebel Web Servers Application Object Manager Servers Gateway NS & Non-Object Manager Servers Database Servers Operational Guidance Summary

4 Overview of High Availability for Siebel Applications What is High Availability Implies some amount of system fault tolerance Eliminate Single Points Of Failure (SPOF) Short-lived unavailability of non-critical components may be acceptable Availability = ability to log into application and perform normal operations Availability = consistent and acceptable system performance For a 24 x 7 system 99.9% availability = upto 8.76 hours of downtime annually

5 High Availability Strategy - Business Determine and define business availability needs: For example, Call Center = 7 am to 7 pm (Don t forget timezones) Reporting = 9 am to 5 am Determine downtime costs for business Translate business needs to HA needs at unit level and complete system /application level Consider reduced capacity / throughput option

6 High Availability Strategy - Technical Evaluate HA options Perform cost-benefit analysis Architect / prototype HA solution Test HA solution at business transaction and system level Implement HA solution Automated and periodic system monitoring with notifications/corrective actions (of network, servers, applications, components, etc.) Complementary operations and management procedures Periodic post-implementation testing and evaluation

7 Key Technologies Hardware redundancy highly recommended (e.g. RAID, redundant I/O controllers) Web Server load-balancing - Off-the-shelf Web Server load-balancers Application Server load-balancing Clustering / Application Failover (Microsoft MCS, VERITAS VCS, IBM HACMP, Sun SunCluster, HP MC Service Guard)

8 Agenda Overview of High Availability for Siebel Web Servers Application Object Manager Servers Gateway NS & Non-Object Manager Servers Database Servers Operational Guidance Summary

9 HA Solutions for Web Servers

10 High Availability Strategy - Technical Related Info Cannot combine web server with any server that has Resonate installed for the same enterprise. Siebel 7.5 Reverse-proxy server not supported for High Interactivity clients. Siebel 7.7 certified with Reverse-proxy server for High Interactivity clients. Analytics Web Server cannot be load-balanced.

11 Agenda Overview of High Availability for Siebel Web Servers Application Object Manager Servers Gateway NS & Non-Object Manager Servers Database Servers Operational Guidance Summary

12 Siebel 7.5 and below - Resonate Central Dispatch Resonate provides both server load-balancing and session coherency Resonate cannot be installed on a cluster machine or on web server for the enterprise Resonate schedulers can coreside with load-balanced Servers (version 3.2.2) Resonate scheduler highly available by definition of secondary scheduler

13 Resonate Central Dispatch Related Info Ensure Resonate certified network adapters in use (most current list of certified adapters available from Siebel Supportweb) Ensure Resonate environment variables are set on servers Resonate Advanced Site Setup Parameters "Heartbeat" parameters Highly recommend dedicated Resonate Scheduler(s) for large environments (> 1,000 concurrent users) Resonate required if - 2 or more load balanced web servers - 2 or more app servers with same AOM s active Resonate and clustering mutually-exclusive on same host can be used in same Enterprise

14 Siebel 7.7 Load-balancing Intra-server Process Load-balancing - New component: Siebel Connection Broker (SCB) - Single port 2321 (default) Server Load-balancing - Two mechanisms supported: - Siebel Native Load-balancing Performed by Session Manager in SWSE Allocates new sessions to servers in turn (round-robin) - Third Party Load-balancing e.g. F5 BigIP (4.5)

15 Load-balanced Application Object Managers

16 Load-balanced Application Object Managers Related info Can load-balance all object managers except econfigurator Object Manager Cannot directly load-balance other components Can indirectly load-balance some others Requests from load-balanced OM will run on the same Siebel Server whenever possible Sessions remain fixed to object manager instance

17 Agenda Overview of High Availability for Siebel Web Servers Application Object Manager Servers Gateway NS & Non-Object Manager Servers Database Servers Operational Guidance Summary

18 Non Load-Balanced Aspects Use of Server Clustering Supported vendors and products only Use of Distributed Processing Built into Siebel Server Architecture

19 Non Load-Balanced Aspects Server Clustering Aspects that can only be Clustered: Siebel Database Siebel Gateway Name Server Siebel File System Siebel Remote / Replication Most Background Mode Siebel Components Aspects that can optionally be Clustered: Object Managers Web Servers Batch aspects will run but not failover Analytics Server provide inherent clustering technology Actuate clustering supported in Siebel 7.7

20 Non Load-Balanced Aspects Distributed Processing Internal requests originate from Siebel Server components Service available from many servers Requests will run on same Siebel Server if component running Can run on Clustered or Load-balanced Siebel Servers Siebel implement through Server Request Broker task Examples: Workflow Processes File System Manager edocument Server Special Case Siebel econfigurator Defined through the Product Configurator Remote Server component parameter using comma-separated list of Siebel Servers

21 Agenda Overview of High Availability for Siebel Web Servers Application Object Manager Servers Gateway NS & Non-Object Manager Servers Database Servers Operational Guidance Summary

22 Database Servers

23 Database Servers Related Info Many components can auto re-connect to database Siebel and 7.5 Increased component support for auto re-connect in Siebel 7.7 Oracle RAC support provided from Siebel 7.7

24 Agenda Overview of High Availability for Siebel Web Servers Application Object Manager Servers Gateway NS & Non-Object Manager Servers Database Servers Operational Guidance Summary

25 Operational Guidance Dynamic reconfiguration of many Siebel component parameters Dynamic component logging level control via event logging Monitoring Tools from 3 rd party vendors Test HA operation routinely Good operational procedures are the foundation of High Availability

26 Agenda Overview of High Availability for Siebel Web Servers Application Object Manager Servers Gateway NS & Non-Object Manager Servers Database Servers Operational Guidance Summary

27 Summary High Availability is not Fault Tolerance High Availability is not a substitute for Backups High Availability is not a substitute for Disaster Recovery High Availability should be viewed holistically High Availability usually requires enhancements in architecture, system testing, system management and operations

28 Additional Resources Siebel Bookshelf Siebel Supportweb 3 rd Party Vendors Expert Services High Availability Workshop and Consultancy