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 topologies, 1.1.2, 10
advantages, 10.1
disadvantages, 10.1
adf-config.xml, 6.1.3.3, 6.1.3.4, 6.3.1.5
Administration Console
redirecting to home page, 6.4.18.4
Administration Server, 2.1.1, 2.1.1.1
administration server, 3.11
administration server failure, 3.11.1
admin.mycompany.com virtual server, 7.2.5.5.2
Apache
version, 9.2.1
Apache HTTP Server, 9.2.1
apachectl, 9.2.3
application failover, 3.4.1
ascrs, 11
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
automatic restart, 1.1.2

B

B2B, 5.6
cluster-wide configuration changes, 5.6.2.2
component characteristics, 5.6.1.1
configuration artifacts, 5.6.1.4
deployments in a cluster, 5.6.2.3
external dependencies, 5.6.1.1
node failure, 5.6.2.1
protection from failures and expected behavior, 5.6.2.1
purge, import, or deployment of metadata, 5.6.2.4.1
request flow, 5.6.1.3
singe-instance characteristics, 5.6.1
startup and shutdown lifecycle, 5.6.1.2
troubleshooting active-active configuration, 5.6.2.4
ui failure, 5.6.2.1
B2B document definitions, 5.6.2.4.2
backup and recovery, 1.1.2
boot.properties file
creating for the Administration Server, 7.3.3.2.3, 7.4.3.2.3, 7.5.3.3, 7.7.3.3

C

cache clusters
authentication, 9.3.2.4
cluster agent, 2.2
cluster configuration, 3.14
cluster objects, 3.5
cluster ready services, 11
clustered server instances, 3.8
clustering, 1.1.2
clusters, 2.1.1.2
authentication, 9.3.2.4
clusterware, 2.2
cluster-wide configuration changes, 5.7.2.2
collocated Identity Management components
additional high availability considerations, 7.8.5
architecture, 7.8.1
architecture diagram, 7.8.1
configuring for high availability, 7.8.2.2
failures and expected behaviors, 7.8.3.2
high availability, 7.8
high availability architecture, 7.8.2
high availability architecture diagram, 7.8.2
prerequisites, 7.8.2.1
troubleshooting high availability, 7.8.4
validating high availability, 7.8.3
validation tests for high availability, 7.8.3.1
configuration
wiki server, 6.4.14
configuration files
adf-config.xml, 6.3.1.5
connections.xml, 6.3.1.5
configuration management, 2.3.2
configure-joc.py script, 5.7.2.3, 6.4.13
configuring a default persistent store for transaction recovery, 5.11.12.3
config.xml, 3.14
connections.xml, 6.3.1.5
constrained candidate servers, 3.10.1
creating a SOA domain, 5.11.3.1, 5.11.5
crs, 11

D

database
configuring for Oracle Fusion Middleware metadata, 7.2.5
database access, 4
database initialization parameters, 5.11.1.7
database mutex, configuring, 5.9.2.2
database prerequisites
Oracle Identity Management high availability, 7.2.2
database repository
configuring, 5.11.1.7
installing, 5.11.1.7
installing and configuring, 7.2.3
database service
adding to a database, 7.2.5.3
assigning to database instances, 7.2.5.3
creating, 7.2.5.3
starting, 7.2.5.3
death detection, 1.1.2
deploying applications, 5.11.14
deploying composites, 5.11.7.5
deployment architecture, 2.3.1
direct implementation, 2.3.4
directory environment, 6.2.1
directory environment variables, 5.11.1.6, 6.4.1.5
disaster recovery, 1.1.2, 2.3.5
Discussions server
configuration files
DNS server, 9.3.1
domains
system component domains, 2.1.2
WebLogic Server, 2.1.1

E

Enterprise Java Beans, 3.5
etc/services file, 7.3.3.1.1, 7.3.3.1.3, 7.3.3.2.2, 7.3.3.2.4, 7.4.3.1.1, 7.4.3.1.2, 7.4.3.2.2, 7.4.3.2.4, 7.5.3.2, 7.5.3.6

