Normalizing Your Previous Internal Database File; Converting The Cms 4.2 Ldif File To A Text Format - Netscape MANAGEMENT SYSTEM 6.01 - COMMAND-LINE Manual

Before Upgrading
The default file name is time stamped and is of the form
<year>_<month>_<day>.ldif
/usr/netscape/server60/slapd-firefly-db/ldif/2002_04_08_123356.l
dif
Normalizing Your Previous Internal Database
File
To import a CMS 4.2 or 4.5 LDIF file into a CMS 6.01 instance, you need to adjust
the LDIF file by deleting the first two LDIF entries. (You don't need to delete the
first two entries in the CMS 6.0 LDIF file.)
For example, delete:
dn: dc=<hostname>,dc=netscape,dc=com ...
dn: cn=ldap://:38900,dc=<hostname>,dc=netscape,dc=com ...
The first line of the LDIF file should now be:
dn: o=netscapeCertificateServer
Next, you need to convert the adjusted LDIF files to a text format:
•

Converting the CMS 4.2 LDIF File to a Text Format

• Converting the CMS 4.5 LDIF File to a Text Format
• Converting the CMS 6.0 LDIF File to a Text Format
NOTE
Converting the CMS 4.2 LDIF File to a Text Format
If you are upgrading from a CMS 4.2 instance to a CMS 6.01 instance:
Execute the
1.
cd <upgrade_tool>/42ToTxt
export SERVER_ROOT=<42_server_root>
run.sh <42_ldif> > <42_txt>
Execute the
2.
20 Netscape Certificate Management System Command-Line Tools Guide • May 2002
. For example:
In the sections that follow, replace
<server_root>/bin/cert/upgrade
command:
42ToTxt
command:
TxtTo601
with
<upgrade_tool>
.