As the legacy Sun product has reached its end of life, many companies are looking at migrating from Sun Directory Server Enterprise Edition [SunDSEE] to ForgeRock Directory Services, built on the OpenDJ project.
Several of our existing customers have already done this migration, whether in house or with the help of partners. Some even did the migration in 2 weeks. In every case, the migration was smooth and easy. Regularly, I’m asked if we have a detailed migration guide and if we can recommend tools to keep the 2 services running side by side, synchronized, until all apps are moved to the ForgeRock Directory Services deployment.
My colleague Wajih, long time directory expert, has just published an article on ForgeRock.org wikis that described in details how to do DSEE to OpenDJ system to system synchronization using ForgeRock Identity Management product.
If you are planning a migration, check it out. It is that simple !
Updates:
- Update on June 8th to add link to A Global Bank case study.
Ludo Sketches 
Hi, I’m new to this area. Currently, I’m trying to migrating CA directory to OpenDJ. First thing to do before I create the connectors, should I replicate the CA custom schema to OpenDJ? Any suggestion how to do that? Thanks.
Yes, you will need to move the CA specific custom schema to OpenDJ. I’ve never put my hands on CA directory so I don’t know what is the format of the schema. May be if you can provide a sample simple CA custom schema file, then I might be able to help.
I can’t seem to find any documentation to help with even getting the OpenIDM liveSync process to run…Any pointers to a write up? Thanks.
LiveSync is properly documented in the IDM Documentation. Here’s the link for ForgeRock IDM 6.5: https://backstage.forgerock.com/docs/idm/6.5/samples-guide/#chap-livesync-with-ad.
The example is with synchronising AD with ForgeRock DS, but that can be adjusted easily to sync between other LDAP servers.