Ashesh Parekh Principal Product Manager Oracle Application Server Oracle Corporation

Oracle Application Server 10 g High Availability

Agenda  Oracle Application Server High Availability – Overall Availability Features  Infrastructure Availability – Cold Failover Cluster and Active Failover Cluster – Identity Management Replication and RAC  Middle Tier Availability – J2EE Application High Availability – Portal, Forms, Reports and other Middle Tiers  Summary

Agenda  Oracle Application Server High Availability – Overall Availability Features  Infrastructure Availability – Cold Failover Cluster and Active Failover Cluster – Identity Management Replication and RAC  Middle Tier Availability – J2EE Application High Availability – Portal, Forms, Reports and other Middle Tiers  Summary

HA Architectural Overview Load Balancer / Web Cache Wireless & Mobile Web Users RAC Middle Tier Clusters OHS with Load Balancing Infrastructure Cluster ClientOracle Application Server 10g End-to-end High Availability Oracle Database

Oracle Application Server HA System Failure Data Failure & Disaster Human Error Load balancers, Clusters, OPMN Disaster Recovery, Backup & Recovery B&R, Configuration “undo” System Maintenance Data Maintenance Rolling Upgrades Shouldn’t be any (data in database) Unplanned Downtime Planned Downtime

Key Messages  Key feature of Grid Computing – Workload and Resource Management  End-to-End High Availability – Self Healing – No single point of Failure – Clustering  Minimal planned or unplanned downtime – Rolling Upgrades – Disaster Recovery for MT as well as Infrastructure

Core HA features of OracleAS  OracleAS Process Monitoring and Notification service (OPMN): – Enables “Self Healing” – Process Monitoring (Death detection and Re- start)  Distributed Configuration Manager (DCM): – File-based repository or database-based repository – Consistent configuration management –prevents human errors

Backup and Recovery  Backup and Recovery Tool – For Middle Tiers as well as Infrastructure – Incremental backup and recovery – Point-in-time recovery  DCM Archival and Recovery – Revert to a previous configuration – Low overhead, quick “undo” – Works with DCM-managed components – Ideal for quick recovery from human error

Disaster Recovery  Site-to-site DR  Active/Standby DR using: – Virtual hostnames – Backup and recovery to synchronize primary & standby sites – Data Guard for Infrastructure database MT 1MT 2 Infra Clients MT 2*MT 1* Infra* Primary SiteStandby Site DR Sync DR Sync Load Balancer

Disaster Recovery MT 1MT 2 Infra Clients MT 2MT 1 Infra Primary SiteStandby Site DR Sync DR Sync Load Balancer  Site-to-site DR  Active/Standby DR using: – Virtual hostnames – Backup and recovery to synchronize primary & standby sites – Data Guard for Infrastructure database

MT 902 Infra Clients MT 902 Infra 902 Clients X MT 904 MT 902 Infra 902 Clients MT 904 MT 902 Infra Clients X Rolling Upgrades

56 MT 904 Infra 902 Clients MT 904 Infra 902 Clients X XX 7 MT 904 Infra 904 Clients.) Rolling Upgrades – contd.

Agenda  Oracle Application Server High Availability – Overall Availability Features  Infrastructure Availability – Cold Failover Cluster and Active Failover Cluster – Identity Management Replication and RAC  Middle Tier Availability – J2EE Application High Availability – Portal, Forms, Reports and other Middle Tiers  Summary

Infrastructure High Availability  Critical Services – Identity Management Services – for SSO/OID – Metadata Repository Services – for Portal, Wireless, Discoverer, etc. – Management Services – for Enterprise Manager  HA Options – Cold Failover Cluster (CFC) – Active Failover Cluster (AFC) – Identity Management (IM) Replication – Install Metadata Repository in existing RAC DB

Cold Failover Cluster  Active/Passive setup  Single Install – On shared disk – Using virtual hostname & IP  Cluster vendors supported: – Sun, HP, Red Hat, IBM, Veritas, Fujitsu-Siemens, Windows, etc. MT Active Infra Clients Inactive Infra Shared storage Hardware cluster $ORACLE_HOME -OID -SSO -DAS -Infra DB instance V. Host

Cold Failover Cluster MT Inactive Infra Clients Active Infra Shared storage Hardware cluster $ORACLE_HOME -OID -SSO -DAS -Infra DB instance V. Host  Active/Passive setup  Single Install – On shared disk – Using virtual hostname & IP  Cluster vendors supported: – Sun, HP, Red Hat, IBM, Veritas, Fujitsu-Siemens, Windows, etc.

Middle Tiers on Cold Failover Cluster  No Failover of Middle Tiers  Use LBR to route requests  Middle Tiers use physical hostname – On local disk  Infrastructure uses virtual hostname – On Shared disk MT 1MT 2 Active Infra Clients Inactive Infra Shared storage Hardware cluster $OH_INFRA Local storage A $OH_A Local storage B $OH_B Load Balancer Node ANode B Virtual Hostname

