The create-sync-pipe-config
tool is used to configure Sync Pipes and
Sync Classes. For bidirectional deployments, configure two Sync Pipes, one for each
directional path.
Use the create-sync-pipe tool to configure synchronization illustrates a bidirectional synchronization deployment in standard mode. The example assumes that two replicated topologies are configured:
- The first endpoint topology consists of two Sun LDAP servers: the main server and one failover. Both servers have Retro change logs enabled and contain the full DIT that will be synchronized to the second endpoint.
- The second endpoint topology consists of two PingDirectory Servers: the main server
and one failover. Both servers have change logs enabled and contain entries similar
to the first endpoint servers, except that they use a
mail
attribute, instead of anemail
attribute.
A specific mail
to email
mapping must also be created
to exclude the source attribute on the Sync Pipe going the other direction.
If the source attribute is not excluded, PingDataSync Server will attempt to
create an email
attribute on the second endpoint, which could fail
if the attribute is not present in the destination server’s schema.
Then, two Sync Classes are defined:
- One to handle the customized
email
tomail
attribute mapping. - Another to handle all other cases (the default Sync Class).
The dsconfig
command is used to create the specific attribute mappings.
The resync
command is used to test the mappings. Synchronization can
start using the realtime-sync
command.