To Upgrade Web Server

Before You Begin

• You need to log in as administrator to perform the upgrade and the user account performing migration should have permission to access the existing Web Server installation directories.

• Any J2EE components running in an Web Server instance should be shut down before you upgrade that instance.

• All Web Server instances corresponding to the same installed Web Server image are upgraded at the same time. All such instances should be shut down.

• After performing a fresh install of Release 5 Web Server, you have to 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. The Release 4 Web Server instance should be shut down before migrating its instance configuration data.

1. Log in as administrator

2. Stop all running instances of Web Server and the Administration Server.

   WebServer6-base\https-instanceName\stop

   WebServer6-base\https-admserv\stop

3. Install Java ES 5 Web Server.

   For Java ES 5 Web Server installation instructions, see the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows.

4. Start the Web Server Administration Server service.

   WebServer7Config-base\admin-server\bin\startserv

5. Migrate Release 4 Web Server instance configurations to Release 5 configurations.

   You can use either the command-line (wadm migrate-server) or graphical user interface administration tools. For more information about data migration, see the Sun Java System Web Server 7.0 Installation and Migration Guide.

   For more information on wadm command and options, see the Sun Java System Web Server 7.0 CLI Reference Manual.

6. Create Release 5 Web Server instances.

   You must create a new Release 5 instance for each migrated Release 4 instance. If you have migrated to the default configuration, a corresponding default instance already exists.

   • If you have not migrated to the default configuration:

     1. Before creating a new instance, verify the migration log and fix any issues in the migrated configuration.

     2. Type the create-instance command to create Web Server instances.

        WebServer7-base\bin\wadm create-instance --config=configName nodehost1 [nodehost2 ...nodehostN]

   • If you have not migrated to the default configuration:

     Deploy the corresponding configuration without first having to create the instance.

     WebServer7-base\bin\wadm deploy-config configName

7. Start each Release 5 instance.

   WebServer7Config-base\https-configName\bin\startserv