Netscape MANAGEMENT SYSTEM 6.1 - COMMAND-LINE Manual page 27

What you do next depends on which version you are converting. Follow
b.
the steps below that apply to the version you are converting:
Migrating from CMS 4.2 / CMS 4.2 (SP 1) / CMS 4.2 (SP 1a)
NOTE: Replace the ca.ocsp_signing.cacertnickname with the
ca.signing.cacertnickname (in CMS.cfg) since one does not exist in CMS 4.2
/ CMS 4.2 (SP 1) / CMS 4.2 (SP 1a)
For example:
servercertnickname (in server.xml)
ca.ocsp_signing.cacertnickname (in CMS.cfg)
ca.signing.cacertnickname (in CMS.cfg)
Migrating from CMS 4.2 (SP 2), CMS 4.5, or CMS 6.0 / CMS 6.01
For example:
servercertnickname (in server.xml)
ca.ocsp_signing.cacertnickname (in CMS.cfg)
ca.signing.cacertnickname (in CMS.cfg)
Dump the old internal directory content into LDIF format. To do this:
7.
Go to the following directory:
a.
<old_server_root>/slapd-<instance>-db
Execute the db2ldif command to export the internal directory content.
b.
Migrating from CMS 4.2 / CMS 4.2 (SP 1) / CMS 4.2 (SP 1a)/ CMS 4.2 (SP
2)/ CMS 4.5 use the following command:
db2ldif
Migrating from CMS 6.0 / CMS 6.01 use the following command:
db2ldif -n userRoot
The LDIF file will be created in the following file:
<old_server_root>/slapd-<instance>-db/ldif
Go to the following directory:
c.
<old_server_root>/slapd-<instance>-db/ldif
Rename the ldif file old.ldif
d.
Dump the new internal directory content into LDIF format. To do this:
8.
Chapter 2 CMS Upgrade Utility
Upgrading
27