1/29
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
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
About 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
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
GridLink Data Sources and Oracle RAC
4.1.3
Using Multi Data Sources with Oracle RAC
4.1.3.1
Configuring Multi Data Sources for MDS Repositories
4.1.3.2
Oracle RAC Configuration Requirements
4.1.3.3
Configuring Schemas for Transactional Recovery Privileges
4.1.4
Configuring GridLink Data Sources with Oracle RAC
4.1.5
Configuring Multi Data Sources with Oracle RAC
4.1.6
JDBC Clients
4.1.7
System Clients
4.1.7.1
Oracle Internet Directory
4.1.7.2
Oracle Forms
4.1.7.3
Oracle Portal
4.1.7.4
Oracle Reports and Oracle Discoverer
4.2
Protecting Idle Connections from Firewall Timeouts
4.3
Troubleshooting
4.4
Using SCAN Addresses with Oracle Database 11g (11.2)
5
Configuring High Availability for Oracle SOA Suite
5.1
Introduction to Oracle SOA Suite
5.2
Oracle SOA Infrastructure High Availability
5.2.1
Oracle SOA Infrastructure Single-Instance Characteristics
5.2.1.1
Oracle SOA Infrastructure Application Characteristics
5.2.1.2
Oracle SOA Infrastructure Startup and Shutdown Lifecyle
5.2.1.3
Oracle SOA Infrastructure External Dependencies
5.2.1.4
Oracle SOA Infrastructure Startup and Shut Down of Processes
5.2.1.5
Oracle SOA Infrastructure Configuration Artifacts
5.2.1.6
Oracle SOA Infrastructure Log File Locations
5.2.2
Oracle SOA Infrastructure High Availability Architecture and Failover Considerations
5.2.2.1
Oracle SOA Infrastructure Protection from Failures and Expected Behavior
5.2.2.1.1
WebLogic Server Failure
5.2.2.1.2
Node Failure
5.2.2.1.3
Database Failure
5.2.2.2
Oracle SOA Infrastructure Cluster-Wide Deployment
5.2.2.3
Online Redeployment of Oracle SOA Infrastructure Composites in a Cluster
5.2.2.4
Oracle SOA 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 BPM Suite and High Availability Concepts
5.4.1
Oracle BPM Suite Single Instance Concepts
5.4.1.1
Oracle BPM Suite Component Characteristics
5.4.1.2
Oracle BPM Suite Component Interaction
5.4.1.3
Oracle BPM Suite Startup and Shutdown Lifecycle
5.4.1.4
Oracle BPM Suite Configuration Artifacts
5.4.2
Oracle BPMN Service Engine High Availability
5.4.2.1
Oracle BPMN Service Engine Single Instance Characteristics
5.4.2.1.1
Oracle BPMN Service Engine Single Instance Architecture
5.4.2.1.2
Oracle BPMN Service Engine External Dependencies
5.4.2.1.3
Oracle BPMN Service Engine Startup and Shutdown Lifecycle
5.4.2.1.4
Oracle BPMN Service Engine Log Files
5.4.2.2
Oracle BPMN Service Engine High Availability Considerations
5.4.2.2.1
Oracle BPMN Service Engine High Availability Architecture and Failover Considerations
5.4.2.2.2
Configuring Oracle BPMN Service Engine for High Availability
5.4.2.2.3
Cluster-Wide Configuration Changes for Oracle BPMN Service Engine
5.4.3
Oracle Business Process Web Applications High Availability
5.4.3.1
Oracle Business Process Web Applications Single Instance Characteristics
5.4.3.1.1
Oracle Business Process Web Applications Single Instance Architecture
5.4.3.1.2
Oracle Business Process Web Applications External Dependencies
5.4.3.1.3
Oracle Business Process Web Applications Startup and Shutdown Lifecycle
5.4.3.1.4
Oracle Business Process Web Applications Log Files
5.4.3.2
Oracle Business Process Web Applications High Availability Considerations
5.4.3.2.1
Oracle Business Process Web Applications High Availability Architecture and Failover Considerations
5.4.3.2.2
Configuring Oracle Business Process Web Applications for High Availability
5.4.3.2.3
Cluster-Wide Configuration Changes for Oracle Business Process Web Applications
5.4.4
Oracle Business Process Analytics High Availability
5.4.4.1
Oracle Business Process Analytics Single Instance Characteristics
5.4.4.1.1
Oracle Business Process Analytics Single Instance Architecture
5.4.4.1.2
Oracle Business Process Analytics External Dependencies
5.4.4.1.3
Oracle Business Process Analytics Startup and Shutdown Lifecycle
5.4.4.1.4
Oracle Business Process Analytics Log Files
5.4.4.2
Oracle Business Process Analytics High Availability Considerations
5.4.4.2.1
Oracle Business Process Analytics High Availability Architecture and Failover Considerations
5.4.4.2.2
Configuring Oracle Business Process Analytics for High Availability
5.4.4.2.3
Cluster-Wide Configuration Changes for Oracle Business Process Analytics
5.5
Oracle Mediator and High Availability Concepts
5.5.1
Oracle Mediator Single-Instance Characteristics
5.5.1.1
Oracle Mediator Component Characteristics
5.5.1.2
Oracle Mediator Startup and Shutdown Lifecycle
5.5.1.3
Oracle Mediator Request Flow
5.5.1.4
Oracle Mediator Configuration Artifacts
5.5.2
Oracle Mediator High Availability Architecture and Failover Considerations
5.5.2.1
Oracle Mediator Protection from Failures and Expected Behavior
5.5.2.1.1
Recovering Failed Mediator Instances
5.5.2.1.2
Oracle Mediator's Resequencing in a Cluster
5.5.2.2
Troubleshooting Oracle Mediator High Availability
5.6
Oracle Human Workflow and High Availability Concepts
5.6.1
Oracle Human Workflow Single-Instance Characteristics
5.6.1.1
Oracle Human Workflow Startup and Shutdown Lifecycle
5.6.1.2
Oracle Human Workflow Request Processing
5.6.1.3
Oracle Human Workflow Configuration Artifacts
5.6.1.3.1
Managing the URI of the Human Task Service Component Task Details Application
5.6.2
Oracle Human Workflow High Availability Architecture and Failover Considerations
5.6.2.1
Oracle Human Workflow Protection from Failures and Expected Behavior
5.6.2.2
Manual Recovery Required for Human Workflow Task in Rejected MSG Table
5.6.3
Troubleshooting Oracle Human Workflow High Availability
5.7
Oracle B2B and High Availability Concepts
5.7.1
Oracle B2B Single-Instance Characteristics
5.7.1.1
Oracle B2B Component Characteristics
5.7.1.2
Oracle B2B Startup and Shutdown Lifecycle
5.7.1.3
Oracle B2B Request Flow
5.7.1.4
Oracle B2B Configuration Artifacts
5.7.2
Oracle B2B High Availability Architecture and Failover Considerations
5.7.2.1
Oracle B2B Protection from Failures and Expected Behavior
5.7.2.2
Oracle B2B Cluster-Wide Configuration Changes
5.7.2.3
Oracle B2B Deployments in a Cluster
5.7.2.4
Troubleshooting Oracle B2B Active-Active Configuration
5.7.2.4.1
Purge, Import, or Deployment of B2B Metadata
5.7.2.4.2
Error While Retrieving Oracle B2B Document Definitions
5.8
Oracle Web Services Manager and High Availability Concepts
5.8.1
Oracle WSM Single-Instance Characteristics
5.8.1.1
Oracle WSM Component Characteristics
5.8.1.2
Oracle WSM Startup and Shutdown Lifecycle
5.8.1.3
Oracle WSM Request Flow
5.8.1.4
Oracle WSM Configuration Artifacts
5.8.2
Oracle WSM High Availability Architecture and Failover Considerations
5.8.2.1
Oracle WSM Protection from Failures and Expected Behavior
5.8.2.2
Oracle WSM Cluster-Wide Configuration Changes
5.8.2.3
Configuring the Java Object Cache for Oracle WSM
5.8.2.4
Configuring Distributed Notifications for the MDS Repository
5.9
Oracle User Messaging Service and High Availability Concepts
5.9.1
Oracle User Messaging Service Single-Instance Characteristics
5.9.1.1
Oracle User Messaging Service Component Characteristics
5.9.1.2
Oracle User Messaging Service Startup and Shutdown Lifecycle
5.9.1.3
Oracle User Messaging Service Request Flow
5.9.1.4
Oracle User Messaging Service Configuration Artifacts
5.9.2
Oracle User Messaging Service High Availability Architecture and Failover Considerations
5.9.2.1
Oracle User Messaging Service Protection from Failures and Expected Behavior
5.9.2.2
Oracle User Messaging Service Cluster-Wide Configuration Changes
5.10
Oracle JCA Adapters and High Availability Concepts
5.10.1
Oracle JCA Adapters Single-Instance Characteristics
5.10.1.1
Oracle JCA Adapters Component Lifecycle
5.10.1.2
Oracle JCA Adapters Reliability and Transactional Behavior
5.10.1.3
Oracle JCA Adapters - Rejected Message Handling
5.10.2
Oracle JCA Adapters High Availability Architecture and Failover Considerations
5.10.2.1
Oracle JCA Adapters High Availability Error Handling
5.10.2.2
Oracle File and FTP Adapters High Availability
5.10.2.3
Oracle Database Adapters High Availability
5.10.2.4
Oracle JMS Adapters High Availability
5.10.2.4.1
Message Redelivery
5.10.2.4.2
Use of WebLogic Server Distributed Destinations
5.10.2.5
Oracle JCA Adapters Log File Locations
5.11
Oracle Business Activity Monitoring and High Availability Concepts
5.11.1
Oracle Business Activity Monitoring Single-Instance Characteristics
5.11.1.1
Oracle Business Activity Monitoring Component Characteristics
5.11.1.2
Oracle Business Activity Monitoring Startup/Shutdown Lifecycle
5.11.1.3
Oracle Business Activity Monitoring Startup and Shutdown of Processes
5.11.1.4
Oracle Business Activity Monitoring Configuration Artifacts
5.11.2
Oracle Business Activity Monitoring High Availability Architecture and Failover Considerations
5.11.2.1
Oracle Business Activity Monitoring Protection from Failures and Expected Behavior
5.11.2.2
Oracle Business Activity Monitoring Cluster-Wide Configuration Changes
5.11.2.3
Considerations for BAM Client Retries
5.12
Oracle Service Bus and High Availability Concepts
5.12.1
Oracle Service Bus Single Node Characteristics
5.12.1.1
Oracle Service Bus Session State
5.12.1.2
Oracle Service Bus External Dependencies
5.12.1.3
Oracle Service Bus Configuration Artifacts
5.12.1.4
Oracle Service Bus Deployment Artifacts
5.12.1.5
Oracle Service Bus Startup and Shutdown
5.12.1.6
Oracle Service Bus Log File Locations
5.12.2
Oracle Service Bus High Availability Architecture and Failover Considerations
5.12.2.1
Oracle Service Bus Protection from Failures and Expected Behavior
5.12.2.1.1
WebLogic Server Failure
5.12.2.1.2
Node Failure
5.12.2.1.3
Database Failure
5.12.2.2
Oracle Service Bus Cluster-Wide Deployment
5.12.2.3
Online Redeployment of Oracle Service Bus in a Cluster
5.12.2.4
Oracle Service Bus Cluster-Wide Configuration Changes
5.13
Configuring High Availability for Oracle SOA Infrastructure and Component Service Engines
5.13.1
Preparing the Environment: Prerequisite Steps Before Setting up a SOA High Availability Configuration
5.13.1.1
Database Prerequisites
5.13.1.2
VIP and IP Prerequisites
5.13.1.3
Shared Storage Prerequisites
5.13.1.4
Installing and Configuring an LDAP Provider
5.13.1.5
Synchronizing System Clocks
5.13.1.6
Terminology for Directories and Directory Environment Variables
5.13.1.7
Installing and Configuring the Database Repository
5.13.1.8
Using Oracle Fusion Middleware Repository Creation Utility to Load the Fusion Middleware Schemas in the Database
5.13.1.8.1
Running RCU
5.13.1.8.2
Configuring SOA Schemas for Transactional Recovery Privileges
5.13.1.9
Configuring Virtual Server Names and Ports for the Load Balancer
5.13.1.10
Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
5.13.1.10.1
Validating Oracle HTTP Server
5.13.2
Installing Oracle Fusion Middleware Home
5.13.2.1
Installing Oracle WebLogic Server
5.13.2.2
Installing Oracle Fusion Middleware for Oracle SOA
5.13.3
Enabling VIP1 in SOAHOST1 and VIP2 in SOAHOST2
5.13.4
Running Oracle Fusion Middleware Configuration Wizard on SOAHOST1 to Create the SOA Domain
5.13.5
Creating boot.properties for the Administration Server on SOAHOST1
5.13.6
Starting and Validating the Administration Server in SOAHOST1
5.13.6.1
Starting the Administration Server on SOAHOST1
5.13.6.2
Validating the Administration Server
5.13.7
Disabling Host Name Verification for the Administration Server and the WLS_SOAn Managed Servers
5.13.8
Configuring Oracle Coherence for Deploying Composites
5.13.9
Starting the System in SOAHOST1
5.13.9.1
Starting Node Manager on SOAHOST1
5.13.9.2
Starting and Validating the WLS_SOA1 Managed Server
5.13.10
Propagating the Domain Configuration to SOAHOST2 with pack/unpack Utilities
5.13.11
Extracting XEngine Files in the Second Node
5.13.12
Starting the System in SOAHOST2
5.13.12.1
Starting Node Manager on SOAHOST2
5.13.12.2
Starting and Validating the WLS_SOA2 Managed Server
5.13.13
Configuring Oracle HTTP Servers for the Administration Server and the WLS_SOAn Managed Servers
5.13.14
Validating Access Through Oracle HTTP Server
5.13.15
Configuring JMS Persistence Store as Shared Across the Servers
5.13.16
Configuring a Default Persistent Store for Transaction Recovery
5.13.17
Setting the Front End HTTP Host and Port
5.13.18
Setting the WLS Cluster Address for Direct Binding/RMI Invocations to Composites
5.13.19
Deploying Applications
5.13.20
Configuring Server Migration for the WLS_SOA Servers
5.13.20.1
Setting Up a User and Tablespace for the Server Migration Leasing Table
5.13.20.2
Creating a GridLink or Multi Data Source Using the Oracle WebLogic Administration Console
5.13.20.3
Editing Node Manager's Properties File
5.13.20.4
Setting Environment and Superuser Privileges for the wlsifconfig.sh Script
5.13.20.5
Configuring Server Migration Targets
5.13.20.6
Testing the Server Migration
5.13.21
Scaling the Topology
5.13.21.1
Scaling Up the Topology (Adding Managed Servers to Existing Nodes)
5.13.21.2
Scaling Out the Topology (Adding Managed Servers to New Nodes)
5.14
Configuring High Availability for Oracle Service Bus, with SOA Infrastructure and Component Service Engines
5.14.1
Preparing the Environment: Prerequisite Steps Before Setting up a SOA High Availability Configuration
5.14.1.1
Database Prerequisites
5.14.1.2
VIP and IP Prerequisites
5.14.1.3
Shared Storage Prerequisites
5.14.1.4
Installing and Configuring an LDAP Provider
5.14.1.5
Synchronizing System Clocks
5.14.1.6
Terminology for Directories and Directory Environment Variables
5.14.1.7
Installing and Configuring the Database Repository
5.14.1.8
Using Oracle Fusion Middleware Repository Creation Utility to Load the Fusion Middleware Schemas in the Database
5.14.1.8.1
Running RCU
5.14.1.8.2
Configuring SOA Schemas for Transactional Recovery Privileges
5.14.1.9
Configuring Virtual Server Names and Ports for the Load Balancer
5.14.1.10
Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
5.14.1.10.1
Validating Oracle HTTP Server
5.14.2
Installing Oracle Fusion Middleware Home
5.14.2.1
Installing Oracle WebLogic Server
5.14.2.2
Installing Oracle Fusion Middleware for Oracle SOA
5.14.2.3
Installing Oracle Service Bus
5.14.3
Enabling VIP1 and VIP3 in SOAHOST1 and VIP2 and VIP4 in SOAHOST2
5.14.4
Running Oracle Fusion Middleware Configuration Wizard on SOAHOST1 to Create the SOA and OSB Domain
5.14.5
Creating boot.properties for the Administration Server on SOAHOST1
5.14.6
Starting and Validating the Administration Server in SOAHOST1
5.14.6.1
Starting the Administration Server on SOAHOST1
5.14.6.2
Validating the Administration Server
5.14.7
Disabling Host Name Verification for the Administration Server and the WLS_SOAn/WLS_OSBn Managed Servers
5.14.8
Configuring Oracle Coherence for Deploying Composites
5.14.9
Configure Oracle Coherence for the Oracle Service Bus Result Cache
5.14.10
Setting Connection Destination Identifiers for B2B Queues
5.14.11
Starting the System in SOAHOST1
5.14.11.1
Starting Node Manager on SOAHOST1
5.14.11.2
Starting and Validating the WLS_SOA1 Managed Server
5.14.12
Propagating the Domain Configuration to SOAHOST2, OSBHOST1, and OSBHOST2 with pack/unpack Utilities
5.14.13
Extracting XEngine Files in the Second Node
5.14.14
Starting the System in SOAHOST2, OSBHOST1, and OSBHOST2
5.14.14.1
Starting Node Manager on SOAHOST2, OSBHOST1, and OSBHOST2
5.14.14.2
Starting and Validating the WLS_SOA2, WLS_OSB1, and WLS_OSB2 Managed Server
5.14.15
Configuring Oracle HTTP Servers for the Administration Server, WLS_SOAn, and WLS_OSBn Managed Servers
5.14.16
Validating Access Through Oracle HTTP Server
5.14.17
Setting the Front End HTTP Host and Port
5.14.18
Configuring a Default Persistent Store for Transaction Recovery
5.14.19
Deploying Applications
5.14.20
Configuring Server Migration for the WLS_SOA Servers
5.14.21
Configuring Server Migration for the WLS_OSB Servers
5.14.22
Scaling the Topology
5.14.22.1
Scaling Up the Topology (Adding Managed Servers to Existing Nodes)
5.14.22.2
Scaling Out the Topology (Adding Managed Servers to New Nodes)
5.15
Configuring High Availability for Oracle BAM
5.15.1
Preparing the Environment: Prerequisite Steps Before Setting up a High Availability Configuration for Oracle BAM
5.15.1.1
Database Prerequisites
5.15.1.2
VIP and IPs Prerequisites
5.15.1.3
Installing and Configuring the Database Repository
5.15.1.4
Using Oracle Fusion Middleware Repository Creation Utility to Load Oracle Fusion Middleware Schemas
5.15.1.4.1
Running RCU
5.15.1.5
Configuring Virtual Server Names and Ports for the Load Balancer
5.15.2
Installing Oracle HTTP Server on WEBHOST1
5.15.2.1
Validating Oracle HTTP Server
5.15.3
Installing Oracle Fusion Middleware Home
5.15.3.1
Installing Oracle WebLogic Server
5.15.3.2
Installing Oracle BAM Using the Oracle SOA Suite Installer
5.15.4
Enabling VIP0 and VIP1 on BAMHOST1
5.15.5
Running Oracle Fusion Middleware Configuration Wizard on BAMHOST1 to Create the WebLogic Server Oracle BAM Domain
5.15.6
Creating boot.properties for the Administration Server and for WLS_BAM1 on BAMHOST1
5.15.7
Starting the Administration Server on BAMHOST1
5.15.8
Disabling Host Name Verification for the Servers
5.15.9
Configuring a JMS Persistence Store for BAM UMS
5.15.10
Configuring a Default Persistence Store for Transaction Recovery
5.15.11
Untargeting the BAM Server System from BAMHOST2
5.15.12
Propagating the Domain Configuration from BAMHOST1 with pack/unpack Utilities
5.15.13
Starting Node Manager on BAMHOST1 and BAMHOST2
5.15.14
Starting the Oracle BAM System
5.15.15
Configuring Oracle RAC Failover for the WLS_BAM Servers
5.15.16
Configuring the BAM Web Applications to Use the BAM Server in BAMHOST1
5.15.17
Configuring Oracle HTTP Servers for the Administration Server and the WLS_BAMn Managed Servers
5.15.18
Validating Access through Oracle HTTP Server
5.15.19
Configuring Server Migration for the WLS_BAM Servers
5.15.19.1
Setting Up the User and Tablespace for the Server Migration Leasing Table
5.15.19.2
Creating a GridLink or Multi Data Source from the Administration Console
5.15.19.3
Edit the Node Manager's Properties File
5.15.19.4
Set Environment and Superuser Privileges for the wlsifconfig.sh Script
5.15.19.5
Configure Server Migration Targets
5.15.19.6
Test Server Migration
5.15.20
Configuring Clients Connecting to the BAM System
6
Configuring High Availability for Oracle ADF and WebCenter Portal Applications
6.1
Oracle ADF and High Availability Concepts
6.1.1
About 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
WebCenter Portal and High Availability Concepts
6.3.1
WebCenter Portal Components and Single-node Architecture
6.3.2
WebCenter High Availability Architecture and Failover Considerations
6.3.2.1
WebCenter Portal Applications
6.3.2.2
Oracle WebCenter Startup Order
6.3.2.3
Deploying WebCenter Portal Application on a Cluster
6.3.2.4
Analytics Collector Clusters
6.3.2.5
WebCenter Portal State Replication
6.3.2.6
Distributed Java Object Cache
6.3.2.7
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
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 Access
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
6.4.17
Configuring Activity Graph
6.4.18
Configuring Clustering for 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 WebCenter Portal Applications
6.5.1
Configuring a Cluster for WebCenter Portal Applications
6.5.2
Adding More WebCenter Portal Applications 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.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.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 (TAF)
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 Additional Hosts (Scaling Out)
8.3.3.2.4
Registering Oracle Internet Directory with a WebLogic Domain
8.3.4
Configuring a Maximum High Availability Oracle Internet Directory Deployment (Multimaster Replication)
8.3.4.1
Replication Types
8.3.4.2
Setting up Multimaster Replication
8.3.4.2.1
Setting Up LDAP Multimaster Replication
8.3.4.2.2
Adding a Node in LDAP Multimaster Replication
8.3.4.2.3
Deleting a Node in LDAP Multimaster Replication
8.3.4.2.4
Setting Up Oracle Advanced Database Multimaster Replication
8.3.4.2.5
Adding a Node in Oracle Advanced Database Multimaster Replication
8.3.4.2.6
Deleting a Node in Oracle Advanced Database Multimaster Replication
8.3.5
Validating Oracle Internet Directory High Availability
8.3.6
Oracle Internet Directory Failover and Expected Behavior
8.3.6.1
Performing an Oracle Internet Directory Failover
8.3.6.2
Performing an Oracle RAC Failover
8.3.7
Troubleshooting Oracle Internet Directory High Availability
8.3.8
Additional Oracle Internet Directory High Availability Issues
8.3.8.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 Additional Hosts (Scaling Out)
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 Services Manager High Availability
8.5.1
Oracle Directory Services Manager Component Architecture
8.5.1.1
Oracle Directory Services Manager Component Characteristics
8.5.1.1.1
Lifecycle Management
8.5.1.1.2
Oracle Directory Services Manager Log File
8.5.2
Oracle Directory Services Manager High Availability Concepts
8.5.2.1
Oracle Directory Services Manager High Availability Architecture
8.5.2.1.1
Starting and Stopping the Cluster
8.5.2.2
Protection from Failures and Expected Behaviors
8.5.2.2.1
Process Failure
8.5.2.2.2
Expected Client Application Behavior When Failure Occurs
8.5.2.2.3
Expected Dependency Failure
8.5.2.3
Oracle Directory Services Manager Prerequisites
8.5.3
Oracle Directory Services Manager High Availability Configuration Steps
8.5.4
Validating Oracle Directory Services Manager High Availability
8.5.4.1
Performing a WebLogic Server Instance Failover
8.5.4.2
Performing an Oracle RAC Database Failover
8.5.5
Oracle Directory Services Manager Failover and Expected Behavior
8.5.5.1
Using Oracle Directory Services Manager to Validate a Failover of a Managed Server
8.5.5.2
Using Oracle Directory Services Manager to Validate a Failover of an Oracle Internet Directory Instance
8.5.5.3
Using Oracle Directory Services Manager to Validate an Oracle RAC Failover
8.5.6
Troubleshooting Oracle Directory Services Manager
8.5.6.1
Dealing with Error Messages Received After Starting WebLogic Node Manager
8.5.6.2
WebLogic Node Manager Fails to Start
8.5.6.3
Oracle Directory Services Manager Failover Using Oracle HTTP Server is Not Transparent
8.5.6.4
Oracle Directory Services Manager Displays "LDAP Server is down" Message During Oracle Internet Directory Failover
8.5.6.5
Oracle Directory Services Manager Temporarily Loses Its Connection During Oracle RAC Failover
8.5.7
Additional Considerations for Oracle Directory Services Manager High Availability
8.6
Oracle Directory Integration Platform High Availability
8.6.1
Oracle Directory Integration Platform Component Architecture
8.6.1.1
Oracle Directory Integration Platform Component Characteristics
8.6.1.1.1
Runtime Processes
8.6.1.1.2
Process Lifecycle
8.6.1.1.3
Request Flow
8.6.1.1.4
Configuration Artifacts
8.6.1.1.5
External Dependencies
8.6.1.1.6
Oracle Directory Integration Platform Log File
8.6.2
Oracle Directory Integration Platform High Availability Concepts
8.6.2.1
Oracle Directory Integration Platform High Availability Architecture
8.6.2.1.1
Starting and Stopping the Cluster
8.6.2.1.2
Cluster-Wide Configuration Changes
8.6.2.2
Protection from Failures and Expected Behavior
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 Integration Platform Prerequisites
8.6.3
Oracle Directory Integration Platform High Availability Configuration Steps
8.6.3.1
Configuring Oracle Directory Integration Platform on IDMHOST1
8.6.3.2
Configuring Oracle Directory Integration Platform and Oracle Directory Services Manager on IDMHOST2
8.6.3.3
Post-Installation Steps for Oracle Directory Integration Platform and Oracle Directory Services Manager
8.6.3.3.1
Copy the Oracle Directory Integration Platform Configuration from IDMHOST1 to IDMHOST2
8.6.3.3.2
Restart the Managed Server on IDMHOST2 in a Cluster
8.6.3.4
Installing Oracle Fusion Middleware Components on WEBHOST1 and WEBHOST2
8.6.3.4.1
Installing Oracle HTTP Server for the Web Tier
8.6.3.4.2
Upgrading the Oracle HTTP Server Oracle Home to Patch Set 3
8.6.4
Oracle Directory Integration Platform Failover and Expected Behavior
8.6.5
Troubleshooting Oracle Directory Integration Platform High Availability
8.6.5.1
Managed Server Log File Exceptions Received for Oracle Directory Integration Platform During an Oracle RAC Failover
8.6.5.2
Error Messages Received After Starting WebLogic Node Manager
8.6.5.3
If WebLogic Node Manager Fails to Start
8.6.5.4
Configuration Changes Do Not Automatically Propagate to All Oracle Directory Integration Platform Instances in a Highly Available Topology
8.6.5.5
Operation Cannot Be Completed for Unknown Errors Message
8.7
Starting and Stopping Components
9
Configuring High Availability for Identity and Access Management Components
9.1
Oracle Identity Manager High Availability
9.1.1
Oracle Identity Manager Component Architecture
9.1.1.1
Oracle Identity Manager Component Characteristics
9.1.1.2
Runtime Processes
9.1.1.3
Component and Process Lifecycle
9.1.1.4
Starting and Stopping Oracle Identity Manager
9.1.1.5
Configuration Artifacts
9.1.1.6
External Dependencies
9.1.1.7
Oracle Identity Manager Log File Locations
9.1.2
Oracle Identity Manager High Availability Concepts
9.1.2.1
Oracle Identity Manager High Availability Architecture
9.1.2.2
Starting and Stopping the Oracle Identity Manager Cluster
9.1.2.3
Cluster-Wide Configuration Changes
9.1.2.4
Considerations for Synchronizing with LDAP
9.1.3
Oracle Identity Manager High Availability Configuration Steps
9.1.3.1
Prerequisites for Oracle Identity Manager Configuration
9.1.3.1.1
Running RCU to Create the OIM Schemas in a Database
9.1.3.1.2
Installing Oracle WebLogic Server
9.1.3.1.3
Installing the Oracle SOA Suite on OIMHOST1 and OIMHOST2
9.1.3.1.4
Installing the Oracle Identity Manager on OIMHOST1 and OIMHOST2
9.1.3.2
Creating and Configuring the WebLogic Domain for OIM and SOA on OIMHOST1
9.1.3.3
Configuring the Database Security Store for the Domain
9.1.3.4
Post-Installation Steps on OIMHOST1
9.1.3.4.1
Update Node Manager on OIMHOST1
9.1.3.4.2
Start Node Manager on OIMHOST1
9.1.3.4.3
Start the Administration Server on OIMHOST1
9.1.3.5
Configuring Oracle Identity Manager on OIMHOST1
9.1.3.5.1
Prerequisites for Configuring Oracle Identity Manager
9.1.3.5.2
Running the Oracle Identity Management Configuration Wizard
9.1.3.6
Post-Configuration Steps for the Managed Servers
9.1.3.6.1
Updating the Coherence Configuration for the Coherence Cluster
9.1.3.6.2
Start the WLS_SOA1 and WLS_OIM1 Managed Servers on OIMHOST1
9.1.3.7
Validate the Oracle Identity Manager Instance on OIMHOST1
9.1.3.8
Propagating Oracle Identity Manager to OIMHOST2
9.1.3.9
Post-Installation Steps on OIMHOST2
9.1.3.9.1
Update Node Manager on OIMHOST2
9.1.3.9.2
Start Node Manager on OIMHOST2
9.1.3.9.3
Start the WLS_SOA2 and WLS_OIM2 Managed Servers on OIMHOST2
9.1.3.10
Validate the Oracle Identity Manager Instance on OIMHOST2
9.1.3.11
Updating SOA Server Default Composite
9.1.3.12
Configuring Oracle Internet Directory using the LDAP Configuration Post-setup Script
9.1.3.13
Configuring Server Migration for the OIM and SOA Managed Servers
9.1.3.13.1
Setting Up a User and Tablespace for the Server Migration Leasing Table
9.1.3.13.2
Creating a Multi Data Source Using the Oracle WebLogic Administration Console
9.1.3.13.3
Editing Node Manager's Properties File
9.1.3.13.4
Setting Environment and Superuser Privileges for the wlsifconfig.sh Script
9.1.3.13.5
Configuring Server MigrationTargets
9.1.3.13.6
Testing the Server Migration
9.1.3.14
Configuring a Shared JMS Persistence Store
9.1.3.15
Configuring a Default Persistence Store for Transaction Recovery
9.1.3.16
Install Oracle HTTP Server on WEBHOST1 and WEBHOST2
9.1.3.17
Configuring Oracle Identity Manager to Work with the Web Tier
9.1.3.17.1
Prerequisites
9.1.3.17.2
Configuring Oracle HTTP Servers to Front End the OIM and SOA Managed Servers
9.1.3.18
Validate the Oracle HTTP Server Configuration
9.1.3.19
Oracle Identity Manager Failover and Expected Behavior
9.1.3.20
Troubleshooting Oracle Identity Manager High Availability
9.1.3.21
Scaling Up and Scaling Out the Oracle Identity Manager Topology
9.1.3.21.1
Scaling Up Oracle Identity Manager
9.1.3.21.2
Scaling Out Oracle Identity Manager
9.2
Oracle Access Management Access Manager High Availability
9.2.1
Access Manager Component Architecture
9.2.1.1
Access Manager Component Characteristics
9.2.1.1.1
Access Manager State Information
9.2.1.1.2
Access Manager Request Flow
9.2.1.1.3
Access Manager Process Lifecycle
9.2.1.1.4
Access Manager Configuration Artifacts
9.2.1.1.5
Access Manager External Dependencies
9.2.1.1.6
Access Manager Log File Location
9.2.2
Access Manager High Availability Concepts
9.2.2.1
Access Manager High Availability Architecture
9.2.2.1.1
Starting and Stopping the Cluster
9.2.2.1.2
Cluster-Wide Configuration Changes
9.2.2.2
Protection from Failures and Expected Behaviors
9.2.2.2.1
WebLogic Server Crash
9.2.2.2.2
Node Failure
9.2.2.2.3
Database Failure
9.2.3
Access Manager High Availability Configuration Steps
9.2.3.1
Prerequisites for Access Manager Configuration
9.2.3.2
Running the Repository Creation Utility to Create the Database Schemas
9.2.3.3
Installing Oracle WebLogic Server
9.2.3.4
Installing and Configuring the Access Manager Application Tier
9.2.3.4.1
Install Oracle Fusion Middleware for Identity Management
9.2.3.4.2
Configure Oracle Identity Management on OAMHOST1
9.2.3.5
Configuring the Database Security Store
9.2.3.6
Creating boot.properties for the Administration Server on OAMHOST1
9.2.3.7
Starting OAMHOST1
9.2.3.7.1
Create the Node Manager Properties File on OAMHOST1
9.2.3.7.2
Start Node Manager
9.2.3.7.3
Start Access Manager on OAMHOST1
9.2.3.8
Validating OAMHOST1
9.2.3.9
Configuring OAM on OAMHOST2
9.2.3.10
Starting OAMHOST2
9.2.3.10.1
Create the Node Manager Properties File on OAMHOST2
9.2.3.10.2
Start Node Manager
9.2.3.10.3
Start Access Manager on OAMHOST2
9.2.3.11
Validating OAMHOST2
9.2.3.12
Configure Access Manager to Work with Oracle HTTP Server
9.2.3.12.1
Update Oracle HTTP Server Configuration
9.2.3.12.2
Restart Oracle HTTP Server
9.2.3.12.3
Make OAM Server Aware of the Load Balancer
9.2.3.13
Configuring Access Manager to use an External LDAP Store
9.2.3.13.1
Extending Directory Schema for Access Manager
9.2.3.13.2
Create Users and Groups in LDAP
9.2.3.13.3
Create a User Identity Store
9.2.3.13.4
Set LDAP to System and Default Store
9.2.3.13.5
Set Authentication to Use External LDAP
9.2.3.14
Validating the Access Manager Configuration
9.2.3.15
Configuring Oracle Coherence to Keep Configuration Files in Sync
9.2.3.16
Scaling Up and Scaling Out the Access Manager Topology
9.2.3.16.1
Scaling Up Access Manager
9.2.3.16.2
Scaling Out Access Manager
9.3
Oracle Adaptive Access Manager High Availability
9.3.1
Oracle Adaptive Access Manager Component Architecture
9.3.1.1
Oracle Adaptive Access Manager Component Characteristics
9.3.1.1.1
Oracle Adaptive Access Manager State Information
9.3.1.1.2
Oracle Adaptive Access Manager Runtime Processes
9.3.1.1.3
Oracle Adaptive Access Manager Process Lifecycle
9.3.1.1.4
Oracle Adaptive Access Manager Configuration Artifacts
9.3.1.1.5
Oracle Adaptive Access Manager Deployment Artifacts
9.3.1.1.6
Oracle Adaptive Access Manager External Dependencies
9.3.1.1.7
Oracle Adaptive Access Manager Log File Location
9.3.2
Oracle Adaptive Access Manager High Availability Concepts
9.3.2.1
Oracle Adaptive Access Manager High Availability Architecture
9.3.2.1.1
Starting and Stopping the Cluster
9.3.2.1.2
Cluster-Wide Configuration Changes
9.3.2.2
Protection from Failures and Expected Behaviors
9.3.3
Oracle Adaptive Access Manager High Availability Configuration Steps
9.3.3.1
Prerequisites for Oracle Adaptive Access Manager Configuration
9.3.3.2
Run the Repository Creation Utility to Create the OAAM Schemas in a Database
9.3.3.3
Installing Oracle WebLogic Server
9.3.3.4
Install and Configure the Oracle Adaptive Access Manager Application Tier
9.3.3.5
Configuring the Database Security Store for the Domain
9.3.3.6
Creating boot.properties for the Administration Server on OAAMHOST1
9.3.3.7
Create the Oracle Adaptive Access Manager Administration User
9.3.3.8
Start OAAMHOST1
9.3.3.8.1
Create the Node Manager Properties File on OAAMHOST1
9.3.3.8.2
Start Node Manager
9.3.3.8.3
Start Oracle Adaptive Access Manager on OAAMHOST1
9.3.3.9
Validating OAAMHOST1
9.3.3.10
Configure Oracle Adaptive Access Manager on OAAMHOST2
9.3.3.11
Start OAAMHOST2
9.3.3.11.1
Create the Node Manager Properties File on OAAMHOST2
9.3.3.11.2
Start Node Manager
9.3.3.11.3
Start Oracle Adaptive Access Manager on OAAMHOST2
9.3.3.12
Validating OAAMHOST2
9.3.3.13
Configure Oracle Adaptive Access Manager to Work with Oracle HTTP Server
9.3.3.13.1
Update Oracle HTTP Server Configuration
9.3.3.13.2
Restart Oracle HTTP Server
9.3.3.13.3
Change Host Assertion in WebLogic
9.3.3.14
Validating the Oracle Adaptive Access Manager Configuration
9.3.3.15
Scaling Up and Scaling Out the Oracle Adaptive Access Manager Topology
9.3.3.15.1
Scaling Up Oracle Adaptive Access Manager
9.3.3.15.2
Scaling Out Oracle Adaptive Access Manager
9.4
Oracle Access Management Security Token Service High Availability
9.4.1
Security Token Service High Availability Architecture
9.4.1.1
Clients and Client Connections
9.4.1.2
Cluster Wide Configuration Changes
9.4.2
Security Token Service Component Characteristics
9.4.2.1
Security Token Service Component Lifecycle
9.4.2.2
Runtime Processes
9.4.2.2.1
Starting and Stopping Security Token Service
9.4.2.2.2
J2EE Components and Subcomponents
9.4.2.2.3
Session State Information
9.4.2.3
Configuration Artifacts
9.4.2.4
External Dependencies
9.4.3
Security Token Service High Availability Configuration Steps
9.4.4
Validating Security Token Service High Availability
9.4.5
Security Token Service Failover and Expected Behavior
9.4.5.1
Death Detection and Restart
9.4.5.2
Node Failure
9.4.6
Disabling and Enabling Security Token Service
9.4.7
Troubleshooting Security Token Service
9.4.8
Log File Location
9.4.9
Additional Considerations
9.5
Oracle Access Management Identity Federation High Availability
9.5.1
Identity Federation Component Architecture
9.5.1.1
Identity Federation Component Characteristics
9.5.1.1.1
Runtime Processes
9.5.1.1.2
Process Lifecycle
9.5.1.1.3
Request Flow
9.5.1.1.4
Configuration Artifacts
9.5.1.1.5
External Dependencies
9.5.1.1.6
Identity Federation Log File Location
9.5.2
Identity Federation High Availability Concepts
9.5.2.1
Identity Federation High Availability Architecture
9.5.2.1.1
Starting and Stopping the Cluster
9.5.2.1.2
Cluster-Wide Configuration Changes
9.5.2.2
Identity Federation Prerequisites
9.5.3
Identity Federation High Availability Configuration
9.5.3.1
Setting the Hostname and Port
9.5.3.2
Changing the ProviderID Value
9.5.3.3
Tuning Identity Federation Parameters
9.5.4
Identity Federation Failover and Expected Behavior
9.5.5
Troubleshooting Identity Federation High Availability
9.6
Oracle Entitlements Server High Availability
9.6.1
Oracle Entitlements Server High Availability Concepts
9.6.1.1
Oracle Entitlements Server High Availability Architecture
9.6.1.1.1
Oracle Entitlements Server Administration Server High Availability
9.6.1.1.2
Security Module (OES Client)/Policy Information Point High Availability
9.6.1.1.3
Security Module in Proxy Mode Working Against Web Service / RMI Security Module in Controlled-Push Mode High Availability
9.6.1.1.4
Security Module in Proxy Mode Working Against Web Service / RMI Security Module in Controlled Pull Mode High Availability
9.6.1.1.5
Oracle Entitlements Server WebLogic Server Security Module High Availability
9.6.1.2
Oracle Entitlements Server Security Module High Availability
9.6.1.3
Load Balancing
9.6.1.4
Failover Considerations
9.6.1.5
Protection from Failures and Expected Behaviors
9.6.1.5.1
Expected Client Application Behavior When Failure Occurs
9.6.1.5.2
Node failure
9.6.1.5.3
Database failure
9.6.1.6
Starting and Stopping the Oracle Entitlements Server Cluster
9.6.1.7
Cluster-Wide Configuration Changes
9.6.1.8
Considerations for Synchronizing with LDAP
9.6.2
Configuring Oracle Entitlements Server High Availability
9.6.2.1
Prerequisites for Oracle Entitlements Server Configuration
9.6.2.2
Configure Weblogic Domain for OES Administration Server on OESHOST1
9.6.2.3
Post-Configuration and Verification
9.6.2.3.1
Starting Node Manager
9.6.2.3.2
Validating the WebLogic Administration Server
9.6.2.3.3
Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server
9.6.2.3.4
Propagate Changes to Remote Server
9.6.2.3.5
Start Node Manager on Remote Hosts
9.6.2.3.6
Stop and Start the WebLogic Administration Server and start oes_server1 and oes_server2
9.6.2.4
Configure OES Security Module in Controlled-push Mode with Oracle Entitlements Server Administration Server High Availability
9.6.2.5
Configure Oracle Entitlements Server Security Module in Proxy Mode with PDP High Availability
9.6.2.6
Configure Oracle Entitlements Server Policy Information Point with High Availability
9.6.2.7
Configuring Oracle Entitlements Server Web Service Security Module on WebLogic High Availability
9.6.2.8
Configuring Oracle Entitlements Server WebLogic Security Module High Availability
9.6.2.9
Using RAC Datasource for Security Module in Controlled-pull Mode and Non-controlled Mode
9.6.2.10
Configuring Oracle Entitlements Server to Work with the Web Tier
9.6.2.10.1
Prerequisites
9.6.2.10.2
Configuring Oracle HTTP Servers to Front End the OES Managed Servers
9.6.2.10.3
Validate the Oracle HTTP Server Configuration
9.7
Oracle Access Management Mobile and Social High Availability
9.7.1
Oracle Access Management Mobile and Social Component Architecture
9.7.1.1
Session State Information
9.7.1.2
Component Lifecycle
9.7.1.3
Component Configuration Artifacts
9.7.1.4
Mobile and Social Deployment Artifacts
9.7.2
Mobile and Social Component Characteristics
9.7.3
Mobile and Social High Availability Concepts
9.7.3.1
Mobile and Social High Availability Architecture
9.7.3.2
Mobile and Social High Availability and Node Failover
9.7.3.2.1
Load Balancing Requirements and Characteristics
9.7.3.2.2
Session State Replication and Failover
9.7.3.2.3
Client Application Startup
9.7.3.2.4
Death Detection / Restart
9.7.4
Configuring Mobile and Social High Availability
9.8
Oracle Privileged Account Manager High Availability
9.8.1
Oracle Privileged Account Manager Component Architecture
9.8.1.1
Runtime Processes
9.8.1.2
Process Lifecycle
9.8.1.3
Session State
9.8.1.4
External Dependencies
9.8.1.5
Deployment Artifacts
9.8.1.6
Log File Locations
9.8.2
Oracle Privileged Account Manager High Availability Concepts
9.8.3
Oracle Privileged Account Manager High Availability Architecture
9.8.3.1
Starting and Stopping the Cluster
9.8.4
Oracle Privileged Account Manager High Availability and Node Failure
9.8.5
Oracle Privileged Account Manager High Availability Configuration
9.8.5.1
Appropriate Development Environment
9.8.5.2
Components Deployed
9.8.5.3
Dependencies
9.8.5.4
High Availability Configuration Procedure
9.8.5.4.1
Configuring Oracle Identity and Access Management on OPAMHOST1
9.8.5.4.2
Configuring the Database Security Store
9.8.5.4.3
Starting Administration Server on OPAMHOST1
9.8.5.4.4
Starting OPAMHOST1
9.8.5.4.5
Starting Oracle Privileged Account Manager on OPAMHOST1
9.8.5.4.6
Configuring OPAM on OPAMHOST2
9.8.5.4.7
Starting OPAMHOST2
9.8.5.5
OHS Load Balancer Configuration
9.8.5.5.1
Configure SSL
9.8.5.5.2
Update the Oracle HTTP Server Configuration
9.8.5.5.3
Restart the Oracle HTTP Server
9.9
Oracle Identity Navigator High Availability
9.9.1
Update the Oracle HTTP Server Configuration
9.9.2
Restart the Oracle HTTP Server
9.10
Oracle Unified Directory High Availability
10
Configuring High Availability for Web Tier Components
10.1
About the Web Tier
10.2
Oracle HTTP Server and High Availability Concepts
10.2.1
Oracle HTTP Server Single-Instance Characteristics
10.2.1.1
Oracle HTTP Server and Oracle WebLogic Server
10.2.1.2
Oracle HTTP Server External Dependencies
10.2.2
Oracle HTTP Server Startup and Shutdown Lifecycle
10.2.3
Starting and Stopping Oracle HTTP Server
10.2.3.1
About the PID File
10.2.3.2
Starting and Stopping Oracle HTTP Server Using Oracle Fusion Middleware Control
10.2.3.3
Starting and Stopping Oracle HTTP Server Using opmnctl
10.2.4
Oracle HTTP Server Configuration Artifacts
10.2.5
Oracle HTTP Server Log File Locations
10.2.6
Oracle HTTP Server High Availability Architecture and Failover Considerations
10.2.7
Oracle HTTP Server Protection from Failures and Expected Behaviors
10.2.8
Oracle HTTP Server Cluster-Wide Configuration Changes
10.2.9
Configuring Oracle HTTP Server for High Availability
10.2.9.1
Prerequisites
10.2.9.1.1
Load Balancer
10.2.9.1.2
Associating Oracle HTTP Server with a WebLogic Domain
10.2.9.2
Install Oracle HTTP Server on WEBHOST1
10.2.9.2.1
Configure Virtual Host(s)
10.2.9.2.2
Configure mod_wl_ohs
10.2.9.2.3
Restart Oracle HTTP Server
10.2.9.2.4
Validate the Oracle HTTP Server Configuration
10.2.9.3
Install Oracle HTTP Server on WEBHOST2
10.2.9.3.1
Configure Virtual Host(s)
10.2.9.3.2
Configure mod_wl_ohs
10.2.9.3.3
Restart Oracle HTTP Server
10.2.9.3.4
Validate the Oracle HTTP Server Configuration
10.3
Oracle Web Cache and High Availability Concepts
10.3.1
Oracle Web Cache Single-Node Characteristics
10.3.1.1
Oracle Web Cache Component Characteristics
10.3.1.2
Oracle Web Cache Process Monitoring
10.3.1.3
Oracle Web Cache Startup and Shutdown Lifecycle
10.3.1.4
Oracle Web Cache Request Flow
10.3.1.5
Oracle Web Cache Configuration Artifacts
10.3.1.6
Log File Locations
10.3.2
Oracle Web Cache High Availability Considerations
10.3.2.1
Oracle Web Cache Stateless Load Balancing
10.3.2.2
Oracle Web Cache Backend Failover
10.3.2.3
Oracle Web Cache Session Binding
10.3.2.4
Oracle Web Cache Cluster-Wide Configuration Changes
10.3.2.5
Oracle Web Cache as a Software Load Balancer
10.3.3
Configuring Oracle Web Cache High Availability Solutions
10.3.3.1
Configure Oracle Web Cache Session Binding
10.3.3.2
Configuring a Cache Cluster
10.3.3.2.1
Configuration Prerequisites
10.3.3.2.2
About Failover Threshold and Capacity Settings
10.3.3.2.3
Task 1: Add Caches to the Cluster and Configure Properties
10.3.3.2.4
Task 2: Enable Tracking of Session Binding
10.3.3.2.5
Task 3: Synchronize Configuration to Cluster Members
10.3.3.2.6
Removing a Cache Member from a Cluster
10.3.3.2.7
Configuring Administration and Invalidation-Only Clusters
10.3.3.3
Configure Oracle Web Cache as a Software Load Balancer
11
Configuring High Availability for WebCenter Content
11.1
Oracle WebCenter Content: Imaging High Availability
11.1.1
Imaging Component Architecture
11.1.1.1
Imaging Component Characteristics
11.1.1.1.1
Imaging State Information
11.1.1.1.2
Imaging Runtime Processes
11.1.1.1.3
Imaging Process Lifecycle
11.1.1.1.4
Imaging Configuration Artifacts
11.1.1.1.5
Imaging External Dependencies
11.1.1.1.6
Imaging Log File Location
11.1.2
Imaging High Availability Concepts
11.1.2.1
Imaging 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
Protection from Failures and Expected Behaviors
11.1.2.3
Creation of Imaging Artifacts in a Cluster
11.1.2.4
Troubleshooting Imaging
11.2
Oracle WebCenter Content High Availability
11.2.1
Oracle WebCenter Content Component Architecture
11.2.1.1
WebCenter Content Component Characteristics
11.2.1.1.1
WebCenter Content State Information
11.2.1.1.2
WebCenter Content Runtime Processes
11.2.1.1.3
WebCenter Content Process Lifecycle
11.2.1.1.4
WebCenter Content Configuration Artifacts
11.2.1.1.5
WebCenter Content Deployment Artifacts
11.2.1.1.6
WebCenter Content External Dependencies
11.2.1.1.7
WebCenter Content Log File Locations
11.2.2
WebCenter Content High Availability Concepts
11.2.2.1
WebCenter Content High Availability Architecture
11.2.2.1.1
Starting and Stopping the Cluster
11.2.2.1.2
Cluster-Wide Configuration Changes
11.2.2.2
WebCenter Content and Inbound Refinery High Availability Architecture
11.2.2.2.1
Content Server and Inbound Refinery Communication
11.2.2.2.2
Content Server Clusters and Inbound Refinery Instances
11.2.2.2.3
Inbound Refinery Instances and Load Balancers
11.2.2.2.4
Inbound Refinery Availability
11.2.2.3
Records High Availability
11.2.2.4
Protection from Failure and Expected Behaviors
11.2.2.5
Troubleshooting WebCenter Content High Availability
11.3
Oracle WebCenter Content High Availability Configuration Steps
11.3.1
Shared Storage
11.3.2
Configuring the Oracle Database
11.3.3
Installing and Configuring WCCHOST1
11.3.3.1
Installing Oracle WebLogic Server on WCCHOST1
11.3.3.2
Installing Oracle WebCenter Content on WCCHOST1
11.3.3.3
Create a High Availability Domain
11.3.3.4
Start the Administration Server and the Managed Servers on WCCHOST1
11.3.3.5
Disabling Host Name Verification for the Administration Server and the Managed Servers for WCCHOST1 and WCCHOST2
11.3.3.6
Configure the WLS_UCM1 Managed Server
11.3.3.7
Configure the WLS_URM1 Managed Server
11.3.4
Installing and Configuring WEBHOST1
11.3.4.1
Installing Oracle HTTP Server on WEBHOST1
11.3.4.2
Configuring Oracle HTTP Server on WEBHOST1
11.3.5
Configuring the Load Balancer
11.3.6
Installing and Configuring WCCHOST2
11.3.6.1
Installing Oracle WebLogic Server on WCCHOST2
11.3.6.2
Installing WCC on WCCHOST2
11.3.6.3
Using pack and unpack to Join the Domain on WCCHOST1
11.3.6.4
Start Node Manager and the WLS_UCM2 Server on WCCHOST2
11.3.6.5
Start the Managed Servers on WCCHOST2
11.3.6.6
Configure the WLS_UCM2 Managed Server
11.3.6.7
Configure the WLS_URM2 Managed Server
11.3.7
Installing and Configuring WEBHOST2
11.3.7.1
Installing Oracle HTTP Server on WEBHOST2
11.3.7.2
Configuring Oracle HTTP Server on WEBHOST2
11.3.8
Configuring the Imaging Managed Servers
11.3.8.1
Configuring a JMS Persistence Store for Imaging JMS
11.3.8.2
Configuring a Default Persistence Store for Transaction Recovery
11.3.8.3
Configuring Imaging with WebCenter Content
11.3.8.3.1
Enabling Imaging in UCM
11.3.8.3.2
Upgrading the Default File Store
11.3.8.3.3
Adding the Imaging Server Listen Addresses to the List of Allowed Hosts in UCM
11.3.8.3.4
Creating a Connection to the UCM System
11.3.8.4
Configuring BPEL CSF Credentials
11.3.8.5
Configuring the BPEL Connection
11.3.8.6
Setting the Front End HTTP Host and Port
11.3.8.7
Configuring Server Migration for Imaging Instances
11.3.8.7.1
About Configuring Server Migration
11.3.8.7.2
Creating a GridLink or Multi Data Source Using the Oracle WebLogic Administration Console
11.3.8.7.3
Testing the Server Migration
11.3.9
Configuration of Inbound Refinery Instances
11.3.9.1
Inbound Refinery and Inbound Refinery Cluster Concepts
11.3.9.2
Content Server and Inbound Refinery Configuration
11.3.9.3
Inbound Refinery Instances and Oracle HTTP Server
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 Platforms
12.2.5.2
Windows Platform
12.2.6
Transforming an Oracle Database
12.2.6.1
Database Instance Platform-Specific Considerations
12.3
Oracle Fusion Middleware 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
Using Oracle Cluster Ready Services
13.1
Introduction to Oracle Clusterware
13.2
Cluster Ready Services and Oracle Fusion Middleware
13.3
Installing and Configuring Oracle Clusterware with CRS
13.3.1
Upgrading Older Versions of ASCRS to the Current ASCRS Version
13.3.2
Installing ASCRS
13.3.3
Configuring ASCRS with Oracle Fusion Middleware
13.4
Using ASCRS to Manage Resources
13.4.1
Creating CRS Managed Resources
13.4.1.1
Creating a Virtual IP Resource
13.4.1.2
Creating a Shared Disk Resource
13.4.1.3
Creating an Oracle Database Listener Resource
13.4.1.4
Creating an Oracle Database Resource
13.4.1.5
Creating a Middleware Resource
13.4.1.5.1
Creating a Resource for OPMN Managed Components
13.4.1.5.2
Creating a Resource for WebLogic Servers
13.4.2
Updating Resources
13.4.3
Starting Up Resources
13.4.4
Shutting Down Resources
13.4.5
Resource Switchover
13.4.6
Deleting Resources
13.4.7
Checking Resource Status
13.4.8
Configuring and Using Health Monitors
13.5
Example Topologies
13.6
Troubleshooting Oracle CRS
13.6.1
OPMN Resource Depends on a Virtual IP Resource
13.6.2
ASCRS Logging
14
Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer
14.1
Overview of Oracle Portal, Forms, Reports, and Discoverer
14.1.1
Oracle Portal, Forms, Reports, and Discoverer Architecture
14.1.2
Common Log Files
14.1.3
Common Component Failures and Expected Behaviors
14.1.3.1
Oracle Web Cache and Oracle HTTP Server Process Failures
14.1.3.2
Common Component Node Failures
14.1.3.3
Common Component WebLogic Managed Server Failures
14.1.3.4
Common Component Database Failures
14.1.4
Oracle Portal, Forms, Reports, and Discoverer Cluster-Wide Configuration Changes
14.1.5
Common Component Log File Information
14.2
Oracle Portal and High Availability Concepts
14.2.1
Oracle Portal Single-Instance Characteristics
14.2.1.1
Oracle Portal Request Flow
14.2.1.2
Oracle Portal Component Characteristics
14.2.1.3
Oracle Portal Startup and Shutdown of Processes and Lifecycle
14.2.1.4
Oracle Portal Deployment Artifacts
14.2.1.5
Oracle Portal Configuration Information
14.2.1.6
Oracle Portal Logging and Log Configuration
14.2.1.6.1
Oracle Portal Log Files
14.2.1.7
Oracle Portal External Dependencies
14.2.2
Oracle Portal Protection from Failures and Expected Behavior
14.2.2.1
Oracle Portal Process Failures
14.2.2.2
Oracle Portal Node Failures
14.2.2.3
Oracle Portal WebLogic Managed Server Failures
14.2.2.4
Oracle Portal Protection from Database Failures
14.3
Oracle Reports and High Availability Concepts
14.3.1
Oracle Reports Single-Instance Characteristics
14.3.1.1
Oracle Reports State Information
14.3.1.2
Oracle Reports External Dependencies
14.3.1.3
Oracle Reports Specific Configuration Files
14.3.1.4
Oracle Reports Connection Retry
14.3.1.5
Oracle Reports Process Flow
14.3.1.6
Oracle Reports Log Files
14.3.2
Oracle Reports Protection from Failure and Expected Behavior
14.3.2.1
Oracle Reports Process Failures
14.3.2.2
Oracle Reports Node Failures
14.3.2.3
Oracle Reports WebLogic Managed Server Failures
14.3.2.4
Oracle Reports Database Failures
14.4
Oracle Forms and High Availability Concepts
14.4.1
Oracle Forms Single-Instance Component Characteristics
14.4.1.1
Oracle Forms State Information
14.4.1.2
Oracle Forms Database Requirements
14.4.1.3
Oracle Forms Request Flow
14.4.1.4
Oracle Forms Configuration Persistence
14.4.1.5
Oracle Forms Runtime Considerations
14.4.1.6
Oracle Forms Process Flow
14.4.1.7
Oracle Forms Configuration Files
14.4.1.8
Oracle Forms External Dependencies
14.4.1.9
Oracle Forms Log Files
14.4.2
Oracle Forms Protection from Failover and Expected Behavior
14.4.2.1
Oracle Forms N+1 Redundancy
14.4.2.2
Oracle Forms N+M Redundancy
14.4.2.3
Oracle Forms Virtual Machines
14.4.2.4
Oracle Forms Configuration Cloning
14.4.2.5
Oracle Forms Process Failures
14.4.2.6
Oracle Forms Node Failures
14.4.2.7
Oracle Forms WebLogic Managed Server Failures
14.4.2.8
Oracle Forms Database Failures
14.5
Oracle Discoverer and High Availability Concepts
14.5.1
Oracle Discoverer Single-Instance Characteristics
14.5.1.1
Oracle Discoverer Runtime Considerations
14.5.1.2
Oracle Discoverer Viewer and Web Cache
14.5.1.3
Oracle Discoverer Configuration Considerations
14.5.1.4
Oracle Discoverer Deployment Considerations
14.5.1.5
Oracle Discoverer Log File Locations
14.5.1.6
Discoverer Log Files
14.5.2
Oracle Discoverer Protection from Failures and Expected Behavior
14.5.2.1
Preference Server Failover
14.5.2.2
Session State Replication and Failover
14.5.2.3
Performance Recommendation
14.5.2.4
Propagation of Configuration Changes Across the Cluster
14.5.2.5
Cluster-Wide Application Deployment
14.5.2.6
Online Application Deployment
14.5.2.7
Oracle Discoverer Process Failures
14.5.2.8
Oracle Discoverer Node Failures
14.5.2.9
Oracle Discoverer WebLogic Managed Server Failures
14.5.2.10
Oracle Discoverer Database Failures
14.6
Configuring Oracle Portal, Forms, Reports, and Discoverer for High Availability
14.6.1
Prerequisites
14.6.1.1
Dependencies
14.6.1.2
Network Requirements
14.6.1.2.1
Load Balancer
14.6.1.2.2
Load Balancer Configuration - Virtual Server Names and Ports
14.6.1.3
Databases
14.6.1.4
Shared Directories
14.6.1.5
Managed Port Numbers
14.6.1.6
Site Names
14.6.2
Assumptions
14.6.2.1
Ports
14.6.3
Creating the Metadata Repository
14.6.3.1
Install the Repository Creation Utility (RCU)
14.6.3.2
Run Repository Creation Utility
14.6.4
Install and Configure Application Tier on APPHOST1
14.6.4.1
Install Oracle WebLogic Server
14.6.4.2
Install Oracle Portal, Forms, Reports, and Discoverer
14.6.4.3
Configure Oracle Portal, Forms, Reports, and Discoverer Software
14.6.4.4
Validation
14.6.4.5
Generic Configuration
14.6.4.5.1
Set Admin Server Listen Address
14.6.4.5.2
Configure Virtual Hosts
14.6.4.5.3
Create boot.properties File
14.6.4.5.4
Configure sqlnet.ora
14.6.4.5.5
Configure Web Cache
14.6.4.5.6
Change the Web Cache Passwords
14.6.4.5.7
Restart Web Tier (Oracle HTTP Server and Web Cache)
14.6.4.5.8
Register with Single Sign-On Server
14.6.4.5.9
Enabling the WebLogic Plug-in
14.6.4.5.10
Change Host Assertion in WebLogic
14.6.4.6
Configure Oracle Portal for High Availability
14.6.4.6.1
Rewire Portal Repository
14.6.4.6.2
Configure Parallel Page Engine Loop-Back with Load Balancer
14.6.4.6.3
Database Wallets and Portal
14.6.4.6.4
Restart All Components
14.6.4.6.5
Post-installation Step for Portal Installation with Oracle RAC
14.6.4.6.6
Validate Configuration
14.6.4.7
Configure Oracle Forms for High Availability
14.6.4.7.1
Create TNSNAMES Entries for Customer Databases
14.6.4.7.2
Restart WLS_FORMS
14.6.4.7.3
Validate Configuration
14.6.4.8
Configure Oracle Reports for High Availability
14.6.4.8.1
Create Reports Queue in Database
14.6.4.8.2
Create a TNSNAMES Entry for Reports Queue
14.6.4.8.3
Create a Security Key for the Reports Queue
14.6.4.8.4
Configure the Database Job Repository for In-Process Reports Servers
14.6.4.8.5
Configure the Reports Server to Access Shared Output Directory
14.6.4.8.6
Restart WLS_REPORTS
14.6.4.8.7
Validate Configuration
14.6.4.9
Configure Oracle Discoverer for High Availability
14.6.4.9.1
Create TNSNAMES Entries for Customer Databases
14.6.4.9.2
Update configuration.xml
14.6.4.9.3
Discoverer Viewer and Web Cache
14.6.4.9.4
Enable Single Sign On
14.6.4.9.5
Restart All Components
14.6.4.9.6
Validate Configuration
14.6.5
Install and Configure Application Tier on APPHOST2
14.6.5.1
Install Oracle WebLogic Server
14.6.5.2
Install Oracle Portal, Forms, Reports, and Discoverer Software
14.6.5.3
Configure Oracle Portal, Forms, Reports, and Discoverer Software
14.6.5.4
Generic Configuration
14.6.5.4.1
Copy Configuration Information from APPHOST1
14.6.5.4.2
Configure Virtual Hosts
14.6.5.4.3
Update Oracle HTTP Server Configuration to be Cluster Aware
14.6.5.4.4
Change the Web Cache Passwords
14.6.5.4.5
Configure Web Cache
14.6.5.4.6
Restart Web Processes on APPHOST1 and APPHOST2
14.6.5.5
Configure Oracle Portal for High Availability
14.6.5.5.1
Copy Configuration Information from APPHOST1
14.6.5.5.2
Create Portal Directories
14.6.5.5.3
Update Instance Paths
14.6.5.5.4
Restart the Web Processes
14.6.5.5.5
Start WLS_PORTAL1
14.6.5.5.6
Validate the Configuration
14.6.5.5.7
Best Practices
14.6.5.6
Configure Oracle Forms for High Availability
14.6.5.6.1
Create a TNSNAMES entries for Customer Databases
14.6.5.6.2
Copy Forms Configuration Files
14.6.5.6.3
Update default.env
14.6.5.6.4
Restart WLS_FORMS1
14.6.5.6.5
Validate the Configuration
14.6.5.6.6
Best Practices
14.6.5.7
Configure Oracle Reports for High Availability
14.6.5.7.1
Create TNSNAMES Entries for Customer Databases
14.6.5.7.2
Configure the Reports Server to Access Shared Output Directory
14.6.5.7.3
Configure the Database Job Repository for In-process Reports Servers
14.6.5.7.4
Creating an Oracle Reports Server Cluster
14.6.5.7.5
Restart WLS_REPORTS and WLS_REPORTS1
14.6.5.7.6
Validate the Configuration
14.6.5.7.7
Managing Connection Availability for Oracle Reports Services
14.6.5.8
Configure Oracle Discoverer for High Availability
14.6.5.8.1
Create TNSNAMES Entries for Customer Databases
14.6.5.8.2
Copy Discoverer Configuration Files.
14.6.5.8.3
Update configuration.xml
14.6.5.8.4
Changing the Preference Store
14.6.5.8.5
Restart WLS_DISCO and WLS_DISCO1
14.6.5.8.6
Validate the Configuration
14.6.5.8.7
Failover of the Preference Server
14.6.5.8.8
Setting up Discoverer WSRP Portlet Producer in a Clustered Environment
14.6.5.8.9
Best Practices
14.6.6
Scaling Out the Deployment
15
Using HA Power Tools
15.1
Enabling HA Power Tools in the Oracle WebLogic Administration Console
15.2
Configuring Java Object Cache for a Cluster Using HA Power Tools
15.3
Configuring Java Object Cache for Managed Servers Using HA Power Tools
16
Configuring High Availability for Oracle Business Intelligence and EPM
16.1
High Availability for Oracle Business Intelligence Enterprise Edition and Enterprise Performance Management
16.1.1
Oracle BI EE Component Architecture
16.1.1.1
Oracle BI EE Component Characteristics
16.1.1.1.1
Process Lifecycle
16.1.1.1.2
External Dependencies
16.1.1.1.3
Configuration Artifacts
16.1.1.1.4
Deployment Artifacts
16.1.1.1.5
Log File Locations
16.1.2
Oracle BI EE High Availability Concepts
16.1.2.1
Oracle BI EE and EPM High Availability Architecture
16.1.2.1.1
Web Server High Availability Considerations
16.1.2.1.2
Oracle BI Presentation Services Plug-in High Availability Considerations
16.1.2.1.3
Presentation Services High Availability Considerations
16.1.2.1.4
BI Cluster Controller High Availability Considerations
16.1.2.1.5
BI Server High Availability Considerations
16.1.2.1.6
Administration Tool High Availability Considerations
16.1.2.1.7
Oracle BI Scheduler High Availability Considerations
16.1.2.1.8
BI JavaHost High Availability Considerations
16.1.2.2
Shared Files and Directories
16.1.2.2.1
Oracle BI Presentation Catalog Shared Files
16.1.2.2.2
Repository Publishing Directory Shared Files
16.1.2.2.3
Global Cache Shared Files
16.1.2.2.4
Oracle BI Scheduler Scripts Shared Files
16.1.2.3
Starting and Stopping the Cluster
16.1.2.4
Cluster-Wide Configuration Changes
16.1.2.5
Protection From Failures and Expected Behaviors
16.1.2.5.1
Machine Failure
16.1.2.5.2
WebLogic Administration Server Failure
16.1.2.5.3
WebLogic Managed Server Failure
16.1.2.5.4
Oracle BI Scheduler Failure
16.1.2.5.5
Cluster Controller Failure
16.1.2.5.6
Presentation Services Failure
16.1.2.5.7
BI Server Failure
16.1.2.5.8
Troubleshooting Oracle BI EE
16.1.3
Oracle Essbase Component Architecture
16.1.3.1
Oracle Essbase Component Characteristics
16.1.3.1.1
State Information
16.1.3.1.2
Runtime Processes
16.1.3.1.3
Process Lifecycle
16.1.3.1.4
Request Flow
16.1.3.1.5
External Dependencies
16.1.3.1.6
Configuration Artifacts
16.1.3.1.7
Deployment Artifacts
16.1.3.1.8
Log Files
16.1.4
Oracle Essbase High Availability Concepts
16.1.4.1
Oracle Essbase High Availability Architecture
16.1.4.1.1
Shared Files and Directories
16.1.4.1.2
Cluster-Wide Configuration Changes
16.1.4.2
Protection from Failures and Expected Behaviors
16.1.4.3
Troubleshooting
16.1.5
Configuring Oracle Essbase Clustering
16.1.5.1
Prerequisites
16.1.5.2
Configuring a shared ARBORPATH
16.1.5.3
Configuring Secondary Instances of Essbase Agent
16.1.6
Oracle Hyperion Provider Services Component Architecture
16.1.6.1
Oracle Hyperion Provider Services Component Characteristics
16.1.6.1.1
State Information
16.1.6.1.2
Runtime Processes
16.1.6.1.3
Process Lifecycle
16.1.6.1.4
Request Flow
16.1.6.1.5
External Dependencies
16.1.6.1.6
Configuration Artifacts
16.1.6.1.7
Deployment Artifacts
16.1.6.1.8
Log Files
16.1.7
Oracle Hyperion Provider Services High Availability Concepts
16.1.7.1
Oracle Hyperion Provider Services High Availability Architecture
16.1.7.1.1
Hyperion Registry Structure for a Provider Services Cluster
16.1.7.1.2
Cluster-Wide Configuration Changes
16.1.7.1.3
OPMN Essbase Cluster Support
16.1.7.1.4
Essbase Database Clustering by Provider Services
16.1.7.2
Protection from Failures and Expected Behaviors
16.1.8
Oracle EPM Workspace Component Architecture
16.1.8.1
Workspace Component Characteristics
16.1.8.1.1
State Information
16.1.8.1.2
Runtime Processes
16.1.8.1.3
Process Lifecycle
16.1.8.1.4
Request Flow
16.1.8.1.5
External Dependencies
16.1.8.1.6
Configuration Artifacts
16.1.8.1.7
Deployment Artifacts
16.1.8.1.8
Log Files
16.1.9
Oracle EPM Workspace High Availability Concepts
16.1.9.1
Workspace High Availability Architecture
16.1.9.1.1
Shared Files and Directories
16.1.9.1.2
Cluster-Wide Configuration Changes
16.1.9.2
Protection from Failures and Expected Behaviors
16.1.9.3
Troubleshooting
16.1.10
Oracle Hyperion Financial Reporting Component Architecture
16.1.10.1
Oracle Hyperion Financial Reporting Component Characteristics
16.1.10.1.1
State Information
16.1.10.1.2
Runtime Processes
16.1.10.1.3
External Dependencies
16.1.10.1.4
Configuration Artifacts
16.1.10.1.5
Deployment Artifacts
16.1.10.1.6
Log Files
16.1.11
Oracle Hyperion Financial Reporting High Availability Concepts
16.1.11.1
Oracle Hyperion Financial Reporting High Availability Architecture
16.1.11.1.1
Shared Files and Directories
16.1.11.1.2
Cluster-Wide Configuration Changes
16.1.11.2
Protection from Failures and Expected Behaviors
16.1.12
Allocation Manager Component Architecture and Characteristics
16.1.13
Oracle BI EE High Availability Configuration Steps
16.1.13.1
Prerequisite Steps Before Setting Up a High Availability Configuration for Oracle BI Enterprise Edition and BI Publisher
16.1.13.1.1
Database Prerequisites
16.1.13.1.2
VIP and IP Prerequisites
16.1.13.1.3
Shared Storage Prerequisites
16.1.13.1.4
Clock Synchronization
16.1.13.1.5
Installing and Configuring the Database Repository
16.1.13.1.6
Using RCU to Load the Business Intelligence Schemas in the Database
16.1.13.1.7
Configuring Virtual Server Names and Ports for the Load Balancer
16.1.13.1.8
Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
16.1.13.1.9
Validating Oracle HTTP Server
16.1.13.2
Installing Oracle Business Intelligence Enterprise Edition for High Availability
16.1.13.2.1
Installing Oracle WebLogic Server
16.1.13.2.2
Installing Oracle Fusion Middleware for Business Intelligence Enterprise Edition and Oracle BI Publisher
16.1.13.3
Enabling VIP1 in APPHOST1 and VIP2 in APPHOST2
16.1.13.4
Creating a Domain with the Administration Server and the First BI_SERVER1 Managed Server
16.1.13.5
Creating boot.properties for the Administration Server on APPHOST1
16.1.13.6
Starting and Validating the Administration Server on APPHOST1
16.1.13.6.1
Starting the Administration Server on APPHOST1
16.1.13.6.2
Validating the Administration Server
16.1.13.7
Setting the Listen Address for BI_SERVER1 Managed Server
16.1.13.7.1
Updating the Oracle BI Publisher Scheduler Configuration
16.1.13.8
Disabling Host Name Verification for the BI_SERVER1 Managed Server
16.1.13.9
Starting the System in APPHOST1
16.1.13.9.1
Starting Node Manager on APPHOST1
16.1.13.9.2
Starting and Validating the BI_SERVER1 Managed Server
16.1.13.9.3
Starting and Validating the BI EE System Components on APPHOST1
16.1.13.10
Configuring Oracle BI EE
16.1.13.10.1
Setting the Location of the Shared Oracle BI Repository
16.1.13.10.2
Setting the Shared Global Cache for BI Server
16.1.13.10.3
Setting the Scheduler Script Path and Default Script Path
16.1.13.10.4
Setting the Location of the Shared Oracle BI Presentation Catalog
16.1.13.11
Setting Server Configuration Options
16.1.13.12
Scaling Out the BI System on APPHOST2
16.1.13.13
Scaling Out BI System Components
16.1.13.14
Making Singleton Components Active-Passive
16.1.13.15
Setting the Listen Address for the BI_SERVER2 Managed Server
16.1.13.15.1
Updating the Oracle BI Publisher Scheduler Configuration on APPHOST1 and APPHOST2
16.1.13.16
Disabling Host Name Verification for the BI_SERVER2 Managed Server
16.1.13.17
Configuring Oracle BI for Microsoft Office SSO Properties
16.1.13.17.1
Validating Oracle BI for Microsoft Office Configuration
16.1.13.18
Configuring Oracle BI Publisher
16.1.13.18.1
Setting Oracle BI Presentation Services Options
16.1.13.18.2
Setting Scheduler Configuration Options
16.1.13.18.3
Setting the Oracle BI EE Data Source
16.1.13.18.4
Configuring JMS for Oracle BI Publisher
16.1.13.18.5
Configuring a Default Persistence Store for Transaction Recovery
16.1.13.19
Starting the System in APPHOST2
16.1.13.19.1
Starting Node Manager on APPHOST2
16.1.13.19.2
Starting and Validating the BI_SERVER2 Managed Server
16.1.13.19.3
Starting and Validating the Business Intelligence Enterprise Edition System Components
16.1.13.20
Configuring Oracle HTTP Server for the BI_SERVERn Managed Servers
16.1.13.20.1
Validating Access Through Oracle HTTP Server
16.1.13.21
Setting the Frontend HTTP Host and Port
16.1.13.22
Configuring Server Migration for the BI_SERVERn Servers
16.1.13.22.1
Setting Up a User and Tablespace for the Server Migration Leasing Table
16.1.13.22.2
Creating a Multi Data Source Using the Administration Console / Creating a GridLink Data Source
16.1.13.22.3
Editing Node Manager's Properties File
16.1.13.22.4
Setting Environment and Superuser Privileges for the wlsifconfig.sh Script
16.1.13.22.5
Configuring Server Migration Targets
16.1.13.22.6
Testing the Server Migration
16.1.13.23
Scaling Up the Oracle BI EE Topology
16.1.13.24
Scaling Out the Oracle BI EE Topology to a New Node (APPHOST3)
16.2
High Availability for Oracle Business Intelligence Publisher
16.2.1
Oracle BI Publisher Component Architecture
16.2.1.1
Oracle BI Publisher Component Characteristics
16.2.1.1.1
State Information
16.2.1.1.2
Runtime Processes
16.2.1.1.3
Process Lifecycle
16.2.1.1.4
Request Flow
16.2.1.1.5
External Dependencies
16.2.1.1.6
Configuration Artifacts
16.2.1.1.7
Deployment Artifacts
16.2.1.1.8
Log Files
16.2.2
Oracle BI Publisher High Availability Concepts
16.2.2.1
Oracle BI Publisher High Availability Architecture
16.2.2.1.1
Shared Files and Directories
16.2.2.1.2
Cluster-Wide Configuration Changes
16.2.2.2
Protection from Failures and Expected Behaviors
16.2.2.3
Troubleshooting
16.2.3
Oracle BI Publisher High Availability Configuration Steps
16.2.3.1
Preparing the Environment: Prerequisite Steps Before Setting Up an Oracle BI Publisher High Availability Configuration
16.2.3.1.1
Database Prerequisites
16.2.3.1.2
VIP and IP Prerequisites
16.2.3.1.3
Shared Storage Prerequisites
16.2.3.1.4
Clock Synchronization
16.2.3.1.5
Installing and Configuring the Database Repository
16.2.3.1.6
Using RCU to Load the Business Intelligence Schemas in the Database
16.2.3.1.7
Configuring Virtual Server Names and Ports for the Load Balancer
16.2.3.1.8
Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
16.2.3.1.9
Validating Oracle HTTP Server
16.2.3.2
Installing Oracle Fusion Middleware Home
16.2.3.2.1
Installing Oracle WebLogic Server
16.2.3.2.2
Installing Oracle Fusion Middleware for BI Publisher
16.2.3.3
Enabling VIP1 in APPHOST1 and VIP2 in APPHOST2
16.2.3.4
Creating a Domain with the Administration Server and the First BI_SERVER1 Managed Server
16.2.3.5
Creating boot.properties for the Administration Server on APPHOST1
16.2.3.6
Starting and Validating the Administration Server on APPHOST1
16.2.3.6.1
Starting the Administration Server on APPHOST1
16.2.3.6.2
Validating the Administration Server
16.2.3.7
Setting the Listen Address for BI_SERVER1 Managed Server
16.2.3.8
Disabling Host Name Verification for the BI_SERVER1 Managed Server
16.2.3.9
Starting the System in APPHOST1
16.2.3.9.1
Starting Node Manager on APPHOST1
16.2.3.9.2
Starting and Validating the BI_SERVER1 Managed Server
16.2.3.10
Prerequisites for Scaling Out the BI System on APPHOST2
16.2.3.10.1
Setting Server Configuration Options
16.2.3.10.2
Setting Scheduler Configuration Options
16.2.3.10.3
Updating the Oracle BI Publisher Scheduler Configuration
16.2.3.11
Scaling Out the BI System on APPHOST2
16.2.3.12
Setting the Listen Address for the BI_SERVER2 Managed Server
16.2.3.13
Disabling Host Name Verification for the BI_SERVER2 Managed Server
16.2.3.14
Configuring Oracle BI Publisher
16.2.3.14.1
Configuring JMS Persistence Store for BI Publisher
16.2.3.14.2
Configuring a Default Persistence Store for Transaction Recovery
16.2.3.15
Starting the System in APPHOST2
16.2.3.15.1
Starting Node Manager on APPHOST2
16.2.3.15.2
Starting and Validating the BI_SERVER2 Managed Server
16.2.3.16
Configuring Oracle HTTP Server for the BI_SERVERn Managed Servers
16.2.3.17
Validating Access Through Oracle HTTP Server
16.2.3.18
Configuring Server Migration for the BI_SERVERn Servers
16.2.3.19
Scaling Out the Oracle BI Publisher Topology to a New Node (APPHOST3)
16.3
High Availability for Oracle Real-Time Decisions
16.3.1
Oracle RTD Component Architecture
16.3.1.1
Oracle RTD Component Characteristics
16.3.1.1.1
Component Lifecycle
16.3.1.1.2
Process Flow
16.3.1.1.3
External Dependencies
16.3.1.1.4
Configuration Artifacts
16.3.1.1.5
Deployment Artifacts
16.3.1.1.6
Log File Locations
16.3.2
Oracle RTD High Availability Concepts
16.3.2.1
Oracle RTD High Availability Architecture
16.3.2.1.1
Starting and Stopping the Cluster
16.3.2.1.2
Cluster-Wide Configuration Changes
16.3.2.2
Protection from Failures and Expected Behaviors
16.3.2.2.1
Decision Server Failure
16.3.2.2.2
Cluster Coordinator Failure
16.3.2.2.3
Learning Service Failure
16.3.2.2.4
Decision Center Failure
16.3.2.2.5
Batch Manager Failure
16.3.3
Oracle RTD High Availability Configuration Steps
16.3.3.1
Prerequisite Steps Before Setting up an Oracle RTD High Availability Configuration
16.3.3.1.1
Database Prerequisites
16.3.3.1.2
Installing and Configuring the Database Repository
16.3.3.1.3
Using RCU to Load the Business Intelligence Schemas into the Database
16.3.3.1.4
Configuring Virtual Server Names and Ports for the Load Balancer
16.3.3.1.5
Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
16.3.3.1.6
Validating Oracle HTTP Server
16.3.3.2
Installing Oracle Fusion Middleware Home
16.3.3.2.1
Installing Oracle WebLogic Server
16.3.3.2.2
Installing Oracle RTD
16.3.3.3
Enabling VIP1 in APPHOST1 and VIP2 in APPHOST2
16.3.3.4
Creating a Domain with the Administration Server and the First BI_SERVER1 Managed Server
16.3.3.5
Creating boot.properties for the Administration Server on APPHOST1
16.3.3.6
Starting and Validating the Administration Server on APPHOST1
16.3.3.6.1
Starting the Administration Server on APPHOST1
16.3.3.6.2
Validating the Administration Server
16.3.3.7
Setting the Listen Address for BI_SERVER1 Managed Server
16.3.3.8
Disabling Host Name Verification for the BI_SERVER1 Managed Server
16.3.3.9
Starting the System in APPHOST1
16.3.3.9.1
Starting Node Manager on APPHOST1
16.3.3.9.2
Starting and Validating the BI_SERVER1 Managed Server
16.3.3.10
Scaling Out the BI System on APPHOST2
16.3.3.11
Setting the Listen Address for the BI_SERVER2 Managed Server
16.3.3.12
Disabling Host Name Verification for the BI_SERVER2 Managed Server
16.3.3.13
Configuring Oracle RTD
16.3.3.13.1
Configuring RTD Cluster-Specific Properties
16.3.3.14
Starting the System in APPHOST2
16.3.3.14.1
Configuring a Default Persistence Store for Transaction Recovery
16.3.3.14.2
Starting Node Manager on APPHOST2
16.3.3.14.3
Starting and Validating the BI_SERVER2 Managed Server
16.3.3.15
Configuring Oracle HTTP Server for the BI_SERVERn Managed Servers
16.3.3.16
Validating Access Through Oracle HTTP Server
16.3.3.17
Configuring Server Migration for the BI_SERVERn Servers
16.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
ascrsctl Online Help
E.1
start
E.2
stop
E.3
status
E.4
switch
E.5
delete
E.6
create/disk
E.7
update/disk
E.8
create/vip
E.9
update/vip
E.10
create/dblsnr
E.11
update/dblsnr
E.12
create/db
E.13
update/db
E.14
create/as
E.15
update/as
F
Configuring the Distributed Java Object Cache
F.1
Configuring the Java Object Cache
F.2
Running CacheWatcher
G
Configuring Distributed Notifications for MDS
Scripting on this page enhances content navigation, but does not change the content in any way.