Migrating Sun Java Directory Server to HP-UX Directory Server White Paper

Configuration Migration

Part of the migration of general configuration settings is a manual process. The sjdsmig.pl script

provides some automated migration, but some settings cannot automatically be migrated by the script

because of the need for additional input.

Creating the DSE Change File

The sjdsmig.pl script can read a dse.ldif file from SJDS and output an LDIF file that contains

change operations applicable to HPDS to activate some settings.

After copying the SJDS instance’s dse.ldif file to the HPDS host, run sjdsmig.pl with the

appropriate options. For example:

# sjdsmig.pl cfg -d dse.ldif -o dse_changes.ldif

For more information about the conversions made by the sjdsmig.pl script, and how to obtain it,

see “Appendix B: sjdsmig.pl script”.

Important:

Some migrated settings, such as password policy, are related to security.

Before applying the change file to HPDS, review this file carefully, referring

to the

HP-UX Directory Server Configuration, Command, and File Reference

to verify the usage of any unfamiliar settings. To change settings, modify

the change file using a text editor. The following example shows a portion

of a file that has settings for worker threads and for the minimum password

length. To use the default number of worker threads, remove the entry that

specifies the worker threads (as indicated by strikethrough in the example).

To modify the minimum password length value, change the value

accordingly (indicated by bold, the new value to being 6.

dn: cn=config

changetype: modify

replace: nsslapd

-threadnumber

nsslapd

-threadnumber: 40

dn: cn=config

changetype: modify

replace: passwordMinLength

passwordMinLength: 6

When satisfied with the change file, apply it to the HPDS instance by using the ldapmodify

command, as in the following example:

# ldapmodify –D “cn=directory manager” –w - -f dse_changes.ldif

After applying the configuration changes, verify the HPDS instance’s errors log. The errors log

indicates which configuration settings require that the instance be restarted before they take effect.

Replication Configuration

The process for adding the migrated instance to a replication topology involves running the HPDS

Admin Console interface, configuring a replica, and depending on the type of replica, adding a

changelog and one or more replication agreements. Additionally, if the replica will receive updates

from other replicas, add a user entry referred to as the supplier bind entry. This entry is required for

authentication of incoming replication sessions. The final step is importing the data, either the data