When you migrate, you see a page (Migrate server_name) that logs all the migration information, including all errors encountered. You receive warnings for the features you used in iPlanet Web Server 4.1 that are not supported in Sun Java System Web Server 6.1. The migration program does not migrate entries in obj.conf corresponding to obsolete features.
If you get fatal errors while migrating, the migration continues. The results page shows what errors occurred and you can use this information to troubleshoot.
You can only migrate individual server instances. You cannot migrate your administration server. After you have migrated your iPlanet Web Server instances, you need to set up features such as distributed administration and clusters again in your 6.1 Administration Server.
You can also migrate keys and certificates.
If you used the Directory Server, you do not need to do anything during the migration process to migrate users and groups. After migrating, in the Administration Server, on the Global Settings tab, use the Configure Directory Service page to point to a Directory Server.
iPlanet Web Server 4.1 provided two methods for creating hardware virtual servers: the object method and the virtual method. Migration of hardware virtual server information depends on which method you used:
If your iPlanet Web Server 4.1 hardware virtual servers were created using the object method, these hardware virtual server settings are migrated from the 4.1 obj.conf file to the 6.1 server.xml file.
If your iPlanet Web Server 4.1 hardware virtual servers were created using the virtual method, these hardware virtual server settings are migrated from the 4.1 virtual.conf file to the 6.1 server.xml file.
iPlanet Web Server 4.1 software virtual servers settings are migrated from the 4.1 obj.conf file to the 6.1 server.xml file.
If you had ACLs set up in your Administration Server 4.1 for distributed administration, these ACLs are not migrated. You must add them manually to your new Administration Server.
The migration process copies the database files in the 4.1_server_root/alias directory, such as key3.db and cert7.db, to the 6.1_server_root/alias directory.
In addition, the SSL parameters located in the magnus.conf file of 4.1 Server are automatically added to the 6.1 server.xml configuration file.
The ACL-related files, secmod.db and dbswitch.conf files are overwritten during migration.
For more information on using certificates with Sun Java System Web Server, see the Sun Java System Web Server 6.1 SP10 Administrator’s Guide.