F

failback, 2.2
failover, 1.1.2, 2.2
configuring RAC database to automate Oracle Internet Directory failover, 7.2.5.3
failover and replication, 3.8
file
etc/services, 7.3.3.1.1, 7.3.3.1.3, 7.3.3.2.2, 7.3.3.2.4, 7.4.3.1.1, 7.4.3.1.2, 7.4.3.2.2, 7.4.3.2.4, 7.5.3.2, 7.5.3.6
file and FTP Adapters, 5.9.2.2
firewall timeouts, 4.2
Fusion Middleware home
installing, 5.11.3

H

hardware cluster, 2.2
high availability database access, 4
high availability framework, 2
home page, redirecting to, 6.4.18.4
hostname
network, 2.2
physical, 2.2
virtual, 2.2
HTTP listener, 9.2.1
Human Workflow, 5.5
configuration artifacts, 5.5.1.3
protection from failures and expected behavior, 5.5.2.1
request processing, 5.5.1.2
singe-instance characteristics, 5.5.1
startup and shutdown lifecycle, 5.5.1.1
troubleshooting high availability, 5.5.3
human workflow service components
URI of task details application, 5.5.1.3.1

I

idle connections, 4.2
initialization parameter
changing the value, 7.2.5.1
integrated high availability, 1.1.2

J

Java components, 2.1
Java EE, 5.2
java object cache, 6.3.2.5
Java Server Pages, 3.5
JCA Adapters, 5.9
component lifecycle, 5.9.1.1
configuring a database mutex, 5.9.2.2
high availability configuration, 5.9.2.2
high availability error handling, 5.9.2.1
log file locations, 5.9.2.5
property changes during runtime, 5.9.1.1
rejected message handling, 5.9.1.3
reliability and transactional behavior, 5.9.1.2
single-instance characteristics, 5.9.1
JMS, 3.10
JMS Adapters, 5.9.2.4
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.11.1.4
LDAP multimaster replication
adding an Oracle Internet Directory node using Fusion Middleware Control, 8.3.1.1
deleting an Oracle Internet Directory node using Fusion Middleware Control, 8.3.1.2
setting up for Oracle Internet Directory, 8.3
setting up for Oracle Internet Directory using Fusion Middleware Control, 8.3.1
load balancer
configuring for Oracle Identity Federation, 7.7.3.6, 7.7.3.6.2
configuring ports, 7.2.5.5
configuring virtual server names, 7.2.5.5
requirements for Oracle Identity Management, 7.2.5.5.1
virtual server names for, 7.2.5.5.1
load balancing, 2.3.2.1, 3.4.3, 3.12

M

managed server
starting, 5.11.7.7
validating, 5.11.7.7
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
mod_dav, 9.2.1
mod_dms, 9.2.1
mod_onsint, 9.2.1
mod_oradav, 9.2.1
mod_ossl, 9.2.1
mod_osso, 9.2.1
mod_perl, 9.2.1, 9.2.1
mod_plsql, 9.2.1
mod_wl_ohs, 9.2.1
modules, 9.2.1
multi data source, 4.1.3
multi data source, configuring, 4.1.2.1, 4.1.3
multi data sources, 4.1.2
multimaster replication
configuring with Oracle Delegated Administration Services 10.1.4.3 and Oracle Internet Directory 11g, 8.3
configuring with Oracle Single Sign-On 10.1.4.3 and Oracle Internet Directory 11g, 8.3
setting up for Oracle Internet Directory, 8.3

N

netstat command, 7.3.3.1.1, 7.3.3.1.3, 7.3.3.2.2, 7.3.3.2.4, 7.4.3.1.1, 7.4.3.1.2, 7.4.3.2.4, 7.7.3.4
network hostname, 2.2
node failure, 5.2.2.1.2
Node Manager, 2.1.1.3, 3.9.1
node manager, 3.9.2.6
starting, 5.11.7.4
node manager failure, 3.11.2

