1/29

Contents

Expand All · Collapse All

List of Examples

List of Figures

List of Tables

Title and Copyright Information

Preface

• Intended Audience
• Documentation Accessibility
• Related Documentation
• Conventions

1 Introduction to High Availability

• 1.1 What is High Availability
  • 1.1.1 High Availability Problems
  • 1.1.2 High Availability Solutions
• 1.2 High Availability Information in Other Documentation

2 Oracle Fusion Middleware High Availability Framework

• 2.1 Understanding Key Oracle Fusion Middleware Concepts
  • 2.1.1 What is a WebLogic Server Domain?
    • 2.1.1.1 What Is the Administration Server?
    • 2.1.1.2 Understanding Managed Servers and Managed Server Clusters
    • 2.1.1.3 What Is Node Manager?
  • 2.1.2 What Is a System Component Domain?
  • 2.1.3 What Is a Middleware Home?
  • 2.1.4 What Is an Oracle Home?
    • 2.1.4.1 What Is an Oracle Common Home?
  • 2.1.5 What Is a WebLogic Server Home?
• 2.2 Oracle Fusion Middleware High Availability Terminology
• 2.3 Oracle Fusion Middleware High Availability Solutions
  • 2.3.1 Local High Availability
  • 2.3.2 Oracle Fusion Middleware High Availability Technologies
    • 2.3.2.1 Server Load Balancing
  • 2.3.3 Active-Passive Deployment
  • 2.3.4 About Active-Active and Active-Passive Solutions
  • 2.3.5 Disaster Recovery
• 2.4 Protection from Planned and Unplanned Down Time

3 High Availability for WebLogic Server

• 3.1 What Is a WebLogic Server Cluster?
• 3.2 WebLogic Server Clusters and WebLogic Server Domains
• 3.3 Benefits of Clustering
• 3.4 Key Capabilities of a Cluster
  • 3.4.1 Application Failover
  • 3.4.2 Migration
  • 3.4.3 Load Balancing
• 3.5 Types of Objects That Can Be Clustered
• 3.6 Communications in a Cluster
• 3.7 Cluster-Wide JNDI Naming Service
• 3.8 Failover and Replication in a Cluster
  • 3.8.1 Session Replication
• 3.9 Whole Server Migration
  • 3.9.1 Node Manager's Role in Whole Server Migration
  • 3.9.2 Server Migration Processes and Communications
    • 3.9.2.1 Startup Process in a Cluster with Migratable Servers
    • 3.9.2.2 Automatic Whole Server Migration Process
    • 3.9.2.3 Manual Whole Server Migration Process
    • 3.9.2.4 Administration Server's Role in Whole Server Migration
    • 3.9.2.5 Migratable Server Behavior in a Cluster
    • 3.9.2.6 Node Manager's Role in Whole Server Migration
    • 3.9.2.7 Cluster Master's Role in Whole Server Migration
• 3.10 JMS and JTA High Availability
  • 3.10.1 User-Preferred Servers and Candidate Servers
• 3.11 Administration Server and Node Manager High Availability
  • 3.11.1 Administration Server Failure
  • 3.11.2 Node Manager Failure
• 3.12 Load Balancing
• 3.13 Multi Data Sources
• 3.14 Cluster Configuration and config.xml
• 3.15 About Singleton Services
• 3.16 WebLogic Server and LDAP High Availability

4 Considerations for High Availability Oracle Database Access

• 4.1 Oracle Real Application Clusters and Fusion Middleware
  • 4.1.1 Java-Based Oracle Fusion Middleware Components Deployed to Oracle WebLogic Server
  • 4.1.2 Using Multi Data Sources with Oracle RAC
    • 4.1.2.1 Configuring Multi Data Sources for MDS Repositories
    • 4.1.2.2 Oracle RAC Configuration Requirements
    • 4.1.2.3 Configuring Schemas for Transactional Recovery Privileges
  • 4.1.3 Configuring Multi Data Sources with Oracle RAC
  • 4.1.4 Oracle RAC Failover with WebLogic Server
  • 4.1.5 JDBC Clients
  • 4.1.6 System Clients
    • 4.1.6.1 Oracle Internet Directory
    • 4.1.6.2 Oracle Forms
    • 4.1.6.3 Oracle Portal
    • 4.1.6.4 Oracle Reports and Oracle Discoverer
• 4.2 Protecting Idle Connections from Firewall Timeouts
• 4.3 Troubleshooting Real Application Clusters
• 4.4 Oracle Fusion Middleware Products are Certified to be used with 11.2 RDBMS Oracle RAC

5 Configuring High Availability for Oracle Fusion Middleware SOA Suite

• 5.1 Introduction to Oracle Fusion Middleware SOA Suite
• 5.2 Oracle SOA Service Infrastructure High Availability
  • 5.2.1 Oracle SOA Service Infrastructure Single-Instance Characteristics
    • 5.2.1.1 Oracle SOA Service Infrastructure Application Characteristics
    • 5.2.1.2 Oracle SOA Service Infrastructure Startup and Shutdown Lifecyle
    • 5.2.1.3 Oracle SOA Service Infrastructure External Dependencies
    • 5.2.1.4 Oracle SOA Service Infrastructure Startup and Shut Down of Processes
    • 5.2.1.5 Oracle SOA Service Infrastructure Configuration Artifacts
    • 5.2.1.6 Oracle SOA Service Infrastructure Log File Locations
  • 5.2.2 Oracle SOA Service Infrastructure High Availability Architecture and Failover Considerations
    • 5.2.2.1 Oracle SOA Service Infrastructure Protection from Failures and Expected Behavior
      • 5.2.2.1.1 WebLogic Server Crash
      • 5.2.2.1.2 Node Failure
      • 5.2.2.1.3 Database Failure
    • 5.2.2.2 Oracle SOA Service Infrastructure Cluster-Wide Deployment
    • 5.2.2.3 Online Redeployment of Oracle SOA Service Infrastructure Composites in Cluster
    • 5.2.2.4 Oracle SOA Service Infrastructure Cluster-Wide Configuration Changes
• 5.3 Oracle BPEL Process Manager and High Availability Concepts
  • 5.3.1 Oracle BPEL Process Manager Single-Instance Characteristics
    • 5.3.1.1 BPEL Process Manager Component Characteristics
    • 5.3.1.2 Oracle BPEL Process Manager Startup and Shutdown Lifecycle
    • 5.3.1.3 Oracle BPEL Process Manager Request Flow and Recovery
    • 5.3.1.4 Oracle BPEL Process Manager Configuration Artifacts
  • 5.3.2 Oracle BPEL Process Manager High Availability Architecture and Failover Considerations
    • 5.3.2.1 Oracle BPEL Process Manager Protection from Failures and Expected Behavior
      • 5.3.2.1.1 Recovering Failed BPEL and Mediator Instances
    • 5.3.2.2 Oracle BPEL Process Manager Cluster-Wide Configuration Changes
• 5.4 Oracle Mediator and High Availability Concepts
  • 5.4.1 Oracle Mediator Single-Instance Characteristics
    • 5.4.1.1 Oracle Mediator Component Characteristics
    • 5.4.1.2 Oracle Mediator Startup and Shutdown Lifecycle
    • 5.4.1.3 Oracle Mediator Request Flow
    • 5.4.1.4 Oracle Mediator Configuration Artifacts
  • 5.4.2 Oracle Mediator High Availability Architecture and Failover Considerations
    • 5.4.2.1 Oracle Mediator Protection from Failures and Expected Behavior
      • 5.4.2.1.1 Recovering Failed Mediator Instances
    • 5.4.2.2 Troubleshooting Oracle Mediator High Availability
• 5.5 Oracle Human Workflow and High Availability Concepts
  • 5.5.1 Oracle Human Workflow Single-Instance Characteristics
    • 5.5.1.1 Oracle Human Workflow Startup and Shutdown Lifecycle
    • 5.5.1.2 Oracle Human Workflow Request Processing
    • 5.5.1.3 Oracle Human Workflow Configuration Artifacts
      • 5.5.1.3.1 Managing the URI of the Human Task Service Component Task Details Application
  • 5.5.2 Oracle Human Workflow High Availability Architecture and Failover Considerations
    • 5.5.2.1 Oracle Human Workflow Protection from Failures and Expected Behavior
    • 5.5.2.2 Manual Recovery Required for Human Workflow Task in Rejected MSG Table
  • 5.5.3 Troubleshooting Oracle Human Workflow High Availability
