Skip Headers
Oracle® Fusion Middleware High Availability Guide
11g Release 1 (11.1.1)

Part Number E10106-11
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
View PDF

Index

A  B  C  D  E  F  H  I  J  K  L  M  N  O  P  R  S  T  U  V  W  X 

A

active-active, 2.3.4
active-active topologies, 1.1.2
active-passive deployment, 2.3.3
active-passive deployments
configuring, 12.2
active-passive topologies, 1.1.2, 12
advantages, 12.1
disadvantages, 12.1
adf-config.xml, 6.1.3.3, 6.1.3.4, 6.3.1.5
Administration Console
redirecting to home page, 6.4.20.4
Administration Server, 2.1.1, 2.1.1.1, 3.11
disabling host name verification, 5.13.7
starting, 5.13.6
starting on OIMHOST1, 8.9.3.3.4
validating, 5.13.6
Administration Server failure, 3.11.1
Apache
version, 11.2.1
Apache HTTP Server, 11.2.1
apachectl, 11.2.3
application failover, 3.4.1
ASCRS, 13
configuring, 13.3.3
installing, 13.3.2
logging, 13.6.2
upgrading older versions, 13.3.1
auditing
configuring the JDBC string for the audit loader, A.2
setting up audit data sources for a RAC database, A.1
setting up multi data sources for a RAC database, A.1
setting up with a RAC database store, A
Authorization Policy Manager
high availability, 8.10
automatic restart, 1.1.2

B

B2B, 5.7
backup and recovery, 1.1.2
boot.properties file
creating for the Administration Server, 5.13.5, 8.3.3.3.2, 8.4.3.2.2, 8.5.3.2, 8.8.3.5, 8.12.3.5, 8.13.3.2, 15.1.3.5, 15.2.3.5, 15.3.3.5

C

cache clusters
authentication, 11.3.2.4
cluster agent, 2.2
cluster configuration, 3.14
cluster objects, 3.5
Cluster Ready Services, 13, 13.2
checking resource status, 13.4.7
creating a shared disk resource, 13.4.1.2
creating a virtual IP resource, 13.4.1.1
creating an Oracle database listener resource, 13.4.1.3
deleting resources, 13.4.6
Example 1 topology, 13.5
Example 2 topology, 13.5
resource switchover, 13.4.5
shutting down resources, 13.4.4
starting up resources, 13.4.3
troubleshooting, 13.6
updating resources, 13.4.2
clustered server instances, 3.8
clustering, 1.1.2
clusters, 2.1.1.2
authentication, 11.3.2.4
clusterware, 2.2
Cold Failover Cluster
destination topologies, 12.4.1
example topologies, 12.3
example topology 1, 12.3.1
example topology 2, 12.3.2
example topology 3, 12.3.3
general requirements, 12.2.1
Single Sign-On re-registration, 12.2.3.14
start topologies, 12.4
terminology for directories and directory environment variables, 12.2.1.1
transforming a custom ADF deployment, 12.2.3.10.6
transforming an Oracle database, 12.2.4
transforming an Oracle Enterprise Content Management Suite, 12.2.3.11
transforming Node Manager, 12.2.2.5
transforming OPMN, 12.2.2.6
transforming Oracle Access Manager, 12.2.3.6.1
transforming Oracle Access Manager clients, 12.2.3.6.2
transforming Oracle Adaptive Access Manager, 12.2.3.7.1
transforming Oracle Adaptive Access Manager clients, 12.2.3.7.2
transforming Oracle BAM, 12.2.3.10.5
transforming Oracle Business Intelligence, 12.2.3.12
transforming Oracle Business Intelligence Publisher, 12.2.3.12.1
transforming Oracle Business Intelligence Publisher clients, 12.2.3.12.1
transforming Oracle Directory Integration Platform and Oracle Directory Services Manager, 12.2.3.3.1
transforming Oracle Directory Integration Platform and Oracle Directory Services Manager clients, 12.2.3.3.2
transforming Oracle Discoverer, 12.2.3.10.3
transforming Oracle Enterprise Manager, 12.2.2.7
transforming Oracle Forms, 12.2.3.10.1
transforming Oracle HTTP Server, 12.2.2.8.1
transforming Oracle Identity Federation, 12.2.3.4.1
transforming Oracle Identity Federation clients, 12.2.3.4.2
transforming Oracle Identity Manager, 12.2.3.8
transforming Oracle Identity Manager clients, 12.2.3.8.2
transforming Oracle Internet Directory, 12.2.3.1.1
transforming Oracle Internet Directory clients, 12.2.3.1.2
transforming Oracle Portal, 12.2.3.10.4
transforming Oracle Portal, Forms, Reports, and Discoverer, 12.2.3.10
transforming Oracle Real-Time Decisions, 12.2.3.12.2
transforming Oracle Real-Time Decisions clients, 12.2.3.12.2
transforming Oracle Reports, 12.2.3.10.2
transforming Oracle SOA Suite, 12.2.3.5
transforming Oracle Virtual Directory, 12.2.3.2.1
transforming Oracle Virtual Directory clients, 12.2.3.2.2
transforming Oracle Web Cache, 12.2.2.8.2
transforming Oracle WebCenter Suite, 12.2.3.9
transforming Oracle WebLogic managed servers, 12.2.2.4
transforming the Administration Server, 12.2.2.3
transforming the Administration Server in an existing domain, 12.4
transforming web tier components and clients, 12.2.2.8
collocated Identity Management components
additional high availability considerations, 8.7.5
architecture, 8.7.1
architecture diagram, 8.7.1
configuring for high availability, 8.7.2.2
failures and expected behaviors, 8.7.3.2
high availability, 8.7
high availability architecture, 8.7.2
high availability architecture diagram, 8.7.2
prerequisites, 8.7.2.1
troubleshooting high availability, 8.7.4
validating high availability, 8.7.3
validation tests for high availability, 8.7.3.1
configuration
targets for server migration, 8.9.3.12.5, 10.3.8.7.6, 15.1.3.21.5
configuration cloning, 14.4.2.4
configuration files
adf-config.xml, 6.3.1.5
connections.xml, 6.3.1.5
configuration management, 2.3.2
configure-joc.py script, F.1
configuring a default persistent store for transaction recovery, 5.13.17
config.xml, 3.14
connections.xml, 6.3.1.5
constrained candidate servers, 3.10.1
creating a SOA domain, 5.13.2.1, 5.13.4, 5.14.2.1
creating CRS managed resources, 13.4.1
CRS, 13
creating a virtual IP resource, 13.4.1.1
creating managed resources, 13.4.1
CRS managed resources, 13.4.1

D

data source, 8.9.3.12.2, 10.3.8.7.3, 15.1.3.21.2
database
configuring for Oracle Fusion Middleware metadata, 8.2.5
database access, 4
database initialization parameters, 5.13.1.7, 5.14.1.7
database mutex, configuring, 5.10.2.2
database prerequisites
Oracle Identity Management high availability, 8.2.2
database repository
configuring, 5.13.1.7
installing, 5.13.1.7
installing and configuring for Oracle Identity Management, 8.2.3
database service
adding to a database, 8.2.5.2
assigning to database instances, 8.2.5.2
creating, 8.2.5.2
starting, 8.2.5.2
death detection, 1.1.2
default persistence store
configuring for Transaction Recovery Service, 5.15.10
deploying applications, 5.13.20
deploying composites, 5.13.8
deployment architecture, 2.3.1
direct implementation, 2.3.4
directory environment, 6.2.1
directory environment variables, 5.13.1.6, 6.4.1.5
disabling
host name verification, 5.13.7
disaster recovery, 1.1.2, 2.3.5
Discussions server
configuration files
DNS server, 11.3.1
domains
system component domains, 2.1.2
WebLogic Server, 2.1.1

E

Enterprise Java Beans, 3.5
environment privileges, 8.9.3.12.4, 10.3.8.7.5, 15.1.3.21.4
etc/services file, 8.3.3.2.1, 8.3.3.2.3, 8.3.3.3.1, 8.3.3.3.3, 8.4.3.1.1, 8.4.3.1.2, 8.4.3.2.1, 8.4.3.2.3, 8.5.3.1, 8.5.3.6, 10.3.4.1, 10.3.7.1

F

failback, 2.2
failover, 1.1.2, 2.2
configuring RAC database to automate Oracle Internet Directory failover, 8.2.5.2
failover and replication, 3.8
file
etc/services, 8.3.3.2.1, 8.3.3.2.3, 8.3.3.3.1, 8.3.3.3.3, 8.4.3.1.1, 8.4.3.1.2, 8.4.3.2.1, 8.4.3.2.3, 8.5.3.1, 8.5.3.6, 10.3.4.1, 10.3.7.1
firewall timeouts, 4.2
Fusion Middleware home
installing, 5.13.2, 5.14.2

H

hardware cluster, 2.2
high availability database access, 4
high availability framework, 2
home page, redirecting to, 6.4.20.4
host name verification
disabling, 5.13.7
hostname
network, 2.2
physical, 2.2
virtual, 2.2
HTTP listener, 11.2.1, 14.4.1.3

I

idle connections, 4.2
Inbound Refinery
and Content Server configuration, 10.3.9.2
and Oracle HTTP Server considerations, 10.3.9.3
cluster concepts, 10.3.9.1
configuration of instances, 10.3.9
database configuration, 10.3.2
high availability configuration steps, 10.3
shared storage, 10.3.1
initialization parameter
changing the value, 8.2.5
integrated high availability, 1.1.2

J

Java components, 2.1
Java EE, 5.2
java object cache, 6.3.2.6
Java Server Pages, 3.5
JCA Adapters, 5.10
JMS, 3.10
JMS persistence store
configuring as shared, 5.13.16
JMS service, 3.10.1
JNDI, 3.4.1, 3.7
JNDI naming service, 3.7
JTA, 3.10