O

oid.mycompany.com virtual server, 7.2.5.5.2
oif.mycompany.com virtual server, 7.2.5.5.2
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 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.1, 6.2.2.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, 8.3.2.1
deleting an Oracle Internet Directory node, 8.3.2.2
setting up for Oracle Internet Directory, 8.3, 8.3.2
Oracle B2B, 5.6
Oracle BAM, 5.10
component characteristics, 5.10.1.1
configuration artifacts, 5.10.1.4
configuring a JMS persistence store for BAM UMS, 5.12.9
configuring high availability, 5.12
configuring RAC failover, 5.12.15
create the WebLogic server Oracle BAM domain, 5.12.5
creating boot.properties, 5.12.6
database prerequisites, 5.12.1.1
disabling host name verification, 5.12.8
external dependencies, 5.10.1.1
installing fusion middleware home, 5.12.3
installing http server, 5.12.2
installing Oracle WebLogic Server, 5.12.3.1
node failure, 5.10.2.1
process failure, 5.10.2.1
protection from failures and expected behavior, 5.10.2.1
real time data streaming clients, 5.10.1.1
single-instance characteristics, 5.10.1
starting the administration server, 5.12.7
startup and shutdown of processes, 5.10.1.3
startup/shutdown lifecycle, 5.10.1.2
vip and ip prerequisites, 5.12.1.2
web applications, 5.10.1.1
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 Business Activity Monitoring, 5.10
Oracle Coherence
deploying composites, 5.11.7.5
Oracle Database adapters, 5.9.2.3
Oracle Directory Integration Platform
asynchronous provisioning, 7.5.1.1.3
cluster-wide configuration changes, 7.5.2.1.2
component architecture, 7.5.1
component architecture diagram, 7.5.1
component characteristics, 7.5.1.1
configuration artifacts, 7.5.1.1.4
copying the domain file if Node Manager fails to start on IDMHOST2, 7.5.5.3
directory integration profiles, 7.5.2.1.2
directory provisioning profiles, 7.5.2.1.2
directory synchronization profiles, 7.5.2.1.2
error message when using manageSync Profiles command, 7.5.5.5
errors received after starting Node Manager, 7.5.5.2
errors received during failover, 7.5.5.1
expected client behavior when failure occurs, 7.5.2.2.2
external dependencies, 7.5.1.1.5
external dependency failure, 7.5.2.2.3
failover and expected behavior, 7.5.4
high availability, 7.5
high availability architecture, 7.5.2.1
high availability architecture diagram, 7.5.2.1
high availability concepts, 7.5.2
high availability configuration steps, 7.5.3
installing and configuring on IDMHOST1, 7.5.3.2
installing and configuring on IDMHOST2, 7.5.3.4
installing the WebLogic Administration Server on IDMHOST1 and IDMHOST2, 7.5.3.1
log file, 7.5.1.1.6
post-installation steps, 7.5.3.5
prerequisites, 7.5.2.3
process failure, 7.5.2.2.1
process lifecycle, 7.5.1.1.2
propagating configuration changes in a high availability topology, 7.5.5.4
protection from failures and expected behavior, 7.5.2.2
provisioning data flow, 7.5.1.1.3
provisioning flow, 7.5.1.1.3
request flow, 7.5.1.1.3
required configuration parameters for starting, 7.5.1.1.4
runtime processes, 7.5.1.1.1
starting, 7.5.1.1.2
starting in a cluster, 7.5.2.1.1
starting the Managed Server on IDMHOST2 in a cluster, 7.5.3.5.2
stopping, 7.5.1.1.2
stopping in a cluster, 7.5.2.1.1
synchronization from a connected directory to Oracle Internet Directory, 7.5.1.1.3
synchronization from Oracle Internet Directory to a connected directory, 7.5.1.1.3
synchronization service flow, 7.5.1.1.3
synchronous provisioning, 7.5.1.1.3
troubleshooting high availability, 7.5.5
Oracle Directory Services Manager
additional high availability considerations, 7.6.7
component architecture, 7.6.1
component architecture diagram, 7.6.1
component characteristics, 7.6.1.1
configuring Oracle HTTP Server, 7.5.3.6.1
copying the domains file if Node Manager fails to start on IDMHOST2, 7.6.6.2
error message displayed during Oracle Internet Directory failover, 7.6.6.4
error messages after starting Node Manager, 7.6.6.1
expected client behavior when failure occurs, 7.6.2.2.2
expected dependency failure, 7.6.2.2.3
failover and expected behavior, 7.6.5
high availability, 7.6
high availability architecture, 7.6.2.1
high availability architecture diagram, 7.6.2.1
high availability concepts, 7.6.2
high availability configuration steps, 7.5.3, 7.6.3
installing and configuring on IDMHOST1, 7.5.3.2
installing and configuring on IDMHOST2, 7.5.3.4
installing Oracle HTTP Server on WEBHOST1 and WEBHOST2, 7.5.3.6
installing the WebLogic Administration Server on IDMHOST1 and IDMHOST2, 7.5.3.1
lifecycle management, 7.6.1.1.1
log file, 7.6.1.1.2
non-transparent failover using Oracle HTTP Server, 7.6.6.3
performing a WebLogic Server instance failover, 7.6.4.1
post-installation steps, 7.5.3.5
prerequisites, 7.6.2.3
process failure, 7.6.2.2.1
protection from failures and expected behaviors, 7.6.2.2
starting in a cluster, 7.6.2.1.1
stopping in a cluster, 7.6.2.1.1
temporary loss of Oracle Internet Directory connection during RAC failover, 7.6.6.5
troubleshooting high availability, 7.6.6
using to validate failover of a Managed Server, 7.6.5.1
using to validate failover of Oracle Internet Directory, 7.6.5.2
using to validate RAC failover, 7.6.5.3
validating high availability, 7.6.4
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, 9.2
components
HTTP listener, 9.2.1
modules, 9.2.1
Perl interpreter, 9.2.1
external dependencies, 9.2.1.2
installing, 5.11.2
Oracle WebLogic Server, 9.2.1.1
single-instance characteristics, 9.2.1
starting, 9.2.3.2, 9.2.3.3
startup and shutdown lifecycle, 9.2.2
Oracle Identity Federation
cluster-wide configuration changes, 7.7.2.1.2
component architecture, 7.7.1
component architecture diagram, 7.7.1
component characteristics, 7.7.1.1
configuration artifacts, 7.7.1.1.4
configuration data store types for different deployments, 7.7.1.1.5
configuring Oracle HTTP Server on OIFHOST1 and OIFHOST2, 7.7.3.5.3
configuring the load balancer, 7.7.3.6
data repositories, 7.7.1.1.5
deployed on WebLogic Server, 7.7.1.1.5
external dependencies, 7.7.1.1.5
failover and expected behavior, 7.7.4
federation data store types for different deployments, 7.7.1.1.5
high availability, 7.7
high availability architecture, 7.7.2.1
high availability architecture diagram, 7.7.2.1
high availability concepts, 7.7.2
high availability configuration steps, 7.7.3
high availability considerations for integration with Oracle Access Manager, 7.7.2.2
installing on OIFHOST1, 7.7.3.2
installing on OIFHOST2, 7.7.3.4
installing Oracle WebLogic Server on OIFHOST1 and OIFHOST2, 7.7.3.1
integrating with highly available LDAP Servers, 7.7.3.8
load balancer configuration, 7.7.3.6.2
log file, 7.7.1.1.6
performing a failover of, 7.7.4.1
post-installation steps, 7.7.3.5
prerequisites, 7.7.2.3
process lifecycle, 7.7.1.1.2
request flow, 7.7.1.1.3
runtime processes, 7.7.1.1.1
starting, 7.7.1.1.2
starting in a cluster, 7.7.2.1.1
starting the Managed Server on OIFHOST2 in a cluster, 7.7.3.5.2
stopping, 7.7.1.1.2
stopping in a cluster, 7.7.2.1.1
transient data store types for different deployments, 7.7.1.1.5
troubleshooting high availability, 7.7.5
using RCU to create schemas in the repositiory, 7.7.2.3.1
validating high availability, 7.7.3.7
virtual server names for load balancer, 7.7.3.6.1
Oracle Internet Directory
additional high availability issues, 7.3.7
changing the password of the ODS schema, 7.3.7
cluster configuration high availability architecture diagram, 7.3.2.1
cluster-wide configuration changes, 7.3.2.1.2
component architecture, 7.3.1
component architecture diagram, 7.3.1
component characteristics, 7.3.1.1
component names assigned by installer, 7.3.3.1.2
configuration artifacts, 7.3.1.1.4
configuring with a WebLogic domain, 7.3.3.2
configuring without a WebLogic domain, 7.3.3.1
expected client behavior when failure occurs, 7.3.2.2.2
external dependencies, 7.3.1.1.5
external dependency failure, 7.3.2.2.3
failover and expected behavior, 7.3.5
high availability, 7.3
high availability architecture, 7.3.2.1
high availability concepts, 7.3.2
high availability configuration steps, 7.3.3
installing on OIDHOST1 with a WebLogic domain, 7.3.3.2.2
installing on OIDHOST1 without a WebLogic domain, 7.3.3.1.1
installing on OIDHOST2 with a WebLogic domain, 7.3.3.2.4
installing on OIDHOST2 without a WebLogic domain, 7.3.3.1.3
installing Oracle WebLogic Server on OIDHOST1, 7.3.3.2.1
log files, 7.3.1.1.6
maximum high availability deployment, 8
maximum high availability deployment diagram, 8.1
monitoring, 7.3.1.1.2
multimaster replication, 8
multimaster replication deployment diagram, 8.1
performing a failover, 7.3.5.1
prerequisites, 7.3.2.3
process failure, 7.3.2.2.1
process lifecycle, 7.3.1.1.2
process status table, 7.3.1.1.2
protection from failures and expected behavior, 7.3.2.2
registering with a WebLogic domain, 7.3.3.1.4
request flow, 7.3.1.1.3
runtime processes, 7.3.1.1.1
starting, 7.3.1.1.2
starting a cluster, 7.3.2.1.1
stopping, 7.3.1.1.2
stopping a cluster, 7.3.2.1.1
synchronizing the time on nodes, 7.3.2.3.1
troubleshooting high availability, 7.3.6
using RCU to create schemas in the repository, 7.3.2.3.2
validating high availability, 7.3.4
virtual server names for load balancer, 7.3.2.3.3
Oracle Mediator, 5.4
cluster-wide configuration changes, 5.4.2.1
component characteristics, 5.4.1.1
configuration artifacts, 5.4.1.4
protection from failures and expected behavior, 5.4.2.1
request flow, 5.4.1.3
singe-instance characteristics, 5.4.1
troubleshooting high availability, 5.4.2.2
Oracle Metadata Repository, 2.1, 2.1
Oracle RAC, 4.1
Oracle RAC, configuration requirements, 4.1.2.2
Oracle Real Application Clusters, 4.1
Oracle User Messaging Service, 5.8
Oracle Virtual Directory
component architecture, 7.4.1
component architecture diagram, 7.4.1
component characteristics, 7.4.1.2
configuring with a RAC database, 7.4.3.3.1
configuring with a WebLogic domain, 7.4.3.2
configuring with highly available data sources, 7.4.3.3
configuring with LDAP repository, 7.4.3.3.2
configuring without a WebLogic domain, 7.4.3.1
failover and expected behavior, 7.4.5
high availability, 7.4
high availability architecture, 7.4.2.1
high availability architecture diagram, 7.4.2.1
high availability concepts, 7.4.2
high availability configuration steps, 7.4.3
high availability connect features, 7.4.2.1.1
installing on OVDHOST1 with a WebLogic domain, 7.4.3.2.2
installing on OVDHOST1 without a WebLogic domain, 7.4.3.1.1
installing on OVDHOST2 with a WebLogic domain, 7.4.3.2.4
installing on OVDHOST2 without a WebLogic domain, 7.4.3.1.2
installing Oracle WebLogic Server on OVDHOST1, 7.4.3.2.1
log files, 7.4.1.2.1
prerequisites, 7.4.2.2
registering with a WebLogic domain, 7.4.3.1.3
runtime considerations, 7.4.1.1
troubleshooting high availability, 7.4.6
validating high availability, 7.4.4
validating high availability using SSL, 7.4.4.1
virtual server names for load balancer, 7.4.2.2.1
Oracle Web Service Manage, 5.7
Oracle WebCenter, 6.3
applications, 6.3.2.1
cluster communications, 6.3.2.3
cluster-wide configuration changes, 6.3.2.9
components, 6.3.1.1
configuration overview, 6.3.1.5
configuring for high availability, 6.4
database prerequisites, 6.4.1.1
deploying application on a cluster, 6.3.2.3
expected behavior for application failover, 6.3.2.7
external dependencies, 6.3.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.10
monitoring logging of application deployments, 6.3.2.8
protection from failover and expected behavior, 6.3.2.6
running RCU, 6.4.1.6.1
session failover requirements, 6.3.2.6
startup order, 6.3.2.2
state and configuration persistence, 6.3.1.3
state replication, 6.3.2.4
terminology for directories and directory environment variables, 6.4.1.5
understanding the distributed java object cache, 6.3.2.5
Oracle WebCenter Discussions Server
See Discussions server
Oracle WebCenter Wiki and Blog Server
configuration files, 6.3.1.5
Oracle WebLogic Server
installing, 5.11.3.1
Oracle WebLogic Server domain, 2.1
Oracle WSM, 5.7, 5.7.2.2
component characteristics, 5.7.1.1
configuration artifacts, 5.7.1.4
external dependencies, 5.7.1.1
node failure, 5.7.2.1
protection from failures and expected behavior, 5.7.2.1
request flow, 5.7.1.3
single-instance characteristics, 5.7.1
startup and shutdown lifecycle, 5.7.1.2
ovd.mycompany.com virtual server, 7.2.5.5.2

