User`s guide

Migrating from Enterprise Server 3.6
72 Installation and Migration Guide
In iPlanet Web Server 4.1, each server instance (including the Administration
Server) has its own certificate/key pair, which is now called a trust database.
You manage the trust database from the Server Manager’s Security tab. The trust
database includes the server certificate and all the included Certificate
Authorities. The certificate and key database files are now named after the
server instance that uses them. If multiple Enterprise Server 3.6 instances use
the same alias, when you migrate each instance you can choose to migrate the
certificate and key pair. The migrated certificate and key pair are named for the
iPlanet Web Server 4.1 instance each time you migrate.
The migration not only migrates the certificate, it migrates the whole trust
database associated with the server instance. All the Certificate Authorities
(CAs) in your 3.6 database are migrated to the 4.1 database. If they duplicate
4.1 CAs, use the 3.6 CA until it expires; then use the 4.1 CA. Do not attempt to
delete duplicate CAs.
When you migrate certificates from Enterprise Server 3.6 to iPlanet Web Server
4.1 make sure that the Administration Server user for 4.1 has read and write
permissions on the Enterprise Server 3.6 database files. The files are
alias -
cert.db and
alias -key.db, located in the 3.6_server_root /alias
directory.
For more information on using certificates with iPlanet Web Server, see the
iPlanet Web Server Administrator’s Guide.
Note If you are migrating an SSL-enabled server, you will have to manually start the
migrated server because you have to specify a password when starting it.
Migrating Web Publishing
If you had web publishing turned on in Enterprise Server 3.6 server, the
configuration files are migrated automatically as part of the migration process.
To successfully migrate web publishing data, you must choose the following
options on the Migration Parameters page:
• In the Document Root section, choose to use your old document root. Web
publishing relies on pathnames, and if you use a new document root your
pathnames change. Choosing to use your old document root also preserves
the web publishing user information.
• In the Web Publishing section, choose to migrate web publishing metadata.
If you do not choose this option, your metadata will be lost.