When it comes to synchronizing between Oracle Directory Server Enterprise Edition (ODSEE) and Oracle Unified Directory (OUD), what options are available and can be exercised?
Several options are available. You can use:
Now, let's evaluate the pros and cons of each method.
Replication Gateway is the default out-of-the-box solution to perform the replication and include OUD instances in an existing ODSEE replication topology.
This feature came into existence, because it works at the
replication protocol level. The gateway performs the required
adaptation of replication protocols between ODSEE and OUD.
The main advantage of this feature is that it provides strong consistency
between the two types of directories. This fully leverages conflict
management implemented in the replication protocols to ensure that
changes are applied in a coherent and ordered manner under all circumstance. It does not
require specific modification on existing ODSEE production
instances, such as enabling retro changelog. Changes are
propagated at near speed of replication in both directions.
As full meta-data are replicated by the Replication gateway, it will also synchronize internal password policy states, ensuring proper account locking and optimal conflict resolution.
OUD replication gateway does not require any specific tool or
installation-specific procedure. It is installed like any OUD component and then managed like any other OUD
OUD Replication Gateway does not perform data adaptation between ODSEE
Using Directory Integration Platform as the synchronization tool.
This brings flexibility in remapping and
transformation between ODSEE and OUD.
However, you need to pay a price to use a tool (like DIP) to perform the
synchronization task. You need to enable the retro change
log to access the changes on the ODSEE side. This in turn has an impact on the disk , CPU usage and performances, which could be a serious
challenge for your existing ODSEE environment, if you have not
provisioned additional hardware and instances.
Using export and import method with standard directory administrative commands.
This seems very simple, but this
methodology cannot ensure an highly-available deployment with up-to-date entries on both sides.
This solution can be used if full
high availability with up-to-date data at any time is not needed. It is often used if data cleaning needs to take place to avoid
polluting a new environment with old unnecessary data.