Go to main content
1/26
Contents
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
Server 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
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.10.2
Considerations for Using File Stores on NFS
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
GridLink Data Sources
3.14
Multi Data Sources
3.15
Cluster Configuration and config.xml
3.16
About Singleton Services
3.17
WebLogic Server and LDAP High Availability
4
Configuring High Availability for Oracle SOA Suite
4.1
Introduction to Oracle SOA Suite
4.2
Oracle SOA Service Infrastructure High Availability
4.2.1
Oracle SOA Service Infrastructure Single-Instance Characteristics
4.2.1.1
Oracle SOA Service Infrastructure Application Characteristics
4.2.1.2
Oracle SOA Service Infrastructure Startup and Shutdown Lifecyle
4.2.1.3
Oracle SOA Service Infrastructure External Dependencies
4.2.1.4
Oracle SOA Service Infrastructure Startup and Shut Down of Processes
4.2.1.5
Oracle SOA Service Infrastructure Configuration Artifacts
4.2.1.6
Oracle SOA Service Infrastructure Log File Locations
4.2.2
Oracle SOA Service Infrastructure High Availability Architecture and Failover Considerations
4.2.2.1
Oracle SOA Service Infrastructure Protection from Failures and Expected Behavior
4.2.2.1.1
WebLogic Server Failure
4.2.2.1.2
Node Failure
4.2.2.1.3
Database Failure
4.2.2.2
Oracle SOA Service Infrastructure Cluster-Wide Deployment
4.2.2.3
Online Redeployment of Oracle SOA Service Infrastructure Composites in a Cluster
4.2.2.4
Oracle SOA Service Infrastructure Cluster-Wide Configuration Changes
4.3
Oracle BPEL Process Manager and High Availability Concepts
4.3.1
Oracle BPEL Process Manager Single-Instance Characteristics
4.3.1.1
BPEL Process Manager Component Characteristics
4.3.1.2
Oracle BPEL Process Manager Startup and Shutdown Lifecycle
4.3.1.3
Oracle BPEL Process Manager Request Flow and Recovery
4.3.1.4
Oracle BPEL Process Manager Configuration Artifacts
4.3.2
Oracle BPEL Process Manager High Availability Architecture and Failover Considerations
4.3.2.1
Oracle BPEL Process Manager Protection from Failures and Expected Behavior
4.3.2.1.1
Recovering Failed BPEL and Mediator Instances
4.3.2.2
Oracle BPEL Process Manager Cluster-Wide Configuration Changes
4.4
Oracle BPM Suite and High Availability Concepts
4.4.1
Oracle BPM Suite Single Instance Concepts
4.4.1.1
Oracle BPM Suite Component Characteristics
4.4.1.2
Oracle BPM Suite Component Interaction
4.4.1.3
Oracle BPM Suite Startup and Shutdown Lifecycle
4.4.1.4
Oracle BPM Suite Configuration Artifacts
4.4.2
Oracle BPMN Service Engine High Availability
4.4.2.1
Oracle BPMN Service Engine Single Instance Characteristics
4.4.2.1.1
Oracle BPMN Service Engine Single Instance Architecture
4.4.2.1.2
Oracle BPMN Service Engine External Dependencies
4.4.2.1.3
Oracle BPMN Service Engine Startup and Shutdown Lifecycle
4.4.2.1.4
Oracle BPMN Service Engine Log Files
4.4.2.2
Oracle BPMN Service Engine High Availability Considerations
4.4.2.2.1
Oracle BPMN Service Engine High Availability Architecture and Failover Considerations
4.4.2.2.2
Configuring Oracle BPMN Service Engine for High Availability
4.4.2.2.3
Cluster-Wide Configuration Changes for Oracle BPMN Service Engine
4.4.3
Oracle Business Process Web Applications High Availability
4.4.3.1
Oracle Business Process Web Applications Single Instance Characteristics
4.4.3.1.1
Oracle Business Process Web Applications Single Instance Architecture
4.4.3.1.2
Oracle Business Process Web Applications External Dependencies
4.4.3.1.3
Oracle Business Process Web Applications Startup and Shutdown Lifecycle
4.4.3.1.4
Oracle Business Process Web Applications Log Files
4.4.3.2
Oracle Business Process Web Applications High Availability Considerations
4.4.3.2.1
Oracle Business Process Web Applications High Availability Architecture and Failover Considerations
4.4.3.2.2
Configuring Oracle Business Process Web Applications for High Availability
4.4.3.2.3
Cluster-Wide Configuration Changes for Oracle Business Process Web Applications
4.4.4
Oracle Business Process Analytics High Availability
4.4.4.1
Oracle Business Process Analytics Single Instance Characteristics
4.4.4.1.1
Oracle Business Process Analytics Single Instance Architecture
4.4.4.1.2
Oracle Business Process Analytics External Dependencies
4.4.4.1.3
Oracle Business Process Analytics Startup and Shutdown Lifecycle
4.4.4.1.4
Oracle Business Process Analytics Log Files
4.4.4.2
Oracle Business Process Analytics High Availability Considerations
4.4.4.2.1
Oracle Business Process Analytics High Availability Architecture and Failover Considerations
4.4.4.2.2
Configuring Oracle Business Process Analytics for High Availability
4.4.4.2.3
Cluster-Wide Configuration Changes for Oracle Business Process Analytics
4.5
Oracle Mediator and High Availability Concepts
4.5.1
Oracle Mediator Single-Instance Characteristics
4.5.1.1
Oracle Mediator Component Characteristics
4.5.1.2
Oracle Mediator Startup and Shutdown Lifecycle
4.5.1.3
Oracle Mediator Request Flow
4.5.1.4
Oracle Mediator Configuration Artifacts
4.5.2
Oracle Mediator High Availability Architecture and Failover Considerations
4.5.2.1
Oracle Mediator Protection from Failures and Expected Behavior
4.5.2.1.1
Recovering Failed Mediator Instances
4.5.2.1.2
Oracle Mediator's Resequencing in a Cluster
4.5.2.2
Troubleshooting Oracle Mediator High Availability
4.6
Oracle Human Workflow and High Availability Concepts
4.6.1
Oracle Human Workflow Single-Instance Characteristics
4.6.1.1
Oracle Human Workflow Startup and Shutdown Lifecycle
4.6.1.2
Oracle Human Workflow Request Processing
4.6.1.3
Oracle Human Workflow Configuration Artifacts
4.6.1.3.1
Managing the URI of the Human Task Service Component Task Details Application
4.6.2
Oracle Human Workflow High Availability Architecture and Failover Considerations
4.6.2.1
Oracle Human Workflow Protection from Failures and Expected Behavior
4.6.2.2
Manual Recovery Required for Human Workflow Task in Rejected MSG Table
4.6.3
Troubleshooting Oracle Human Workflow High Availability
4.7
Oracle B2B and High Availability Concepts
4.7.1
Oracle B2B Single-Instance Characteristics
4.7.1.1
Oracle B2B Component Characteristics
4.7.1.2
Oracle B2B Startup and Shutdown Lifecycle
4.7.1.3
Oracle B2B Request Flow
4.7.1.4
Oracle B2B Configuration Artifacts
4.7.2
Oracle B2B High Availability Architecture and Failover Considerations
4.7.2.1
Oracle B2B Protection from Failures and Expected Behavior
4.7.2.2
Oracle B2B High Availability Best Practices
4.7.2.3
Oracle B2B Cluster-Wide Configuration Changes
4.7.2.4
Oracle B2B Deployments in a Cluster
4.7.2.5
Troubleshooting Oracle B2B Active-Active Configuration
4.7.2.5.1
Purge, Import, or Deployment of B2B Metadata
4.7.2.5.2
Error While Retrieving Oracle B2B Document Definitions
4.8
Oracle Web Services Manager and High Availability Concepts
4.8.1
Oracle WSM Single-Instance Characteristics
4.8.1.1
Oracle WSM Component Characteristics
4.8.1.2
Oracle WSM Startup and Shutdown Lifecycle
4.8.1.3
Oracle WSM Request Flow
4.8.1.4
Oracle WSM Configuration Artifacts
4.8.2
Oracle WSM High Availability Architecture and Failover Considerations
4.8.2.1
Oracle WSM Protection from Failures and Expected Behavior
4.8.2.2
Oracle WSM Cluster-Wide Configuration Changes
4.8.2.3
Configuring the Java Object Cache for Oracle WSM
4.8.2.4
Configuring Distributed Notifications for the MDS Repository
4.9
Oracle User Messaging Service and High Availability Concepts
4.9.1
Oracle User Messaging Service Single-Instance Characteristics
4.9.1.1
Oracle User Messaging Service Component Characteristics
4.9.1.2
Oracle User Messaging Service Startup and Shutdown Lifecycle
4.9.1.3
Oracle User Messaging Service Request Flow
4.9.1.4
Oracle User Messaging Service Configuration Artifacts
4.9.2
Oracle User Messaging Service High Availability Architecture and Failover Considerations
4.9.2.1
Oracle User Messaging Service Protection from Failures and Expected Behavior
4.9.2.2
Oracle User Messaging Service Cluster-Wide Configuration Changes
4.10
Oracle JCA Adapters and High Availability Concepts
4.10.1
Oracle JCA Adapters Single-Instance Characteristics
4.10.1.1
Oracle JCA Adapters Component Lifecycle
4.10.1.2
Oracle JCA Adapters Reliability and Transactional Behavior
4.10.1.3
Oracle JCA Adapters - Rejected Message Handling
4.10.2
Oracle JCA Adapters High Availability Architecture and Failover Considerations
4.10.2.1
Oracle JCA Adapters High Availability Error Handling
4.10.2.2
Oracle File and FTP Adapters High Availability
4.10.2.3
Oracle Database Adapters High Availability
4.10.2.4
Oracle JMS Adapters High Availability
4.10.2.4.1
Message Redelivery
4.10.2.4.2
Use of WebLogic Server Distributed Destinations
4.10.2.5
Oracle JCA Adapters Log File Locations
4.11
Oracle Business Activity Monitoring and High Availability Concepts
4.11.1
Oracle Business Activity Monitoring Single-Instance Characteristics
4.11.1.1
Oracle Business Activity Monitoring Component Characteristics
4.11.1.2
Oracle Business Activity Monitoring Startup/Shutdown Lifecycle
4.11.1.3
Oracle Business Activity Monitoring Startup and Shutdown of Processes
4.11.1.4
Oracle Business Activity Monitoring Configuration Artifacts
4.11.2
Oracle Business Activity Monitoring High Availability Architecture and Failover Considerations
4.11.2.1
Oracle Business Activity Monitoring Protection from Failures and Expected Behavior
4.11.2.2
Oracle Business Activity Monitoring Cluster-Wide Configuration Changes
4.11.2.3
Considerations for BAM Client Retries
4.12
Oracle Service Bus and High Availability Concepts
4.12.1
Oracle Service Bus Single Node Characteristics
4.12.1.1
Oracle Service Bus Session State
4.12.1.2
Oracle Service Bus External Dependencies
4.12.1.3
Oracle Service Bus Configuration Artifacts
4.12.1.4
Oracle Service Bus Deployment Artifacts
4.12.1.5
Oracle Service Bus Startup and Shutdown
4.12.1.6
Oracle Service Bus Log File Locations
4.12.2
Oracle Service Bus High Availability Architecture and Failover Considerations
4.12.2.1
Oracle Service Bus Protection from Failures and Expected Behavior
4.12.2.1.1
WebLogic Server Failure
4.12.2.1.2
Node Failure
4.12.2.1.3
Database Failure
4.12.2.2
Oracle Service Bus Cluster-Wide Deployment
4.12.2.3
Online Redeployment of Oracle Service Bus in a Cluster
4.12.2.4
Oracle Service Bus Cluster-Wide Configuration Changes
4.13
Configuring High Availability for Oracle SOA Service Infrastructure and Component Service Engines
4.13.1
Preparing the Environment: Prerequisite Steps Before Setting up a SOA High Availability Configuration
4.13.1.1
Database Prerequisites
4.13.1.2
VIP and IP Prerequisites
4.13.1.3
Shared Storage Prerequisites
4.13.1.4
Installing and Configuring an LDAP Provider
4.13.1.5
Synchronizing System Clocks
4.13.1.6
Terminology for Directories and Directory Environment Variables
4.13.1.7
Installing and Configuring the Database Repository
4.13.1.8
Using Oracle Fusion Middleware Repository Creation Utility to Load the Fusion Middleware Schemas in the Database
4.13.1.8.1
Running RCU
4.13.1.8.2
Configuring SOA Schemas for Transactional Recovery Privileges
4.13.1.9
Configuring Virtual Server Names and Ports for the Load Balancer
4.13.1.10
Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
4.13.1.10.1
Validating Oracle HTTP Server
4.13.2
Installing Oracle Fusion Middleware Home
4.13.2.1
Installing Oracle WebLogic Server
4.13.2.2
Installing Oracle Fusion Middleware for Oracle SOA
4.13.3
Enabling VIP1 in SOAHOST1 and VIP2 in SOAHOST2
4.13.4
Running Oracle Fusion Middleware Configuration Wizard on SOAHOST1 to Create the SOA Domain
4.13.5
Creating boot.properties for the Administration Server on SOAHOST1
4.13.6
Starting and Validating the Administration Server in SOAHOST1
4.13.6.1
Starting the Administration Server on SOAHOST1
4.13.6.2
Validating the Administration Server
4.13.7
Disabling Host Name Verification for the Administration Server and the WLS_SOAn Managed Servers
4.13.8
Configuring Oracle Coherence for Deploying Composites
4.13.9
Starting the System in SOAHOST1
4.13.9.1
Starting Node Manager on SOAHOST1
4.13.9.2
Starting and Validating the WLS_SOA1 Managed Server
4.13.10
Propagating the Domain Configuration to SOAHOST2 with pack/unpack Utilities
4.13.11
Extracting XEngine Files in the Second Node
4.13.12
Starting the System in SOAHOST2
4.13.12.1
Starting Node Manager on SOAHOST2
4.13.12.2
Starting and Validating the WLS_SOA2 Managed Server
4.13.13
Configuring Oracle HTTP Servers for the Administration Server and the WLS_SOAn Managed Servers
4.13.14
Validating Access Through Oracle HTTP Server
4.13.15
Configuring JMS Persistence Store as Shared Across the Servers
4.13.16
Configuring a Default Persistent Store for Transaction Recovery
4.13.17
Setting the Front End HTTP Host and Port
4.13.18
Setting the WLS Cluster Address for Direct Binding/RMI Invocations to Composites
4.13.19
Deploying Applications
4.13.20
Configuring Server Migration for the WLS_SOA Servers
4.13.20.1
Setting Up a User and Tablespace for the Server Migration Leasing Table
4.13.20.2
Creating a GridLink or Multi Data Source Using the Oracle WebLogic Administration Console
4.13.20.3
Editing Node Manager's Properties File
4.13.20.4
Setting Environment and Superuser Privileges for the wlsifconfig.sh Script
4.13.20.5
Configuring Server Migration Targets
4.13.20.6
Testing the Server Migration
4.13.21
Scaling the Topology
4.13.21.1
Scaling Up the Topology (Adding Managed Servers to Existing Nodes)
4.13.21.2
Scaling Out the Topology (Adding Managed Servers to New Nodes)
4.14
Configuring High Availability for Oracle Service Bus, with SOA Service Infrastructure and Component Service Engines
4.14.1
Preparing the Environment: Prerequisite Steps Before Setting up a SOA High Availability Configuration
4.14.1.1
Database Prerequisites
4.14.1.2
VIP and IP Prerequisites
4.14.1.3
Shared Storage Prerequisites
4.14.1.4
Installing and Configuring an LDAP Provider
4.14.1.5
Synchronizing System Clocks
4.14.1.6
Terminology for Directories and Directory Environment Variables
4.14.1.7
Installing and Configuring the Database Repository
4.14.1.8
Using Oracle Fusion Middleware Repository Creation Utility to Load the Fusion Middleware Schemas in the Database
4.14.1.8.1
Running RCU
4.14.1.8.2
Configuring SOA Schemas for Transactional Recovery Privileges
4.14.1.9
Configuring Virtual Server Names and Ports for the Load Balancer
4.14.1.10
Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
4.14.1.10.1
Validating Oracle HTTP Server
4.14.2
Installing Oracle Fusion Middleware Home
4.14.2.1
Installing Oracle WebLogic Server
4.14.2.2
Installing Oracle Fusion Middleware for Oracle SOA
4.14.2.3
Installing Oracle Service Bus
4.14.3
Enabling VIP1 and VIP3 in SOAHOST1 and VIP2 and VIP4 in SOAHOST2
4.14.4
Running Oracle Fusion Middleware Configuration Wizard on SOAHOST1 to Create the SOA and OSB Domain
4.14.5
Creating boot.properties for the Administration Server on SOAHOST1
4.14.6
Starting and Validating the Administration Server in SOAHOST1
4.14.6.1
Starting the Administration Server on SOAHOST1
4.14.6.2
Validating the Administration Server
4.14.7
Disabling Host Name Verification for the Administration Server and the WLS_SOAn/WLS_OSBn Managed Servers
4.14.8
Configuring Oracle Coherence for Deploying Composites
4.14.9
Configure Oracle Coherence for the Oracle Service Bus Result Cache
4.14.10
Setting Connection Destination Identifiers for B2B Queues
4.14.11
Starting the System in SOAHOST1
4.14.11.1
Starting Node Manager on SOAHOST1
4.14.11.2
Starting and Validating the WLS_SOA1 Managed Server
4.14.12
Propagating the Domain Configuration to SOAHOST2, OSBHOST1, and OSBHOST2 with pack/unpack Utilities
4.14.13
Extracting XEngine Files in the Second Node
4.14.14
Starting the System in SOAHOST2, OSBHOST1, and OSBHOST2
4.14.14.1
Starting Node Manager on SOAHOST2, OSBHOST1, and OSBHOST2
4.14.14.2
Starting and Validating the WLS_SOA2, WLS_OSB1, and WLS_OSB2 Managed Server
4.14.15
Configuring Oracle HTTP Servers for the Administration Server, WLS_SOAn, and WLS_OSBn Managed Servers
4.14.16
Validating Access Through Oracle HTTP Server
4.14.17
Setting the Front End HTTP Host and Port
4.14.18
Configuring a Default Persistent Store for Transaction Recovery
4.14.19
Deploying Applications
4.14.20
Configuring Server Migration for the WLS_SOA Servers
4.14.21
Configuring Server Migration for the WLS_OSB Servers
4.14.22
Scaling the Topology
4.14.22.1
Scaling Up the Topology (Adding Managed Servers to Existing Nodes)
4.14.22.2
Scaling Out the Topology (Adding Managed Servers to New Nodes)
4.15
Configuring High Availability for Oracle BAM
4.15.1
Preparing the Environment: Prerequisite Steps Before Setting up a High Availability Configuration for Oracle BAM
4.15.1.1
Database Prerequisites
4.15.1.2
VIP and IPs Prerequisites
4.15.1.3
Installing and Configuring the Database Repository
4.15.1.4
Using Oracle Fusion Middleware Repository Creation Utility to Load Oracle Fusion Middleware Schemas
4.15.1.4.1
Running RCU
4.15.1.5
Configuring Virtual Server Names and Ports for the Load Balancer
4.15.2
Installing Oracle HTTP Server on WEBHOST1
4.15.2.1
Validating Oracle HTTP Server
4.15.3
Installing Oracle Fusion Middleware Home
4.15.3.1
Installing Oracle WebLogic Server
4.15.3.2
Installing Oracle BAM Using the Oracle SOA Suite Installer
4.15.4
Enabling VIP0 and VIP1 on BAMHOST1
4.15.5
Running Oracle Fusion Middleware Configuration Wizard on BAMHOST1 to Create the WebLogic Server Oracle BAM Domain
4.15.6
Creating boot.properties for the Administration Server and for WLS_BAM1 on BAMHOST1
4.15.7
Starting the Administration Server on BAMHOST1
4.15.8
Disabling Host Name Verification for the Servers
4.15.9
Configuring a JMS Persistence Store for BAM UMS
4.15.10
Configuring a Default Persistence Store for Transaction Recovery
4.15.11
Untargeting the BAM Server System from BAMHOST2
4.15.12
Propagating the Domain Configuration from BAMHOST1 with pack/unpack Utilities
4.15.13
Starting Node Manager on BAMHOST1 and BAMHOST2
4.15.14
Starting the Oracle BAM System
4.15.15
Configuring Oracle RAC Failover for the WLS_BAM Servers
4.15.16
Configuring the BAM Web Applications to Use the BAM Server in BAMHOST1
4.15.17
Configuring Oracle HTTP Servers for the Administration Server and the WLS_BAMn Managed Servers
4.15.18
Validating Access through Oracle HTTP Server
4.15.19
Configuring Server Migration for the WLS_BAM Servers
4.15.19.1
Setting Up the User and Tablespace for the Server Migration Leasing Table
4.15.19.2
Creating a GridLink or Multi Data Source from the Administration Console
4.15.19.3
Edit the Node Manager's Properties File
4.15.19.4
Set Environment and Superuser Privileges for the wlsifconfig.sh Script
4.15.19.5
Configure Server Migration Targets
4.15.19.6
Test Server Migration
4.15.20
Configuring Clients Connecting to the BAM System
5
Considerations for High Availability Oracle Database Access
5.1
Oracle Real Application Clusters and Fusion Middleware
5.1.1
Java-Based Oracle Fusion Middleware Components Deployed to Oracle WebLogic Server
5.1.2
GridLink Data Sources and Oracle RAC
5.1.3
Using Multi Data Sources with Oracle RAC
5.1.3.1
Configuring Multi Data Sources for MDS Repositories
5.1.3.2
Oracle RAC Configuration Requirements
5.1.3.3
Configuring Schemas for Transactional Recovery Privileges
5.1.4
Configuring GridLink Data Sources with Oracle RAC
5.1.5
Configuring Multi Data Sources with Oracle RAC
5.1.6
JDBC Clients
5.1.7
System Clients
5.1.7.1
Oracle Internet Directory
5.1.7.2
Oracle Forms
5.1.7.3
Oracle Portal
5.1.7.4
Oracle Reports and Oracle Discoverer
5.2
Protecting Idle Connections from Firewall Timeouts
5.3
Troubleshooting
5.4
Using SCAN Addresses with Oracle Database 11g (11.2)
6
Configuring High Availability for Oracle ADF and Oracle WebCenter Portal
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 WebCenter Portal Managed Servers
6.2.9.6
Validating Access through Oracle HTTP Server
6.2.10
Scaling the Topology
6.2.10.1
Scaling Up the Topology (Adding Managed Servers to Existing Nodes)
6.2.10.2
Scaling Out the Topology (Adding Managed Servers to New Nodes)
6.3
Oracle WebCenter Portal and High Availability Concepts
6.3.1
Understanding Oracle WebCenter Portal
6.3.1.1
Oracle WebCenter Portal Components
6.3.1.2
Oracle WebCenter Portal Single-node Architecture
6.3.1.3
Oracle WebCenter Portal: State and Configuration Persistence
6.3.1.4
Oracle WebCenter Portal Log File Locations
6.3.2
WebCenter Portal High Availability Architecture and Failover Considerations
6.3.2.1
WebCenter Portal and Portal Framework applications
6.3.2.2
Oracle WebCenter Portal Startup Order
6.3.2.3
Deploying WebCenter Portal or Portal Framework Applications on a Cluster
6.3.2.4
Oracle WebCenter Portal's Analytics Collector
6.3.2.5
Oracle WebCenter Portal State Replication
6.3.2.6
Understanding the Distributed Java Object Cache
6.3.2.7
Oracle WebCenter Portal Protection from Failover and Expected Behavior
6.3.2.8
Expected Behavior for Application Failover
6.3.2.9
Monitoring Logging of Application Deployments
6.3.2.10
Oracle WebCenter Portal Cluster-wide Configuration Changes
6.3.2.11
Maintaining Configuration in a Clustered Environment
6.4
Configuring High Availability for WebCenter Portal
6.4.1
Preparing the Environment: Prerequisite Steps Before Setting up a WebCenter Portal 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 WebCenter Portal
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 WebCenter Portal 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 WebCenter Portal Managed Servers
6.4.11.1
Configuring a Virtual Host for Sharepoint
6.4.11.1.1
Virtual Hosts Requirement
6.4.11.1.2
Additional Configuration
6.4.11.2
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 the Distributed Notifications for the MDS Repository
6.4.15
Configuring WebCenter Portal for Replication
6.4.16
Configuring Analytics for WebCenter Portal
6.4.17
Configuring Activity Graph for WebCenter Portal
6.4.18
Configuring Clustering for the Discussions Server
6.4.19
Scaling the Topology
6.4.19.1
Scaling Up the Topology (Adding Managed Servers to Existing Nodes)
6.4.19.2
Scaling Out the Topology (Adding Managed Servers to New Nodes)
6.4.20
Troubleshooting WebCenter Portal High Availability
6.4.20.1
Troubleshooting WebCenter Portal Deployment Issues
6.4.20.2
Troubleshooting WebCenter Portal Replication and Failover Issues
6.4.20.3
Troubleshooting Lost Changes to Policies
6.4.20.4
Troubleshooting JOC Configuration
6.4.21
Converting Discussions from Multicast to Unicast
6.5
Configuring High Availability for Portal Framework Applications
6.5.1
Configuring a Cluster for WebCenter Portal Framework Applications
6.5.2
Adding More Portal Framework Application Servers
6.5.3
Configuring Distributed Notifications for the MDS Repository
7
High Availability for Oracle Data Integrator
7.1
Introduction to Oracle Data Integrator
7.2
Oracle Data Integrator Single Instance Characteristics
7.2.1
Oracle Data Integrator Sessions Lifecycle and Recovery
7.2.1.1
Sessions Interruption
7.2.1.2
Recovering Sessions
7.2.2
Agent Startup and Shutdown Cycle
7.2.3
Oracle Data Integrator External Dependencies
7.2.4
Oracle Data Integrator Startup and Shutdown Process
7.2.5
Oracle Data Integrator Configuration Artifacts
7.2.5.1
Java EE Agent Configuration
7.2.5.2
Standalone Agent Configuration
7.2.5.3
Oracle Data Integrator Console Configuration
7.2.5.4
Oracle Data Integrator Log Locations and Configuration
7.2.5.4.1
Oracle Data Integrator Session Logs
7.2.5.4.2
Java EE Agent Log Files
7.2.5.4.3
Standalone Agent Log Files
7.2.5.4.4
Oracle Data Integrator Console Log Files
7.3
Oracle Data Integrator High Availability and Failover Considerations
7.3.1
Oracle Data Integrator Clustered Deployment
7.3.2
Standalone Agent High Availability with OPMN
7.3.3
Oracle Data Integrator Protection from Failure and Expected Behavior
7.3.3.1
WebLogic Server or Standalone Agent Crash
7.3.3.2
Repository Database Failure
7.3.3.3
Scheduler Node Failure
7.4
Configuring High Availability for Oracle Data Integrator
7.4.1
Running RCU to Create the Master and Work Repositories
7.4.2
Installation and Configuration of the First Oracle Data Integrator Host
7.4.2.1
Installing the Oracle WebLogic Server on APPHOST1
7.4.2.2
Install Oracle Data Integrator on APPHOST1
7.4.2.3
Create the High Availability Domain
7.4.2.4
Start the Administration Server
7.4.2.5
Configure the Credential Store
7.4.2.5.1
Configuring Credentials Using WLST
7.4.2.5.2
Configuring Credentials using Enterprise Manager
7.4.2.6
Configure the Default Agent
7.4.2.7
Configure Coherence for the Cluster
7.4.2.8
Configure Node Manager and Start odi_server1
7.4.2.9
Verify the Oracle Data Integrator Agent is Running
7.4.3
Installation and Configuration of the Second Oracle Data Integrator Host
7.4.3.1
Installing the Oracle WebLogic Server on APPHOST2
7.4.3.2
Pack and Unpack the Domain from APPHOST1 to APPHOST2
7.4.3.3
Configure Node Manager and Start odi_server2
7.4.3.4
Verify the Oracle Data Integrator Agent is Running
7.4.4
Installing Oracle HTTP Server
7.4.4.1
Upgrading the Oracle HTTP Server Oracle Home
7.4.4.2
Configuring Oracle HTTP Server
7.4.4.3
Configuring the Load Balancer
7.4.4.4
Verify the Oracle Data Integrator Agent is Running
7.4.4.5
Reconfigure Agents
8
Configuring High Availability for Identity Management Components
8.1
Identity Management Product Components and High Availability Concepts
8.1.1
About the 11
g
Oracle Identity Management Products
8.2
Prerequisites for Oracle Identity Management High Availability Configuration
8.2.1
Oracle Home Requirement
8.2.2
Database Prerequisites
8.2.3
Installing and Configuring the Database Repository
8.2.4
Obtaining the Repository Creation Utility Software
8.2.4.1
Running the Repository Creation Utility
8.2.5
Configuring the Database for Oracle Fusion Middleware 11g Metadata
8.2.5.1
Database Examples in This Chapter
8.2.5.2
Database Services
8.2.5.3
Verifying Transparent Application Failover
8.2.5.4
Configuring Virtual Server Names and Ports for the Load Balancer
8.2.5.4.1
Load Balancers
8.2.5.4.2
Virtual Server Names
8.3
Oracle Internet Directory High Availability
8.3.1
Oracle Internet Directory Component Architecture
8.3.1.1
Oracle Internet Directory Component Characteristics
8.3.1.1.1
Runtime Processes
8.3.1.1.2
Process Lifecycle
8.3.1.1.3
Request Flow
8.3.1.1.4
Configuration Artifacts
8.3.1.1.5
External Dependencies
8.3.1.1.6
Oracle Internet Directory Log File
8.3.2
Oracle Internet Directory High Availability Concepts
8.3.2.1
Oracle Internet Directory High Availability Architecture
8.3.2.1.1
Starting and Stopping the Cluster
8.3.2.1.2
Cluster-Wide Configuration Changes
8.3.2.2
Protection from Failures and Expected Behavior
8.3.2.2.1
Oracle Internet Directory Process Failure
8.3.2.2.2
Expected Client Application Behavior When Failure Occurs
8.3.2.2.3
External Dependency Failure
8.3.2.3
Oracle Internet Directory Prerequisites
8.3.2.3.1
Synchronizing the Time on Oracle Internet Directory Nodes
8.3.2.3.2
Using RCU to Create Oracle Internet Directory Schemas in the Repository
8.3.2.3.3
Load Balancer Virtual Server Names for Oracle Internet Directory
8.3.3
Oracle Internet Directory High Availability Configuration Steps
8.3.3.1
Installing Oracle Fusion Middleware Components
8.3.3.1.1
Install Oracle WebLogic Server
8.3.3.1.2
Installing Oracle Fusion Middleware for Identity Management
8.3.3.1.3
Upgrading Oracle Identity Management
8.3.3.2
Configuring Oracle Internet Directory Without a WebLogic Domain
8.3.3.2.1
Configuring Oracle Internet Directory on OIDHOST1
8.3.3.2.2
Oracle Internet Directory Component Names Assigned by Oracle Identity Management Installer
8.3.3.2.3
Configuring Oracle Internet Directory on OIDHOST2
8.3.3.2.4
Registering Oracle Internet Directory with a WebLogic Domain
8.3.3.3
Configuring Oracle Internet Directory With a WebLogic Domain
8.3.3.3.1
Configuring Oracle Internet Directory on OIDHOST1
8.3.3.3.2
Creating boot.properties for the Administration Server on OIDHOST1
8.3.3.3.3
Configuring Oracle Internet Directory on OIDHOST2
8.3.4
Validating Oracle Internet Directory High Availability
8.3.5
Oracle Internet Directory Failover and Expected Behavior
8.3.5.1
Performing an Oracle Internet Directory Failover
8.3.5.2
Performing an Oracle RAC Failover
8.3.6
Troubleshooting Oracle Internet Directory High Availability
8.3.7
Additional Oracle Internet Directory High Availability Issues
8.3.7.1
Changing the Password of the ODS Schema Used by Oracle Internet Directory
8.4
Oracle Virtual Directory High Availability
8.4.1
Oracle Virtual Directory Component Architecture
8.4.1.1
Oracle Virtual Directory Runtime Considerations
8.4.1.2
Oracle Virtual Directory Component Characteristics
8.4.1.2.1
Oracle Virtual Directory Log File
8.4.2
Oracle Virtual Directory High Availability Concepts
8.4.2.1
Oracle Virtual Directory High Availability Architecture
8.4.2.1.1
Oracle Virtual Directory High Availability Connect Features
8.4.2.2
Oracle Virtual Directory Prerequisites
8.4.2.2.1
Load Balancer Virtual Server Names for Oracle Virtual Directory
8.4.3
Oracle Virtual Directory High Availability Configuration Steps
8.4.3.1
Configuring Oracle Virtual Directory Without a WebLogic Domain
8.4.3.1.1
Configuring Oracle Virtual Directory on OVDHOST1
8.4.3.1.2
Configuring Oracle Virtual Directory on OVDHOST2
8.4.3.1.3
Registering Oracle Virtual Directory with a WebLogic Domain
8.4.3.2
Configuring Oracle Virtual Directory With a WebLogic Domain
8.4.3.2.1
Configuring Oracle Virtual Directory on OVDHOST1
8.4.3.2.2
Creating boot.properties for the Administration Server on OVDHOST1
8.4.3.2.3
Configuring Oracle Virtual Directory on OVDHOST2
8.4.3.3
Configuring Oracle Virtual Directory with Highly Available Data Sources
8.4.3.3.1
Configuring Oracle Virtual Directory with an Oracle RAC Database
8.4.3.3.2
Configuring Oracle Virtual Directory with LDAP
8.4.4
Validating Oracle Virtual Directory High Availability
8.4.4.1
Validating Oracle Virtual Directory High Availability Using SSL
8.4.5
Oracle Virtual Directory Failover and Expected Behavior
8.4.5.1
Performing an Oracle Virtual Directory Failover
8.4.5.2
Performing an Oracle RAC Failover
8.4.6
Troubleshooting Oracle Virtual Directory High Availability
8.4.6.1
Troubleshooting LDAP Adapter Creation
8.5
Oracle Directory Integration Platform High Availability
8.5.1
Oracle Directory Integration Platform Component Architecture
8.5.2
Oracle Directory Integration Platform High Availability Concepts
8.5.2.1
Oracle Directory Integration Platform High Availability Architecture (OID backend)
8.5.2.1.1
Starting and Stopping the Cluster
8.5.2.1.2
Cluster-Wide Configuration Changes (OID)
8.5.2.2
Oracle Directory Integration Platform High Availability Architecture (OUD Backend)
8.5.2.2.1
Cluster-Wide Configuration Changes (OUD)
8.5.2.3
Protection from Failures and Expected Behavior
8.5.2.3.1
Process Failure
8.5.2.3.2
Updating the Oracle Directory Integration Platform Server Configuration
8.5.2.3.3
External Dependency Failure
8.5.2.4
Oracle Directory Integration Platform Prerequisites
8.5.2.4.1
Installing and Configuring Oracle Internet Directory
8.5.2.4.2
Installing and Configuring Oracle Unified Directory
8.5.3
Configuring Oracle Directory Integration Platform for High Availability
8.5.3.1
Configuring High Availability for an OID Backend Server
8.5.3.1.1
Configuring Oracle Directory Integration Platform on IDMHOST1 (OID)
8.5.3.1.2
Creating boot.properties for the Administration Server on IDMHOST1 (OID)
8.5.3.1.3
Configuring Oracle Directory Integration Platform on IDMHOST2 (OID)
8.5.3.1.4
Post-Installation Steps for Oracle Directory Integration Platform (OID)
8.5.3.1.5
Copy the Oracle Directory Integration Platform Configuration from IDMHOST1 to IDMHOST2
8.5.3.1.6
Restart the Managed Server on IDMHOST2 in a Cluster
8.5.3.2
Configuring High Availability for an OUD Backend Server
8.5.3.2.1
Configuring Oracle Directory Integration Platform on IDMHOST1 (OUD)
8.5.3.2.2
Creating boot.properties for the Administration Server on IDMHOST1
8.5.3.2.3
Starting the Administration Server
8.5.3.2.4
Configuring Oracle Directory Integration Platform on IDMHOST2 (OUD)
8.5.3.2.5
Starting Node Manager on IDMHOST2 (OUD)
8.5.3.2.6
Registering the OUD Back-end Directory with Oracle Directory Integration Platform
8.5.3.2.7
Configuring ODIP2
8.5.3.2.8
Configuring the Load Balancer
8.5.4
Connected Directories
8.5.4.1
Failing Over Oracle Directory Server Enterprise Edition Manually
8.5.4.2
Oracle Unified Directory
8.5.4.3
Microsoft Active Directory
8.5.4.4
Novell eDirectory
8.5.4.5
OpenLDAP
8.5.4.6
IBM Tivoli Directory Server
8.5.4.7
Oracle Internet Directory
8.5.5
Oracle Directory Integration Platform Failover and Expected Behavior
8.5.6
Troubleshooting Oracle Directory Integration Platform High Availability
8.5.6.1
Managed Server Log File Exceptions Received for Oracle Directory Integration Platform During an Oracle RAC Failover
8.5.6.2
Dealing with Error Messages Received After Starting WebLogic Node Manager
8.5.6.3
If WebLogic Node Manager Fails to Start
8.5.6.4
Configuration Changes Do Not Automatically Propagate to All Oracle Directory Integration Platform Instances in a Highly Available Topology
8.5.6.5
Operation Cannot Be Completed for Unknown Errors Message
8.6
Oracle Directory Services Manager High Availability
8.6.1
Oracle Directory Services Manager Component Architecture
8.6.1.1
Oracle Directory Services Manager Component Characteristics
8.6.1.1.1
Lifecycle Management
8.6.1.1.2
Oracle Directory Services Manager Log File
8.6.2
Oracle Directory Services Manager High Availability Concepts
8.6.2.1
Oracle Directory Services Manager High Availability Architecture
8.6.2.1.1
Starting and Stopping the Cluster
8.6.2.2
Protection from Failures and Expected Behaviors
8.6.2.2.1
Process Failure
8.6.2.2.2
Expected Client Application Behavior When Failure Occurs
8.6.2.2.3
External Dependency Failure
8.6.2.3
Oracle Directory Services Manager Prerequisites
8.6.3
Oracle Directory Services Manager High Availability Configuration Steps
8.6.4
Validating Oracle Directory Services Manager High Availability
8.6.4.1
Performing a WebLogic Server Instance Failover
8.6.4.2
Performing an Oracle RAC Database Failover
8.6.5
Oracle Directory Services Manager Failover and Expected Behavior
8.6.5.1
Using Oracle Directory Services Manager to Validate a Failover of a Managed Server
8.6.5.2
Using Oracle Directory Services Manager to Validate a Failover of an Oracle Internet Directory Instance
8.6.5.3
Using Oracle Directory Services Manager to Validate an Oracle RAC Failover
8.6.6
Troubleshooting Oracle Directory Services Manager
8.6.6.1
Resolving Error Messages Received After Starting WebLogic Node Manager
8.6.6.2
If WebLogic Node Manager Fails to Start
8.6.6.3
Oracle Directory Services Manager Failover Using Oracle HTTP Server is Not Transparent
8.6.6.4
Oracle Directory Services Manager Displays "LDAP Server is down" Message During Oracle Internet Directory Failover
8.6.6.5
Oracle Directory Services Manager Temporarily Loses Its Connection During Oracle RAC Failover
8.6.7
Additional Considerations for Oracle Directory Services Manager High Availability
8.7
Collocated Architecture High Availability
8.7.1
Collocated Architecture Overview
8.7.2
Collocated Architecture High Availability Deployment
8.7.2.1
Collocated Architecture Prerequisites
8.7.2.2
Configuring Collocated Components for High Availability
8.7.3
Validating the Collocated Components High Availability
8.7.3.1
Validation Tests
8.7.3.2
Failures and Expected Behaviors
8.7.4
Troubleshooting Collocated Components Manager High Availability
8.7.5
Additional Considerations for Collocated Components High Availability
8.8
Starting and Stopping Components
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
Configuring Identity Management for Maximum High Availability
10.1
Introduction to the Maximum High Availability Identity Management Deployment
10.2
Overview of Replication
10.3
Setting up Multimaster Replication
10.3.1
Setting Up LDAP Multimaster Replication
10.3.1.1
Adding a Node in LDAP Multimaster Replication
10.3.1.2
Deleting a Node in LDAP Multimaster Replication
10.3.2
Setting Up Oracle Advanced Database Multimaster Replication
10.3.2.1
Adding a Node in Oracle Advanced Database Multimaster Replication
10.3.2.2
Deleting a Node in Oracle Advanced Database Multimaster Replication
11
Configuring High Availability for Oracle WebCenter Content
11.1
Oracle WebCenter Content High Availability
11.1.1
Oracle WebCenter Content Component Architecture
11.1.1.1
WebCenter Content Component Characteristics
11.1.1.1.1
WebCenter Content State Information
11.1.1.1.2
WebCenter Content Runtime Processes
11.1.1.1.3
WebCenter Content Process Lifecycle
11.1.1.1.4
WebCenter Content Configuration Artifacts
11.1.1.1.5
WebCenter Content Deployment Artifacts
11.1.1.1.6
WebCenter Content External Dependencies
11.1.1.1.7
WebCenter Content Log File Locations
11.1.2
WebCenter Content High Availability Concepts
11.1.2.1
WebCenter Content High Availability Architecture
11.1.2.1.1
Starting and Stopping the Cluster
11.1.2.1.2
Cluster-Wide Configuration Changes
11.1.2.2
WebCenter Content and Inbound Refinery High Availability Architecture
11.1.2.2.1
Content Server and Inbound Refinery Communication
11.1.2.2.2
Content Server Instances in a WebCenter Content Cluster
11.1.2.2.3
Inbound Refinery Instances and Load Balancers
11.1.2.2.4
Inbound Refinery Availability
11.1.2.3
Records High Availability
11.1.2.4
Protection from Failure and Expected Behaviors
11.1.2.5
Troubleshooting WebCenter Content High Availability
11.2
Oracle WebCenter Content High Availability Configuration Steps
11.2.1
Shared Storage
11.2.2
Configuring the Oracle Database
11.2.3
Installing and Configuring Oracle WebCenter Content WCCHOST1
11.2.3.1
Installing Oracle WebLogic Server on WCCHOST1
11.2.3.2
Installing Oracle WebCenter Content on WCCHOST1
11.2.3.3
Create a High Availability Domain
11.2.3.4
Start the Administration Server and Managed Servers on WCCHOST1
11.2.3.5
Disabling Host Name Verification for the Administration Server and the Managed Servers for WCCHOST1 and WCCHOST2
11.2.3.6
Configure the WLS_UCM1 Managed Server
11.2.3.7
Configure the WLS_URM1 Managed Server
11.2.4
Installing and Configuring WEBHOST1
11.2.4.1
Installing Oracle HTTP Server on WEBHOST1
11.2.4.2
Configuring Oracle HTTP Server on WEBHOST1
11.2.5
Configuring the Load Balancer
11.2.6
Installing and Configuring Oracle WebCenter Content on WCCHOST2
11.2.6.1
Installing Oracle WebLogic Server on WCCHOST2
11.2.6.2
Installing Oracle WebCenter Content on WCCHOST2
11.2.6.3
Using pack and unpack to Join the Domain on WCCHOST1
11.2.6.4
Start Node Manager and the WLS_UCM2 Server on WCCHOST2
11.2.6.5
Start the Managed Servers on WCCHOST2
11.2.6.6
Configure the WLS_UCM2 Managed Server
11.2.6.7
Configure the WLS_URM2 Managed Server
11.2.7
Installing and Configuring Oracle HTTP Server on WEBHOST2
11.2.7.1
Installing Oracle HTTP Server on WEBHOST2
11.2.7.2
Configuring Oracle HTTP Server on WEBHOST2
11.2.8
Reassociating the Oracle WebCenter Content Domain with an OPSS Security Store in Oracle Database
11.2.9
Configuring the Imaging Managed Servers
11.2.9.1
Configuring JMS Persistence Store for Imaging JMS
11.2.9.2
Configuring Imaging with WebCenter Content
11.2.9.2.1
Enabling WebCenter Content as the Imaging Repository
11.2.9.2.2
Upgrading the Default File Store
11.2.9.2.3
Adding Imaging Server Listen Addresses to the Allowed Hosts Lists
11.2.9.2.4
Creating a Connection to Content Server
11.2.9.3
Configuring BPEL CSF Credentials
11.2.9.4
Configuring the BPEL PM Connection
11.2.9.5
Setting the Front End HTTP Host and Port
11.2.9.6
Configuring Server Migration for Imaging Managed Servers
11.2.9.6.1
About Configuring Server Migration
11.2.9.6.2
Creating a GridLink or Multi Data Source
11.2.9.6.3
Testing the Server Migration
11.2.10
Configuring Inbound Refinery Instances
11.2.10.1
Inbound Refinery and Cluster Concepts
11.2.10.2
Content Server and Inbound Refinery Configuration
11.2.10.3
Inbound Refinery Instances and Oracle HTTP Server
11.2.11
Configuring WebCenter Content User Interface for High Availability
11.3
Oracle WebCenter Content: Imaging High Availability
11.3.1
Imaging Component Architecture
11.3.1.1
Imaging Component Characteristics
11.3.1.1.1
Imaging State Information
11.3.1.1.2
Imaging Runtime Processes
11.3.1.1.3
Imaging Process Lifecycle
11.3.1.1.4
Imaging Configuration Artifacts
11.3.1.1.5
Imaging External Dependencies
11.3.1.1.6
Imaging Log File Location
11.3.2
Imaging High Availability Concepts
11.3.2.1
Imaging High Availability Architecture
11.3.2.1.1
Starting and Stopping the Cluster
11.3.2.1.2
Cluster-Wide Configuration Changes
11.3.2.2
Protection from Failures and Expected Behaviors
11.3.2.3
Creation of Imaging Artifacts in a Cluster
11.3.2.4
Troubleshooting Imaging
11.4
Oracle WebCenter Enterprise Capture High Availability
11.4.1
Capture Component Architecture
11.4.1.1
Capture Component Characteristics
11.4.1.1.1
Capture State Information
11.4.1.1.2
Capture Runtime Processes
11.4.1.1.3
Capture Process Lifecycle
11.4.1.1.4
Capture Configuration Artifacts
11.4.1.1.5
Capture External Dependencies
11.4.1.1.6
Capture Log File Location
11.4.2
Capture High Availability Concepts
11.4.2.1
Capture High Availability Architecture
11.4.2.1.1
Starting and Stopping the Cluster
11.4.2.1.2
Cluster-Wide Configuration Changes
11.4.2.2
Protection from Failures and Expected Behaviors
11.4.2.3
Creation of Capture Artifacts in a Cluster
11.4.2.4
Troubleshooting Capture
11.4.3
Configuring Capture for High Availability
11.4.3.1
Configuring Capture Clusters
11.4.3.2
Configuring the OHS Load Balancer for Capture
11.4.3.3
Setting the Front End HTTP Host and Port
11.4.3.4
Configuring the WebCenter Content and Imaging Connections
11.4.3.5
Configuring the Policy Store
11.4.3.6
Configuring Server Migration
11.4.3.7
Setting the Batch Commit (Redelivery Limit) Time Limit
12
Active-Passive Topologies for Oracle Fusion Middleware High Availability
12.1
Oracle Fusion Middleware Cold Failover Cluster Topology Concepts
12.2
Configuring Oracle Fusion Middleware for Active-Passive Deployments
12.2.1
Cold Failover Cluster Requirements
12.2.2
Directories and Environment Variables Terminology
12.2.3
Transforming Oracle Fusion Middleware Infrastructure Components
12.2.3.1
Administration Server Topology 1
12.2.3.2
Topology 1 Installation Procedure
12.2.3.3
Administration Server Topology 2
12.2.3.4
Topology 2 Installation Procedure
12.2.3.5
Transforming the Administration Server for Cold Failover Cluster
12.2.3.6
Transforming Oracle WebLogic Managed Servers
12.2.3.6.1
Transforming an Oracle WebLogic Managed Server using the Fusion Middleware Administration Console
12.2.3.6.2
Transforming an Oracle WebLogic Managed Server using the WLST Command Line
12.2.3.7
Transforming Node Manager
12.2.3.8
Transforming Oracle Process Management and Notification Server
12.2.3.9
Transforming Oracle Enterprise Manager for an Oracle Instance
12.2.3.10
Transforming Web Tier Components and Clients
12.2.3.10.1
Transforming Oracle HTTP Server
12.2.3.10.2
Transforming Oracle Web Cache
12.2.4
Transforming Oracle Fusion Middleware Components
12.2.4.1
Transforming Oracle Internet Directory and Its Clients
12.2.4.1.1
Transforming Oracle Internet Directory
12.2.4.1.2
Transforming Oracle Internet Directory Clients
12.2.4.2
Transforming Oracle Virtual Directory and Its Clients
12.2.4.2.1
Transforming Oracle Virtual Directory
12.2.4.2.2
Generating a New Key for the Keystore
12.2.4.2.3
Transforming Oracle Virtual Directory Clients
12.2.4.3
Transforming Oracle Directory Integration Platform and Oracle Directory Services Manager and Their Clients
12.2.4.3.1
Transforming Oracle Directory Integration Platform and Oracle Directory Services Manager
12.2.4.3.2
Transforming Oracle Directory Integration Platform and Oracle Directory Services Manager Clients
12.2.4.4
Transforming Oracle Identity Federation and Its Client
12.2.4.4.1
Transforming Oracle Identity Federation
12.2.4.4.2
Transforming Oracle Identity Federation Clients
12.2.4.5
Transforming an Oracle SOA Suite
12.2.4.6
Transforming Oracle Access Manager and Its Clients
12.2.4.6.1
Transforming Oracle Access Manager
12.2.4.6.2
Transforming Oracle Access Manager Clients
12.2.4.7
Transforming Oracle Adaptive Access Manager and Its Clients
12.2.4.7.1
Transforming Oracle Adaptive Access Manager
12.2.4.7.2
Transforming Oracle Adaptive Access Manager Clients
12.2.4.8
Transforming Oracle Identity Manager and Its Clients
12.2.4.8.1
Transforming Oracle Identity Manager
12.2.4.8.2
Transforming Oracle Identity Manager Clients
12.2.4.9
Transforming an Oracle WebCenter Portal Suite
12.2.4.10
Transforming Oracle Portal, Forms, Reports, and Discoverer
12.2.4.10.1
Transforming Oracle Forms for Cold Failover Cluster
12.2.4.10.2
Transforming Oracle Reports for Cold Failover Cluster
12.2.4.10.3
Transforming Oracle Discoverer for Cold Failover Cluster
12.2.4.10.4
Transforming Oracle Portal for Cold Failover Cluster
12.2.4.10.5
Transforming Oracle Business Activity Management (BAM)
12.2.4.10.6
Transforming a Custom ADF Deployment
12.2.4.11
Transforming Oracle WebCenter Content
12.2.4.12
Transforming Oracle Business Intelligence
12.2.4.12.1
Transforming Oracle Business Intelligence Enterprise Edition and its Clients
12.2.4.12.2
Transforming Oracle Business Intelligence Publisher and its Clients
12.2.4.12.3
Transforming Oracle Real-Time Decisions and its Clients
12.2.4.13
Transforming Oracle BI for Microsoft Office and its Clients
12.2.4.14
Transforming Oracle Data Integrator
12.2.4.15
Single Sign-On Reregistration (If required)
12.2.5
Additional Actions for Fusion Middleware Failover
12.2.5.1
UNIX Platform
12.2.5.2
Windows Platform
12.2.6
Transforming an Oracle Database
12.2.6.1
Database Instance Platform-Specific Considerations
12.3
Cold Failover Cluster Example Topologies
12.3.1
Example Topology 1
12.3.2
Example Topology 2
12.3.3
Example Topology 3
12.4
Transforming the Administration Server in an Existing Domain for Cold Failover Cluster
12.4.1
Destination Topologies
12.4.2
Cold Failover Cluster Transformation Procedure
13
Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer
13.1
Overview of Oracle Portal, Forms, Reports, and Discoverer
13.1.1
Oracle Portal, Forms, Reports, and Discoverer Architecture
13.1.2
Common Log Files
13.1.3
Common Component Failures and Expected Behaviors
13.1.3.1
Oracle Web Cache and Oracle HTTP Server Process Failures
13.1.3.2
Common Component Node Failures
13.1.3.3
Common Component WebLogic Managed Server Failures
13.1.3.4
Common Component Database Failures
13.1.4
Oracle Portal, Forms, Reports, and Discoverer Cluster-Wide Configuration Changes
13.1.5
Common Component Log File Information
13.2
Oracle Portal and High Availability Concepts
13.2.1
Oracle Portal Single-Instance Characteristics
13.2.1.1
Oracle Portal Request Flow
13.2.1.2
Oracle Portal Component Characteristics
13.2.1.3
Oracle Portal Startup and Shutdown of Processes and Lifecycle
13.2.1.4
Oracle Portal Deployment Artifacts
13.2.1.5
Oracle Portal Configuration Information
13.2.1.6
Oracle Portal Logging and Log Configuration
13.2.1.6.1
Oracle Portal Log Files
13.2.1.7
Oracle Portal External Dependencies
13.2.2
Oracle Portal Protection from Failures and Expected Behavior
13.2.2.1
Oracle Portal Process Failures
13.2.2.2
Oracle Portal Node Failures
13.2.2.3
Oracle Portal WebLogic Managed Server Failures
13.2.2.4
Oracle Portal Protection from Database Failures
13.3
Oracle Reports and High Availability Concepts
13.3.1
Oracle Reports Single-Instance Characteristics
13.3.1.1
Oracle Reports State Information
13.3.1.2
Oracle Reports External Dependencies
13.3.1.3
Oracle Reports Specific Configuration Files
13.3.1.4
Oracle Reports Connection Retry
13.3.1.5
Oracle Reports Process Flow
13.3.1.6
Oracle Reports Log Files
13.3.2
Oracle Reports Protection from Failure and Expected Behavior
13.3.2.1
Oracle Reports Process Failures
13.3.2.2
Oracle Reports Node Failures
13.3.2.3
Oracle Reports WebLogic Managed Server Failures
13.3.2.4
Oracle Reports Database Failures
13.4
Oracle Forms and High Availability Concepts
13.4.1
Oracle Forms Single-Instance Component Characteristics
13.4.1.1
Oracle Forms State Information
13.4.1.2
Oracle Forms Database Requirements
13.4.1.3
Oracle Forms Request Flow
13.4.1.4
Oracle Forms Configuration Persistence
13.4.1.5
Oracle Forms Runtime Considerations
13.4.1.6
Oracle Forms Process Flow
13.4.1.7
Oracle Forms Configuration Files
13.4.1.8
Oracle Forms External Dependencies
13.4.1.9
Oracle Forms Log Files
13.4.2
Oracle Forms Protection from Failover and Expected Behavior
13.4.2.1
Oracle Forms N+1 Redundancy
13.4.2.2
Oracle Forms N+M Redundancy
13.4.2.3
Oracle Forms Virtual Machines
13.4.2.4
Oracle Forms Configuration Cloning
13.4.2.5
Oracle Forms Process Failures
13.4.2.6
Oracle Forms Node Failures
13.4.2.7
Oracle Forms WebLogic Managed Server Failures
13.4.2.8
Oracle Forms Database Failures
13.5
Oracle Discoverer and High Availability Concepts
13.5.1
Oracle Discoverer Single-Instance Characteristics
13.5.1.1
Oracle Discoverer Runtime Considerations
13.5.1.2
Oracle Discoverer Viewer and Web Cache
13.5.1.3
Oracle Discoverer Configuration Considerations
13.5.1.4
Oracle Discoverer Deployment Considerations
13.5.1.5
Oracle Discoverer Log File Locations
13.5.1.6
Discoverer Log Files
13.5.2
Oracle Discoverer Protection from Failures and Expected Behavior
13.5.2.1
Preference Server Failover
13.5.2.2
Session State Replication and Failover
13.5.2.3
Performance Recommendation
13.5.2.4
Propagation of Configuration Changes Across the Cluster
13.5.2.5
Cluster-Wide Application Deployment
13.5.2.6
Online Application Deployment
13.5.2.7
Oracle Discoverer Process Failures
13.5.2.8
Oracle Discoverer Node Failures
13.5.2.9
Oracle Discoverer WebLogic Managed Server Failures
13.5.2.10
Oracle Discoverer Database Failures
13.6
Configuring Oracle Portal, Forms, Reports, and Discoverer for High Availability
13.6.1
Prerequisites
13.6.1.1
Dependencies
13.6.1.2
Network Requirements
13.6.1.2.1
Load Balancer
13.6.1.2.2
Load Balancer Configuration - Virtual Server Names and Ports
13.6.1.3
Databases
13.6.1.4
Shared Directories
13.6.1.5
Managed Port Numbers
13.6.1.6
Site Names
13.6.2
Assumptions
13.6.2.1
Ports
13.6.3
Creating the Metadata Repository
13.6.3.1
Install the Repository Creation Utility (RCU)
13.6.3.2
Run Repository Creation Utility
13.6.4
Install and Configure Application Tier on APPHOST1
13.6.4.1
Install Oracle WebLogic Server
13.6.4.2
Install Oracle Portal, Forms, Reports, and Discoverer
13.6.4.3
Configure Oracle Portal, Forms, Reports, and Discoverer Software
13.6.4.4
Validation
13.6.4.5
Generic Configuration
13.6.4.5.1
Set Admin Server Listen Address
13.6.4.5.2
Configure Virtual Hosts
13.6.4.5.3
Create boot.properties File
13.6.4.5.4
Configure sqlnet.ora
13.6.4.5.5
Configure Web Cache
13.6.4.5.6
Change the Web Cache Passwords
13.6.4.5.7
Restart Web Tier (Oracle HTTP Server and Web Cache)
13.6.4.5.8
Register with Single Sign-On Server
13.6.4.5.9
Enabling the WebLogic Plug-in
13.6.4.5.10
Change Host Assertion in WebLogic
13.6.4.6
Configure Oracle Portal for High Availability
13.6.4.6.1
Rewire Portal Repository
13.6.4.6.2
Configure Parallel Page Engine Loop-Back with Load Balancer
13.6.4.6.3
Database Wallets and Portal
13.6.4.6.4
Restart All Components
13.6.4.6.5
Post-installation Step for Portal Installation with Oracle RAC
13.6.4.6.6
Validate Configuration
13.6.4.7
Configure Oracle Forms for High Availability
13.6.4.7.1
Create TNSNAMES Entries for Customer Databases
13.6.4.7.2
Restart WLS_FORMS
13.6.4.7.3
Validate Configuration
13.6.4.8
Configure Oracle Reports for High Availability
13.6.4.8.1
Create Reports Queue in Database
13.6.4.8.2
Create a TNSNAMES Entry for Reports Queue
13.6.4.8.3
Create a Security Key for the Reports Queue
13.6.4.8.4
Configure the Database Job Repository for In-Process Reports Servers
13.6.4.8.5
Configure the Reports Server to Access Shared Output Directory
13.6.4.8.6
Restart WLS_REPORTS
13.6.4.8.7
Validate Configuration
13.6.4.9
Configure Oracle Discoverer for High Availability
13.6.4.9.1
Create TNSNAMES Entries for Customer Databases
13.6.4.9.2
Update configuration.xml
13.6.4.9.3
Discoverer Viewer and Web Cache
13.6.4.9.4
Enable Single Sign On
13.6.4.9.5
Restart All Components
13.6.4.9.6
Validate Configuration
13.6.5
Install and Configure Application Tier on APPHOST2
13.6.5.1
Install Oracle WebLogic Server
13.6.5.2
Install Oracle Portal, Forms, Reports, and Discoverer Software
13.6.5.3
Configure Oracle Portal, Forms, Reports, and Discoverer Software
13.6.5.4
Generic Configuration
13.6.5.4.1
Copy Configuration Information from APPHOST1
13.6.5.4.2
Configure Virtual Hosts
13.6.5.4.3
Update Oracle HTTP Server Configuration to be Cluster Aware
13.6.5.4.4
Change the Web Cache Passwords
13.6.5.4.5
Configure Web Cache
13.6.5.4.6
Restart Web Processes on APPHOST1 and APPHOST2
13.6.5.5
Configure Oracle Portal for High Availability
13.6.5.5.1
Copy Configuration Information from APPHOST1
13.6.5.5.2
Create Portal Directories
13.6.5.5.3
Update Instance Paths
13.6.5.5.4
Restart the Web Processes
13.6.5.5.5
Start WLS_PORTAL1
13.6.5.5.6
Validate the Configuration
13.6.5.5.7
Best Practices
13.6.5.6
Configure Oracle Forms for High Availability
13.6.5.6.1
Create a TNSNAMES entries for Customer Databases
13.6.5.6.2
Copy Forms Configuration Files
13.6.5.6.3
Update default.env
13.6.5.6.4
Restart WLS_FORMS1
13.6.5.6.5
Validate the Configuration
13.6.5.6.6
Best Practices
13.6.5.7
Configure Oracle Reports for High Availability
13.6.5.7.1
Create TNSNAMES Entries for Customer Databases
13.6.5.7.2
Configure the Reports Server to Access Shared Output Directory
13.6.5.7.3
Configure the Database Job Repository for In-process Reports Servers
13.6.5.7.4
Creating an Oracle Reports Server Cluster
13.6.5.7.5
Restart WLS_REPORTS and WLS_REPORTS1
13.6.5.7.6
Validate the Configuration
13.6.5.7.7
Managing Connection Availability for Oracle Reports Services
13.6.5.8
Configure Oracle Discoverer for High Availability
13.6.5.8.1
Create TNSNAMES Entries for Customer Databases
13.6.5.8.2
Copy Discoverer Configuration Files.
13.6.5.8.3
Update configuration.xml
13.6.5.8.4
Changing the Preference Store
13.6.5.8.5
Restart WLS_DISCO and WLS_DISCO1
13.6.5.8.6
Validate the Configuration
13.6.5.8.7
Failover of the Preference Server
13.6.5.8.8
Setting up Discoverer WSRP Portlet Producer in a Clustered Environment
13.6.5.8.9
Best Practices
13.6.6
Scaling Out the Deployment
14
Configuring High Availability for Oracle Business Intelligence and EPM
14.1
High Availability for Oracle Business Intelligence Enterprise Edition and Enterprise Performance Management
14.1.1
Oracle BI EE Component Architecture
14.1.1.1
Oracle BI EE Component Characteristics
14.1.1.1.1
Process Lifecycle
14.1.1.1.2
External Dependencies
14.1.1.1.3
Configuration Artifacts
14.1.1.1.4
Deployment Artifacts
14.1.1.1.5
Log File Locations
14.1.2
Oracle BI EE High Availability Concepts
14.1.2.1
Oracle BI EE and EPM High Availability Architecture
14.1.2.1.1
Web Server High Availability Considerations
14.1.2.1.2
Oracle BI Presentation Services Plug-in High Availability Considerations
14.1.2.1.3
Presentation Services High Availability Considerations
14.1.2.1.4
BI Cluster Controller High Availability Considerations
14.1.2.1.5
BI Server High Availability Considerations
14.1.2.1.6
Administration Tool High Availability Considerations
14.1.2.1.7
Oracle BI Scheduler High Availability Considerations
14.1.2.1.8
BI JavaHost High Availability Considerations
14.1.2.2
Shared Files and Directories
14.1.2.2.1
Oracle BI Presentation Catalog Shared Files
14.1.2.2.2
Repository Publishing Directory Shared Files
14.1.2.2.3
Global Cache Shared Files
14.1.2.2.4
Oracle BI Scheduler Scripts Shared Files
14.1.2.3
Starting and Stopping the Cluster
14.1.2.4
Cluster-Wide Configuration Changes
14.1.2.5
Protection From Failures and Expected Behaviors
14.1.2.5.1
Machine Failure
14.1.2.5.2
WebLogic Administration Server Failure
14.1.2.5.3
WebLogic Managed Server Failure
14.1.2.5.4
Oracle BI Scheduler Failure
14.1.2.5.5
Cluster Controller Failure
14.1.2.5.6
Presentation Services Failure
14.1.2.5.7
BI Server Failure
14.1.2.5.8
Troubleshooting Oracle BI EE
14.1.3
Oracle Essbase Component Architecture
14.1.3.1
Oracle Essbase Component Characteristics
14.1.3.1.1
State Information
14.1.3.1.2
Runtime Processes
14.1.3.1.3
Process Lifecycle
14.1.3.1.4
Request Flow
14.1.3.1.5
External Dependencies
14.1.3.1.6
Configuration Artifacts
14.1.3.1.7
Deployment Artifacts
14.1.3.1.8
Log Files
14.1.4
Oracle Essbase High Availability Concepts
14.1.4.1
Oracle Essbase High Availability Architecture
14.1.4.1.1
Shared Files and Directories
14.1.4.1.2
Cluster-Wide Configuration Changes
14.1.4.2
Protection from Failures and Expected Behaviors
14.1.4.3
Troubleshooting
14.1.5
Configuring Oracle Essbase Clustering
14.1.5.1
Prerequisites
14.1.5.2
Configuring a shared ARBORPATH
14.1.5.3
Configuring Secondary Instances of Essbase Agent
14.1.6
Oracle Hyperion Provider Services Component Architecture
14.1.6.1
Oracle Hyperion Provider Services Component Characteristics
14.1.6.1.1
State Information
14.1.6.1.2
Runtime Processes
14.1.6.1.3
Process Lifecycle
14.1.6.1.4
Request Flow
14.1.6.1.5
External Dependencies
14.1.6.1.6
Configuration Artifacts
14.1.6.1.7
Deployment Artifacts
14.1.6.1.8
Log Files
14.1.7
Oracle Hyperion Provider Services High Availability Concepts
14.1.7.1
Oracle Hyperion Provider Services High Availability Architecture
14.1.7.1.1
Hyperion Registry Structure for a Provider Services Cluster
14.1.7.1.2
Cluster-Wide Configuration Changes
14.1.7.1.3
OPMN Essbase Cluster Support
14.1.7.1.4
Essbase Database Clustering by Provider Services
14.1.7.2
Protection from Failures and Expected Behaviors
14.1.8
Oracle EPM Workspace Component Architecture
14.1.8.1
Workspace Component Characteristics
14.1.8.1.1
State Information
14.1.8.1.2
Runtime Processes
14.1.8.1.3
Process Lifecycle
14.1.8.1.4
Request Flow
14.1.8.1.5
External Dependencies
14.1.8.1.6
Configuration Artifacts
14.1.8.1.7
Deployment Artifacts
14.1.8.1.8
Log Files
14.1.9
Oracle EPM Workspace High Availability Concepts
14.1.9.1
Workspace High Availability Architecture
14.1.9.1.1
Shared Files and Directories
14.1.9.1.2
Cluster-Wide Configuration Changes
14.1.9.2
Protection from Failures and Expected Behaviors
14.1.9.3
Troubleshooting
14.1.10
Oracle Hyperion Financial Reporting Component Architecture
14.1.10.1
Oracle Hyperion Financial Reporting Component Characteristics
14.1.10.1.1
State Information
14.1.10.1.2
Runtime Processes
14.1.10.1.3
External Dependencies
14.1.10.1.4
Configuration Artifacts
14.1.10.1.5
Deployment Artifacts
14.1.10.1.6
Log Files
14.1.11
Oracle Hyperion Financial Reporting High Availability Concepts
14.1.11.1
Oracle Hyperion Financial Reporting High Availability Architecture
14.1.11.1.1
Shared Files and Directories
14.1.11.1.2
Cluster-Wide Configuration Changes
14.1.11.2
Protection from Failures and Expected Behaviors
14.1.12
Allocation Manager Component Architecture and Characteristics
14.1.13
Oracle BI EE High Availability Configuration Steps
14.1.13.1
Prerequisite Steps Before Setting Up a High Availability Configuration for Oracle BI Enterprise Edition and BI Publisher
14.1.13.1.1
Database Prerequisites
14.1.13.1.2
VIP and IP Prerequisites
14.1.13.1.3
Shared Storage Prerequisites
14.1.13.1.4
Clock Synchronization
14.1.13.1.5
Installing and Configuring the Database Repository
14.1.13.1.6
Using RCU to Load the Business Intelligence Schemas in the Database
14.1.13.1.7
Configuring Virtual Server Names and Ports for the Load Balancer
14.1.13.1.8
Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
14.1.13.1.9
Validating Oracle HTTP Server
14.1.13.2
Installing Oracle Business Intelligence Enterprise Edition for High Availability
14.1.13.2.1
Installing Oracle WebLogic Server
14.1.13.2.2
Installing Oracle Fusion Middleware for Business Intelligence Enterprise Edition and Oracle BI Publisher
14.1.13.3
Enabling VIP1 in APPHOST1 and VIP2 in APPHOST2
14.1.13.4
Creating a Domain with the Administration Server and the First BI_SERVER1 Managed Server
14.1.13.5
Creating boot.properties for the Administration Server on APPHOST1
14.1.13.6
Starting and Validating the Administration Server on APPHOST1
14.1.13.6.1
Starting the Administration Server on APPHOST1
14.1.13.6.2
Validating the Administration Server
14.1.13.7
Setting the Listen Address for BI_SERVER1 Managed Server
14.1.13.7.1
Updating the Oracle BI Publisher Scheduler Configuration
14.1.13.8
Disabling Host Name Verification for the BI_SERVER1 Managed Server
14.1.13.9
Starting the System in APPHOST1
14.1.13.9.1
Starting Node Manager on APPHOST1
14.1.13.9.2
Starting and Validating the BI_SERVER1 Managed Server
14.1.13.9.3
Starting and Validating the BI EE System Components on APPHOST1
14.1.13.10
Configuring Oracle BI EE
14.1.13.10.1
Setting the Location of the Shared Oracle BI Repository
14.1.13.10.2
Setting the Shared Global Cache for BI Server
14.1.13.10.3
Setting the Scheduler Script Path and Default Script Path
14.1.13.10.4
Setting the Location of the Shared Oracle BI Presentation Catalog
14.1.13.11
Setting Server Configuration Options
14.1.13.12
Scaling Out the BI System on APPHOST2
14.1.13.13
Scaling Out BI System Components
14.1.13.14
Making Singleton Components Active-Passive
14.1.13.15
Setting the Listen Address for the BI_SERVER2 Managed Server
14.1.13.15.1
Updating the Oracle BI Publisher Scheduler Configuration on APPHOST1 and APPHOST2
14.1.13.16
Disabling Host Name Verification for the BI_SERVER2 Managed Server
14.1.13.17
Configuring Oracle BI for Microsoft Office SSO Properties
14.1.13.17.1
Validating Oracle BI for Microsoft Office Configuration
14.1.13.18
Configuring Oracle BI Publisher
14.1.13.18.1
Setting Oracle BI Presentation Services Options
14.1.13.18.2
Setting Scheduler Configuration Options
14.1.13.18.3
Setting the Oracle BI EE Data Source
14.1.13.18.4
Configuring JMS for Oracle BI Publisher
14.1.13.18.5
Configuring a Default Persistence Store for Transaction Recovery
14.1.13.19
Starting the System in APPHOST2
14.1.13.19.1
Starting Node Manager on APPHOST2
14.1.13.19.2
Starting and Validating the BI_SERVER2 Managed Server
14.1.13.19.3
Starting and Validating the Business Intelligence Enterprise Edition System Components
14.1.13.20
Configuring Oracle HTTP Server for the BI_SERVERn Managed Servers
14.1.13.20.1
Validating Access Through Oracle HTTP Server
14.1.13.21
Setting the Frontend HTTP Host and Port
14.1.13.22
Configuring Server Migration for the BI_SERVERn Servers
14.1.13.22.1
Setting Up a User and Tablespace for the Server Migration Leasing Table
14.1.13.22.2
Creating a Multi Data Source Using the Administration Console / Creating a GridLink Data Source
14.1.13.22.3
Editing Node Manager's Properties File
14.1.13.22.4
Setting Environment and Superuser Privileges for the wlsifconfig.sh Script
14.1.13.22.5
Configuring Server Migration Targets
14.1.13.22.6
Testing the Server Migration
14.1.13.23
Scaling Up the Oracle BI EE Topology
14.1.13.24
Scaling Out the Oracle BI EE Topology to a New Node (APPHOST3)
14.2
High Availability for Oracle Business Intelligence Publisher
14.2.1
Oracle BI Publisher Component Architecture
14.2.1.1
Oracle BI Publisher Component Characteristics
14.2.1.1.1
State Information
14.2.1.1.2
Runtime Processes
14.2.1.1.3
Process Lifecycle
14.2.1.1.4
Request Flow
14.2.1.1.5
External Dependencies
14.2.1.1.6
Configuration Artifacts
14.2.1.1.7
Deployment Artifacts
14.2.1.1.8
Log Files
14.2.2
Oracle BI Publisher High Availability Concepts
14.2.2.1
Oracle BI Publisher High Availability Architecture
14.2.2.1.1
Shared Files and Directories
14.2.2.1.2
Cluster-Wide Configuration Changes
14.2.2.2
Protection from Failures and Expected Behaviors
14.2.2.3
Troubleshooting
14.2.3
Oracle BI Publisher High Availability Configuration Steps
14.2.3.1
Preparing the Environment: Prerequisite Steps Before Setting Up an Oracle BI Publisher High Availability Configuration
14.2.3.1.1
Database Prerequisites
14.2.3.1.2
VIP and IP Prerequisites
14.2.3.1.3
Shared Storage Prerequisites
14.2.3.1.4
Clock Synchronization
14.2.3.1.5
Installing and Configuring the Database Repository
14.2.3.1.6
Using RCU to Load the Business Intelligence Schemas in the Database
14.2.3.1.7
Configuring Virtual Server Names and Ports for the Load Balancer
14.2.3.1.8
Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
14.2.3.1.9
Validating Oracle HTTP Server
14.2.3.2
Installing Oracle Fusion Middleware Home
14.2.3.2.1
Installing Oracle WebLogic Server
14.2.3.2.2
Installing Oracle Fusion Middleware for BI Publisher
14.2.3.3
Enabling VIP1 in APPHOST1 and VIP2 in APPHOST2
14.2.3.4
Creating a Domain with the Administration Server and the First BI_SERVER1 Managed Server
14.2.3.5
Creating boot.properties for the Administration Server on APPHOST1
14.2.3.6
Starting and Validating the Administration Server on APPHOST1
14.2.3.6.1
Starting the Administration Server on APPHOST1
14.2.3.6.2
Validating the Administration Server
14.2.3.7
Setting the Listen Address for BI_SERVER1 Managed Server
14.2.3.8
Disabling Host Name Verification for the BI_SERVER1 Managed Server
14.2.3.9
Starting the System in APPHOST1
14.2.3.9.1
Starting Node Manager on APPHOST1
14.2.3.9.2
Starting and Validating the BI_SERVER1 Managed Server
14.2.3.10
Prerequisites for Scaling Out the BI System on APPHOST2
14.2.3.10.1
Setting Server Configuration Options
14.2.3.10.2
Setting Scheduler Configuration Options
14.2.3.10.3
Updating the Oracle BI Publisher Scheduler Configuration
14.2.3.11
Scaling Out the BI System on APPHOST2
14.2.3.12
Setting the Listen Address for the BI_SERVER2 Managed Server
14.2.3.13
Disabling Host Name Verification for the BI_SERVER2 Managed Server
14.2.3.14
Configuring Oracle BI Publisher
14.2.3.14.1
Configuring JMS Persistence Store for BI Publisher
14.2.3.14.2
Configuring a Default Persistence Store for Transaction Recovery
14.2.3.15
Starting the System in APPHOST2
14.2.3.15.1
Starting Node Manager on APPHOST2
14.2.3.15.2
Starting and Validating the BI_SERVER2 Managed Server
14.2.3.16
Configuring Oracle HTTP Server for the BI_SERVERn Managed Servers
14.2.3.17
Validating Access Through Oracle HTTP Server
14.2.3.18
Configuring Server Migration for the BI_SERVERn Servers
14.2.3.19
Scaling Out the Oracle BI Publisher Topology to a New Node (APPHOST3)
14.3
High Availability for Oracle Real-Time Decisions
14.3.1
Oracle RTD Component Architecture
14.3.1.1
Oracle RTD Component Characteristics
14.3.1.1.1
Component Lifecycle
14.3.1.1.2
Process Flow
14.3.1.1.3
External Dependencies
14.3.1.1.4
Configuration Artifacts
14.3.1.1.5
Deployment Artifacts
14.3.1.1.6
Log File Locations
14.3.2
Oracle RTD High Availability Concepts
14.3.2.1
Oracle RTD High Availability Architecture
14.3.2.1.1
Starting and Stopping the Cluster
14.3.2.1.2
Cluster-Wide Configuration Changes
14.3.2.2
Protection from Failures and Expected Behaviors
14.3.2.2.1
Decision Server Failure
14.3.2.2.2
Cluster Coordinator Failure
14.3.2.2.3
Learning Service Failure
14.3.2.2.4
Decision Center Failure
14.3.2.2.5
Batch Manager Failure
14.3.3
Oracle RTD High Availability Configuration Steps
14.3.3.1
Prerequisite Steps Before Setting up an Oracle RTD High Availability Configuration
14.3.3.1.1
Database Prerequisites
14.3.3.1.2
Installing and Configuring the Database Repository
14.3.3.1.3
Using RCU to Load the Business Intelligence Schemas into the Database
14.3.3.1.4
Configuring Virtual Server Names and Ports for the Load Balancer
14.3.3.1.5
Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
14.3.3.1.6
Validating Oracle HTTP Server
14.3.3.2
Installing Oracle Fusion Middleware Home
14.3.3.2.1
Installing Oracle WebLogic Server
14.3.3.2.2
Installing Oracle RTD
14.3.3.3
Enabling VIP1 in APPHOST1 and VIP2 in APPHOST2
14.3.3.4
Creating a Domain with the Administration Server and the First BI_SERVER1 Managed Server
14.3.3.5
Creating boot.properties for the Administration Server on APPHOST1
14.3.3.6
Starting and Validating the Administration Server on APPHOST1
14.3.3.6.1
Starting the Administration Server on APPHOST1
14.3.3.6.2
Validating the Administration Server
14.3.3.7
Setting the Listen Address for BI_SERVER1 Managed Server
14.3.3.8
Disabling Host Name Verification for the BI_SERVER1 Managed Server
14.3.3.9
Starting the System in APPHOST1
14.3.3.9.1
Starting Node Manager on APPHOST1
14.3.3.9.2
Starting and Validating the BI_SERVER1 Managed Server
14.3.3.10
Scaling Out the BI System on APPHOST2
14.3.3.11
Setting the Listen Address for the BI_SERVER2 Managed Server
14.3.3.12
Disabling Host Name Verification for the BI_SERVER2 Managed Server
14.3.3.13
Configuring Oracle RTD
14.3.3.13.1
Configuring RTD Cluster-Specific Properties
14.3.3.14
Starting the System in APPHOST2
14.3.3.14.1
Configuring a Default Persistence Store for Transaction Recovery
14.3.3.14.2
Starting Node Manager on APPHOST2
14.3.3.14.3
Starting and Validating the BI_SERVER2 Managed Server
14.3.3.15
Configuring Oracle HTTP Server for the BI_SERVERn Managed Servers
14.3.3.16
Validating Access Through Oracle HTTP Server
14.3.3.17
Configuring Server Migration for the BI_SERVERn Servers
14.3.3.18
Scaling Out the Oracle RTD Topology to a New Node (APPHOST3)
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
Component Workbooks
D.1
Oracle SOA Suite Workbook
D.1.1
Workbook Tables for Oracle SOA Suite
D.2
Oracle Identity Management Workbook
D.2.1
Workbook Tables for Oracle Identity Management
D.3
Oracle WebCenter Portal Workbook
D.3.1
Workbook Tables for Oracle WebCenter Portal
D.4
Oracle Portal, Forms, Reports, and Discoverer Workbook
D.4.1
Workbook Tables for Oracle Portal, Forms, Reports, and Discoverer
D.5
Oracle WebCenter Content Workbook
D.5.1
Workbook Tables for Oracle WebCenter Content
D.6
Oracle Data Integrator Workbook
D.6.1
Workbook Tables for Oracle Data Integrator
D.7
Oracle Business Intelligence Platform Workbook
D.7.1
Workbook Tables for Oracle Business Intelligence Platform
E
Configuring the Distributed Java Object Cache
E.1
Configuring the Java Object Cache
E.2
Running CacheWatcher
F
Configuring Distributed Notifications for MDS
Scripting on this page enhances content navigation, but does not change the content in any way.