K

key concepts, 2.1

L

LDAP, 3.16
installing and configuring, 5.13.1.4
LDAP configuration post-setup script, 8.9.3.10
LDAP configuration pre-setup script, 8.9.3.4.1
LDAP multimaster replication
adding an Oracle Internet Directory node using Fusion Middleware Control, 9.3.1.1
deleting an Oracle Internet Directory node using Fusion Middleware Control, 9.3.1.2
setting up for Oracle Internet Directory, 9.3
setting up for Oracle Internet Directory using Fusion Middleware Control, 9.3.1
leasing table for server migration, 8.9.3.12.1, 10.3.8.7.2, 15.1.3.21.1
leasing.ddl script, 8.9.3.12.1, 10.3.8.7.2, 15.1.3.21.1
load balancer
configuring for Oracle BAM, 5.15.1.5
configuring for Oracle Identity Federation, 8.13.3.5, 8.13.3.5.2
configuring ports, 8.2.5.4
configuring virtual server names, 8.2.5.4
prerequisites for Oracle SOA Suite, 5.13.1.9
requirements for Oracle Identity Management, 8.2.5.4.1
virtual server names for, 8.2.5.4.1
load balancing, 2.3.2.1, 3.4.3, 3.12

M

managed server
starting, 5.13.10.2, 5.14.11.2
validating, 5.13.10.2, 5.14.11.2
managed servers, 2.1.1, 2.1.1.2
MDS customizations, 6.3.1.5
MDS repositories, 4.1.2.1
MDS repository
configuration files, 6.3.1.5
Middleware home, 2.1.3
migratable servers, 3.9.2.1
migration, 3.4.2
migration server
set environment and superuser privileges, 5.15.19.4
mod_dav, 11.2.1
mod_dms, 11.2.1
mod_onsint, 11.2.1
mod_oradav, 11.2.1
mod_ossl, 11.2.1
mod_osso, 11.2.1
mod_perl, 11.2.1, 11.2.1
mod_plsql, 11.2.1
mod_wl_ohs, 11.2.1
modules, 11.2.1
multi data source, 4.1.2, 4.1.3, 8.9.3.12.2, 10.3.8.7.3, 15.1.3.21.2
multi data source, configuring, 4.1.2.1, 4.1.3
multimaster replication
configuring with Oracle Delegated Administration Services 10.1.4.3 and Oracle Internet Directory 11g, 9.3
configuring with Oracle Single Sign-On 10.1.4.3 and Oracle Internet Directory 11g, 9.3
setting up for Oracle Internet Directory, 9.3

N

netstat command, 8.3.3.2.1, 8.3.3.2.3, 8.3.3.3.1, 8.3.3.3.3, 8.4.3.1.1, 8.4.3.1.2, 8.4.3.2.3, 8.13.3.3
network hostname, 2.2
node failure, 5.2.2.1.2
Node Manager, 2.1.1.3, 3.9.1, 3.9.2.6
properties file, 8.9.3.12.3, 10.3.8.7.4, 15.1.3.21.3
node manager
starting, 5.13.10.1, 5.14.11.1
Node Manager failure, 3.11.2

O

