My coworker Chris Ridd has spent a little bit of spare time writing a small utility that can parse the output of OpenDJ monitoring information to extract the details of the replication topology. Give the output to some graphical tool and here’s the result (based on one of our biggest customer -anonymized- data) :
This is a worldwide deployment with many directory services in 4 regions and 8 replication services fully connected. Each directory service is connected to a single replication server, but can failover in matter of seconds, by priority in the same region.
If you want to give it a try on your own replication topology, it’s simple. The tool is open source and part of the OpenDJ utilities that Chris has pushed to GitHub. Just feed it with the output of ldapsearch on cn=monitor.
Ludo Sketches 
This is a great piece of information. Given this topology how to make sure OpenIDMs are kept in sync? Is it using live sync? or is that not a consideration at all? We are trying to set up openDJ replication along with live sync with IDMs – just to avoid duplicates in global regions. Is there an ideal approach for this?
OpenDJ’s replication feature is meant to keep the servers’ data in sync, across all nodes in a topology, including distributed data-centers.
OpenIDM shouldn’t be used to synchronize data between OpenDJ servers, but to synchronize the data between the OpenDJ directory service and other systems.
Thanks, My concern was, even if DJs are in sync how to bring IDMs in sync to prevent – for example – provisioning of duplicate user across regions?