P

pack/unpack, 5.11.9
path, Oracle home, specifying, 7.3.3.1.1, 7.3.3.1.3, 7.3.3.2.2, 7.3.3.2.4, 7.4.3.1.1, 7.4.3.1.2, 7.4.3.2.2, 7.4.3.2.4
Perl interpreter, 9.2.1
persistent store, 5.11.12.3
physical hostname, 2.2
PID file, 9.2.3.1
planned and unplanned down time, 2.4
port
determining availability with netstat, 7.3.3.1.1, 7.3.3.1.3, 7.3.3.2.2, 7.3.3.2.4, 7.4.3.1.1, 7.4.3.1.2, 7.4.3.2.4, 7.7.3.4
freeing, 7.3.3.1.1, 7.3.3.1.3, 7.3.3.2.2, 7.3.3.2.4, 7.4.3.1.1, 7.4.3.1.2, 7.4.3.2.2, 7.4.3.2.4, 7.5.3.2, 7.5.3.6
Oracle Directory Services Manager, 7.5.3.2
Oracle HTTP Server, 7.5.3.6
Oracle Internet Directory, 7.3.3.1.1, 7.3.3.1.3, 7.3.3.2.2, 7.3.3.2.4
Oracle Virtual Directory, 7.4.3.1.1, 7.4.3.1.2, 7.4.3.2.2, 7.4.3.2.4
prerequisites
Oracle Identity Management high availability, 7.2
primary node, 2.2
process death detection, 1.1.2
PROCESSES parameter for database, 5.11.1.7, 5.12.1.3, 6.4.1.3
propagating the domain configuration, 5.11.9

