Skip Navigation Links | |
Exit Print View | |
Oracle Fusion Middleware Deployment Planning Guide for Oracle Unified Directory 11g Release 1 (11.1.1) |
1. Overview of Oracle Unified Directory
2. Overview of the Directory Server
3. Overview of the Proxy Server
4. Overview of the Replication Gateway
What Is the Replication Gateway?
Setting Up the Replication Gateway
Deploying the Replication Gateway
How the Replication Gateway Works
5. Building Blocks of the Proxy Server
6. Example Deployments Using the Directory Server
7. Example Deployments Using the Proxy Server
8. Simple Proxy Deployments Using the Command Line Interface
The replication gateway does not manage the following aspects:
Data initialization. Total update is not supported through the replication gateway. To initialize an Oracle Directory Server Enterprise Edition topology with data from an Oracle Unified Directory server, the data must be exported from the Oracle Unified Directory server and then imported to one Oracle Directory Server Enterprise Edition master server.
Schema coherency. The replication gateway does not ensure that schema is coherent across the disparate servers. The administrator must define coherent schema.
Feature translation. The replication gateway does not translate features between the disparate servers, and assumes that the topologies are heterogeneous, with regard to features. The best way to handle incompatible features (for example, macro ACIs, CoS, password policies) is to filter out the affected object classes and attribute types before replication occurs.
The replication gateway does provide a filtering option, for replication from Oracle Directory Server Enterprise Edition to Oracle Unified Directory. This option enables you to filter out object classes and attribute types that do not apply to Oracle Unified Directory servers. The default values that are configured for filtering take into account differences in CoS, roles, password policies and conflict resolution.