• 5.6 Oracle B2B and High Availability Concepts
  • 5.6.1 Oracle B2B Single-Instance Characteristics
    • 5.6.1.1 Oracle B2B Component Characteristics
    • 5.6.1.2 Oracle B2B Startup and Shutdown Lifecycle
    • 5.6.1.3 Oracle B2B Request Flow
    • 5.6.1.4 Oracle B2B Configuration Artifacts
  • 5.6.2 Oracle B2B High Availability Architecture and Failover Considerations
    • 5.6.2.1 Oracle B2B Protection from Failures and Expected Behavior
    • 5.6.2.2 Oracle B2B Cluster-Wide Configuration Changes
    • 5.6.2.3 Oracle B2B deployments in a Cluster
    • 5.6.2.4 Troubleshooting Oracle B2B Active-Active Configuration
      • 5.6.2.4.1 Purge, Import, or Deployment of B2B Metadata
      • 5.6.2.4.2 Error While Retrieving Oracle B2B Document Definitions
• 5.7 Oracle Web Service Manager and High Availability Concepts
  • 5.7.1 Oracle WSM Single-Instance Characteristics
    • 5.7.1.1 Oracle WSM Component Characteristics
    • 5.7.1.2 Oracle WSM Startup and Shutdown Lifecycle
    • 5.7.1.3 Oracle WSM Request Flow
    • 5.7.1.4 Oracle WSM Configuration Artifacts
  • 5.7.2 Oracle WSM High Availability Architecture and Failover Considerations
    • 5.7.2.1 Oracle WSM Protection from Failures and Expected Behavior
    • 5.7.2.2 Oracle WSM Cluster-Wide Configuration Changes
    • 5.7.2.3 Configuring the Java Object Cache for Oracle WSM
• 5.8 Oracle User Messaging Service and High Availability Concepts
  • 5.8.1 Oracle User Messaging Service Single-Instance Characteristics
    • 5.8.1.1 Oracle User Messaging Service Component Characteristics
    • 5.8.1.2 Oracle User Messaging Service Startup and Shutdown Lifecycle
    • 5.8.1.3 Oracle User Messaging Service Request Flow
    • 5.8.1.4 Oracle User Messaging Service Configuration Artifacts
  • 5.8.2 Oracle User Messaging Service High Availability Architecture and Failover Considerations
    • 5.8.2.1 Oracle User Messaging Service Protection from Failures and Expected Behavior
    • 5.8.2.2 Oracle User Messaging Service Cluster-Wide Configuration Changes
• 5.9 Oracle JCA Adapters and High Availability Concepts
  • 5.9.1 Oracle JCA Adapters Single-Instance Characteristics
    • 5.9.1.1 Oracle JCA Adapters Component Lifecycle
    • 5.9.1.2 Oracle JCA Adapters Reliability and Transactional Behavior
    • 5.9.1.3 Oracle JCA Adapters - Rejected Message Handling
  • 5.9.2 Oracle JCA Adapters High Availability Architecture and Failover Considerations
    • 5.9.2.1 Oracle JCA Adapters High Availability Error Handling
    • 5.9.2.2 Oracle File and FTP Adapters High Availability
    • 5.9.2.3 Oracle Database Adapters High Availability
    • 5.9.2.4 Oracle JMS Adapters High Availability
    • 5.9.2.5 Oracle JCA Adapters Log File Locations
• 5.10 Oracle Business Activity Monitoring and High Availability Concepts
  • 5.10.1 Oracle Business Activity Monitoring Single-Instance Characteristics
    • 5.10.1.1 Oracle Business Activity Monitoring Component Characteristics
    • 5.10.1.2 Oracle Business Activity Monitoring Startup/Shutdown Lifecycle
    • 5.10.1.3 Oracle Business Activity Monitoring Startup and Shutdown of Processes
    • 5.10.1.4 Oracle Business Activity Monitoring Configuration Artifacts
  • 5.10.2 Oracle Business Activity Monitoring High Availability Architecture and Failover Considerations
    • 5.10.2.1 Oracle Business Activity Monitoring Protection from Failures and Expected Behavior
    • 5.10.2.2 Oracle Business Activity Monitoring Cluster-Wide Configuration Changes
• 5.11 Configuring High Availability for Oracle SOA Service Infrastructure and Component Service Engines
  • 5.11.1 Preparing the Environment: Prerequisite Steps Before Setting up a SOA High Availability Configuration
    • 5.11.1.1 Database Prerequisites
    • 5.11.1.2 VIP and IP Prerequisites
    • 5.11.1.3 Shared Storage Prerequisites
    • 5.11.1.4 Installing and Configuring an LDAP Provider
    • 5.11.1.5 Synchronizing System Clocks
    • 5.11.1.6 Terminology for Directories and Directory Environment Variables
    • 5.11.1.7 Installing and Configuring the Database Repository
    • 5.11.1.8 Using Oracle Fusion Middleware Repository Creation Utility to Load the Fusion Middleware Schemas in the Database
      • 5.11.1.8.1 Running RCU
      • 5.11.1.8.2 Configuring SOA Schemas for Transactional Recovery Privileges
  • 5.11.2 Installing Oracle HTTP Server on WebHost1
    • 5.11.2.1 Validating Oracle HTTP Server
  • 5.11.3 Installing Oracle Fusion Middleware Home
    • 5.11.3.1 Installing Oracle WebLogic Server
    • 5.11.3.2 Installing Oracle Fusion Middleware for Oracle SOA
  • 5.11.4 Enabling VIP1 in APPHOST1 and VIP2 APPHOST2
  • 5.11.5 Running Oracle Fusion Middleware Configuration Wizard on APPHOST1 to Create the SOA Domain
  • 5.11.6 Creating boot.properties for the Administration Server on APPHOST1
  • 5.11.7 Starting the System in APPHOST1
    • 5.11.7.1 Starting the Administration Server on APPHOST1
    • 5.11.7.2 Validating the Administration Server
    • 5.11.7.3 Disabling Host Name Verification for the Administration Server and the WLS_SOA1 Managed Server
    • 5.11.7.4 Starting Node Manager on APPHOST1
    • 5.11.7.5 Using Oracle Coherence for Deploying Composites
    • 5.11.7.6 Running the soa-createUDD.py Script
    • 5.11.7.7 Starting and Validating the WLS_SOA1 Managed Server
  • 5.11.8 Install WebLogic Server and Oracle SOA on APPHOST2
  • 5.11.9 Propagating the Domain Configuration to APPHOST2 with pack/unpack Utilities
  • 5.11.10 Extracting XEngine Files in the Second Node
  • 5.11.11 Starting the System in APPHOST2
    • 5.11.11.1 Disabling Host Name Verification for the WLS_SOA2 Managed Server
    • 5.11.11.2 Starting Node Manager on APPHOST2
    • 5.11.11.3 Starting and Validating the WLS_SOA2 Managed Server
  • 5.11.12 Configuring Oracle HTTP Server for the Administration Server and the WLS_SOAn Managed Servers
    • 5.11.12.1 Validating Access through Oracle HTTP Server
    • 5.11.12.2 Configuring JMS Persistence Store as Shared Across the Servers
    • 5.11.12.3 Configuring a Default Persistent Store for Transaction Recovery
  • 5.11.13 Setting the Front End HTTP Host and Port
  • 5.11.14 Deploying Applications
  • 5.11.15 Configuring Server Migration for the WLS_SOA Servers
  • 5.11.16 Scaling the Topology
    • 5.11.16.1 Scaling Up the Topology (Adding Managed Servers to Existing Nodes)
    • 5.11.16.2 Scaling Out the Topology (Adding Managed Servers to New Nodes)