oaam.mycompany.com virtual server, 8.2.5.4.2
oid.mycompany.com virtual server, 8.2.5.4.2
oif.mycompany.com virtual server, 8.2.5.4.2
opmn, 14.1.1
Oracle Access Manager
changing the request cache type, 8.8.3.11
component architecture, 8.8.1
component characteristics, 8.8.1.1
configuration artifacts, 8.8.1.1.4
configuration changes, 8.8.2.1.2
configuring on OAMHOST2, 8.8.3.8
configuring Oracle Coherence, 8.8.3.15
configuring to use an external LDAP store, 8.8.3.13
configuring with a load balancer, 8.8.3.12.3
configuring with Oracle HTTP Server, 8.8.3.12
creating a user identity store, 8.8.3.13.2
creating LDAP users and groups, 8.8.3.13.1
creating the Node Manager properties file, 8.8.3.6.1, 8.8.3.9.1
external dependencies, 8.8.1.1.5
high availability, 8.8
high availability architecture, 8.8.2.1
high availability concepts, 8.8.2
high availability configuration prerequisites, 8.8.3.1
high availability configuration steps, 8.8.3
installing and configuring the application tier, 8.8.3.4
installing Oracle WebLogic Server, 8.8.3.3
log file location, 8.8.1.1.6
process lifecycle, 8.8.1.1.3
protection from failures and expected behaviors, 8.8.2.2
request flow, 8.8.1.1.2
restarting Oracle HTTP Server, 8.8.3.12.2
running RCU to create the OAM schemas, 8.8.3.2
set LDAP as primary authentication store, 8.8.3.13.3
starting, 8.8.3.6.3
starting and stopping the cluster, 8.8.2.1.1
starting Node Manager, 8.8.3.6.2, 8.8.3.9.2
starting on OAMHOST2, 8.8.3.9.3
state information, 8.8.1.1.1
testing server migration, 8.9.3.12.6
updating Oracle HTTP Server configuration, 8.8.3.12.1
validating OAMHOST1, 8.8.3.7
validating OAMHOST2, 8.8.3.10
validating the configuration, 8.8.3.14
Oracle Adaptive Access Manager
changing host assertion in WebLogic, 8.12.3.12.3
cluster-wide configuration changes, 8.12.2.1.2
component architecture, 8.12.1
component characteristics, 8.12.1.1
configuration artifacts, 8.12.1.1.4
configuring on OAMHOST2, 8.12.3.9
configuring to work with Oracle HTTP Server, 8.12.3.12
creating the Administrative user, 8.12.3.6
creating the Node Manager properties file, 8.12.3.7.1, 8.12.3.10.1
deployment artifacts, 8.12.1.1.5
external dependencies, 8.12.1.1.6
high availability, 8.12
high availability architecture, 8.12.2.1
high availability concepts, 8.12.2
high availability configuration prerequisites, 8.12.3.1
high availability configuration steps, 8.12.3
installing and configuring the application tier, 8.12.3.4
installing Oracle WebLogic Server, 8.12.3.3
log file locations, 8.12.1.1.7
process lifecycle, 8.12.1.1.3
protection from failures and expected behaviors, 8.12.2.2
restarting Oracle HTTP Server, 8.12.3.12.2
runtime processes, 8.12.1.1.2
starting and stopping the cluster, 8.12.2.1.1
starting Node Manager, 8.12.3.7.2, 8.12.3.10.2
starting on OAAMHOST1, 8.12.3.7.3
starting on OAAMHOST2, 8.12.3.10.3
state information, 8.12.1.1.1
updating the Oracle HTTP Server configuration, 8.12.3.12.1
using RCU to create OAAM schemas, 8.12.3.2
validating OAAMHOST1, 8.12.3.8
validating OAAMHOST2, 8.12.3.11
validating the configuration, 8.12.3.13
Oracle ADF, 6.1
active data services, 6.1.2.3
business components, 6.1.1.1.1
components, 6.1.1.1
configuring adf-config.xml, 6.1.3.3, 6.1.3.4
configuring application modules, 6.1.3.1
configuring for high availability, 6.1.3, 6.2
configuring high availability for custom applications, 6.5
configuring the application module for Oracle RAC, 6.1.2.4
configuring weblogic.xml, 6.1.3.2
Controller, 6.1.1.1.3
expected behavior for application failover, 6.1.2.2
external dependencies, 6.1.1.3
faces rich client, 6.1.1.1.4
failover and expected behavior, 6.1.2.2
installing Oracle HTTP Server, 6.2.3
log file, 6.1.1.4
Model Layer, 6.1.1.1.2
running RCU, 6.2.2.1
scaling out the topology, 6.2.10.2
scaling up the topology, 6.2.10.1
scope and session state, 6.1.2.1
session failover requirements, 6.1.2.2
single node architecture, 6.1.1.2
terminology for directories and directory environment variable, 6.2.1
troubleshooting high availability, 6.1.4
Oracle Advanced Database multimaster replication
adding an Oracle Internet Directory node, 9.3.2.1
deleting an Oracle Internet Directory node, 9.3.2.2
setting up for Oracle Internet Directory, 9.3, 9.3.2
Oracle B2B, 5.7
cluster-wide configuration changes, 5.7.2.2
component characteristics, 5.7.1.1
configuration artifacts, 5.7.1.4
database failure, 5.7.2.1
deployments in a cluster, 5.7.2.3
document definitions, 5.7.2.4.2
external dependencies, 5.7.1.1
node failure, 5.7.2.1
protection from failures and expected behavior, 5.7.2.1
purge, import, or deployment of metadata, 5.7.2.4.1
request flow, 5.7.1.3
setting connection destination identifiers for B2B queues, 5.13.9
single-instance characteristics, 5.7.1
startup and shutdown lifecycle, 5.7.1.2
troubleshooting active-active configuration, 5.7.2.4
UI failure, 5.7.2.1
Oracle BAM, 5.11
component characteristics, 5.11.1.1
configuration artifacts, 5.11.1.4
configuring a JMS persistence store for BAM UMS, 5.15.9
configuring clients connecting to, 5.15.20
configuring high availability, 5.15
configuring Oracle HTTP Server, 5.15.17
configuring RAC failover, 5.15.15
configuring server migration, 5.15.19
create the WebLogic Server Oracle BAM domain, 5.15.5
creating boot.properties, 5.15.6
creating repository schemas using RCU, 5.15.1.4
database prerequisites, 5.15.1.1
disabling host name verification, 5.15.8
external dependencies, 5.11.1.1
installing, 5.15.3.2
installing Fusion Middleware home, 5.15.3
installing Oracle HTTP Server, 5.15.2
installing Oracle WebLogic Server, 5.15.3.1
load balancer prequisites, 5.15.1.5
node failure, 5.11.2.1
prerequisites for high availability, 5.15.1
process failure, 5.11.2.1
propagating the domain configuration, 5.15.12
protection from failures and expected behavior, 5.11.2.1
real time data streaming clients, 5.11.1.1
single-instance characteristics, 5.11.1
starting the administration server, 5.15.7
starting the managed server, 5.15.14
startup and shutdown of processes, 5.11.1.3
startup/shutdown lifecycle, 5.11.1.2
validating access through Oracle HTTP Server, 5.15.18
VIP and IP prerequisites, 5.15.1.2
web applications, 5.11.1.1
Oracle BI Administration Tool
high availability considerations, 15.1.2.1.6
Oracle BI Cluster Controller
high availability considerations, 15.1.2.1.4
Oracle BI EE
BI Scheduler failure, 15.1.2.5.4
BI Server failure, 15.1.2.5.7
central configuration, 15.1.1.1.3
clock synchronization, 15.1.3.1.4
Cluster Controller failure, 15.1.2.5.5
cluster-wide configuration changes, 15.1.2.4
component characteristics, 15.1.1.1
configuration artifacts, 15.1.1.1.3
configuration of local Java components, 15.1.1.1.3
configuration of local system components, 15.1.1.1.3
configuring, 15.1.3.15
configuring default persistence store for transaction recovery, 15.1.3.17.6
configuring enterprise reporting and publishing, 15.1.3.17
configuring JMS, 15.1.3.17.5
configuring Oracle HTTP Server for the managed servers, 15.1.3.19
configuring server migration for the BI_SERVERn managed servers, 15.1.3.21, 15.3.3.17
creating a domain with Administration Server and first BI managed server, 15.1.3.4
creating a multi data source, 15.1.3.21.2
database prerequisites, 15.1.3.1.1
deployment artifacts, 15.1.1.1.4
disabling host name verification for the BI_SERVER1 managed server, 15.1.3.8
disabling host name verification for the BI_SERVER2 managed server, 15.1.3.14
enabling VIP1 and VIP2, 15.1.3.3, 15.3.3.3
external dependencies, 15.1.1.1.2
high availability, 15.1
high availability architecture, 15.1.2.1
high availability concepts, 15.1.2
installing, 15.1.3.2.2
installing and configuring the database repository, 15.1.3.1.5
installing Oracle BI EE for high availability, 15.1.3.2
installing Oracle HTTP Server, 15.1.3.1.7
installing Oracle HTTP Server on WEBHOST1 and WEBHOST2, 15.1.3.1.8
installing Oracle WebLogic Server, 15.1.3.2.1
load balancers, 15.1.3.1.7
loading the BI schemas into the repository database, 15.1.3.1.6
log file locations, 15.1.1.1.5
making it highly available, 15.1.2
making singleton components active-passive, 15.1.3.12
Presentation Services failure, 15.1.2.5.6
process lifecycle, 15.1.1.1.1
protection from failures and expected behaviors, 15.1.2.5
scaling out the BI EE system components, 15.1.3.11
scaling out the BI system on APPHOST2, 15.1.3.10
scaling out the topology to a new node (APPHOST3), 15.1.3.23
scaling up the topology, 15.1.3.22
setting Oracle BI Presentation Services options, 15.1.3.17.2
setting Oracle BI Publisher server configuration options, 15.1.3.17.1
setting the frontend HTTP host and port, 15.1.3.20
setting the listen address for the BI_SERVER1 managed server, 15.1.3.7
setting the listen address for the BI_SERVER2 managed server, 15.1.3.13
setting the Oracle BI EE data source, 15.1.3.17.4
shared files and directories, 15.1.2.2
shared storage prerequisites, 15.1.3.1.3
single instance architecture, 15.1.1
starting and stopping the cluster, 15.1.2.3
starting and validating BI EE system components, 15.1.3.9.3
starting and validating the BI_SERVER1 managed server, 15.1.3.9.2
starting and validating the BI_SERVER2 managed server, 15.1.3.18.2
starting Node Manager on APPHOST1, 15.1.3.9.1
starting Node Manager on APPHOST2, 15.1.3.18.1
starting the Administration Server on APPHOST1, 15.1.3.6.1
starting the system in APPHOST1, 15.1.3.9
starting the system in APPHOST2, 15.1.3.18
troubleshooting, 15.1.2.5.8
validating access through Oracle HTTP Server, 15.1.3.19.1
validating Oracle HTTP Server, 15.1.3.1.9
validating the Administration Server on APPHOST1, 15.1.3.6.2
verifying server migration, 15.1.3.21.6
VIP and IP prerequisites, 15.1.3.1.2
virtual server names, 15.1.3.1.7
web server high availability considerations, 15.1.2.1.1
WebLogic Administration Server failure, 15.1.2.5.2
WebLogic Managed Server failure, 15.1.2.5.3
Oracle BI global cache
shared files, 15.1.2.2.3
Oracle BI JavaHost
high availability considerations, 15.1.2.1.8
Oracle BI Presentation Catalog
shared files, 15.1.2.2.1
Oracle BI Presentation Server
setting the location, 15.1.3.15.4
Oracle BI Presentation Services
high availability considerations, 15.1.2.1.3
Oracle BI Presentation Services Plug-in
high availability, 15.1.2.1.2
Oracle BI Publisher
clock synchronization, 15.2.3.1.4
cluster-wide configuration changes, 15.2.2.1.2
component architecture, 15.2.1
component characteristics, 15.2.1.1
configuration artifacts, 15.2.1.1.6
configuring, 15.2.3.13
configuring default persistence store for transaction recovery, 15.2.3.13.5, 15.3.3.14.1
configuring JMS persistence store, 15.2.3.13.3
configuring Oracle HTTP Server for the managed servers, 15.2.3.15
creating a domain with Administration Server and first BI managed server, 15.2.3.4
database prerequisites, 15.2.3.1.1
deployment artifacts, 15.2.1.1.7
disabling host name verification for the BI_SERVER1 managed server, 15.2.3.8
disabling host name verification for the BI_SERVER2 managed server, 15.2.3.12
enabling VIP1 and VIP2, 15.2.3.3
external dependencies, 15.2.1.1.5
high availability, 15.2
high availability architecture, 15.2.2.1
high availability concepts, 15.2.2
high availability configuration steps, 15.2.3
installing, 15.2.3.2.2
installing and configuring the database repository, 15.2.3.1.5
installing Oracle HTTP Server, 15.2.3.1.7
installing Oracle HTTP Server on WEBHOST1 and WEBHOST2, 15.2.3.1.8
installing Oracle WebLogic Server, 15.2.3.2.1
installing the Oracle Fusion Middleware home, 15.2.3.2
load balancers, 15.2.3.1.7
loading the BI schemas into the repository database, 15.2.3.1.6
log files, 15.2.1.1.8
prerequisites before setting up a high availability configuration, 15.2.3.1
process lifecycle, 15.2.1.1.3
protection from failures and expected behaviors, 15.2.2.2
request flow, 15.2.1.1.4
runtime processes, 15.2.1.1.2
scaling out the BI system on APPHOST2, 15.2.3.10
scaling out the topology to a new node, 15.2.3.18
setting scheduler configuration options, 15.1.3.17.3, 15.2.3.13.2
setting server configuration options, 15.2.3.13.1
setting the listen address for the BI_SERVER1 managed server, 15.2.3.7
setting the listen address for the BI_SERVER2 managed server, 15.2.3.11
shared files and directories, 15.2.2.1.1
shared storage prerequisites, 15.2.3.1.3
starting and validating the BI_SERVER1 managed server, 15.2.3.9.2
starting and validating the BI_SERVER2 managed server, 15.2.3.14.2
starting Node Manager on APPHOST1, 15.2.3.9.1
starting Node Manager on APPHOST2, 15.2.3.14.1
starting the Administration Server on APPHOST1, 15.2.3.6.1
starting the system in APPHOST1, 15.2.3.9
starting the system in APPHOST2, 15.2.3.14
state information, 15.2.1.1.1
troubleshooting, 15.2.2.3
validating access through Oracle HTTP Server, 15.2.3.16
validating Oracle HTTP Server, 15.2.3.1.9
validating the Administration Server on APPHOST1, 15.2.3.6.2
VIP and IP prerequisites, 15.2.3.1.2
virtual server names, 15.2.3.1.7
Oracle BI repository publishing directory
shared files, 15.1.2.2.2
Oracle BI Scheduler
high availability considerations, 15.1.2.1.7
Oracle BI Scheduler scripts
shared files, 15.1.2.2.4
Oracle BI Server
communication to databases, 15.1.2.1.5
high availability considerations, 15.1.2.1.5
setting the shared global cache, 15.1.3.15.2
Oracle BPEL Process Manager, 5.3
cluster-wide configuration changes, 5.3.2.2
configuration artifacts, 5.3.1.4
protection from failures and expected behavior, 5.3.2.1
request flow and recovery, 5.3.1.3
single-instance characteristics, 5.3.1
startup and shutdown lifecycle, 5.3.1.2
Oracle BPM Suite
analytical infrastructure, 5.4.4.1.1
component characteristics, 5.4.1.1
components and interfaces, 5.4.1.1
configuration artifacts, 5.4.1.4
high availability concepts, 5.4
single instance architecture, 5.4.1
single instance concepts, 5.4.1
startup and shutdown lifecycle, 5.4.1.3
Oracle BPM Suite component interaction, 5.4.1.2
Oracle BPM Suite components
BPM Composer, 5.4.1.1
BPM Infrastructure Libraries, 5.4.1.1
BPM Workspace, 5.4.1.1
BPMN Service Engine, 5.4.1.1
Oracle BPMN service engine
cluster-wide configuration changes, 5.4.2.2.3
configuring for high availability, 5.4.2.2.2
external dependencies, 5.4.2.1.2
high availability, 5.4.2
high availability architecture and failover considerations, 5.4.2.2.1
high availability considerations, 5.4.2.2
log files, 5.4.2.1.4
single instance architecture, 5.4.2.1.1
single instance characteristics, 5.4.2.1
startup and shutdown lifecycle, 5.4.2.1.3
Oracle Business Activity Monitoring, 5.11
Oracle Business Process analytics
cluster-wide configuration changes, 5.4.4.2.3
configuring for high availability, 5.4.4.2.2
external dependencies, 5.4.4.1.2
high availability, 5.4.4
high availability architecture and failover considerations, 5.4.4.2.1
high availability considerations, 5.4.4.2
log file, 5.4.4.1.4
single instance architecture, 5.4.4.1.1
single instance characteristics, 5.4.4.1
startup and shutdown lifecycle, 5.4.4.1.3
Oracle Business Process web applications
cluster-wide configuration changes, 5.4.3.2.3
configuring for high availability, 5.4.3.2.2
external dependencies, 5.4.3.1.2
high avaiilability architecture and failover considerations, 5.4.3.2.1
high availability, 5.4.3
high availability considerations, 5.4.3.2
log files, 5.4.3.1.4
single instance architecture, 5.4.3.1.1
single instance characteristics, 5.4.3.1
startup and shutdown lifecycle, 5.4.3.1.3
Oracle Clusterware
installing and configuring, 13.3
introduction, 13.1
Oracle Coherence
deploying composites, 5.13.8
Oracle Data Integrator
agent startup and shutdown, 7.2.2
clustered deployment, 7.3.1
configuration artifacts, 7.2.5
configuring Coherence for the cluster, 7.4.2.7
configuring credentials using Enterprise Manager, 7.4.2.5.2
configuring credentials using WLST, 7.4.2.5.1
configuring high availability, 7.4
configuring Node Manager, 7.4.2.8, 7.4.3.3
configuring Oracle HTTP Server, 7.4.4.2
configuring the credential store, 7.4.2.5
configuring the default agent, 7.4.2.6
configuring the load balancer, 7.4.4.3
Console configuration, 7.2.5.3
Console log files, 7.2.5.4.4
creating the high availability domain, 7.4.2.3
effect of repository database failure, 7.3.3.2
effect of WebLogic Server or standalone agent crash, 7.3.3.1
external dependencies, 7.2.3
failover considerations, 7.3
high availability considerations, 7.3
installation and configuration of the first host, 7.4.2
installation and configuration of the second host, 7.4.3
installing on the first host, 7.4.2.2
installing Oracle HTTP Server on a separate host, 7.4.4
installing Oracle WebLogic Server on the first host, 7.4.2.1
installing Oracle WebLogic Server on the second host, 7.4.3.1
introduction, 7.1
Java EE agent configuration, 7.2.5.1
Java EE agent log files, 7.2.5.4.2
log file locations and configuration, 7.2.5.4
packing and unpacking the domain, 7.4.3.2
protection from failure and expected behavior, 7.3.3
reconfigure agents, 7.4.4.5
running RCU to create repositories, 7.4.1
session logs, 7.2.5.4.1
sessions lifecycle and recovery, 7.2.1
single instance characteristics, 7.2
standalone agent configuration, 7.2.5.2
standalone agent high availability with OPMN, 7.3.2
standalone agent log files, 7.2.5.4.3
starting odi_server1, 7.4.2.8
starting odi_server2, 7.4.3.3
starting the Administration Server, 7.4.2.4
startup and shutdown process, 7.2.4
upgrading the Oracle HTTP Server to the latest patch set, 7.4.4.1
verifying the agent is running, 7.4.2.9, 7.4.3.4, 7.4.4.4
Oracle Database adapters, 5.10.2.3
Oracle Directory Integration Platform
asynchronous provisioning, 8.5.1.1.3
cluster-wide configuration changes, 8.5.2.1.2
component architecture, 8.5.1
component architecture diagram, 8.5.1
component characteristics, 8.5.1.1
configuration artifacts, 8.5.1.1.4
copying the domain file if Node Manager fails to start on IDMHOST2, 8.5.5.3
directory integration profiles, 8.5.2.1.2
directory provisioning profiles, 8.5.2.1.2
directory synchronization profiles, 8.5.2.1.2
error message when using manageSync Profiles command, 8.5.5.5
errors received after starting Node Manager, 8.5.5.2
errors received during failover, 8.5.5.1
expected client behavior when failure occurs, 8.5.2.2.2
external dependencies, 8.5.1.1.5
external dependency failure, 8.5.2.2.3
failover and expected behavior, 8.5.4
high availability, 8.5
high availability architecture, 8.5.2.1
high availability architecture diagram, 8.5.2.1
high availability concepts, 8.5.2
high availability configuration steps, 8.5.3
installing and configuring on IDMHOST1, 8.5.3.1
installing and configuring on IDMHOST2, 8.5.3.3
log file, 8.5.1.1.6
post-installation steps, 8.5.3.4
prerequisites, 8.5.2.3
process failure, 8.5.2.2.1
process lifecycle, 8.5.1.1.2
propagating configuration changes in a high availability topology, 8.5.5.4
protection from failures and expected behavior, 8.5.2.2
provisioning data flow, 8.5.1.1.3
provisioning flow, 8.5.1.1.3
request flow, 8.5.1.1.3
required configuration parameters for starting, 8.5.1.1.4
runtime processes, 8.5.1.1.1
starting, 8.5.1.1.2
starting in a cluster, 8.5.2.1.1
starting the Managed Server on IDMHOST2 in a cluster, 8.5.3.4.2
stopping, 8.5.1.1.2
stopping in a cluster, 8.5.2.1.1
synchronization from a connected directory to Oracle Internet Directory, 8.5.1.1.3
synchronization from Oracle Internet Directory to a connected directory, 8.5.1.1.3
synchronization service flow, 8.5.1.1.3
synchronous provisioning, 8.5.1.1.3
troubleshooting high availability, 8.5.5
Oracle Directory Services Manager
additional high availability considerations, 8.6.7
component architecture, 8.6.1
component architecture diagram, 8.6.1
component characteristics, 8.6.1.1
configuring Oracle HTTP Server, 8.5.3.6.1
copying the domains file if Node Manager fails to start on IDMHOST2, 8.6.6.2
error message displayed during Oracle Internet Directory failover, 8.6.6.4
error messages after starting Node Manager, 8.6.6.1
expected client behavior when failure occurs, 8.6.2.2.2
expected dependency failure, 8.6.2.2.3
failover and expected behavior, 8.6.5
high availability, 8.6
high availability architecture, 8.6.2.1
high availability architecture diagram, 8.6.2.1
high availability concepts, 8.6.2
high availability configuration steps, 8.5.3, 8.6.3
installing and configuring on IDMHOST1, 8.5.3.1
installing and configuring on IDMHOST2, 8.5.3.3
installing Oracle HTTP Server on WEBHOST1 and WEBHOST2, 8.5.3.6
lifecycle management, 8.6.1.1.1
log file, 8.6.1.1.2
non-transparent failover using Oracle HTTP Server, 8.6.6.3
performing a WebLogic Server instance failover, 8.6.4.1
post-installation steps, 8.5.3.4
prerequisites, 8.6.2.3
process failure, 8.6.2.2.1
protection from failures and expected behaviors, 8.6.2.2
starting in a cluster, 8.6.2.1.1
stopping in a cluster, 8.6.2.1.1
temporary loss of Oracle Internet Directory connection during RAC failover, 8.6.6.5
troubleshooting high availability, 8.6.6
using to validate failover of a Managed Server, 8.6.5.1
using to validate failover of Oracle Internet Directory, 8.6.5.2
using to validate RAC failover, 8.6.5.3
validating high availability, 8.6.4
Oracle Discover
connection protocols, 14.5.1.1
Oracle Discoverer, 14.5
best practices, 14.6.5.8.9
changing the preference store, 14.6.5.8.4
cluster-wide application deployment, 14.5.2.5
configuration considerations, 14.5.1.3
configure for high availability, 14.6.4.9
configuring for high availability, 14.6.5.8
copying configuration files, 14.6.5.8.2
creating TNSNAMES entries for customer databases, 14.6.4.9.1, 14.6.5.8.1
database failures, 14.5.2.10
deployment considerations, 14.5.1.4
determining whether to configure Discoverer Viewer with Web Cache, 14.6.4.9.3
Discoverer Preference Server, 14.5.1.1
Discoverer Services Status, 14.5.1.1
Discoverer Servlet, 14.5.1.1
Discoverer Session Server, 14.5.1.1
enable Single Sign-On, 14.6.4.9.4
external dependencies, 14.5.1.1
failover of the preference server, 14.6.5.8.7
log file locations, 14.5.1.5
log files, 14.5.1.6
node failures, 14.5.2.8
online application deployment, 14.5.2.6
performance recommendation, 14.5.2.3
preference server, 14.6.5.8.9
preference server failover, 14.5.2.1
process failures, 14.5.2.7
process flow, 14.5.1.1
propagation of configuration changes, 14.5.2.4
protection from failures and expected behavior, 14.5.2
restart the WLS_DISCO and WLS_DISCO1 managed servers, 14.6.5.8.5
restarting components, 14.6.4.9.5
runtime considerations, 14.5.1.1
session state replication and failover, 14.5.2.2
setting up the preference store, 14.6.5.8.8
setting up the WSRP portlet producer in a cluster, 14.6.5.8.8
single-instance characteristics, 14.5.1
update configuration.xml, 14.6.4.9.2, 14.6.5.8.3
using the migration utility to transfer preference store content, 14.6.5.8.8
validate the configuration, 14.6.5.8.6
Viewer and Web Cache, 14.5.1.2
WebLogic Managed Server failures, 14.5.2.9
Oracle ECM
configuring Oracle HTTP Server on WEBHOST1, 10.3.4.2
configuring Oracle HTTP Server on WEBHOST2, 10.3.7.2
configuring the load balancer, 10.3.5
configuring the managed server on ECMHOST2, 10.3.6.6
creating a high availability domain, 10.3.3.3
database configuration, 10.3.2
disabling host name verification for the Administration Server and managed servers, 10.3.3.5
high availability architecture, 10.3
high availability configuration steps, 10.3
installation and configuration steps for ECMHOST2, 10.3.6
installation and configuration steps for WEBHOST1, 10.3.4
installation and configuration steps for WEBHOST2, 10.3.7
installing ECM on ECMHOST2, 10.3.6.2
installing on ECMHOST1, 10.3.3.2
installing Oracle HTTP Server on WEBHOST1, 10.3.4.1
installing Oracle HTTP Server on WEBHOST2, 10.3.7.1
installing Oracle WebLogic Server on ECMHOST2, 10.3.6.1
installing WebLogic Server on ECMHOST1, 10.3.3.1
shared storage, 10.3.1
starting Node Manager and the managed server on ECMHOST2, 10.3.6.4
starting the Administration Server and managed servers on ECMHOST1, 10.3.3.4
starting the managed servers on ECMHOST2, 10.3.6.5
upgrading the default file store, 10.3.8.3.2
using pack and unpack to join the domain on ECMHOST1, 10.3.6.3
Oracle File and FTP Adapters, 5.10.2.2
Oracle Forms, 14.4
best practices, 14.6.5.6.6
configuration cloning, 14.4.2.4
configuration files, 14.4.1.7
configuration persistence, 14.4.1.4
configure for high availability, 14.6.5.6
configuring for high availability, 14.6.4.7
copy configuration files from APPHOST1 to APPHOST2, 14.6.5.6.2
create TNSNAMES entries for customer databases, 14.6.4.7.1, 14.6.5.6.1
database failures, 14.4.2.8
database requirements, 14.4.1.2
external dependencies, 14.4.1.8
Forms Client, 14.4.1.5
HTTP listener, 14.4.1.3
listener servlet, 14.4.1.5
log files, 14.4.1.9
n+1 redundancy, 14.4.2.1
n+m redundancy, 14.4.2.2
node failures, 14.4.2.6
process failures, 14.4.2.5
process flow, 14.4.1.6
protection from failover and expected behavior, 14.4.2
request flow, 14.4.1.3
restart the WLS_FORMS managed server, 14.6.4.7.2
restart the WLS_FORMS1 managed server, 14.6.5.6.4
runtime considerations, 14.4.1.5
runtime process, 14.4.1.5
single-instance component characteristics, 14.4.1
state information, 14.4.1.1
update the default.env file, 14.6.5.6.3
validate the configuration, 14.6.4.7.3, 14.6.5.6.5
virtual machines, 14.4.2.3
WebLogic managed server failures, 14.4.2.7
Oracle Fusion Middleware Audit Framework
introduction, A
Oracle Fusion Middleware SOA Suite, 5
Oracle Fusion Middleware SOA Suite, introduction, 5.1
Oracle home, 2.1.4
Oracle HTTP Server, 11.2, 14.1.1
components
HTTP listener, 11.2.1
modules, 11.2.1
Perl interpreter, 11.2.1
external dependencies, 11.2.1.2
installing, 5.13.1.10
Oracle WebLogic Server, 11.2.1.1
single-instance characteristics, 11.2.1
starting, 11.2.3.2, 11.2.3.3
startup and shutdown lifecycle, 11.2.2
Oracle Human Workflow, 5.6
configuration artifacts, 5.6.1.3
manually recovering a task in the rejected MSG table, 5.6.2.2
protection from failures and expected behavior, 5.6.2.1
request processing, 5.6.1.2
single-instance characteristics, 5.6.1
startup and shutdown lifecycle, 5.6.1.1
troubleshooting high availability, 5.6.3
Oracle Human Workflow service components
URI of task details application, 5.6.1.3.1
Oracle Identity Federation
cluster-wide configuration changes, 8.13.2.1.2
component architecture, 8.13.1
component architecture diagram, 8.13.1
component characteristics, 8.13.1.1
configuration artifacts, 8.13.1.1.4
configuration data store types for different deployments, 8.13.1.1.5
configuring Oracle HTTP Server on OIFHOST1 and OIFHOST2, 8.13.3.4.3
configuring the load balancer, 8.13.3.5
data repositories, 8.13.1.1.5
deployed on WebLogic Server, 8.13.1.1.5
external dependencies, 8.13.1.1.5
failover and expected behavior, 8.13.4
federation data store types for different deployments, 8.13.1.1.5
high availability, 8.13
high availability architecture, 8.13.2.1
high availability architecture diagram, 8.13.2.1
high availability concepts, 8.13.2
high availability configuration steps, 8.13.3
high availability considerations for integration with Oracle Access Manager, 8.13.2.2
installing on OIFHOST1, 8.13.3.1
installing on OIFHOST2, 8.13.3.3
integrating with highly available LDAP Servers, 8.13.3.7
load balancer configuration, 8.13.3.5.2
log file, 8.13.1.1.6
performing a failover of, 8.13.4.1
post-installation steps, 8.13.3.4
prerequisites, 8.13.2.3
process lifecycle, 8.13.1.1.2
request flow, 8.13.1.1.3
runtime processes, 8.13.1.1.1
starting, 8.13.1.1.2
starting in a cluster, 8.13.2.1.1
starting the Managed Server on OIFHOST2 in a cluster, 8.13.3.4.2
stopping, 8.13.1.1.2
stopping in a cluster, 8.13.2.1.1
transient data store types for different deployments, 8.13.1.1.5
troubleshooting high availability, 8.13.5
using RCU to create schemas in the repository, 8.13.2.3.1
validating high availability, 8.13.3.6
virtual server names for load balancer, 8.13.3.5.1
Oracle Identity Management
high availability prerequisites, 8.2
Oracle home requirements, 8.2.1
Oracle Identity Management components
high availability concepts, 8.1
introduction, 8.1.1
Oracle Identity Manager
cluster-wide configuration changes, 8.9.2.3
component and process lifecycle, 8.9.1.3
component architecture, 8.9.1
component characteristics, 8.9.1.1
configuration artifacts, 8.9.1.5
configuration prerequisites, 8.9.3.1
configuring a default persistence store for transaction recovery, 8.9.3.14
configuring a shared JMS persistence store, 8.9.3.13
configuring Node Manager on OIMHOST1, 8.9.3.11
configuring Node Manager on OIMHOST2, 8.9.3.11
configuring OIM and SOA on OIMHOST1, 8.9.3.2
configuring Oracle Identity Manager to work with the web tier, 8.9.3.16
configuring server migration for instances, 8.9.3.12
creating a multi data source, 8.9.3.12.2
creating boot.properties for the Administration Server, 8.9.3.3.1
creating the domain, 8.9.3.2
creating the wlfullclient.jar file, 8.9.3.1
external dependencies, 8.9.1.6
failover and expected behavior, 8.9.3.18
high availability, 8.9
high availability architecture, 8.9.2.1
high availability concepts, 8.9.2
high availability configuration steps, 8.9.3
installing on OIMHOST1 and OIMHOST2, 8.9.3.1.5
installing Oracle HTTP Server, 8.9.3.15
installing Oracle WebLogic Server, 8.9.3.1.2
installing the Oracle SOA Suite on OIMHOST1 and OIMHOST2, 8.9.3.1.3
log file locations, 8.9.1.7
post-configuration steps for the managed servers, 8.9.3.5
post-installation steps on OIMHOST2, 8.9.3.8
propagating from OIMHOST1 to OIMHOST2, 8.9.3.7
running RCU to create OIM schemas, 8.9.3.1.1
runtime processes, 8.9.1.2
scaling out, 8.9.3.20.2
scaling up, 8.9.3.20.1
starting and stopping, 8.9.1.4
starting and stopping the cluster, 8.9.2.2
starting Node Manager on OIMHOST1, 8.9.3.3.3
starting Node Manager on OIMHOST2, 8.9.3.8.2
starting WLS_SOA1 and WLS_OIM1, 8.9.3.5.1
starting WLS_SOA2 and WLS_OIM2, 8.9.3.8.3
synchronizing with LDAP, 8.9.2.4
troubleshooting high availability, 8.9.3.19
updating Node Manager on OIMHOST1, 8.9.3.3.2
updating Node Manager on OIMHOST2, 8.9.3.8.1
updatng Coherence configuration for the SOA managed servers, 8.9.3.5.3
upgrading the Oracle SOA Suite on OIMHOST1 and OIMHOST2, 8.9.3.1.4
validating OIMHOST1, 8.9.3.6
validating on OIMHOST2, 8.9.3.9
validating the Oracle HTTP Server configuration, 8.9.3.17
verifying server migration, 8.9.3.12.6
Oracle Identity Navigator
high availability, 8.11
Oracle Internet Directory
additional high availability issues, 8.3.7
changing the password of the ODS schema, 8.3.7
cluster configuration high availability architecture diagram, 8.3.2.1
cluster-wide configuration changes, 8.3.2.1.2
component architecture, 8.3.1
component architecture diagram, 8.3.1
component characteristics, 8.3.1.1
component names assigned by installer, 8.3.3.2.2
configuration artifacts, 8.3.1.1.4
configuring on OIDHOST1 with a WebLogic domain, 8.3.3.3.1
configuring on OIDHOST1 without a WebLogic domain, 8.3.3.2.1
configuring on OIDHOST2 with a WebLogic domain, 8.3.3.3.3
configuring on OIDHOST2 without a WebLogic domain, 8.3.3.2.3
configuring with a WebLogic domain, 8.3.3.3
configuring without a WebLogic domain, 8.3.3.2
expected client behavior when failure occurs, 8.3.2.2.2
external dependencies, 8.3.1.1.5
external dependency failure, 8.3.2.2.3
failover and expected behavior, 8.3.5
high availability, 8.3
high availability architecture, 8.3.2.1
high availability concepts, 8.3.2
high availability configuration steps, 8.3.3
log files, 8.3.1.1.6
maximum high availability deployment, 9
maximum high availability deployment diagram, 9.1
monitoring, 8.3.1.1.2
multimaster replication, 9
multimaster replication deployment diagram, 9.1
performing a failover, 8.3.5.1
prerequisites, 8.3.2.3
process failure, 8.3.2.2.1
process lifecycle, 8.3.1.1.2
process status table, 8.3.1.1.2
protection from failures and expected behavior, 8.3.2.2
registering with a WebLogic domain, 8.3.3.2.4
request flow, 8.3.1.1.3
runtime processes, 8.3.1.1.1
starting, 8.3.1.1.2
starting a cluster, 8.3.2.1.1
stopping, 8.3.1.1.2
stopping a cluster, 8.3.2.1.1
synchronizing the time on nodes, 8.3.2.3.1
troubleshooting high availability, 8.3.6
using RCU to create schemas in the repository, 8.3.2.3.2
validating high availability, 8.3.4
virtual server names for load balancer, 8.3.2.3.3
Oracle I/PM
cluster-wide configuration changes, 10.1.2.1.2
component architecture, 10.1.1
component characteristics, 10.1.1.1
configuration artifacts, 10.1.1.1.4
configuring a default persistence store for transaction recovery, 10.3.8.2
configuring a JMS persistence store for JMS, 10.3.8.1
configuring server migration for instances, 10.3.8.7
configuring the managed servers, 10.3.8
configuring with Oracle UCM, 10.3.8.3
creating a multi data source, 10.3.8.7.3
creation of artifacts in a cluster, 10.1.2.3
database configuration, 10.3.2
effect of outages in components I/PM depends on, 10.1.2.2
enabling in Oracle UCM, 10.3.8.3.1
external dependencies, 10.1.1.1.5
high availability architecture, 10.1.2.1
high availability concepts, 10.1.2
high availability configuration steps, 10.3
high availability troubleshooting, 10.1.2.4
log file location, 10.1.1.1.6
node failure, 10.1.2.2
process lifecycle, 10.1.1.1.3
protection from failures and expected behaviors, 10.1.2.2
runtime processes, 10.1.1.1.2
setting the frontend HTTP host and port for the cluster, 10.3.8.6
shared storage, 10.3.1
starting and stopping a cluster, 10.1.2.1.1
state information, 10.1.1.1.1
verifying server migration, 10.3.8.7.7
Oracle JCA Adapters, 5.10
component lifecycle, 5.10.1.1
configuring a database mutex, 5.10.2.2
high availability configuration, 5.10.2.2
high availability error handling, 5.10.2.1
log file locations, 5.10.2.5
property changes during runtime, 5.10.1.1
rejected message handling, 5.10.1.3
reliability and transactional behavior, 5.10.1.2
single-instance characteristics, 5.10.1
Oracle JMS Adapters, 5.10.2.4
Oracle Mediator, 5.5
cluster-wide configuration changes, 5.5.2.1
component characteristics, 5.5.1.1
configuration artifacts, 5.5.1.4
ContainerIdLeaseRefresh configuration parameter, 5.5.2.1.2
ContainerIdLeaseTimeout configuration parameter, 5.5.2.1.2
external dependencies, 5.5.1.1
node failure, 5.5.2.1
process failure, 5.5.2.1
protection from failures and expected behavior, 5.5.2.1
recovering failed instances, 5.5.2.1.1
request flow, 5.5.1.3
resequencing in a cluster, 5.5.2.1.2
single-instance characteristics, 5.5.1
startup and shutdown lifecycle, 5.5.1.2
troubleshooting high availability, 5.5.2.2
Oracle Metadata Repository, 2.1, 2.1
Oracle Node Manager, 14.1.1
Oracle Portal, 14.2
best practices, 14.6.5.5.7
component characteristics, 14.2.1.2
configuration information, 14.2.1.5
configure for high availability, 14.6.4.6
configure the Parallel Page Engine with the load balancer, 14.6.4.6.2
configuring for high availability, 14.6.5.5
copying configuration information from APPHOST1, 14.6.5.5.1
creating Oracle Portal directories, 14.6.5.5.2
creating the database wallet, 14.6.4.6.3
deployment artifacts, 14.2.1.4
external dependencies, 14.2.1.7
identifying the database wallet, 14.6.4.6.3
logging and log configuration, 14.2.1.6
node failures, 14.2.2.2
post-installation step for Oracle RAC, 14.6.4.6.5
process failures, 14.2.2.1
protection from database failures, 14.2.2.4
request flow, 14.2.1.1
restart the web processes, 14.6.5.5.4
restart the WLS_PORTAL1 managed server, 14.6.5.5.5
rewire the repository, 14.6.4.6.1
single-instance characteristics, 14.2.1
startup and shutdown of processes and lifecycle, 14.2.1.3
troubleshooting Single Sign-On errors, 14.6.4.6.6
updating instance paths, 14.6.5.5.3
validate the configuration, 14.6.4.6.6, 14.6.5.5.6
WebLogic managed server failure, 14.2.2.3
Oracle Portal, Forms, Reports, and Discoverer, 14.1
architecture, 14.1.1
assumptions, 14.6.2
change host assertion in WebLogic, 14.6.4.5.10
change the Web Cache passwords, 14.6.5.4.4
change Web Cache passwords, 14.6.4.5.6
cluster-wide configuration changes, 14.1.4
common component log file information, 14.1.5
common components, 14.1.1, 14.1.3
common log files, 14.1.2
configure sqlnet.ora, 14.6.4.5.4
configure virtual hosts, 14.6.4.5.2
configure Web Cache, 14.6.4.5.5, 14.6.5.4.5
configuring, 14.6.4.3
configuring for high availability, 14.6
configuring on APPHOST2, 14.6.5.3
configuring virtual hosts, 14.6.5.4.2
copying configuration information from APPHOST1, 14.6.5.4.1
creating the boot.properties file, 14.6.4.5.3
creating the metadata repository, 14.6.3
databases, 14.6.1.3
dependencies, 14.6.1.1
failures and expected behaviors, 14.1.3
generic configuration, 14.6.4.5, 14.6.5.4
installing and configuring the application tier on APPHOST1, 14.6.4
installing and configuring the application tier on APPHOST2, 14.6.5
installing on APPHOST1, 14.6.4.2
installing on APPHOST2, 14.6.5.2
installing Oracle WebLogic Server on APPHOST1, 14.6.4.1
installing Oracle WebLogic Server on APPHOST2, 14.6.5.1
installing RCU, 14.6.3.1
load balancer, 14.6.1.2.1
load balancer configuration, 14.6.1.2.2
managed port numbers, 14.6.1.5
network requirements, 14.6.1.2
ports, 14.6.1.2.2
prerequisites, 14.6.1
register with Single Sign-On Server, 14.6.4.5.8
restart the web tier, 14.6.4.5.7
restart web processes on APPHOST1 and APPHOST2, 14.6.5.4.6
restarting components, 14.6.4.6.4
running RCU, 14.6.3.2
set the Administration Server address, 14.6.4.5.1
shared directories, 14.6.1.4
site names, 14.6.1.6
start Node Manager on APPHOST2, 14.6.5.4.7
typical ports, 14.6.2.1
updating Oracle HTTP Server configuration to be cluster aware, 14.6.5.4.3
validating the initial installation, 14.6.4.4
virtual server names, 14.6.1.2.2
web cache, 14.6.1.2.2
Oracle Process Manager and Notification Server, 14.1.1
Oracle RAC, 4.1
Oracle RAC, configuration requirements, 4.1.2.2
Oracle Real Application Clusters, 4.1
Oracle Reports, 14.3
configure for high availability, 14.6.4.8, 14.6.5.7
configure Reports Server to access shared output directory, 14.6.4.8.5
configure the database job repository, 14.6.4.8.4, 14.6.5.7.3
configure the Reports Server to access shared output directories, 14.6.5.7.2
connection retry, 14.3.1.4
create a security key for reports queue, 14.6.4.8.3
create a TNSNAMES entry for reports queue, 14.6.4.8.2
create reports queue in database, 14.6.4.8.1
create TNSNAMES entries for customer databases, 14.6.5.7.1
creating an Oracle Reports server cluster, 14.6.5.7.4
external dependencies, 14.3.1.2
log files, 14.3.1.6
managing connection availability for Reports Services, 14.6.5.7.7
process flow, 14.3.1.5
protection from failures and expected behavior, 14.3.2
restart the WLS_REPORTS and WLS_REPORTS1 managed servers, 14.6.5.7.5
restart the WLS_REPORTS managed server, 14.6.4.8.6
single-instance characteristics, 14.3.1
specific configuration files, 14.3.1.3
state information, 14.3.1.1
validate the configuration, 14.6.4.8.7, 14.6.5.7.6
Oracle RTD
administration, 15.3.1
Batch Manager failure, 15.3.2.2.5
cluster considerations, 15.3.2.1
cluster coordinator, 15.3.2.1
cluster coordinator failure, 15.3.2.2.2
cluster-wide configuration changes, 15.3.2.1.2
component architecture, 15.3.1
component characteristics, 15.3.1.1
component lifecycle, 15.3.1.1.1
configuration artifacts, 15.3.1.1.4
configuring cluster-specific properties, 15.3.3.13.1
configuring Oracle HTTP Server for the managed servers, 15.3.3.15
configuring ports for the load balancer, 15.3.3.1.4
configuring virtual server names for the load balancer, 15.3.3.1.4
creating a domain with Administration Server and first BI managed server, 15.3.3.4
database prerequisites, 15.3.3.1.1
database repository configuration, 15.3.3.1.2
database repository installation, 15.3.3.1.2
Decision Center, 15.3.1
Decision Center failure, 15.3.2.2.4
Decision Server, 15.3.1
Decision Server failure, 15.3.2.2.1
Decision Studio, 15.3.1
deployment artifacts, 15.3.1.1.5
disabling host name verification for the BI_SERVER1 managed server, 15.3.3.8
disabling host name verification for the BI_SERVER2 managed server, 15.3.3.12
external dependencies, 15.3.1.1.3
high availability, 15.3
high availability architecture, 15.3.2.1
high availability concepts, 15.3.2
high availability configuration steps, 15.3.3
high availability prerequisite steps, 15.3.3.1
installing, 15.3.3.2.2
installing Oracle HTTP Server, 15.3.3.1.4
installing Oracle HTTP Server on WEBHOST1 and WEBHOST2, 15.3.3.1.5
installing Oracle WebLogic Server, 15.3.3.2.1
installing the Oracle Fusion Middleware home, 15.3.3.2
Learning Service failure, 15.3.2.2.3
Learning Services, 15.3.1
load balancers, 15.3.3.1.4
loading the BI schemas into the repository database, 15.3.3.1.3
log files, 15.3.1.1.6
process flow, 15.3.1.1.2
protection from failures and expected behaviors, 15.3.2.2
RTD clients, 15.3.1
scaling out the BI system on APPHOST2, 15.3.3.10
scaling out the topology to a new node (APPHOST3), 15.3.3.18
setting the listen address for the BI_SERVER1 managed server, 15.3.3.7
setting the listen address for the BI_SERVER2 managed server, 15.3.3.11
singleton services, 15.3.2.1
starting and stopping the cluster, 15.3.2.1.1
starting and validating the BI_SERVER1 managed server, 15.3.3.9.2
starting and validating the BI_SERVER2 managed server, 15.3.3.14.3
starting Node Manager on APPHOST1, 15.3.3.9.1
starting Node Manager on APPHOST2, 15.3.3.14.2
starting the Administration Server on APPHOST1, 15.3.3.6.1
starting the system in APPHOST1, 15.3.3.9
starting the system in APPHOST2, 15.3.3.14
tools, 15.3.1
validating access through Oracle HTTP Server, 15.3.3.16
validating Oracle HTTP Server, 15.3.3.1.6
validating the Administration Server on APPHOST1, 15.3.3.6.2
virtual server names, 15.3.3.1.4
Oracle Service Bus
cluster-wide configuration changes, 5.12.2.4
cluster-wide deployment, 5.12.2.2
configuration artifacts, 5.12.1.3
database failure, 5.12.2.1.3
deployment artifacts, 5.12.1.4
external dependencies, 5.12.1.2
high availability architecture and failover considerations, 5.12.2
high availability concepts, 5.12
log file locations, 5.12.1.6
online redeployment, 5.12.2.3
session state, 5.12.1.1
single node characteristics, 5.12.1
Oracle Single Sign-On, 14.1.1
Oracle SOA
setting the frontend HTTP host and port for the cluster, 5.13.18
setting WLS cluster address for direct binding to composites, 5.13.19
Oracle SOA domain
creating, 5.13.2.1, 5.13.4, 5.14.2.1
Oracle SOA Servers
validating access, 5.13.15
Oracle SOA Service Infrastructure, 5.2
application characteristics, 5.2.1.1
cluster-wide configuration changes, 5.2.2.4
components, 5.2.2
configuring for high availability, 5.13
deploying applications, 5.13.20
external dependencies, 5.2.1.3
high availability architecture, 5.2.2
log file locations, 5.2.1.6
online redeployment of composites, 5.2.2.3
prerequisite steps, 5.13.1
scaling out, 5.13.22, 5.13.22.2
scaling up, 5.13.22.1
startup and shut down of processes, 5.2.1.4
startup and shutdown lifecyle, 5.2.1.2
VIP and IP prerequisites, 5.13.1.2
Oracle SOA Suite, 5
installing, 5.13.2.2, 5.14.2.2
load balancer prerequisites, 5.13.1.9
validating Oracle HTTP Server, 5.13.1.10.1, 5.14.1.10.1
virtual server names, 5.13.1.9, 5.14.1.9
Oracle UCM
adding Oracle I/PM server listen addresses, 10.3.8.3.3
cluster-wide configuration changes, 10.2.2.1.2
component architecture, 10.2.1
component characteristics, 10.2.1.1
configuration artifacts, 10.2.1.1.4
configuring the managed server on ECMHOST1, 10.3.3.6
configuring the managed server on ECMHOST2, 10.3.6.6
Content Server and Inbound Refinery communication, 10.2.2.2.1
Content Server clusters and Inbound Refinery instances, 10.2.2.2.2
creating a connection, 10.3.8.3.4
database configuration, 10.3.2
deployment artifacts, 10.2.1.1.5
external dependencies, 10.2.1.1.6
high availability architecture, 10.2.2.1
high availability architecture with Inbound Refinery, 10.2.2.2
high availability concepts, 10.2.2
high availability configuration steps, 10.3
high availability troubleshooting, 10.2.2.5
Inbound Refinery availability, 10.2.2.2.4
Inbound Refinery instances and load balancers, 10.2.2.2.3
log file locations, 10.2.1.1.7
process lifecycle, 10.2.1.1.3
protection from failure and expected behaviors, 10.2.2.4
runtime processes, 10.2.1.1.2
shared storage, 10.3.1
starting and stopping a cluster, 10.2.2.1.1
starting Node Manager and the managed server on ECMHOST2, 10.3.6.4
state information, 10.2.1.1.1
Oracle UMS, 5.9
client application startup, 5.9.1.2
cluster-wide configuration changes, 5.9.2.2
component characteristics, 5.9.1.1
configuration artifacts, 5.9.1.4
database failure, 5.9.2.1
driver startup, 5.9.1.2
external dependencies, 5.9.1.1
node failure, 5.9.2.1
process failure, 5.9.2.1
protection from external Messaging Gateway failures, 5.9.2.1
protection from failures and expected behavior, 5.9.2.1
server startup, 5.9.1.2
service request flow, 5.9.1.3
single instance characteristics, 5.9.1
startup and shutdown lifecycle, 5.9.1.2
Oracle URM
configuring the managed server on ECMHOST1, 10.3.3.7
configuring the managed server on ECMHOST2, 10.3.6.7
database configuration, 10.3.2
high availability, 10.2.2.3
high availability configuration steps, 10.3
shared storage, 10.3.1
Oracle User Messaging Service, 5.9
Oracle Virtual Directory
component architecture, 8.4.1
component architecture diagram, 8.4.1
component characteristics, 8.4.1.2
configuring with a RAC database, 8.4.3.3.1
configuring with a WebLogic domain, 8.4.3.2
configuring with highly available data sources, 8.4.3.3
configuring with LDAP repository, 8.4.3.3.2
configuring without a WebLogic domain, 8.4.3.1
failover and expected behavior, 8.4.5
high availability, 8.4
high availability architecture, 8.4.2.1
high availability architecture diagram, 8.4.2.1
high availability concepts, 8.4.2
high availability configuration steps, 8.4.3
high availability connect features, 8.4.2.1.1
installing on OVDHOST1 with a WebLogic domain, 8.4.3.2.1
installing on OVDHOST1 without a WebLogic domain, 8.4.3.1.1
installing on OVDHOST2 with a WebLogic domain, 8.4.3.2.3
installing on OVDHOST2 without a WebLogic domain, 8.4.3.1.2
log files, 8.4.1.2.1
performing a failover, 8.4.5.1
prerequisites, 8.4.2.2
registering with a WebLogic domain, 8.4.3.1.3
runtime considerations, 8.4.1.1
troubleshooting high availability, 8.4.6
troubleshooting LDAP adapter creation, 8.4.6.1
validating high availability, 8.4.4
validating high availability using SSL, 8.4.4.1
virtual server names for load balancer, 8.4.2.2.1
Oracle Web Cache, 14.1.1
Oracle Web Service Manage, 5.8
Oracle WebCenter, 6.3
adding new servers to a custom applications cluster, 6.5.2
applications, 6.3.2.1
cluster communications, 6.3.2.3
cluster-wide configuration changes, 6.3.2.10
components, 6.3.1.1
configuration overview, 6.3.1.5
configure the WebCenter Spaces Servers, 6.4.16.1
configuring a cluster for Oracle WebCenter Portal Applications, 6.5.1
configuring Activity Graph, 6.4.17
configuring for high availability, 6.4
configuring high availability for Oracle WebCenter Portal Applications., 6.5
configuring the Analytics Collector, 6.4.16
database prerequisites, 6.4.1.1
deploying application on a cluster, 6.3.2.3
expected behavior for application failover, 6.3.2.8
external dependencies, 6.3.1.4
installing and configuring an LDAP provider, 6.4.1.4
installing Oracle HTTP Server, 6.4.2
log file locations, 6.3.1.6
maintaining configuration in a clustered environment, 6.3.2.11
monitoring logging of application deployments, 6.3.2.9
protection from failover and expected behavior, 6.3.2.7
running RCU, 6.4.1.6.1
session failover requirements, 6.3.2.7
startup order, 6.3.2.2
state and configuration persistence, 6.3.1.3
state replication, 6.3.2.5
terminology for directories and directory environment variables, 6.4.1.5
understanding the distributed java object cache, 6.3.2.6
Oracle WebCenter Activity Graph
introduction, 6.3.1.1
Oracle WebCenter Analytics
communications, 6.3.2.4
introduction, 6.3.1.1
Oracle WebCenter Discussions Server
See Discussions server
Oracle WebCenter Personalization Server
introduction, 6.3.1.1
Oracle WebLogic Administration Server, 14.1.1
Oracle WebLogic Managed Servers, 14.1.1
Oracle WebLogic Server
installing, 5.13.2.1, 5.14.2.1
Oracle WebLogic Server and LDAP, 3.16
Oracle WebLogic Server cluster, 3.1
Oracle WebLogic Server crash, 5.2.2.1.1
Oracle WebLogic Server domain, 2.1, 2.1.1
Oracle WebLogic Server home, 2.1.5
Oracle WSM, 5.8
cluster-wide configuration changes, 5.8.2.2
component characteristics, 5.8.1.1
configuration artifacts, 5.8.1.4
configuring the Java object cache, 5.8.2.3
external dependencies, 5.8.1.1
node failure, 5.8.2.1
process failure, 5.8.2.1
protection from failures and expected behavior, 5.8.2.1
request flow, 5.8.1.3
single-instance characteristics, 5.8.1
startup and shutdown lifecycle, 5.8.1.2
ovd.mycompany.com virtual server, 8.2.5.4.2

