Chapter 4 Web Server

This chapter describes how to upgrade Web Server software from previous Java ES versions to Java ES 5 (Release 5): Web Server 7.0.

This chapter provides a general overview of upgrade issues and procedures for the different upgrade paths supported by Release 5. This chapter covers the following sections:

• Overview of Web Server Upgrades

• Upgrading Web Server from Java ES Release 4

---

Note –

File locations in this chapter are specified with respect to a directory path referred to as WebServer-base. At least part of this path might have been specified as an installation directory when Web Server was initially installed. If not, the Java ES installer assigned a default value.

The default values of these directory paths are:

WebServer6-base

C:\Sun\WebServer

WebServer7-base

C:\Program Files\Sun\JavaES5\webserver7

WebServer7Config-base

C:\Program Files\Sun\JavaES5\webserver7

---

Overview of Web Server Upgrades

The following sections describe general aspects of Web Server that impact upgrading to Release 5:

• About Java ES 5 Web Server

• Web Server Upgrade Roadmap

• Web Server Data

• Web Server Compatibility Issues

• Web Server Dependencies

About Java ES 5 Web Server

Java ES Release 5 Web Server represents a major release with respect to Release 4. It has a number of new features and interface enhancements.

Release 5 Web Server has a new administrative infrastructure with new administrative tools. The administrative infrastructure includes an Administration Server instance which hosts configuration information for any number of Web Server instances. A new command line interface (wadm) and new graphical user interface are used to create Web Server instances, either locally or on remote computers, and to configure and manage these instances. The new administrative tools require an administrator user name and password.

For more information about the new administrative infrastructure, see the Web Server 7.0 Administrator's Guide.

Web Server Upgrade Roadmap

The following table shows the supported Web Server upgrade paths to Java ES Release 4.

Table 4–1 Upgrade Paths to Java ES 5 Web Server 7.0

Java ES Release	Web Server Release	General Approach	Reconfiguration Required
Release 4	Sun Java System Web Server 6.1 SP 5 2005Q4	Direct upgrade: Fresh install followed by data migration	Migration of instance configuration to new instance

Web Server Data

The following table shows the type of data that could be impacted by an upgrade of Web Server software.

Table 4–2 Web Server Data Usage

Type of Data	Location	Usage
Configuration data	Web Server 6.x (Java ES 4):  WebServer6-base\https-instanceName\config Web Server 7.0 (Java ES Release 5):  WebServer7Config-base\https-configName\config Web Server 7.0 (Java ES Release 5):  Central Configuration Store. This is not a public interface that is managed by the admin-server instance.	Configuration of Web Server instance

Web Server Compatibility Issues

Java ES Release 5 Web Server does not introduce any changes in public interfaces and is backwardly compatible with earlier versions. However, the new administrative interfaces for deploying web applications impact the upgrade and redeployment of web applications including, for example, Java ES components.

In particular, Release 5 Web Server uses different defaults for instance directories and virtual server names, as shown in the following table.

Table 4–3 Web Server Instance Directories and Virtual Server Names

Item	Java ES 4 Web Server 6.x Default	Java ES 5 Web Server 7.0 Default
Configuration name		hostName.domainName
Instance directory path	WebServer6-base\https-hostName.domainName	WebServer7Config-base https-hostName.domainName
Virtual server name	https-hostName.domainName	hostName.domainName

Web Server Dependencies

Web Server has no dependencies on other Java ES components other than on Java ES shared components, as listed in Table 1–7.

Upgrading Web Server from Java ES Release 4

This section includes information about upgrading Web Server from Release 4 to Release 5. This section covers the following topics:

• Introduction to Upgrading Web Server

• Web Server Upgrade

Introduction to Upgrading Web Server

When upgrading Release 4 Web Server to Release 5, consider the following aspects of the upgrade process:

• General Upgrade Approach. The upgrade is performed by doing a fresh install of Release 5 Web Server, migrating Release 4 Web Server instance configuration information to a Release 5 configuration, and then creating Release 5 Web Server instances that correspond to the Release 4 instances.

• Upgrade Dependencies. Web Server has dependencies on a number of Java ES shared components, all of which are automatically upgraded to Release 5 by the Java ES installer when you perform an upgrade of Web Server. These dependencies are listed in Table 1–7. Web Server has hard upgrade dependencies only on NSS and NSPR shared components.

  Backward Compatibility. Release 5 Web Server is backwardly compatible with the Release 4 version.

  Upgrade Rollback. Rollback of the Release 5 upgrade is achieved by reverting to the Release 4 installation, which remains intact.

Web Server Upgrade

This section describes how to perform an upgrade of Web Server from Release 4 to Release 5. This section covers the following topics:

• Pre-Upgrade Tasks

• To Verify Current Version Information

• Post-Upgrade Tasks

• To Roll Back the Upgrade

Pre-Upgrade Tasks

Before you upgrade Web Server you should perform the tasks described below.

Upgrading Web Server Dependencies

All Java ES components on a computer system and in a computing environment should be upgraded to Java ES Release 5. However, all shared components required by Web Server are upgraded automatically by the Java ES installer when you perform an upgrade of Web Server to Release 5.

Backing Up Web Server Data

The Web Server upgrade from Release 4 to Release 5 does not modify the existing configuration data, which is left intact. You do not need to back up current data.

To Verify Current Version Information

Type the following command:

WebServer6-base\https-hostName.domainName\start -version

This command returns the Web Server version information.

Release 5

Sun Java System Web Server 7.0

Release 4

Sun Java System Web Server 6.1 SP5

Upgrade Considerations

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

---

Note –

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.

  ---

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

To Verify the Upgrade

Type the following command:

WebServer6-base\https-hostName.domainName\start -version

This command returns the Web Server version information.

Release 5

Sun Java System Web Server 7.0

Release 4

Sun Java System Web Server 6.1 SP5

Post-Upgrade Tasks

The main post-upgrade task concerns performing manual migration, if needed, of certain Release 4 data. This is data normally associated with one or more virtual servers configured for Release 4 and specified in the server.xml configuration file.

For more information about data migration, see the Web Server 7.0 Installation and Migration Guide.

To Roll Back the Upgrade

1. Log in as administrator.

2. Stop all running Web Server instances one by one.

   WebServer7Config-base\https-configName\bin\stopserv

3. Remove the Release 5 Web Server installation.

   This step includes deleting all Release 5 instances and configurations.

4. Restart the Web Server instances that were stopped when upgrading Web Server.

   For more information, see To Upgrade Web Server.