• 5.12 Configuring High Availability for Oracle BAM
  • 5.12.1 Preparing the Environment: Prerequisite Steps Before Setting up a High Availability Configuration for Oracle BAM
    • 5.12.1.1 Database Prerequisites
    • 5.12.1.2 VIP and IPs Prerequisites
    • 5.12.1.3 Installing and Configuring the Database Repository
    • 5.12.1.4 Using Oracle Fusion Middleware Repository Creation Utility to Load Oracle Fusion Middleware schemas
      • 5.12.1.4.1 Running RCU
  • 5.12.2 Installing Oracle HTTP Server on WebHost1
    • 5.12.2.1 Validating Oracle HTTP Server
  • 5.12.3 Installing Oracle Fusion Middleware Home
    • 5.12.3.1 Installing Oracle WebLogic Server
    • 5.12.3.2 Installing Oracle Fusion Middleware for Oracle SOA
  • 5.12.4 Enabling VIP0 and VIP1 on APPHOST1
  • 5.12.5 Running Oracle Fusion Middleware Configuration Wizard on APPHOST1 to Create the WebLogic Server Oracle BAM Domain
  • 5.12.6 Creating boot.properties for the Administration Server and for WLS_BAM1 on APPHOST1
  • 5.12.7 Starting the Administration Server on APPHOST1
  • 5.12.8 Disabling Host Name Verification for the Servers
  • 5.12.9 Configuring a JMS Persistence Store for BAM UMS
  • 5.12.10 Configuring a Default Persistence Store for Transaction Recovery
  • 5.12.11 Untargeting the BAM Server System from APPHOST2
  • 5.12.12 Propagating the Domain Configuration from APPHOST1 with pack/unpack Utilities
  • 5.12.13 Starting Node Manager on APPHOST1 and APPHOST2
  • 5.12.14 Starting the Oracle BAM System
  • 5.12.15 Configuring RAC Failover for the WLS_BAM Servers
  • 5.12.16 Configuring the BAM Web Applications to Use the BAM Server in APPHOST1
  • 5.12.17 Configuring the ADCServer to Use the Appropriate BAMServer Address
  • 5.12.18 Configuring Oracle HTTP Server for the Administration Server and the WLS_BAMn Managed Servers
  • 5.12.19 Validating Access through Oracle HTTP Server
  • 5.12.20 Configuring Server Migration for the WLS_BAM Servers
    • 5.12.20.1 Setting Up the User and Tablespace for the Server Migration Leasing Table
    • 5.12.20.2 Creating a Multi-Data Source from the WebLogic Server Administration Console
    • 5.12.20.3 Edit the Node Manager's Properties File
    • 5.12.20.4 Set Environment and Superuser Privileges for the wlsifconfig.sh Script
    • 5.12.20.5 Configure Server Migration Targets
    • 5.12.20.6 Test Server Migration

6 Configuring High Availability for Oracle ADF and WebCenter Applications

• 6.1 Oracle ADF and High Availability Concepts
  • 6.1.1 Understanding Oracle ADF
    • 6.1.1.1 Oracle ADF Components
      • 6.1.1.1.1 ADF Business Components
      • 6.1.1.1.2 ADF Model Layer
      • 6.1.1.1.3 ADF Controller
      • 6.1.1.1.4 ADF Faces Rich Client
    • 6.1.1.2 Oracle ADF Single Node Architecture
    • 6.1.1.3 Oracle ADF External Dependencies
    • 6.1.1.4 Oracle ADF Log File
  • 6.1.2 Oracle ADF High Availability Considerations
    • 6.1.2.1 Oracle ADF Scope and Session State
    • 6.1.2.2 Oracle ADF Failover and Expected Behavior
    • 6.1.2.3 Oracle ADF Active Data Services
    • 6.1.2.4 Configuring the ADF Application Module for Oracle RAC
  • 6.1.3 Configuring Oracle ADF for High Availability
    • 6.1.3.1 Configuring Application Modules
    • 6.1.3.2 Configuring weblogic.xml
    • 6.1.3.3 Configuring adf-config.xml
    • 6.1.3.4 Configuring org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
  • 6.1.4 Troubleshooting Oracle ADF High Availability
    • 6.1.4.1 Troubleshooting Oracle ADF Development Issues
    • 6.1.4.2 Troubleshooting Oracle ADF Deployment Issues
    • 6.1.4.3 Troubleshooting Oracle ADF Replication and Failover Issues
• 6.2 Configuring an Oracle ADF High Availability Deployment
  • 6.2.1 Terminology for Directories and Directory Environment Variables
  • 6.2.2 Using RCU to Load Fusion Middleware Schemas in the Database
    • 6.2.2.1 Running RCU
  • 6.2.3 Installing Oracle HTTP Server on WEBHOST1
    • 6.2.3.1 Validating Oracle HTTP Server
  • 6.2.4 Installing the Oracle Fusion Middleware Home
    • 6.2.4.1 Installing Oracle WebLogic Server
    • 6.2.4.2 Installing Oracle Fusion Middleware for Oracle ADF Applications
  • 6.2.5 Administration Server High Availability
  • 6.2.6 Running the Configuration Wizard on APPHOST1 to Create the WebLogic Server ADF Domain
    • 6.2.6.1 Creating boot.properties for the Administration Server and Managed Servers on APPHOST1
  • 6.2.7 Starting the System in APPHOST1
    • 6.2.7.1 Starting the Administration Server on APPHOST1
    • 6.2.7.2 Validating the Administration Server
    • 6.2.7.3 Disabling Host Name Verification for the Administration Server and Managed Servers for APPHOST1 and APPHOST2
    • 6.2.7.4 Starting Node Manager on APPHOST1
  • 6.2.8 Installing Oracle WebLogic Server and Oracle ADF on APPHOST2
  • 6.2.9 Propagating the Domain Configuration to APPHOST2 with pack/unpack Utilities
    • 6.2.9.1 Creating boot.properties for the Administration Server and Managed Servers on APPHOST2
    • 6.2.9.2 Starting Node Manager on APPHOST2
    • 6.2.9.3 Configuring the ADF Application for Replication
    • 6.2.9.4 Deploying the ADF Application
    • 6.2.9.5 Configuring Oracle HTTP Server for the Administration Server and Oracle WebCenter Managed Servers
    • 6.2.9.6 Validating Access through Oracle HTTP Server
• 6.3 Oracle WebCenter and High Availability Concepts
  • 6.3.1 Understanding Oracle WebCenter
    • 6.3.1.1 Oracle WebCenter Components
    • 6.3.1.2 Oracle WebCenter Single-node Architecture
    • 6.3.1.3 Oracle WebCenter State and Configuration Persistence
    • 6.3.1.4 Oracle WebCenter External Dependencies
    • 6.3.1.5 Oracle WebCenter Configuration Considerations
    • 6.3.1.6 Oracle WebCenter Log File Locations
  • 6.3.2 WebCenter High Availability Architecture and Failover Considerations
    • 6.3.2.1 Oracle WebCenter Applications
    • 6.3.2.2 Oracle WebCenter Startup Order
    • 6.3.2.3 Deploying WebCenter Application on a Cluster
    • 6.3.2.4 Oracle WebCenter State Replication
    • 6.3.2.5 Understanding the Distributed Java Object Cache
    • 6.3.2.6 Oracle WebCenter Protection from Failover and Expected Behavior
    • 6.3.2.7 Expected Behavior for Application Failover
    • 6.3.2.8 Monitoring Logging of Application Deployments
    • 6.3.2.9 Oracle WebCenter Cluster-wide Configuration Changes
    • 6.3.2.10 Maintaining Configuration in a Clustered Environment