P

pack/unpack, 5.13.11
passivating
transaction state, 6.1.3.1
path, Oracle home, specifying, 8.3.3.2.1, 8.3.3.2.3, 8.3.3.3.1, 8.3.3.3.3, 8.4.3.1.1, 8.4.3.1.2, 8.4.3.2.1, 8.4.3.2.3
Perl interpreter, 11.2.1
persistent store, 5.13.17
physical hostname, 2.2
PID file, 11.2.3.1
planned and unplanned down time, 2.4
port
determining availability with netstat, 8.3.3.2.1, 8.3.3.2.3, 8.3.3.3.1, 8.3.3.3.3, 8.4.3.1.1, 8.4.3.1.2, 8.4.3.2.3, 8.13.3.3
freeing, 8.3.3.2.1, 8.3.3.2.3, 8.3.3.3.1, 8.3.3.3.3, 8.4.3.1.1, 8.4.3.1.2, 8.4.3.2.1, 8.4.3.2.3, 8.5.3.1, 8.5.3.6, 10.3.4.1, 10.3.7.1
Oracle Directory Services Manager, 8.5.3.1
Oracle HTTP Server, 8.5.3.6, 10.3.4.1, 10.3.7.1
Oracle Internet Directory, 8.3.3.2.1, 8.3.3.2.3, 8.3.3.3.1, 8.3.3.3.3
Oracle Virtual Directory, 8.4.3.1.1, 8.4.3.1.2, 8.4.3.2.1, 8.4.3.2.3
prerequisites
Oracle BAM high availability, 5.15.1
Oracle Identity Management high availability, 8.2
primary node, 2.2
process death detection, 1.1.2
PROCESSES parameter for database, 5.13.1.7, 5.14.1.7, 5.15.1.3, 6.4.1.3
propagating the domain configuration, 5.13.11
properties file of Node Manager, 8.9.3.12.3, 10.3.8.7.4, 15.1.3.21.3

