JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Directory Server Enterprise Edition Deployment Planning Guide 11g Release 1 (11.1.1.5.0)
search filter icon
search icon

Document Information

Preface

Part I Overview of Deployment Planning for Directory Server Enterprise Edition

1.  Introduction to Deployment Planning for Directory Server Enterprise Edition

2.  Business Analysis for Directory Server Enterprise Edition

Part II Technical Requirements

3.  Usage Analysis for Directory Server Enterprise Edition

4.  Defining Data Characteristics

5.  Defining Service Level Agreements

6.  Tuning System Characteristics and Hardware Sizing

7.  Identifying Security Requirements

8.  Identifying Administration and Monitoring Requirements

Part III Logical Design

9.  Designing a Basic Deployment

10.  Designing a Scaled Deployment

Using Load Balancing for Read Scalability

Using Replication for Load Balancing

Basic Replication Concepts

Assessing Initial Replication Requirements

Load Balancing With Multi-Master Replication in a Single Data Center

Load Balancing With Replication in Large Deployments

Using Server Groups to Simplify Multi-Master Topologies

Using Directory Proxy Server for Load Balancing

Using Distribution for Write Scalability

Using Multiple Databases

Using Directory Proxy Server for Distribution

Routing Based on the DIT

Routing Based on a Custom Algorithm

Using Directory Proxy Server to Distribute Requests Based on Bind DN

Distributing Data Lower Down in a DIT

Logical View of Distributed Data

Physical View of Data Storage

Directory Server Configuration for Sample Distribution Scenario

Directory Proxy Server Configuration for Sample Distribution Scenario

Considerations for Data Growth

Using Referrals For Distribution

Using Directory Proxy Server With Referrals

11.  Designing a Global Deployment

12.  Designing a Highly Available Deployment

Part IV Advanced Deployment Topics

13.  Using LDAP-Based Naming With Solaris

14.  Deploying a Virtual Directory

15.  Designing a Deployment With Synchronized Data

Index

Using Referrals For Distribution

A referral is information returned by a server that tells a client application which server to contact to proceed with an operation request. If you do not use Directory Proxy Server to manage distribution logic, you must define the relationships between distributed data in another way. One way to define relationships is using referrals.

Directory Server supports three ways of configuring how and when referrals are returned:

The following figure illustrates how referrals are used to direct clients from the UK to the appropriate server in a global topology. In this scenario, the client application must be able to connect to all the servers in the topology (at the TCP/IP level), to enable it to follow the referral.

Figure 10-14 Using Referrals to Direct Clients to a Specific Server

image:Figure shows client sending a request to consumer Directory Server, which refers the client to a different server in the topology.

Using Directory Proxy Server With Referrals

You can use Directory Proxy Server in conjunction with the referral mechanism to achieve the same result. The advantage of using Directory Proxy Server in this regard is that the load and complexity of client applications is reduced. Client applications are only aware of the Directory Proxy Server URL. If the distribution logic is changed, for any reason, this change is transparent to client applications.

The following figure illustrates how the scenario described previously can be simplified with the use of Directory Proxy Server. Client applications always connect to the Proxy Server, which handles the referrals itself.

Figure 10-15 Using Directory Proxy Server With Referrals

image:Figure shows clients sending requests to Directory Proxy Server, which handles all referrals.