• 6.4 Configuring High Availability for Oracle WebCenter
  • 6.4.1 Preparing the Environment: Prerequisite Steps Before Setting up an Oracle WebCenter High Availability Configuration
    • 6.4.1.1 Database Prerequisites
    • 6.4.1.2 VIP and IP Prerequisites
    • 6.4.1.3 Installing and Configuring the Database Repository
    • 6.4.1.4 Installing and Configuring an LDAP Provider
    • 6.4.1.5 Terminology for Directories and Directory Environment Variables
    • 6.4.1.6 Using Oracle Fusion Middleware Repository Creation Utility to Load the Fusion Middleware Schemas in the Database
      • 6.4.1.6.1 Running RCU
  • 6.4.2 Installing Oracle HTTP Server on WebHost1
    • 6.4.2.1 Validating Oracle HTTP Server
  • 6.4.3 Installing Oracle Fusion Middleware Home
    • 6.4.3.1 Installing Oracle WebLogic Server
    • 6.4.3.2 Installing Oracle Fusion Middleware for Oracle WebCenter
  • 6.4.4 Enabling the Administration Server VIP
  • 6.4.5 Running Oracle Fusion Middleware Configuration Wizard on APPHOST1 to Create the WebLogic Server WebCenter Domain
  • 6.4.6 Creating boot.properties for the Administration Server and for Managed Servers on APPHOST1
  • 6.4.7 Starting the System in APPHOST1
    • 6.4.7.1 Starting the Administration Server on APPHOST1
    • 6.4.7.2 Validating the Administration Server
    • 6.4.7.3 Disabling Host name Verification for the Administration Server and the Managed Servers for APPHOST1 and APPHOST2
    • 6.4.7.4 Starting Node Manager on APPHOST1
  • 6.4.8 Install WebLogic Server and Oracle WebCenter on APPHOST2
  • 6.4.9 Propagating the Domain Configuration to APPHOST2 with pack/unpack Utilities
  • 6.4.10 Starting Node Manager on APPHOST2
  • 6.4.11 Configuring Oracle HTTP Server for the Administration Server and Oracle WebCenter Managed Servers
    • 6.4.11.1 Validating Access through Oracle HTTP Server
  • 6.4.12 Configuring Manual Failover of the Administration Server to APPHOST2
  • 6.4.13 Configuring the Java Object Cache
  • 6.4.14 Configuring Wiki Server
  • 6.4.15 Configuring Oracle WebCenter for Replication
  • 6.4.16 Configuring Clustering for Discussion Server
  • 6.4.17 Scaling the Topology
    • 6.4.17.1 Scaling Up the Topology (Adding Managed Servers to Existing Nodes)
    • 6.4.17.2 Scaling Out the Topology (Adding Managed Servers to New Nodes)
  • 6.4.18 Troubleshooting Oracle WebCenter High Availability
    • 6.4.18.1 Troubleshooting Oracle WebCenter Deployment Issues
    • 6.4.18.2 Troubleshooting Oracle WebCenter Replication and Failover Issues
    • 6.4.18.3 Troubleshooting Lost Changes to Policies
    • 6.4.18.4 Troubleshooting JOC Configuration
  • 6.4.19 Converting Discussions Forum from Multicast to Unicast
• 6.5 Configuring High Availability for Custom Oracle ADF and WebCenter Applications
  • 6.5.1 Configuring a Custom Application Cluster
  • 6.5.2 Provisioning the Custom Application Cluster

7 Configuring High Availability for Identity Management Components

• 7.1 Identity Management Product Components and High Availability Concepts
  • 7.1.1 About the 11g Oracle Identity Management Products
• 7.2 Prerequisites for Oracle Identity Management High Availability Configuration
  • 7.2.1 Oracle Home Requirement
  • 7.2.2 Database Prerequisites
  • 7.2.3 Installing and Configuring the Database Repository
  • 7.2.4 Installing the Repository Creation Utility Software
  • 7.2.5 Configuring the Database for Oracle Fusion Middleware 11g Metadata
    • 7.2.5.1 Initialization Parameters
    • 7.2.5.2 Database Examples in This Chapter
    • 7.2.5.3 Database Services
    • 7.2.5.4 Verifying Transparent Application Failover (TAF)
    • 7.2.5.5 Configuring Virtual Server Names and Ports for the Load Balancer
      • 7.2.5.5.1 Load Balancers
      • 7.2.5.5.2 Virtual Server Names
• 7.3 Oracle Internet Directory High Availability
  • 7.3.1 Oracle Internet Directory Component Architecture
    • 7.3.1.1 Oracle Internet Directory Component Characteristics
      • 7.3.1.1.1 Runtime Processes
      • 7.3.1.1.2 Process Lifecycle
      • 7.3.1.1.3 Request Flow
      • 7.3.1.1.4 Configuration Artifacts
      • 7.3.1.1.5 External Dependencies
      • 7.3.1.1.6 Oracle Internet Directory Log File
  • 7.3.2 Oracle Internet Directory High Availability Concepts
    • 7.3.2.1 Oracle Internet Directory High Availability Architecture
      • 7.3.2.1.1 Starting and Stopping the Cluster
      • 7.3.2.1.2 Cluster-Wide Configuration Changes
    • 7.3.2.2 Protection from Failures and Expected Behavior
      • 7.3.2.2.1 Oracle Internet Directory Process Failure
      • 7.3.2.2.2 Expected Client Application Behavior When Failure Occurs
      • 7.3.2.2.3 External Dependency Failure
    • 7.3.2.3 Oracle Internet Directory Prerequisites
      • 7.3.2.3.1 Synchronizing the Time on Oracle Internet Directory Nodes
      • 7.3.2.3.2 Using RCU to Create Oracle Internet Directory Schemas in the Repository
      • 7.3.2.3.3 Load Balancer Virtual Server Names for Oracle Internet Directory
  • 7.3.3 Oracle Internet Directory High Availability Configuration Steps
    • 7.3.3.1 Configuring Oracle Internet Directory Without a WebLogic Domain
      • 7.3.3.1.1 Installing Oracle Internet Directory on OIDHOST1
      • 7.3.3.1.2 Oracle Internet Directory Component Names Assigned by Oracle Identity Management Installer
      • 7.3.3.1.3 Installing Oracle Internet Directory on OIDHOST2
      • 7.3.3.1.4 Registering Oracle Internet Directory with a WebLogic Domain
    • 7.3.3.2 Configuring Oracle Internet Directory With a WebLogic Domain
      • 7.3.3.2.1 Installing Oracle WebLogic Server
      • 7.3.3.2.2 Installing Oracle Internet Directory on OIDHOST1
      • 7.3.3.2.3 Creating boot.properties for the Administration Server on OIDHOST1
      • 7.3.3.2.4 Installing Oracle Internet Directory on OIDHOST2
  • 7.3.4 Validating Oracle Internet Directory High Availability
  • 7.3.5 Oracle Internet Directory Failover and Expected Behavior
    • 7.3.5.1 Performing an Oracle Internet Directory Failover
    • 7.3.5.2 Performing a RAC Failover
  • 7.3.6 Troubleshooting Oracle Internet Directory High Availability
  • 7.3.7 Additional Oracle Internet Directory High Availability Issues
    • 7.3.7.1 Changing the Password of the ODS Schema Used by Oracle Internet Directory
• 7.4 Oracle Virtual Directory High Availability
  • 7.4.1 Oracle Virtual Directory Component Architecture
    • 7.4.1.1 Oracle Virtual Directory Runtime Considerations
    • 7.4.1.2 Oracle Virtual Directory Component Characteristics
      • 7.4.1.2.1 Oracle Virtual Directory Log File
  • 7.4.2 Oracle Virtual Directory High Availability Concepts
    • 7.4.2.1 Oracle Virtual Directory High Availability Architecture
      • 7.4.2.1.1 Oracle Virtual Directory High Availability Connect Features
    • 7.4.2.2 Oracle Virtual Directory Prerequisites
      • 7.4.2.2.1 Load Balancer Virtual Server Names for Oracle Virtual Directory
  • 7.4.3 Oracle Virtual Directory High Availability Configuration Steps
    • 7.4.3.1 Configuring Oracle Virtual Directory Without a WebLogic Domain
      • 7.4.3.1.1 Installing Oracle Virtual Directory on OVDHOST1
      • 7.4.3.1.2 Installing Oracle Virtual Directory on OVDHOST2
      • 7.4.3.1.3 Registering Oracle Virtual Directory with a WebLogic Domain
    • 7.4.3.2 Configuring Oracle Virtual Directory With a WebLogic Domain
      • 7.4.3.2.1 Installing Oracle WebLogic Server
      • 7.4.3.2.2 Installing the First Oracle Virtual Directory
      • 7.4.3.2.3 Creating boot.properties for the Administration Server on OVDHOST1
      • 7.4.3.2.4 Installing an Additional Oracle Virtual Directory
    • 7.4.3.3 Configuring Oracle Virtual Directory with Highly Available Data Sources
      • 7.4.3.3.1 Configuring Oracle Virtual Directory with a RAC Database
      • 7.4.3.3.2 Configuring Oracle Virtual Directory with LDAP
  • 7.4.4 Validating Oracle Virtual Directory High Availability
    • 7.4.4.1 Validating Oracle Virtual Directory High Availability Using SSL
  • 7.4.5 Oracle Virtual Directory Failover and Expected Behavior
    • 7.4.5.1 Performing an Oracle Virtual Directory Failover
    • 7.4.5.2 Performing a RAC Failover
  • 7.4.6 Troubleshooting Oracle Virtual Directory High Availability
    • 7.4.6.1 Troubleshooting LDAP Adapter Creation