R

RAC failover
performing to check Oracle Directory Services Manager high availability, 8.6.4.2
performing to check Oracle Identity Federation high availability, 8.13.4.2
performing to check Oracle Internet Directory high availability, 8.3.5.2
performing to check Oracle Virtual Directory high availability, 8.4.5.2
RCU
loading schemas in the database, 5.13.1.8
running, 5.13.1.8.1, 5.14.1.8.1, 8.2.4.1
Real Application Clusters, troubleshooting, 4.3
recovering failed BPEL and Mediator instances, 5.3.2.1.1
redirecting to home page, 6.4.20.4
replication
LDAP multimaster replication, 9.2
one-way fan-out replication, 9.2
Oracle Advanced Database multimaster replication, 9.2
two-way fan-out replication, 9.2
replication types
for Oracle Internet Directory, 9.2
Repository Creation Utility
obtaining, 8.2.4
resequencing of messages
by Oracle Mediator in a cluster, 5.5.2.1.2
rolling patching, 1.1.2

S

scaling out, 5.13.22, 5.13.22.2
scaling up, 5.13.22.1
scripts
configure-joc.py, F.1
leasing.ddl, 8.9.3.12.1, 10.3.8.7.2, 15.1.3.21.1
wlsifconfig.sh, 8.9.3.12.4, 10.3.8.7.5, 15.1.3.21.4
secondary node, 2.2
server heartbeat messages, 3.8
server load balancing, 1.1.2, 2.3.2.1
server migration, 1.1.2, 5.13.21
configure server migration targets, 5.15.19.5
configuring, 5.13.21
configuring for Oracle BAM, 5.15.19
configuring targets, 8.9.3.12.5, 10.3.8.7.6, 15.1.3.21.5
create a multi data source, 5.13.21, 5.14.20, 5.14.21, 5.15.19.2
creating a multi data source, 8.9.3.12.2, 10.3.8.7.3, 15.1.3.21.2
edit the nodemanager properties file, 5.13.21, 5.14.20, 5.14.21, 5.15.19.3
editing Node Manager's properties file, 8.9.3.12.3, 10.3.8.7.4, 15.1.3.21.3
leasing table, 8.9.3.12.1, 10.3.8.7.2, 15.1.3.21.1
multi data source, 8.9.3.12.2, 10.3.8.7.3, 15.1.3.21.2
set environment and superuser privileges, 5.13.21, 5.14.20, 5.14.21
setting environment and superuser privileges, 8.9.3.12.4, 10.3.8.7.5, 15.1.3.21.4
setting up user and tablespace, 8.9.3.12.1, 10.3.8.7.2, 15.1.3.21.1
setting up user and tablespace for leasing table, 5.13.21, 5.14.20, 5.14.21, 5.15.19.1
test, 5.13.21, 5.14.20, 5.14.21, 5.15.19.6
testing, 5.13.21, 5.14.20, 5.14.21, 8.9.3.12.6, 10.3.8.7.7, 15.1.3.21.6
server migration processes, 3.9.2
server-side load balancing, 4.1.2.2
session replication, 3.4.1, 3.8.1
setting the front end HTTP host and port for Oracle I/PM cluster, 10.3.8.6
setting the front end HTTP host and port for Oracle SOA cluster, 5.13.18
shared storage, 2.2
shared storage prerequisites
for SOA high availability, 5.13.1.3
socket connections, 3.8
specifying
log files
PID file, 11.2.3.1
specifying a Dscoverer preferences server, 14.6.5.8.4
sso.mycompany.com virtual server, 8.2.5.4.2
starting, 11.2.3.2, 11.2.3.3
starting the administration server, 5.13.6.1, 5.14.6.1
state replication and routing, 1.1.2
superuser privileges, 8.9.3.12.4, 10.3.8.7.5, 15.1.3.21.4
switchover, 2.2
system component, 2.1
system component domains, 2.1.2

