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.