• 7.5 Oracle Directory Integration Platform High Availability
  • 7.5.1 Oracle Directory Integration Platform Component Architecture
    • 7.5.1.1 Oracle Directory Integration Platform Component Characteristics
      • 7.5.1.1.1 Runtime Processes
      • 7.5.1.1.2 Process Lifecycle
      • 7.5.1.1.3 Request Flow
      • 7.5.1.1.4 Configuration Artifacts
      • 7.5.1.1.5 External Dependencies
      • 7.5.1.1.6 Oracle Directory Integration Platform Log File
  • 7.5.2 Oracle Directory Integration Platform High Availability Concepts
    • 7.5.2.1 Oracle Directory Integration Platform High Availability Architecture
      • 7.5.2.1.1 Starting and Stopping the Cluster
      • 7.5.2.1.2 Cluster-Wide Configuration Changes
    • 7.5.2.2 Protection from Failures and Expected Behavior
      • 7.5.2.2.1 Process Failure
      • 7.5.2.2.2 Expected Client Application Behavior When Failure Occurs
      • 7.5.2.2.3 External Dependency Failure
    • 7.5.2.3 Oracle Directory Integration Platform Prerequisites
  • 7.5.3 Oracle Directory Integration Platform and Oracle Directory Services Manager High Availability Configuration Steps
    • 7.5.3.1 Installing the WebLogic Administration Server on IDMHOST1 and IDMHOST2
    • 7.5.3.2 Installing and Configuring Oracle Directory Integration Platform and Oracle Directory Services Manager on IDMHOST1
    • 7.5.3.3 Creating boot.properties for the Administration Server on IDMHOST1
    • 7.5.3.4 Installing and Configuring Oracle Directory Integration Platform and Oracle Directory Services Manager on IDMHOST2
    • 7.5.3.5 Post-Installation Steps for Oracle Directory Integration Platform and Oracle Directory Services Manager
      • 7.5.3.5.1 Copy the Oracle Directory Integration Platform Configuration from IDMHOST1 to IDMHOST2
      • 7.5.3.5.2 Start the Managed Server on IDMHOST2 in a Cluster
    • 7.5.3.6 Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
      • 7.5.3.6.1 Configuring Oracle HTTP Server for Oracle Directory Services Manager High Availability
  • 7.5.4 Oracle Directory Integration Platform Failover and Expected Behavior
  • 7.5.5 Troubleshooting Oracle Directory Integration Platform High Availability
    • 7.5.5.1 Managed Server Log File Exceptions Received for Oracle Directory Integration Platform During a RAC Failover
    • 7.5.5.2 Dealing with Error Messages Received After Starting WebLogic Node Manager
    • 7.5.5.3 If WebLogic Node Manager Fails to Start
    • 7.5.5.4 Configuration Changes Do Not Automatically Propagate to All Oracle Directory Integration Platform Instances in a Highly Available Topology
    • 7.5.5.5 Operation Cannot Be Completed for Unknown Errors Message
• 7.6 Oracle Directory Services Manager High Availability
  • 7.6.1 Oracle Directory Services Manager Component Architecture
    • 7.6.1.1 Oracle Directory Services Manager Component Characteristics
      • 7.6.1.1.1 Lifecycle Management
      • 7.6.1.1.2 Oracle Directory Services Manager Log File
  • 7.6.2 Oracle Directory Services Manager High Availability Concepts
    • 7.6.2.1 Oracle Directory Services Manager High Availability Architecture
      • 7.6.2.1.1 Starting and Stopping the Cluster
    • 7.6.2.2 Protection from Failures and Expected Behaviors
      • 7.6.2.2.1 Process Failure
      • 7.6.2.2.2 Expected Client Application Behavior When Failure Occurs
      • 7.6.2.2.3 Expected Dependency Failure
    • 7.6.2.3 Oracle Directory Services Manager Prerequisites
  • 7.6.3 Oracle Directory Services Manager High Availability Configuration Steps
  • 7.6.4 Validating Oracle Directory Services Manager High Availability
    • 7.6.4.1 Performing a WebLogic Server Instance Failover
    • 7.6.4.2 Performing a RAC Database Failover
  • 7.6.5 Oracle Directory Services Manager Failover and Expected Behavior
    • 7.6.5.1 Using Oracle Directory Services Manager to Validate a Failover of a Managed Server
    • 7.6.5.2 Using Oracle Directory Services Manager to Validate a Failover of an Oracle Internet Directory Instance
    • 7.6.5.3 Using Oracle Directory Services Manager to Validate a RAC Failover
  • 7.6.6 Troubleshooting Oracle Directory Services Manager
    • 7.6.6.1 Dealing with Error Messages Received After Starting WebLogic Node Manager
    • 7.6.6.2 If WebLogic Node Manager Fails to Start
    • 7.6.6.3 Oracle Directory Services Manager Failover Using Oracle HTTP Server is Not Transparent
    • 7.6.6.4 Oracle Directory Services Manager Displays "LDAP Server is down" Message During Oracle Internet Directory Failover
    • 7.6.6.5 Oracle Directory Services Manager Temporarily Loses Its Connection During RAC Failover
  • 7.6.7 Additional Considerations for Oracle Directory Services Manager High Availability
• 7.7 Oracle Identity Federation High Availability
  • 7.7.1 Oracle Identity Federation Component Architecture
    • 7.7.1.1 Oracle Identity Federation Component Characteristics
      • 7.7.1.1.1 Runtime Processes
      • 7.7.1.1.2 Process Lifecycle
      • 7.7.1.1.3 Request Flow
      • 7.7.1.1.4 Configuration Artifacts
      • 7.7.1.1.5 External Dependencies
      • 7.7.1.1.6 Oracle Identity Federation Log File Location
  • 7.7.2 Oracle Identity Federation High Availability Concepts
    • 7.7.2.1 Oracle Identity Federation High Availability Architecture
      • 7.7.2.1.1 Starting and Stopping the Cluster
      • 7.7.2.1.2 Cluster-Wide Configuration Changes
    • 7.7.2.2 High Availability Considerations for Integration with Oracle Access Manager
    • 7.7.2.3 Oracle Identity Federation Prerequisites
      • 7.7.2.3.1 Using RCU to Create Oracle Identity Federation Schemas in the Repository
  • 7.7.3 Oracle Identity Federation High Availability Configuration Steps
    • 7.7.3.1 Installing Oracle WebLogic Server
    • 7.7.3.2 Installing Oracle Identity Federation on OIFHOST1
    • 7.7.3.3 Creating boot.properties for the Administration Server on OIFHOST1
    • 7.7.3.4 Installing Oracle Identity Federation on OIFHOST2
    • 7.7.3.5 Post-Installation Steps for Oracle Identity Federation
      • 7.7.3.5.1 Copy the Oracle Identity Federation Configuration Directory from OIFHOST1 to OIFHOST2
      • 7.7.3.5.2 Start the Managed Server on OIFHOST2 in a Cluster
      • 7.7.3.5.3 Configure Oracle HTTP Server
    • 7.7.3.6 Configuring the Load Balancer
      • 7.7.3.6.1 Load Balancer Virtual Server Name Setup
      • 7.7.3.6.2 Oracle Identity Federation Configuration
    • 7.7.3.7 Validating Oracle Identity Federation High Availability
    • 7.7.3.8 Enabling Oracle Identity Federation Integration with Highly Available LDAP Servers
  • 7.7.4 Oracle Identity Federation Failover and Expected Behavior
    • 7.7.4.1 Performing an Oracle Identity Federation Failover
    • 7.7.4.2 Performing a RAC Failover
  • 7.7.5 Troubleshooting Oracle Identity Federation High Availability