T

tablespace for server migration, 8.9.3.12.1, 10.3.8.7.2, 15.1.3.21.1
targets for server migration, 8.9.3.12.5, 10.3.8.7.6, 15.1.3.21.5
terminology for directories, 5.13.1.6, 6.2.1, 6.4.1.5
testing of server migration, 8.9.3.12.6, 10.3.8.7.7, 15.1.3.21.6
third party implementation, 2.3.4
Transaction Manager, 4.1.2.2
transaction recovery, 5.13.17
Transaction Recovery Service
configuring default persistence store, 5.15.10
transactional issues with endpoints, 5.3.2.1
Transparent Application Failover
configuring, 8.2.5.2
validating configuration, 8.2.5.3
troubleshooting
error while retrieving B2B document definitions., 5.7.2.4.2
redirecting to home page, 6.4.20.4

U

UMS, 5.9
unicast, 5.13.8, 5.14.8
unicast communication, 5.13.8, 5.14.8

V

validating Oracle HTTP Server
for Oracle SOA Suite, 5.13.1.10.1, 5.14.1.10.1
validating the administration server, 5.13.6.2, 5.14.6.2
validation
server migration, 8.9.3.12.6, 10.3.8.7.7, 15.1.3.21.6
virtual host names
enabling for Oracle SOA, 5.13.3
virtual hostname, 2.2
virtual IP, 2.2
virtual server names
for Oracle Identity Management deployment, 8.2.5.4.2
for Oracle SOA Suite, 5.13.1.9, 5.14.1.9
oaam.mycompany.com, 8.2.5.4.2
oid.mycompany.com, 8.2.5.4.2
oif.mycompany.com, 8.2.5.4.2
ovd.mycompany.com, 8.2.5.4.2
sso.mycompany.com, 8.2.5.4.2

W

WebLogic plugin
enabling, 14.6.4.5.9
weblogic.xml, 6.1.3.2
whole server migration, 3.9
whole server migration, manual processes, 3.9.2.3
wlfullclient.jar file
creating, 8.9.3.1
wlsifconfig.sh script, 8.9.3.12.4, 10.3.8.7.5, 15.1.3.21.4

X

XA data sources, 4.1.3
XA recovery, 4.1.2.2
XA transactions, 4.1.2.2
XEngine Files, extracting, 5.13.12