R

RAC failover
performing to check Oracle Directory Services Manager high availability, 7.6.4.2
performing to check Oracle Identity Federation high availability, 7.7.4.2
performing to check Oracle Internet Directory high availability, 7.3.5.2
performing to check Oracle Virtual Directory high availability, 7.4.5.2
RCU
loading schemas in the database, 5.11.1.8
running, 5.11.1.8.1
Real Application Clusters, troubleshooting, 4.3
recovering failed BPEL and Mediator instances, 5.3.2.1.1
redirecting to home page, 6.4.18.4
replication
LDAP multimaster replication, 8.2
one-way fan-out replication, 8.2
Oracle Advanced Database multimaster replication, 8.2
two-way fan-out replication, 8.2
replication types
for Oracle Internet Directory, 8.2
Repository Creation Utility
creating Oracle Identity Management schemas, 7.2.4
rolling patching, 1.1.2
running the soa-createUDD.py script, 5.11.7.6

S

scaling out, 5.11.16
scripts
configure-joc.py, 5.7.2.3, 6.4.13
soa-createUDD.py, 5.11.7.6
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.11.15
configure server migration targets, 5.11.15
configuring, 5.11.15
create a multi data source, 5.11.15
edit the node manager properties file, 5.11.15
set environment and superuser privileges, 5.11.15
setting up user and tablespace for leasing table, 5.11.15
test, 5.11.15
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, 5.11.13
shared storage, 2.2
SOA domain
creating, 5.11.3.1, 5.11.5
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.11
deploying applications, 5.11.14
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.11.1
scaling out, 5.11.16
startup and shut down of processes, 5.2.1.4
startup and shutdown lifecyle, 5.2.1.2
vip and ip prerequisites, 5.11.1.2
SOA Suite, 5
soa-createUDD.py script, 5.11.7.6
socket connections, 3.8
specifying
log files
PID file, 9.2.3.1
starting, 9.2.3.2, 9.2.3.3
starting the administration server, 5.11.7.1
state replication and routing, 1.1.2
switchover, 2.2
system component, 2.1
system component domains, 2.1.2