• 7.8 Collocated Architecture High Availability
  • 7.8.1 Collocated Architecture Overview
  • 7.8.2 Collocated Architecture High Availability Deployment
    • 7.8.2.1 Collocated Architecture Prerequisites
    • 7.8.2.2 Configuring Collocated Components for High Availability
  • 7.8.3 Validating the Collocated Components High Availability
    • 7.8.3.1 Validation Tests
    • 7.8.3.2 Failures and Expected Behaviors
  • 7.8.4 Troubleshooting Collocated Components Manager High Availability
  • 7.8.5 Additional Considerations for Collocated Components High Availability

8 Configuring Identity Management for Maximum High Availability

• 8.1 Introduction to the Maximum High Availability Identity Management Deployment
• 8.2 Overview of Replication
• 8.3 Setting up Multimaster Replication
  • 8.3.1 Setting Up LDAP Multimaster Replication
    • 8.3.1.1 Adding a Node in LDAP Multimaster Replication
    • 8.3.1.2 Deleting a Node in LDAP Multimaster Replication
  • 8.3.2 Setting Up Oracle Advanced Database Multimaster Replication
    • 8.3.2.1 Adding a Node in Oracle Advanced Database Multimaster Replication
    • 8.3.2.2 Deleting a Node in Oracle Advanced Database Multimaster Replication

9 Configuring High Availability for Web Tier Components

• 9.1 About the Web Tier
• 9.2 Oracle HTTP Server and High Availability Concepts
  • 9.2.1 Oracle HTTP Server Single-Instance Characteristics
    • 9.2.1.1 Oracle HTTP Server and Oracle WebLogic Server
    • 9.2.1.2 Oracle HTTP Server External Dependencies
  • 9.2.2 Oracle HTTP Server Startup and Shutdown Lifecycle
  • 9.2.3 Starting and Stopping Oracle HTTP Server
    • 9.2.3.1 Understanding the PID File
    • 9.2.3.2 Starting and Stopping Oracle HTTP Server Using Oracle Fusion Middleware Control
    • 9.2.3.3 Starting and Stopping Oracle HTTP Server Using opmnctl
  • 9.2.4 Oracle HTTP Server Configuration Artifacts
  • 9.2.5 Oracle HTTP Server Log File Locations
  • 9.2.6 Oracle HTTP Server High Availability Architecture and Failover Considerations
  • 9.2.7 Oracle HTTP Server Protection from Failures and Expected Behaviors
  • 9.2.8 Oracle HTTP Server Cluster-Wide Configuration Changes
  • 9.2.9 Configuring Oracle HTTP Server for High Availability
    • 9.2.9.1 Prerequisites
      • 9.2.9.1.1 Load Balancer
      • 9.2.9.1.2 Associating Oracle HTTP Server with a WebLogic Domain
    • 9.2.9.2 Install Oracle HTTP Server on Webhost1
      • 9.2.9.2.1 Configure Virtual Host(s)
      • 9.2.9.2.2 Configure mod_wl_ohs
      • 9.2.9.2.3 Restart Oracle HTTP Server
      • 9.2.9.2.4 Validate the Oracle HTTP Server Configuration
    • 9.2.9.3 Install Oracle HTTP Server on Webhost2
      • 9.2.9.3.1 Configure Virtual Host(s)
      • 9.2.9.3.2 Configure mod_wl_ohs
      • 9.2.9.3.3 Restart Oracle HTTP Server
      • 9.2.9.3.4 Validate the Oracle HTTP Server Configuration
• 9.3 Oracle Web Cache and High Availability Concepts
  • 9.3.1 Oracle Web Cache Single-Node Characteristics
    • 9.3.1.1 Oracle Web Cache Component Characteristics
    • 9.3.1.2 Oracle Web Cache Process Monitoring
    • 9.3.1.3 Oracle Web Cache Startup and Shutdown Lifecycle
    • 9.3.1.4 Oracle Web Cache Request Flow
    • 9.3.1.5 Oracle Web Cache Configuration Artifacts
    • 9.3.1.6 Log File Locations
  • 9.3.2 Oracle Web Cache High Availability Considerations
    • 9.3.2.1 Oracle Web Cache Stateless Load Balancing
    • 9.3.2.2 Oracle Web Cache Backend Failover
    • 9.3.2.3 Oracle Web Cache Session Binding
    • 9.3.2.4 Oracle Web Cache Cluster-Wide Configuration Changes
    • 9.3.2.5 Oracle Web Cache as a Software Load Balancer
  • 9.3.3 Configuring Oracle Web Cache High Availability Solutions
    • 9.3.3.1 Configure Oracle Web Cache Session Binding
    • 9.3.3.2 Configuring a Cache Cluster
      • 9.3.3.2.1 Configuration Prerequisites
      • 9.3.3.2.2 Understanding Failover Threshold and Capacity Settings
      • 9.3.3.2.3 Task 1: Add Caches to the Cluster and Configure Properties
      • 9.3.3.2.4 Task 2: Enable Tracking of Session Binding
      • 9.3.3.2.5 Task 3: Synchronize Configuration to Cluster Members
      • 9.3.3.2.6 Removing a Cache Member from a Cluster
      • 9.3.3.2.7 Configuring Administration and Invalidation-Only Clusters
    • 9.3.3.3 Configure Oracle Web Cache as a Software Load Balancer

10 Active-Passive Topologies for Oracle Fusion Middleware High Availability

• 10.1 Oracle Fusion Middleware Cold Failover Cluster Topology Concepts
• 10.2 Configuring Oracle Fusion Middleware for Active-Passive Deployments
  • 10.2.1 General Requirements for Cold Failover Clusters
    • 10.2.1.1 Terminology for Directories and Directory Environment Variables
  • 10.2.2 Transforming Oracle Fusion Middleware Infrastructure Components
    • 10.2.2.1 Administration Server Topology 1
      • 10.2.2.1.1 Topology 1 Installation Procedure
    • 10.2.2.2 Administration Server Topology 2
      • 10.2.2.2.1 Topology 2 Installation Procedure
    • 10.2.2.3 Transforming the Administration Server for Cold Failover Clusters
    • 10.2.2.4 Transforming Oracle WebLogic Managed Servers
      • 10.2.2.4.1 Transforming an Oracle WebLogic Managed Server using the Fusion Middleware Administration Console
      • 10.2.2.4.2 Transforming an Oracle WebLogic Managed Server using the WLST Command Line
    • 10.2.2.5 Transforming Node Manager
    • 10.2.2.6 Transforming Oracle Process Management and Notification Server
    • 10.2.2.7 Transforming Oracle Enterprise Manager for an Oracle Instance
    • 10.2.2.8 Transforming Web Tier Components and Clients
      • 10.2.2.8.1 Transforming Oracle HTTP Server
      • 10.2.2.8.2 Transforming Oracle Web Cache
    • 10.2.2.9 Instance-specific considerations
      • 10.2.2.9.1 UNIX Platforms
      • 10.2.2.9.2 Windows Platform
  • 10.2.3 Transforming Oracle Fusion Middleware Components
    • 10.2.3.1 Transforming Oracle Internet Directory and Its Clients
      • 10.2.3.1.1 Transforming Oracle Internet Directory
      • 10.2.3.1.2 Transforming Oracle Internet Directory Clients
    • 10.2.3.2 Transforming Oracle Virtual Directory and Its Clients
      • 10.2.3.2.1 Transforming Oracle Virtual Directory
      • 10.2.3.2.2 Transforming Oracle Virtual Directory Clients
    • 10.2.3.3 Transforming Oracle Directory Integration Platform and Oracle Directory Services Manager and Their Clients
      • 10.2.3.3.1 Transforming Oracle Directory Integration Platform and Oracle Directory Services Manager
      • 10.2.3.3.2 Transforming Oracle Directory Integration Platform and Oracle Directory Services Manager Clients
    • 10.2.3.4 Transforming Oracle Identity Federation and Its Client
      • 10.2.3.4.1 Transforming Oracle Identity Federation
      • 10.2.3.4.2 Transforming Oracle Identity Federation Clients
    • 10.2.3.5 Transforming an Oracle SOA Suite
    • 10.2.3.6 Transforming an Oracle WebCenter Suite
    • 10.2.3.7 Transforming Oracle Portal, Forms, Reports, and Discoverer
      • 10.2.3.7.1 Transforming Oracle Forms for Cold Failover Clusters
      • 10.2.3.7.2 Transforming Oracle Reports for Cold Failover Clusters
      • 10.2.3.7.3 Transforming Oracle Discoverer for Cold Failover Clusters
      • 10.2.3.7.4 Transforming Oracle Portal for Cold Failover Clusters
      • 10.2.3.7.5 Transforming Oracle Business Activity Management (BAM)
      • 10.2.3.7.6 Transforming a Custom ADF Deployment
    • 10.2.3.8 Single Sign-On Re-registration (If required)
  • 10.2.4 Transforming an Oracle Database
    • 10.2.4.1 Database Instance Platform-Specific Considerations
