Home / Middleware

Contents

List of Examples

List of Figures

List of Tables

Title and Copyright Information

Preface

• Audience
• Purpose of this Guide
• Documentation Accessibility
• Related Documents
• Conventions

Part I Introduction to High Availability

1 Introduction and Roadmap

• 1.1 How to Use This Guide
• 1.2 New and Changed Features in This Release
• 1.3 What is High Availability?
• 1.4 High Availability Solutions
• 1.5 Understanding the Oracle Fusion Middleware Standard HA Topology

2 High Availability Concepts

• 2.1 Server Load Balancing in a High Availability Environment
  • 2.1.1 Third-Party Load Balancer Requirements
  • 2.1.2 Third-Party Load Balancer Configuration
  • 2.1.3 Server Load Balancing with Oracle HTTP Server or Oracle Traffic Director
• 2.2 Application Failover
• 2.3 Real Application Clusters
• 2.4 Coherence Clusters and High Availability
• 2.5 Disaster Recovery
• 2.6 Install Time Configuration
  • 2.6.1 Domain (Topology) Profiles
  • 2.6.2 Persistence Profiles
• 2.7 Application and Service Failover
  • 2.7.1 Whole Server Migration
  • 2.7.2 Automatic Service Migration
• 2.8 Roadmap for Setting Up a High Availability Topology

Part II Creating a High Availability Environment

3 Using Shared Storage

• 3.1 Overview of Shared Storage
• 3.2 Shared Storage Prerequisites
• 3.3 Using Shared Storage for Binary (Oracle Home) Directories
  • 3.3.1 About the Binary (Oracle Home) Directories
  • 3.3.2 About Using Redundant Binary (Oracle Home) Directories
• 3.4 Using Shared Storage for Domain Configuration Files
  • 3.4.1 About Oracle WebLogic Server Administration and Managed Server Domain Configuration Files
  • 3.4.2 Shared Storage Considerations for Administration and Managed Server Domain Configuration Files
• 3.5 Shared Storage Requirements for JMS Stores and JTA Logs
• 3.6 Directory Structure and Configurations

4 Database Considerations

• 4.1 About Oracle Real Application Clusters
• 4.2 About RAC Database Connections and Failover
  • 4.2.1 About XA Transactions
• 4.3 About Data Sources
  • 4.3.1 Active GridLink Data Sources
  • 4.3.2 Multi Data Sources
• 4.4 Configuring Active GridLink Data Sources with Oracle RAC
  • 4.4.1 Requirements
  • 4.4.2 Configuring Component Data Sources as Active GridLink Data Sources
  • 4.4.3 Using Single Client Access Name (SCAN) Addresses for Hosts and Ports
• 4.5 Configuring Multi Data Sources
  • 4.5.1 Configuring Multi Data Sources with Oracle RAC
    • 4.5.1.1 Requirements
    • 4.5.1.2 Configuring Component Data Sources as Multi Data Sources
    • 4.5.1.3 Modifying or Creating Multi Data Sources After Initial Configuration
  • 4.5.2 Configuring Multi Data Sources for MDS Repositories

5 JMS and JTA High Availability

• 5.1 About JMS and JTA Services for High Availability
• 5.2 Configuring JMS and JTA Services for High Availability
• 5.3 User-Preferred Servers and Candidate Servers
• 5.4 Considerations for Using File Persistence (WebLogic JMS)
  • 5.4.1 Considerations for Using File Stores on NFS
• 5.5 Configuring Schemas for Transactional Recovery Privileges

6 Scaling Out a Topology (Machine Scale Out)

• 6.1 About Machine Scale Out
• 6.2 Roadmap for Scaling Out Your Topology
• 6.3 Optional Scale Out Procedure
• 6.4 About Scale Out Prerequisites
• 6.5 Resource Requirements
• 6.6 Creating a New Machine
  • 6.6.1 Shutting Down the Managed Server
  • 6.6.2 Creating a New Machine
  • 6.6.3 Assigning Managed Servers to the New Machine
• 6.7 Packing the Domain on APPHOST1
• 6.8 Preparing the New Machine
• 6.9 Running Unpack to Transfer the Template
• 6.10 Starting the Node Manager
• 6.11 Starting the Managed Servers
• 6.12 Verifying Machine Scale Out

Part III Component Procedures

7 Configuring High Availability for Web Tier Components

• 7.1 Oracle HTTP Server and High Availability Concepts
• 7.2 Oracle HTTP Server Single-Instance Characteristics
  • 7.2.1 Oracle HTTP Server and Oracle WebLogic Server
• 7.3 Oracle HTTP Server Startup and Shutdown Lifecycle
• 7.4 Starting and Stopping Oracle HTTP Server
• 7.5 Oracle HTTP Server High Availability Architecture and Failover Considerations
• 7.6 Oracle HTTP Server Protection from Failures and Expected Behaviors
• 7.7 Oracle HTTP Server Cluster-Wide Configuration Changes
• 7.8 Configuring Oracle HTTP Server for High Availability
  • 7.8.1 Prerequisites
    • 7.8.1.1 Configuring the Load Balancer
    • 7.8.1.2 Installing Oracle HTTP Server on WEBHOST1
    • 7.8.1.3 Configuring Virtual Host(s)
    • 7.8.1.4 Configuring mod_wl_ohs.conf
  • 7.8.2 Installing Oracle HTTP Server on WEBHOST2
  • 7.8.3 Configuring and Validating the OHS High Availability Deployment
    • 7.8.3.1 Configuring Virtual Host(s)
    • 7.8.3.2 Validating the Oracle HTTP Server Configuration

8 Configuring High Availability for Oracle Application Development Framework

• 8.1 Oracle ADF High Availability Considerations
  • 8.1.1 Oracle ADF Scope and Session State
  • 8.1.2 Oracle ADF Failover and Expected Behavior
  • 8.1.3 Configuring the ADF Application Module for Oracle RAC
• 8.2 Configuring Oracle ADF for High Availability
  • 8.2.1 Configuring Application Modules
  • 8.2.2 Configuring weblogic.xml
  • 8.2.3 Configuring adf-config.xml
  • 8.2.4 Configuring org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
• 8.3 Troubleshooting Oracle ADF High Availability
  • 8.3.1 Troubleshooting Oracle ADF Development Issues
  • 8.3.2 Troubleshooting Oracle ADF Deployment Issues
    • 8.3.2.1 Verifying the JRF Runtime Installation
    • 8.3.2.2 Verifying the Success of All Application Deployments
  • 8.3.3 Troubleshooting Oracle ADF Replication and Failover Issues

9 Configuring High Availability for Other Components

• 9.1 Deploying the Oracle Virtual Assembly Builder Deployer
• 9.2 Deploying Oracle Data Integrator
  • 9.2.1 Oracle RAC Retry Connectivity for Source and Target Connections
  • 9.2.2 Configuring Repository Connections to Oracle RAC