slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Ashesh Parekh Principal Product Manager Oracle Application Server Oracle Corporation PowerPoint Presentation
Download Presentation
Ashesh Parekh Principal Product Manager Oracle Application Server Oracle Corporation

Loading in 2 Seconds...

play fullscreen
1 / 34

Ashesh Parekh Principal Product Manager Oracle Application Server Oracle Corporation - PowerPoint PPT Presentation


  • 141 Views
  • Uploaded on

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

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Ashesh Parekh Principal Product Manager Oracle Application Server Oracle Corporation' - zoltin


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide2

Ashesh ParekhPrincipal Product Manager

Oracle Application Server

Oracle Corporation

agenda
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
agenda1
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
HA Architectural Overview

Web

Users

Middle Tier

Clusters

Load

Balancer /

Web Cache

Oracle

Database

Wireless &Mobile

OHS with

Load Balancing

Infrastructure

Cluster

Client

Oracle Application Server 10g

RAC

End-to-end High Availability

oracle application server ha
Oracle Application Server HA

System Failure

Load balancers, Clusters, OPMN

UnplannedDowntime

Data Failure& Disaster

Disaster Recovery, Backup & Recovery

Human Error

B&R, Configuration “undo”

SystemMaintenance

Rolling Upgrades

PlannedDowntime

Data Maintenance

Shouldn’t be any (data in database)

key messages
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
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
  • 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

Clients

Load Balancer

Load Balancer

DR Sync

MT 1

MT 2

MT 2*

MT 1*

DR

Sync

Infra

DR Sync

Infra*

Primary Site

Standby Site

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
disaster recovery1
Disaster Recovery

Clients

  • Site-to-site DR
  • Active/Standby DR using:
    • Virtual hostnames
    • Backup and recovery to synchronize primary & standby sites
    • Data Guard for Infrastructure database

Load Balancer

Load Balancer

DR Sync

MT 1

MT 2

MT 2

MT 1

DR

Sync

Infra

DR Sync

Infra

Primary Site

Standby Site

rolling upgrades
Rolling Upgrades

4

1

2

3

Clients

Clients

Clients

Clients

X

X

MT902

MT902

MT902

MT902

MT904

MT902

MT904

MT902

Infra902

Infra902

Infra902

Infra902

rolling upgrades contd
Rolling Upgrades – contd.

7

5

6

.)

Clients

Clients

Clients

X

X

MT904

MT904

MT904

MT904

MT904

MT904

X

Infra902

Infra902

Infra904

agenda2
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
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
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.

Clients

MT

MT

  • OID
  • SSO
  • DAS
  • Infra DBinstance

ActiveInfra

InactiveInfra

V. Host

Hardware

cluster

Sharedstorage

$ORACLE_HOME

cold failover cluster1
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.

Clients

MT

MT

  • OID
  • SSO
  • DAS
  • Infra DBinstance

InactiveInfra

ActiveInfra

V. Host

Hardware

cluster

Sharedstorage

$ORACLE_HOME

middle tiers on cold failover cluster
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

Clients

Load Balancer

MT 1

Node A

MT 2

Node B

ActiveInfra

InactiveInfra

Virtual Hostname

Hardware

cluster

Localstorage B

Localstorage A

Sharedstorage

$OH_A

$OH_B

$OH_INFRA

middle tiers on cold failover cluster1
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

Clients

Load Balancer

Node A

MT 1

MT 2

Node B

InactiveInfra

ActiveInfra

Virtual Hostname

Hardware

cluster

Localstorage B

Localstorage A

Sharedstorage

$OH_A

$OH_B

$OH_INFRA

active failover cluster
Active Failover Cluster

Clients

  • 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

MT

MT

Load Balancer

OID 1

SSO 1

DAS 1

DB instance 1

OID 2

SSO 2

DAS 2

DB instance 2

ActiveInfraNode 1

ActiveInfraNode 2

Hardware

cluster

Localstorage

Localstorage

Sharedstorage

$O_H1

$O_H2

Infra DB files

active failover cluster1
Active Failover Cluster

Clients

  • 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

MT

MT

Load Balancer

OID 1

SSO 1

DAS 1

DB instance 1

OID 2

SSO 2

DAS 2

DB instance 2

ActiveInfraNode 1

ActiveInfraNode 2

Hardware

cluster

Localstorage

Localstorage

Sharedstorage

$O_H1

$O_H2

Infra DB files

im service replication
IM Service Replication

MT 1

W

A

N

MT 2

  • Multiple IM Middle Tiers
  • Multiple OID
  • Multiple IM DBs (kept synchronized using Replication)
  • Ideal for geographically dispersed sites

Local DNS

Local DNS

IdentityMgmtMT 1

IdentityMgmtMT 2

SSO 1

SSO 2

OID 1

OID 2

DataReplication

DB1

DB2

San Francisco

London

metadata repository in existing rac db
Metadata Repository in 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)

MT

OHS

OC4J

SSO

IdentityMgmt

Infrastructure

DB2

InfrastructureMetadata Repository

DB1

Pre-existing RAC DB

agenda3
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
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
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

Oracle Application Server Clusters

HTTP Request

HTTP Request

Load Balancer

LB-1

LB-1

Web Cache

WC-1

WC-2

WC-3

OHS Instances

OHS

OHS

OHS

OC4J Instances

Beta

Prod

Beta

Prod

Beta

Prod

OC4J Islands

IB1

IP3

IB1

IP3

IP4

IP1

IP2

OC4J Processes

2

3

1

1

2

3

4

2

3

Cluster, Instances, and Islands

portal forms reports and other middle tiers

Middle Tier

Clusters

Load

Balancer /

Web Cache

OHS with

Load Balancing

Infrastructure

Cluster

Oracle Application Server 10g

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
oracle application server future roadmap
Oracle Application Server Future Roadmap
  • Active Failover Cluster enhancements
  • Improve Cloning capabilities
  • Disaster Recovery enhancements
  • Maximum Availability Architecture (MAA)
cohesive ha maa
Cohesive HA: MAA

Application Server

Application Server

WAN Traffic Manager

Dedicated Network

Data Guard

RAC

RAC

Primary Site

Secondary Site

resources
Resources
  • Oracle Technology Network (OTN):
    • http://otn.oracle.com/products/ias/hi_av/content.html
    • http://otn.oracle.com/deploy/availability/content.html
    • http://otn.oracle.com/deploy/availability/htdocs/maa.htm
  • Oracle Application Server 10g (9.0.4) Documentation:
    • High Availability Guide, Install Guide, Admin Guide
  • Oracle University Curriculum:
    • Admin courses, OUOnline courses
summary
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