Upgrade Considerations

When upgrading Web Server software to Java ES Release 5 you should take into account the following considerations:

There are some issue with migration of Java ES 4 data to Java ES 5. For more information about Web Server migration issues, see the Sun Java System Web Server 7.0 Release Notes for Microsoft Windows.

• Migration of a default Release 4 instance configuration. When performing an upgrade, you migrate configuration data for each Release 4 Web Server instance to a central configuration store maintained by the Web Server Administration Server. The migration is achieved using the wadm migrate-server command or the Release 5 Administration Console.

  If an instance being migrated is a default Release 4 Web Server (6.x) instance, it has the same name (hostName.domainName) as the default Release 5 Web Server (7.0) configuration, which is automatically created by the Configure automatically during installation option.

  There are three approaches to performing the migration of a default Release 4 instance configuration to Release 5, each of which results in a different configuration name. The approach you choose can impact the subsequent upgrade of deployed web applications. For example, the upgrade of deployed Java ES components (such as Access Manager and Portal Server) and Sun Java Communications Suite components (such as Communications Express, Instant Messaging, and Delegated Administrator) generally requires that the person performing such upgrades know the name of the Release 5 configuration to which the Release 4 instance configuration has been migrated.

  The three approaches are the following:

  • Specify a new configuration name different from the default name. The wadm migrate-server command will then create a new configuration. Subsequently upgraded web applications would need to be redeployed to the new configuration.

  • Do not specify a new configuration name, but delete the new default Release 5 instance and configuration (hostName.domainName) before running the migrate-server command. The migrate-server command will then create a new configuration with the default name (hostName.domainName). The sequence would be as follows:

    1. wadm delete-instance

    2. wadm delete-config

    3. wadm migrate-server

    4. wadm create-instance

    Subsequently upgraded web applications would need to be redeployed to the hostName.domainName configuration, which is the same as the default Release 4 instance name.

  • Do not specify a new configuration name, and do not delete the new default Release 5 configuration. The migrate-server command will then create a new configuration with the following name: hostName.domainName-1.

• Migration of configuration data. When migrating Release 4 instance configurations, the following information is automatically migrated:

  • All the configuration information in the Release 4 Web Server instance directory: WebServer6-base\https-instanceName\config. This includes configuration information for all web applications deployed in the Release 4 instance. For example, Java ES components such as Access Manager and Portal Server.

  • acl information from WebServer6-base\httpacl

  • auth-db information from WebServer6-base\userdb

  • Scheduler information from WebServer6-base\https-admserv\config

  • Certificate information from WebServer6-base\alias

  • Search collection information and index files, as specified when you perform the migration.

  The automatic migration does not include the following data:

  • The new configuration will point to the old docroot and a log message will be recorded in the migration log.

  • Webdav collection information will be migrated. Instead, they will point to the Release 4 file and a log message will be recorded in the migration log.

  • 3rd party NSAPI plug-ins.

  • Log files.

  • Changes to the search collection docroot.

  • Command line utilities, startsvr, startsvr.bat, stopsvr, stopsvr.bat, restart, reconfig, and reconfig.bat.

• Creation of Release 5 Web Server instances. After migration, you have to explicitly create a Release 5 Web Server instance corresponding to the migrated Release 4 instance. This operation is not done automatically.

  ---

  Note –

  Windows does not allow two services with same name on a single host. For this reason, if you install Java ES 5 Web Server on a host that already has Java ES 4 Web Server installed on it then the default instance name for Java ES 5 Web Server instance will be https-hostname-1 but the document root will be created under WebServer7–base\http-instancename.

  ---