JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Fusion Middleware Deployment Planning Guide for Oracle Unified Directory 11g Release 1 (11.1.1)
search filter icon
search icon

Document Information


1.  Overview of Oracle Unified Directory

2.  Overview of the Directory Server

3.  Overview of the Proxy Server

4.  Overview of the Replication Gateway

5.  Building Blocks of the Proxy Server

6.  Example Deployments Using the Directory Server

7.  Example Deployments Using the Proxy Server

Deciding Your Proxy Deployment Type

Configuration 1: Simple Load Balancing

Configuration 2: Simple Distribution

Configuration 3: Failover Between Data Centers

Configuration 4: Distribution with Load Balancing

Configuration 5: Distribution with Failover Between Data Centers

Multiple Replicated Proxies

8.  Simple Proxy Deployments Using the Command Line Interface

9.  Deploying Advanced Proxy Architectures

Configuration 5: Distribution with Failover Between Data Centers

In a deployment of Oracle Unified Directory proxy using distribution with failover load balancing between two data centers, the data is split into partitions, where each partition is managed through a failover load balancing route. As illustrated in Figure 7-5, not only are the remote LDAP servers holding the partitioned data replicated within the data center, but in addition, the data centers are replicated, with one of the two acting as the backup.

Figure 7-5 Distribution with Failover Between Data Centers

Distribution with Failover Between Data Centers, with multiple instances of the failover workflow element and of the load balancing workflow element.

In other words, requests sent to the Oracle Unified Directory proxy deployed with this configuration are first distributed to the partition in which the data is stored. For example, a request for data Garry would be forwarded to partition 1. The failover load balancer then forwards the request through the main route, depending on the load balancing algorithm set, to one of the one of the remote LDAP servers holding the data for A..L.



In the deployment illustrated in Figure 7-5, Data Center 2 acts as a backup, and is only used on failure of the first data center. However, this same deployment could be configured to use saturation, rather than a failover load balancer. This way, if Data Center 1 in one geographical location (for example in one time-zone) becomes saturated, the other data center can pick up the excess traffic.

The advantages of this deployment are the speed of the reads through the distribution algorithm, and the high availability offered since the remote LDAP servers are replicated, and one data center acts as a backup.

For more information on the different distribution algorithms, see Data Distribution Using the Proxy.

For more information on the different load balancing algorithms, see Load Balancing Using the Proxy.

For details on deploying this configuration, see Configuring Distribution with Failover Between Data Centers.