Middle Tiers on Cold Failover Cluster MT 1MT 2 Inactive Infra Clients Active Infra Shared storage Hardware cluster $OH_INFRA Local storage A $OH_A Local storage B $OH_B Load Balancer Node ANode B Virtual Hostname  No Failover of Middle Tiers  Use LBR to route requests  Middle Tiers use physical hostname – On local disk  Infrastructure uses virtual hostname – On Shared disk

Active Failover Cluster MT Clients Shared storage Load Balancer Active Infra Node 1 Active Infra Node 2 Hardware cluster Infra DB files Local storage $O_H2$O_H1 OID 1 SSO 1 DAS 1 DB instance 1 OID 2 SSO 2 DAS 2 DB instance 2  Active/Active setup  “High 9s” uptime  Single Install – DB (RAC) on shared disk – Rest-of-infra on local disks – Requires load balancer  Limited Release in 9.0.4

Active Failover Cluster MT Clients Shared storage Load Balancer Active Infra Node 1 Active Infra Node 2 Hardware cluster Infra DB files Local storage OID 1 SSO 1 DAS 1 DB instance 1 OID 2 SSO 2 DAS 2 DB instance 2 $O_H2$O_H1  Active/Active setup  “High 9s” uptime  Single Install – DB (RAC) on shared disk – Rest-of-infra on local disks – Requires load balancer  Limited Release in 9.0.4

IM Service Replication  Multiple IM Middle Tiers  Multiple OID  Multiple IM DBs (kept synchronized using Replication)  Ideal for geographically dispersed sites Identity Mgmt MT 1 OID 2 DB1 SSO 2 Identity Mgmt MT 2 SSO 1 OID 1 DB2 Data Replication MT 1MT 2 LondonSan Francisco WANWAN Local DNS

Metadata Repository in existing RAC DB Identity Mgmt DB1 OHS OC4J SSO DB2 MT Infrastructure Infrastructure Metadata Repository Pre-existing RAC DB  Install MR in existing RAC database  No database in the Infrastructure installation  Provides HA for MR, but not for the rest of Infrastructure (IM)

Agenda  Oracle Application Server High Availability – Overall Availability Features  Infrastructure Availability – Cold Failover Cluster and Active Failover Cluster – Identity Management Replication and RAC  Middle Tier Availability – J2EE Application High Availability – Portal, Forms, Reports and other Middle Tiers  Summary

Middle Tier High Availability  Web Cache clusters provide redundancy and fault tolerance  OHS/mod_oc4j load balancing and smart routing – weighted, metrics-based, round robin, random – local affinity  File based repository for OC4J clusters  EJB Client Proxy: – Auto-rerouting of requests from EJB Clients  Hot Deployment of J2EE applications

Transparent Application Failover (TAF)  TAF of JDBC connections to RAC database – Supported with JDBC Thick driver (OCI driver) – Define oracle.jdbc.OracleOCIFailover Interface for stateful applications (to handle state restore)  Configuration modes: – Basic Method: re-connect upon failure – Pre-connect Method: maintain backup (shadow) connection to another instance for faster TAF – For non RAC database auto-retry (with timeout)

Oracle Application Server Clusters  Load Balancing  Scale middle-tier ‘linearly’  Session Replication  Configuration Cloning  Deploy across clusters LB-1 WC-1WC-3WC-2 OHS BetaProdBetaProd BetaProd IB1 IP1IP2 IP3 IP LB-1 HTTP Request Web Cache Load Balancer OC4J Processes OC4J Islands OC4J Instances OHS Instances HTTP Request Cluster, Instances, and Islands

Portal, Forms, Reports, and other Middle Tiers  Configuration: – Load Balancer – Web Cache Clusters – Multiple Middle Tiers – Infrastructure CFC or Active Failover Cluster – Backend RAC DB Load Balancer / Web Cache Middle Tier Clusters OHS with Load Balancing Infrastructure Cluster Oracle Application Server 10g

Oracle Application Server Future Roadmap  Active Failover Cluster enhancements  Improve Cloning capabilities  Disaster Recovery enhancements  Maximum Availability Architecture (MAA)

Cohesive HA: MAA Dedicated Network WAN Traffic Manager Application Server Primary Site RAC Secondary Site RAC Data Guard

Resources  Oracle Technology Network (OTN): – – –  Oracle Application Server 10g (9.0.4) Documentation: – High Availability Guide, Install Guide, Admin Guide  Oracle University Curriculum: – Admin courses, OUOnline courses

Summary  End-to-End High Availability – No Single Point of Failure  Self Healing – Quick Recovery  Ease of Configuration – Minimize human errors  Rolling Upgrades  Minimal planned or unplanned downtime