Sun Java System Web Server 7.0 Release Notes

Migration

The following table lists the known issues in the migration area of Web Server 7.0.

Table 11 Known Issues in Migration

Problem ID 

Description 

6407877 

Incorrect migration occurs while migrating from Web Server 6.0 to 7.0 if the installed.pkg file is not found.

In Web Server 6.0 to 7.0 migration, if the installed.pkg file is missing, Web Server incorrectly migrates the NSServlet entries in the magnus.conf file.

6490124 

6.x -> 7.0: Migrated scheduled events still points to 6.x paths in the server.xml file.

 

6502529 

6.1->7.0: Migration does not handle relative path set for search-collection-dir correctly.

During instance migration, specifying a relative path for the target path into which the search collections should be copied, results in the search collection directory being created with respect to the config-store. When the instance is instantiated, the indexes are created without properly migrating the search collections.

6502769 

6.x->7.0: Migration ignores any "document-root" NameTrans specified in the obj.conf file.

6498806 

On Windows, Web Server Admin Console does not appropriately warn users during migration.

Administration Server does not detect if the selected new configuration or the service name already exists on Windows and hence does not appropriately warn the users to select a different configuration name or suggest a different configuration name as default. 

6500509 

Web Server 7.0 migration tool is unable to successfully migrate from Web Server 6.1 if it has Root Certs installed in it.