Hi Ludovic

Thanks for your answer but in my architecture, openldap already exist and i'm obliged to work with .

regards Stan

Le 20/06/2012 15:07, Ludovic Poitou a écrit :

Hi Stanislas,

Sun DSEE replication protocol is proprietary and thus interoperating with any other LDAP directory server. I'm sure there are several people who have migrated from Sun DSEE to OpenLDAP (and the biggest hurdles are schema and aci) , although in my part of the industry I hear more about those who migrate to OpenDJ (initially started by Sun as OpenDS to replace Sun DSEE).

Cordialement,

Ludovic

Ludovic Poitou ForgeRock - Product Manager for OpenDJ. http://forgerock.com http://ludopoitou.wordpress.com

On Wednesday, June 20, 2012 at 14:45 , Stanislas LEVEAU wrote:

...

Hi

I wonder if someone has already migrated from a Sun DSEE to openldap and establishment of a replication from SUN DSEE to openldap.

thanks in advance Regards -- *Stanislas LEVEAU**

*Rectorat de Caen 168, rue Caponière B.P. 6184 14061 CAEN Cedex Direction des Systèmes d'Information de l'Académie de Caen Département des infrastructures

stanislas.leveau@ac-caen.fr mailto:stanislas.leveau@ac-caen.fr Tel : 02.31.30.17.86

Clément OUDOT wrote:

2012/6/20 Stanislas LEVEAU <stanislas.leveau@ac-caen.fr mailto:stanislas.leveau@ac-caen.fr>

Hi

I wonder if someone has already migrated from a Sun DSEE to openldap
and establishment of a replication from SUN DSEE to openldap.

Hi,

we have done a lot of migration ot this kind. We published some documentation about it: http://www.linid.org/projects/openldap-manager/wiki/MigrationSunOracle

You have to study the data, the schema, the plugins...

As said by Ludovic, you will not be able to use the built-in synchronization mechanism, but you can use LSC project to synchronize some data.

Pretty sure that LSC would be the easiest route at the moment. There are stubs in the syncrepl consumer code for replicating from a SunDS style retro changelog, but that code was left incomplete due to lack of demand/interest. As I recall, it could only operate in polling mode (i.e. refreshOnly) but it's been a while since I looked at that aspect.