• 10.3 Oracle Fusion Middleware Cold Failover Cluster Example Topologies
  • 10.3.1 Example Topology 1
  • 10.3.2 Example Topology 2
  • 10.3.3 Example Topology 3
• 10.4 Transforming the Administration Server in an Existing Domain for Cold Failover Clusters
  • 10.4.1 Destination Topologies
  • 10.4.2 Cold Failover Clusters Transformation Procedure

11 Using Oracle Cluster Ready Services

• 11.1 Introduction to Oracle Clusterware
• 11.2 Cluster Ready Services and Oracle Fusion Middleware
• 11.3 Installing and Configuring Oracle Clusterware with CRS
  • 11.3.1 Installing ASCRS
  • 11.3.2 Configuring ASCRS with Oracle Fusion Middleware
• 11.4 Using ASCRS to Manage Resources
  • 11.4.1 Creating CRS Managed Resources
    • 11.4.1.1 Creating a Virtual IP Resource
    • 11.4.1.2 Creating a Shared Disk Resource
    • 11.4.1.3 Creating an Oracle Database Listener Resource
    • 11.4.1.4 Creating an Oracle Database Resource
    • 11.4.1.5 Creating a Middleware Resource
  • 11.4.2 Updating Resources
  • 11.4.3 Starting Up Resources
  • 11.4.4 Shutting Down Resources
  • 11.4.5 Resource Switchover
  • 11.4.6 Deleting Resources
  • 11.4.7 Checking Resource Status
  • 11.4.8 Configuring the Oracle WebLogic Environment
• 11.5 Example Topologies
• 11.6 Troubleshooting Oracle CRS

12 Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer

• 12.1 Overview of Oracle Portal, Forms, Reports, and Discoverer
  • 12.1.1 Oracle Portal, Forms, Reports, and Discoverer Architecture
  • 12.1.2 Common Log Files
  • 12.1.3 Common Component Failures and Expected Behaviors
    • 12.1.3.1 Oracle Web Cache and Oracle HTTP Server Process Failures
    • 12.1.3.2 Common Component Node Failures
    • 12.1.3.3 Common Component WebLogic Managed Server Failures
    • 12.1.3.4 Common Component Database Failures
  • 12.1.4 Oracle Portal, Forms, Reports, and Discoverer Cluster-Wide Configuration Changes
  • 12.1.5 Common Component Log File Information
• 12.2 Oracle Portal and High Availability Concepts
  • 12.2.1 Oracle Portal Single-Instance Characteristics
    • 12.2.1.1 Oracle Portal Request Flow
    • 12.2.1.2 Oracle Portal Component Characteristics
    • 12.2.1.3 Oracle Portal Startup and Shutdown of Processes and Lifecycle
    • 12.2.1.4 Oracle Portal Deployment Artifacts
    • 12.2.1.5 Oracle Portal Configuration Information
    • 12.2.1.6 Oracle Portal Logging and Log Configuration
      • 12.2.1.6.1 Oracle Portal Log Files
    • 12.2.1.7 Oracle Portal External Dependencies
  • 12.2.2 Oracle Portal Protection from Failures and Expected Behavior
    • 12.2.2.1 Oracle Portal Process Failures
    • 12.2.2.2 Oracle Portal Node Failures
    • 12.2.2.3 Oracle Portal WebLogic Managed Server Failures
    • 12.2.2.4 Oracle Portal Protection from Database Failures
• 12.3 Oracle Reports and High Availability Concepts
  • 12.3.1 Oracle Reports Single-Instance Characteristics
    • 12.3.1.1 Oracle Reports State Information
    • 12.3.1.2 Oracle Reports External Dependencies
    • 12.3.1.3 Oracle Reports Specific Configuration Files
    • 12.3.1.4 Oracle Reports Connection Retry
    • 12.3.1.5 Oracle Reports Process Flow
    • 12.3.1.6 Oracle Reports Log Files
  • 12.3.2 Oracle Reports Protection from Failure and Expected Behavior
    • 12.3.2.1 Oracle Reports Process Failures
    • 12.3.2.2 Oracle Reports Node Failures
    • 12.3.2.3 Oracle Reports WebLogic Managed Server Failures
    • 12.3.2.4 Oracle Reports Database Failures
• 12.4 Oracle Forms and High Availability Concepts
  • 12.4.1 Oracle Forms Single-Instance Component Characteristics
    • 12.4.1.1 Oracle Forms State Information
    • 12.4.1.2 Oracle Forms Database Requirements
    • 12.4.1.3 Oracle Forms Request Flow
    • 12.4.1.4 Oracle Forms Configuration Persistence
    • 12.4.1.5 Oracle Forms Runtime Considerations
    • 12.4.1.6 Oracle Forms Process Flow
    • 12.4.1.7 Oracle Forms Configuration Files
    • 12.4.1.8 Oracle Forms External Dependencies
    • 12.4.1.9 Oracle Forms Log Files
  • 12.4.2 Oracle Forms Protection from Failover and Expected Behavior
    • 12.4.2.1 Oracle Forms N+1 Redundancy
    • 12.4.2.2 Oracle Forms N+M Redundancy
    • 12.4.2.3 Oracle Forms Virtual Machines
    • 12.4.2.4 Oracle Forms Configuration Cloning
    • 12.4.2.5 Oracle Forms Process Failures
    • 12.4.2.6 Oracle Forms Node Failures
    • 12.4.2.7 Oracle Forms WebLogic Managed Server Failures
    • 12.4.2.8 Oracle Forms Database Failures
• 12.5 Oracle Discoverer and High Availability Concepts
  • 12.5.1 Oracle Discoverer Single-Instance Characteristics
    • 12.5.1.1 Oracle Discoverer Runtime Considerations
    • 12.5.1.2 Oracle Discoverer Viewer and Web Cache
    • 12.5.1.3 Oracle Discoverer Configuration Considerations
    • 12.5.1.4 Oracle Discoverer Deployment Considerations
    • 12.5.1.5 Oracle Discoverer Log File Locations
    • 12.5.1.6 Discoverer Log Files
  • 12.5.2 Oracle Discoverer Protection from Failures and Expected Behavior
    • 12.5.2.1 Preference Server Failover
    • 12.5.2.2 Session State Replication and Failover
    • 12.5.2.3 Performance Recommendation
    • 12.5.2.4 Propagation of Configuration Changes Across the Cluster
    • 12.5.2.5 Cluster-Wide Application Deployment
    • 12.5.2.6 Online Application Deployment
    • 12.5.2.7 Oracle Discoverer Process Failures
    • 12.5.2.8 Oracle Discoverer Node Failures
    • 12.5.2.9 Oracle Discoverer WebLogic Managed Server Failures
    • 12.5.2.10 Oracle Discoverer Database Failures
