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

To convert the exported data for HPDS compatibility, run the sjdsmig.pl script with the appropriate

input files and output file specified. For example:

# sjdsmig.pl data -i example_export.ldif -s /tmp/searched.ldif -d dse.ldif -o

example_converted.ldif

For details on the conversions made by the sjdsmig.pl script, see “Appendix A: Migration

checklist”.

Step 4: Importing the Converted LDIF File into the HPDS Instance

Use the ldif2db command to import LDIF to the HPDS instance. For example:

# /opt/dirsrv/slapd-instance1/ldif2db -s dc=example,dc=com –i example_converted.ldif

Note:

When using the ldif2db command, both informational and error

messages are displayed on the screen. If there is a problem importing an

entry, that entry will be skipped and a message will explain why. If there is

a general schema violation that affects many users, numerous error

messages might be displayed. In that case, abort the import using the

interrupt character (typically Ctrl-c), rectify the problem (for example, by

adding any missing schema), and start the import again.

ldif2db completely overwrites the specified directory server database

and replaces it with the data found in the specified LDIF file.

Step 5: (Optional) Exporting the Imported LDIF File for Use by Replicas

If additional HPDS instances participate in replication with the instance having the imported and

converted LDIF, export the LDIF file to all of those instances. This may seem redundant, given that the

data itself has not changed, but additional data has been inserted, such as data version information

that identifies the data as being of the same origin when it is imported into another replica instance.

To ensure that metadata for replication is included, use the –r option when exporting the LDIF. For

example:

# /opt/dirsrv/slapd-instance1/db2ldif -s dc=example,dc=com –a example_for_replicas.ldif -r

Validation

After configuration and data migration has been completed, validation is strongly recommended for

proper operation of the HP-UX Directory Server. Depending on the deployment requirements of the

directory server, specific security, configuration, scalability or other functions may need to be

validated before putting the migrated directory server into operation.

Validation specifics will vary depending on product usage. As an example, verifying that a migrated

user can still authenticate can be done using the ldapsearch command:

# /opt/dirsrv/bin/ldapsearch –D uid=user,dc=example,dc=com –w – –s base –b “”

“objectclass=*”