T

terminology for directories, 5.11.1.6, 6.2.1, 6.4.1.5
third party implementation, 2.3.4
Transaction Manager, 4.1.2.2
transaction recovery, 5.11.12.3
transactional issues with endpoints, 5.3.2.1
Transparent Application Failover
configuring, 7.2.5.3
validating configuration, 7.2.5.4
troubleshooting
error while retrieving B2B document definitions., 5.6.2.4.2
redirecting to home page, 6.4.18.4

U

UMS, 5.8
client application startup, 5.8.1.2
cluster-wide configuration changes, 5.8.2.2
component characteristics, 5.8.1.1
configuration artifacts, 5.8.1.4
database failure, 5.8.2.1
driver startup, 5.8.1.2
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
server startup, 5.8.1.2
service request flow, 5.8.1.3
startup and shutdown lifecycle, 5.8.1.2
unicast, 5.11.7.5
unicast communication, 5.11.7.5

V

validating the administration server, 5.11.7.2
virtual hostname, 2.2
virtual IP, 2.2
virtual server names
admin.mycompany.com, 7.2.5.5.2
for Oracle Identity Management deployment, 7.2.5.5.2
oid.mycompany.com, 7.2.5.5.2
oif.mycompany.com, 7.2.5.5.2
ovd.mycompany.com, 7.2.5.5.2

W

WebCenter
wiki server, 6.4.14
WebLogic Server
crash, 5.2.2.1.1
WebLogic Server and LDAP, 3.16
WebLogic Server cluster, 3.1
WebLogic Server crash, 5.2.2.1.1
WebLogic Server domain, 2.1.1
WebLogic Server home, 2.1.5
weblogic.xml, 6.1.3.2
whole server migration, 3.9
whole server migration, manual processes, 3.9.2.3
wiki server, 6.4.14

X

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