• 12.6 Configuring Oracle Portal, Forms, Reports, and Discoverer for High Availability
  • 12.6.1 Prerequisites
    • 12.6.1.1 Dependencies
    • 12.6.1.2 Network Requirements
      • 12.6.1.2.1 Load Balancer
      • 12.6.1.2.2 Load Balancer Configuration - Virtual Server Names and Ports
    • 12.6.1.3 Databases
    • 12.6.1.4 Shared Directories
    • 12.6.1.5 Managed Port Numbers
    • 12.6.1.6 Site Names
  • 12.6.2 Assumptions
    • 12.6.2.1 Ports
  • 12.6.3 Creating the Metadata Repository
    • 12.6.3.1 Install the Repository Creation Utility (RCU)
    • 12.6.3.2 Run Repository Creation Utility
  • 12.6.4 Install and Configure Application Tier on APPHOST1
    • 12.6.4.1 Install Oracle WebLogic Server
    • 12.6.4.2 Install Oracle Portal, Forms, Reports, and Discoverer Software
    • 12.6.4.3 Validation
    • 12.6.4.4 Generic Configuration
      • 12.6.4.4.1 Set Admin Server Listen Address
      • 12.6.4.4.2 Configure Virtual Hosts
      • 12.6.4.4.3 Create boot.properties File
      • 12.6.4.4.4 Configure sqlnet.ora
      • 12.6.4.4.5 Configure Web Cache
      • 12.6.4.4.6 Change the Web Cache Passwords
      • 12.6.4.4.7 Restart Web Tier (Oracle HTTP Server and Web Cache)
      • 12.6.4.4.8 Register with Single Sign On Server
      • 12.6.4.4.9 Change Host Assertion in WebLogic
    • 12.6.4.5 Configure Oracle Portal for High Availability
      • 12.6.4.5.1 Rewire Portal Repository
      • 12.6.4.5.2 Configure Parallel Page Engine Loop-Back with Load Balancer
      • 12.6.4.5.3 Database Wallets and Portal
      • 12.6.4.5.4 Restart All Components
      • 12.6.4.5.5 Post-installation Step for Portal Installation with Oracle RAC
      • 12.6.4.5.6 Validate Configuration
    • 12.6.4.6 Configure Oracle Forms for High Availability
      • 12.6.4.6.1 Create TNSNAMES Entries for Customer Databases
      • 12.6.4.6.2 Restart WLS_FORMS
      • 12.6.4.6.3 Validate Configuration
    • 12.6.4.7 Configure Oracle Reports for High Availability
      • 12.6.4.7.1 Create Reports Queue in Database
      • 12.6.4.7.2 Create a TNSNAMES Entry for Reports Queue
      • 12.6.4.7.3 Create a Security Key for the Reports Queue
      • 12.6.4.7.4 Configure the Database Job Repository for In-Process Reports Servers
      • 12.6.4.7.5 Configure the Reports Server to Access Shared Output Directory
      • 12.6.4.7.6 Restart WLS_REPORTS
      • 12.6.4.7.7 Validate Configuration
    • 12.6.4.8 Configure Oracle Discoverer for High Availability
      • 12.6.4.8.1 Create TNSNAMES Entries for Customer Databases
      • 12.6.4.8.2 Update configuration.xml
      • 12.6.4.8.3 Discoverer Viewer and Web Cache
      • 12.6.4.8.4 Enable Single Sign On
      • 12.6.4.8.5 Restart All Components
      • 12.6.4.8.6 Validate Configuration
  • 12.6.5 Install and Configure Application Tier on APPHOST2
    • 12.6.5.1 Install Oracle WebLogic Server
    • 12.6.5.2 Install Oracle Portal, Forms, Reports, and Discoverer Software
    • 12.6.5.3 Generic Configuration
      • 12.6.5.3.1 Copy Configuration Information from APPHOST1
      • 12.6.5.3.2 Configure Virtual Hosts
      • 12.6.5.3.3 Update Oracle HTTP Server Configuration to be Cluster Aware
      • 12.6.5.3.4 Change the Web Cache Passwords
      • 12.6.5.3.5 Configure Web Cache
      • 12.6.5.3.6 Restart Web Processes on APPHOST1 and APPHOST2
      • 12.6.5.3.7 Start Oracle Node Manager on APPHOST2
    • 12.6.5.4 Configure Oracle Portal for High Availability
      • 12.6.5.4.1 Copy Configuration Information from APPHOST1
      • 12.6.5.4.2 Create Portal Directories
      • 12.6.5.4.3 Update Instance Paths
      • 12.6.5.4.4 Restart the Web Process
      • 12.6.5.4.5 Start WLS_PORTAL1
      • 12.6.5.4.6 Validate the Configuration
      • 12.6.5.4.7 Best Practices
    • 12.6.5.5 Configure Oracle Forms for High Availability
      • 12.6.5.5.1 Create a TNSNAMES entries for Customer Databases
      • 12.6.5.5.2 Copy Forms Configuration Files
      • 12.6.5.5.3 Update default.env
      • 12.6.5.5.4 Restart WLS_FORMS1
      • 12.6.5.5.5 Validate the Configuration
      • 12.6.5.5.6 Best Practices
    • 12.6.5.6 Configure Oracle Reports for High Availability
      • 12.6.5.6.1 Create a TNSNAMES entries for Customer Databases
      • 12.6.5.6.2 Configure the Reports Server to Access Shared output directory.
      • 12.6.5.6.3 Configure the database job repository for in-process Reports Servers
      • 12.6.5.6.4 Creating an Oracle Reports Server Cluster
      • 12.6.5.6.5 Restart WLS_REPORTS and WLS_REPORTS1
      • 12.6.5.6.6 Validate the Configuration
      • 12.6.5.6.7 Managing Connection Availability for Oracle Reports Services
    • 12.6.5.7 Configure Oracle Discoverer for High Availability
      • 12.6.5.7.1 Create a TNSNAMES entries for Customer Databases
      • 12.6.5.7.2 Copy Discoverer Configuration Files.
      • 12.6.5.7.3 Update configuration.xml
      • 12.6.5.7.4 Changing the Preference Store
      • 12.6.5.7.5 Restart WLS_DISCO and WLS_DISCO1
      • 12.6.5.7.6 Validate the Configuration
      • 12.6.5.7.7 Failover of the Preference Server
      • 12.6.5.7.8 Setting up Discoverer WSRP Portlet Producer in a Clustered Environment
      • 12.6.5.7.9 Best Practices
  • 12.6.6 Scaling Out the Deployment

13 Using HA Power Tools

• 13.1 Enabling HA Power Tools in the Oracle WebLogic Administration Console
• 13.2 Creating UDDs for SOA, BAM and JRF WS Async Services Using HA Power Tools
• 13.3 Configuring Java Object Cache for a Cluster Using HA Power Tools
• 13.4 Configuring Java Object Cache for a Managed Servers Using HA Power Tools

A Setting Up Auditing with an Oracle RAC Database Store

• A.1 Using WebLogic Server to Configure Audit Data Sources and Multi Data Sources
• A.2 Configuring the JDBC String for the Audit Loader

B Recommended Multi Data Sources

• B.1 JDBC Multi Data Source-0
• B.2 JDBC Data Source-0 (non-XA)
• B.3 JDBC Data Source-0 (XA)

C Whole Server Migration for Windows

• C.1 Using Windows Control Panel
• C.2 Using the netsh Command Line

D Oracle SOA Suite Workbook

• D.1 Workbook Tables for Oracle SOA Suite

E Identity Management Workbook

• E.1 Workbook Tables for Oracle Identity Management

F WebCenter Workbook

• F.1 Workbook Tables for Oracle WebCenter

G Oracle Portal, Forms, Reports, and Discoverer Workbook

• G.1 Workbook Tables for Oracle Portal, Forms, Reports, and Discoverer

H ascrsctl Online Help

• H.1 create/as
• H.2 create/db
• H.3 create/dnlsnr
• H.4 create/disk
• H.5 create/vip
• H.6 delete
• H.7 start
• H.8 status
• H.9 stop
• H.10 switch
• H.11 update/as
• H.12 update/db
• H.13 update/dblsnr
• H.14 update/disk
• H.15 update/vip

I Running CacheWatcher to verify Java Object Cache

• I.1 Running CacheWatcher

Index