Oracle iPlanet Web Server 7.0.9 Installation and Migration Guide

Chapter 5 Migrating to Web Server 7.0

This chapter describes the migration of Sun ONE Web Server 6.0 and Sun Java System Web Server 6.1 configurations to Web Server 7.0.

This chapter contains the following sections:

Migration Overview

Web Server 7.0 enables you to migrate server instances from Sun ONE Web Server 6.0 and Sun Java System Web Server 6.1. For a general overview of this terminology and distinction, see New Administration Framework.

You must first migrate the Web Server 6.0 and 6.1 instance to create a Web Server 7.0 configuration. The Web Server 7.0 configuration is then used to create a Web Server 7.0 instance. Web Server 7.0 includes a new command-line interface for migration, so migration can now be performed either from the graphical interface or from the command line. See Migrating Using the Graphical Interface or Migrating Using the Command-Line Interface for specific procedures.


Note –

The server being migrated and the Web Server 7.0 Administration Server must reside on the same host. However, an instance can be created on an associated remote node.


Only Sun ONE Web Server 6.0 and Sun Java System Web Server 6.1 instances can be migrated. Direct migration from earlier product versions is not supported. To migrate earlier versions, first migrate them to Sun Java System Web Server 6.1 and confirm that the migration is successful. For information see the latest Sun Java System Web Server 6.1 documenation collection at http://docs.sun.com/prod/sjs.websrv61#hic.

Detailed migration information is provided during and after the migration process in the migration log file. It lists the settings and configurations that were and were not migrated, warns about required manual changes, and indicates whether the migration succeeded or failed. For more information about this file, see Viewing the Migration Log File. Many but not all settings are migrated, as described in What Is and Is Not Migrated.

A configuration is created during the migration process. Following migration, the configuration is available in the install-dir/admin-server/config-store directory. As mentioned earlier, Web Server 7.0 server instances are created from these configurations using either the administration GUI or CLI. If a configuration exists with the same name, -x is added to config_name, where x is an integer.

What Is and Is Not Migrated

Many but not all settings are migrated. This section lists what is and is not migrated during migration.

What Is Migrated

The following are migrated by the migration tool:

What Is Not Migrated

The following are not migrated by the migration tool:

Files Requiring Manual Migration

Command-line scripts are not migrated to Web Server 7.0. The default command-line scripts will be created, and you must make any necessary changes in the relevant Web Server 7.0 command-line scripts.

The following command-line scripts are not migrated:

Configuration File Changes

In previous releases, server configuration was spread over multiple files. In Web Server 7.0, server configuration has been consolidated for better manageability. Many changes have been made to consolidate instance-specific configuration files in the config directory and to simplify and enhance existing configuration files. In general, no new configuration files have been added, some configuration files have been removed, and significant changes have been made to files carried forward from previous releases, such as server.xml and magnus.conf.

Some configuration file changes are briefly mentioned here but are not described in detail. For complete information about configuration file changes in Web Server 7.0, see the Web Server 7.0 Administrator's Configuration File Reference.

Configuration Files Removed

The following configuration files have been removed in Web Server 7.0:

For more information, see File Layout Changes.

File Layout Changes

The following table lists file layout changes between Sun Java System Web Server 6.1 and Web Server 7.0. These changes are made automatically during migration.

For information about changes made in Sun Java System Web Server 6.1 and earlier product versions, see the latest Sun Java System Web Server 6.1 documenation collection at http://docs.sun.com/prod/sjs.websrv61#hic.

Table 5–1 File Layout Changes

Web Server 6.1 

Web Server 7.0 

install_root/alias/https-server_id-hostname-certx.db

install-dir/https-server_id/config/certx.db, where x=7 or 8 (Web Server 7.0 supports both cert7 and cert8)

install_root/alias/https-server_id-hostname-key3.db

install-dir/https-server_id/config/key3.db

install_root/alias/secmod.db

install-dir/https-server_id/config/secmod.db

install_root/httpacl/generated.https-server_id.acl

install-dir/https-server_id/config/default.acl

install_root/httpacl/genwork.https-server_id.acl

Removed 

install_root/userdb/certmap.conf

install-dir/https-server_id/config/certmap.conf

install_root/userdb/dbswitch.conf

Removed; functionality moved to the auth-db element in server.xml.

instance-dir/config/nsfc.conf

Removed; functionality moved to the file-cache element in server.xml.

instance-dir/config/snmp.conf

Remove; functionality moved to the snmp element in server.xml.

admsrv_dir/config/scheduler.conf

Removed; functionality moved to the event element in server.xml and entries migrated to Web Server 7.0 (no manual changes are required).

admsrv_dir/config/schedulerd.conf

Removed 

instance-dir/config/*.clfilter

Removed 

instance-dir/config/magnus.conf

install-dir/https-server_id/config/magnus.conf

Retained for NSAPI plug-in configuration, but all functionality not related to NSAPI plug-ins has been moved to server.xml. Support for some obsolete directives has been dropped. The magnus.conf file is copied into the new server configuration during migration. If any removed or obsolete directives are found, a warning is issued.

The following new elements will be created in server.xml:

  • access-log

  • access-log-buffer

  • acl-cache

  • cgi

  • dns

  • dns-cache

  • http

  • keep-alive

  • localization

  • pkcs11

  • qos

  • ssl-session-cache

  • stats

  • temp-path

  • thread-pool

  • user

For detailed information about these changes, see the Web Server 7 Administrator's Configuration File Reference.

instance-dir/config/obj.conf

install-dir/https-server_id/config/obj.conf

Retained. In Web Server 6.1, all virtual servers within a given VSCLASS shared a common obj.conf. In Web Server 7.0, each virtual server can have its own obj.conf, or can still share the same obj.conf. For detailed information about these changes, see Chapter 6, Syntax and Use of obj.conf, in Oracle iPlanet Web Server 7.0.9 Administrator’s Configuration File Reference and Chapter 2, Configuration, Instances, and Nodes, in Oracle iPlanet Web Server 7.0.9 Administrator’s Guide

instance-dir/config/server.xml

install-dir/https-server_id/config/server.xml

Most of the attribute names have changed. Some elements have been consolidated and some have split. For detailed information about these changes, see the Web Server 7.0 Administrator's Configuration File Reference.

The Web Server 6.0 or 6.1 server.xml file is parsed and the values written in the new server.xml file, which is created during migration.

server_instance/config/mime.types

install-dir/https-server_id/config/mime.type

During migration, the mime.types file of the old instance in the server_instance/config/mime.types directory is migrated into the new server_instance/config directory. Non-default mime.types (mime1.types, mime2.types, and so on) in the old server_instance/config directory and listed in the MIME element of server.xml are migrated into the new server_instance/config directory.

Other Migration-Related Changes

The following sections contain information on other migration-related changes when moving from Web Server 6.1 to Web Server 7.0. These changes are made automatically during migration.

Content-type Header

After migration from 6.1, Web Server 7.0 will not return Content-type:text/html when there is no message body, for instance, a redirection location header. Since response doesn't contain the message body, there's no reason to specify a Content-Type header hence this is a conscious change made in 7.0 as compared to 6.1. For customers who still depend on Content-type can make the following configuration changes in 7.0.

To add back the content-type in output stage

Add the following content into Web Server 7.0 obj.conf


Service method="(GET|HEAD)" type="magnus-internal/directory" fn="index-common"
Service method="(GET|HEAD|POST)" type="*~magnus-internal/*" fn="send-file"
Service method="TRACE" fn="service-trace"
<If $uri =~ ".jsp$">
Output fn="set-variable" insert-srvhdrs="Content-type: text/html"
</If>
Error fn="error-j2ee"
AddLog fn="flex-log"
</Object>

When content-type is 302


<If  $code = "302" >
Output fn="set-variable" insert-srvhdrs="content-type:text/html"
</If>

When content-length is zero


<If $srvhdrs{'content-length'} = "0">
Output fn="set-variable" insert-srvhdrs="content-type:text/html"
</If>

Config Store Directory

As described in New Administration Framework, Web Server 7.0 makes it easier to manage Web Server configurations across hardware nodes in a server farm. This administration framework provides necessary services to graphical and command-line clients to manage server configurations, and to replicate configurations across nodes within data centers or server farms.


Caution – Caution –

Do not edit any files under config-store directory. The files under this directory are created by Web Server for internal use.


Metadata for the configurations managed by the administration infrastructure is stored within a directory called config-store, under the root directory of the Administration Server instance. When a server is migrated, data is transferred and a configuration is created under config-store. Configuration files, applications, and other elements that are part of a configuration are stored in config-store, as are search collections if a different search collection index directory is not specified during migration (for more information, see Search). Web Server 7.0 instances are created from these configurations.

For more information about the config-store directory structure and about configuration files, see the Web Server 7.0 Administrator's Configuration File Reference. For more information about managing Web Server configurations in data centers and server farms, see the Oracle iPlanet Web Server 7.0.9 Administrator’s Guide.

JNDI and JDBC

The following table lists changes related to Java Naming and Directory Interface (JNDI) and JDBC.

Table 5–2 Changes Related to JNDI and JDBC

Change in Web Server 7.0 

Description 

JDBCRESOURCE and JDBCCONNECTIONPOOL element changes

The JDBCRESOURCE and JDBCCONNECTIONPOOL elements in server.xml have been consolidated into the jdbc-resource element.

For each existing JDBCRESOURCE, a corresponding jdbc-resource element will be created in the new server-instance/config/server.xml.

Element name changes in server.xml

The following element names have changed: 

  • MAILRESOURCE is now mail-resource.

  • CUSTOMRESOURCE is now custom-resource.

  • EXTERNALJNDIRESOURCE is now external-jndi-resource, and most of the attribute names have also changed.

Legacy Servlets

There are no changes to this functionality from Web Server 6.1 to Web Server 7.0. For more information on legacy servlets, see Migrating Legacy Servlets in Oracle iPlanet Web Server 7.0.9 Developer’s Guide to Java Web Applications

Log Files

Log files are not migrated.

Search

When migrating search, necessary server.xml changes are made and the collections directory from the Web Server 6.1 server instance is moved to the search collection index directory specified during migration. If the directory is not specified, the search collection will not be migrated.

Also note the following considerations:

The following table lists other changes related to search.

Table 5–3 Changes Related to Search

Changes in Web Server 7.0 

Description 

Element changes in server.xml

  • SEARCH is now called search-app.

  • SEARCHCOLLECTION is now called search-collection-copy-path.

  • The PROPERTY subelement has been removed from SEARCHCOLLECTION.

  • The WEBAPP subelement has been removed, a uri attribute has been added to point to the search web application, and most of the attribute names have changed.

search-collection-copy-path

Specifies the path to which search collection information will be copied when migrating search collections. The following migration scenarios are possible: If the Web Server 6.0 or 6.1 search collection path is outside the Web Server 6.0 or 6.1 instance, then the migrated search collection path will point to the Web Server 6.0 or 6.1 search collection path, and this option will be disregarded. If the Web Server 6.0 or 6.1 search collection path is within the Web Server 6.0 or 6.1 instance, and a valid path is specified for this option, then the search collection information will be copied to the following directory: searchCollectionPath/configName/virtualServerName/collectionName. If the specified path is not valid, an error message will be logged. If the Web Server 6.0 or 6.1 search collection path is within the Web Server 6.0 or 6.1 instance but no path is specified for this option, then the search collection information will not be copied. A message will be written to the migration log asking the user to manually copy the search collection information using the wadm add-search-docs command. In this case, the migrated search collection path will be the following: WebServer7Config-base/https-configName/config/collections/virtualServerName/collectionName.

Security

The following table lists changes related to security.

Table 5–4 Changes Related to Security

Changes in Web Server 7.0 

Description 

SECURITY element moved and renamed security (all lower case)

In Web Server 6.1, the SECURITY element was under the JAVA element in server.xml. In Web Server 7.0, the JAVA element has been split into two elements: jvm and servlet-container. In Web Server 7.0, the security element is under the servlet-container element and is called security (all lower case) instead of SECURITY. The necessary changes are made in the new server_instance/config/server.xml.

Servlet Container

The following table list changes related to servlet container.

Table 5–5 Changes Related to Servlet Container

Changes in Web Server 7.0 

Description 

Decode Cookies 

In Web Server 6.1, + in cookie values were not decoded. However, in Web Server 7.0 the plus + is decoded to spaces. The default value is false.

Session Manager

There are no changes to this functionality from Web Server 6.1 to Web Server 7.0.

User Libraries

User libraries are not migrated. A warning message is recorded in the migration log file.

Web Applications

The following table lists changes related to web applications.

Table 5–6 Changes Related to Web Applications

Changes in Web Server 7.0 

Description 

WEBAPP element changed in server.xml

The WEBAPP element is now called web-app and has been moved under the virtual-server element. The changes are made in the new install-dir/admin-server/config-store/config_name/config/server.xml. Changes are also be made in the sun-web.xml and web.xml files for the web applications. If the web application was located inside the old install-dir, it is physically migrated and changes are made in sun-web.xml and web.xml files of the web applications else, the web applications path element in the migrated server.xml is modified to point to the old web application directory. No changes will be made to sun-web.xml and web.xml. A warning message is recorded in the migration log file to manually edit these XML files.

 

WebDAV

The following table lists changes related to WebDAV.

Table 5–7 Changes Related to WebDAV

Changes in Web Server 7.0 

Description 

Element changes in server.xml

  • DAV is now called dav.

  • DAVCOLLECTION is now called dav-collection.

  • The PROPERTY subelement has been removed.

  • The dav-collection subelement has been moved under the virtual-server element and most of the attribute names have changed. The necessary changes are made in server.xml.

Changes to obj.conf

Necessary modifications are made in the obj.conf file. Specifically:

  • ACL and REPORTS are added in the default object's service-dav list of methods. For example:

    <Object name="default">
    ...
    Service fn="service-dav"
    method="(OPTIONS|PUT|DELETE|COPY
    |MOVE|PROPFIND|PROPPATCH|LOCK
    |UNLOCK|MKCOL|ACL|REPORT)"
    Error fn="error-j2ee"
    AddLog fn="flex-log"
    name="access"
    <Object>
  • ACL and REPORTS are added in the dav object's service-dav list of methods. For example:

    <Object name="dav"
    PathCheck fn="check-acl"
    acl="dav-src"
    Service fn="service-dav"
    method="(GET|HEAD|POST|PUT|DELETE
    |COPY|MOVE|PROPFIND|PROPPATCH|LOCK
    |UNLOCK|MKCOL|ACL|REPORT)"
    </Object>

New ACL entry in default.acl

The following new ACL entry is added in default.acl only if the dav-src ACL exists in generated.https-server_id.acl:

acl uri=/magnus-internal/";
deny (all) user="anyone";
allow (list) user="all";

Migrating From Web Server 6.0 and 6.1 to Web Server 7.0

This section describes how to migrate Web Server 6.0 and 6.1 to Web Server 7.0 using both the graphical and the command-line interfaces. Note the following considerations:

To Migrate From Non-Supported Linux Version

Linux versions supported by the Web Server 7.0.9 are listed in Release Notes, see Supported Platforms in Oracle iPlanet Web Server 7.0.9 Release Notes

If you are using a non-supported Linux version, you must perform one of the following tasks to upgrade to the Web Server 7.0.9. You can perform the following task in Java ES environment as well.

  1. Stop the Web Server 6.0 or 6.1 instances.

  2. Upgrade the Linux operating system to one of the Web Server 7.0.9 supported Linux versions.

  3. Migrate the Web Server 6.0 or 6.1 instances to Web Server 7.0.9.


    Note –

    You must upgrade the Linux operating system to one of the supported versions.


or

  1. Archive the Web Server 6.0 or 6.1 installation directory, including all necessary resources like document root, libraries, and web applications.

  2. Extract the archive to the system running Web Server 7.0.9.

  3. Migrate the extracted Web Server 6.0 or 6.1 instances to Web Server 7.0.9.


    Note –

    Ensure that the directory structure is the same as in Web Server 6.0 or 6.1.


Resolving Service ID Conflicts on Windows

On Windows, creating an instance for any configuration registers a service-id with Windows services. If the service-id exists, there is a service-id conflict and the instance creation fails. For example, you might migrate a 6.0 or 6.1 instance named foo. If the foo service-id exists, the creation fails.

To avoid the conflict, during migration, change the configuration name using either the CLI or the Admin Console. Another option is to copy the configuration to a new configuration that uses a unique service-id. Use either the wadm> copy-config command, or the Copy button on the Admin Console Configurations page to copy the configuration.

Migrating Using the Graphical Interface

The following procedure describes how to migrate server instances using the graphical interface. There are two distinct phases to the migration process. You first migrate data from a 6.0 or 6.1 instance to create a Web Server 7.0 configuration, and then deploy that configuration on a node to create a Web Server 7.0 instance.


Note –

For detailed information about these and other tasks performed using the Administration Server console, see the Oracle iPlanet Web Server 7.0.9 Administrator’s Guide.


ProcedureTo Migrate Using the Graphical Interface

  1. Access the Administration Server console and click the Configurations tab.

  2. In the Configuration Tasks table on the resulting Tasks screen, click Migrate Configuration.

    The Migrate Instances Wizard displays.

  3. In the wizard:

    1. Supply the absolute path to the installation directory of the 6.0 or 6.1 Web Server you want to migrate, then click Next.

    2. The Instances selection screen appears.

    This wizard creates a configuration in the config-store directory of the Web Server 7.0 Administration Server. You will then use this configuration to create a server instance, as described in the following steps.


    Note –

    Before creating the instance from the migrated configuration, it is imperative that you review the migration log file and fix any issues. For information about accessing the migration log, see Viewing the Migration Log File.


  4. In the Configuration Tasks table on the Tasks screen, click New Instance.

    The New Instance Wizard displays.

  5. In the wizard:

    1. Select the configuration you migrated and click Next.

    2. Select the nodes on which to create an instance of the configuration and click Next.


      Note –

      If you want to migrate to another host than while creating an instance select the remote node.


    3. Verify the information on the summary page and click Finish.

  6. Start the migrated server and ensure that the server is working properly.

Migrating Using the Command-Line Interface

The migrate-server command is used to migrate server instances and create Web Server 7.0 configurations using the administration command-line interface (CLI).

The wadm utility is located in install-dir/bin. For detailed information about using the administration CLI, see the man pages and the Oracle iPlanet Web Server 7.0.9 CLI Reference Manual document. For basic information that will help you get started, also see Using the Administration Command-Line Interface in this document.

The migrate-server syntax is as follows:

wadm> migrate-server [--user=admin-user] [--password-file=admin-pswd-file][--host=admin-host][--port=admin-port][--no-ssl][--rcfile=rcfile][--echo][--no-prompt][--verbose][--search-collection-copy-path=directory][--log-dir=directory]([--all|[--config=newconfigname[--instance=instancename]) --server-root=path

The following examples demonstrate how to use the command-line interface to migrate one or several server instances.

Migrating a Single Instance

The following is an example of using the CLI to migrate a single instance from Sun ONE Web Server 6.0 or Sun Java System Web Server 6.1 to Oracle iPlanet Web Server 7.0 using the same name for the migrated configuration as the Sun ONE Web Server 6.0 or Sun Java System Web Server 6.1 instance :

wadm> migrate-server [--user=admin-user] [--password-file=admin-pswd-file][--host=admin-host][--port=admin-port][--no-ssl][--rcfile=rcfile][--echo][--no-prompt][--verbose][--search-collection-copy-path=directory][[--log-dir=directory]([--all|[--config=newconfigname[--instance=instancename]) --server-root=path

--instance=instance_name
--server-root=6.xwebserver_install_root

where, for example, 6.xwebserver_install_root might be/opt/SUNWwbsvr and instance_name might be https-foo.com.

The following is an example of migrate a single instance from Sun ONE Web Server 6.0 or Sun Java System Web Server 6.1 to Oracle iPlanet Web Server 7.0 using a different name from the Sun ONE Web Server 6.0 or Sun Java System Web Server 6.1 instance for the migrated configuration:

wadm> migrate-server [--user=admin-user] [--password-file=admin-pswd-file][--host=admin-host][--port=admin-port][--no-ssl][--rcfile=rcfile][--echo][--no-prompt][--verbose][--search-collection-copy-path=directory][[--log-dir=directory]([--all|[--config=newconfigname[--instance=instancename]) --server-root=path

--instance=instance_name
--config=new-foo
--server-root=6.xwebserver_install_root

where, for example, 6.x webserver_install_root might be/opt/SUNWwbsvr and instance_name might be https-foo.com.

The following is an example to migrate single instance from Sun ONE Web Server 6.0 or Sun Java System Web Server 6.1 to Oracle iPlanet Web Server 7.0 using a different name from the Sun ONE Web Server 6.0 or Sun Java System Web Server 6.1 instance for the migrated configuration.

wadm> migrate-server [--user=admin-user] [--password-file=admin-pswd-file][--host=admin-host][--port=admin-port][--no-ssl][--rcfile=rcfile][--echo][--no-prompt][--verbose][--search-collection-copy-path=directory][[--log-dir=directory]([--all|[--config=newconfigname[--instance=instancename]) --server-root=path

--instance=instance_name
--config=new-foo
--server-root=6.xwebserver_install_root

where, for example, 6.x webserver_install_root might be/opt/SUNWwbsvr and instance_name might be https-foo.com.

The following is an example of migrate single instance from Sun ONE Web Server 6.0 or Sun Java System Web Server 6.1 to Oracle iPlanet Web Server 7.0 using a different name from the Sun ONE Web Server 6.0 or Sun Java System Web Server 6.1 instance for the migrated configuration.

wadm> migrate-server [--user=admin-user] [--password-file=admin-pswd-file][--host=admin-host][--port=admin-port][--no-ssl][--rcfile=rcfile][--echo][--no-prompt][--verbose][--search-collection-copy-path=directory][--log-dir=directory]([--all|[--config=newconfigname[--instance=instancename]) --server-root=path

--instance=instance_name
--config=new-foo
--search-collection-copy-path=custom_path
--server-root=6.xwebserver_install_root

where, for example, 6.x webserver_install_root might be/opt/SUNWwbsvr and instance_name might be https-foo.com.

The following is an example of migrate single instance from Sun ONE Web Server 6.0 or Sun Java System Web Server 6.1 to Oracle iPlanet Web Server 7.0 using a different name from the Sun ONE Web Server 6.0 or Sun Java System Web Server 6.1 instance for the migrated configuration. Specify a different log directory for migration logs:

wadm> migrate-server [--user=admin-user] [--password-file=admin-pswd-file][--host=admin-host][--port=admin-port][--no-ssl][--rcfile=rcfile][--echo][--no-prompt][--verbose][--search-collection-copy-path=directory][[--log-dir=directory]([--all|[--config=newconfigname[--instance=instancename]) --server-root=path

--instance=instance_name
--config=new-foo
--search-collection-copy-path=custom_path
--log-dir=log_path
--server-root=6.xwebserver_install_root

where, for example, 6.x webserver_install_root might be/opt/SUNWwbsvr and instance_name might be https-foo.com.

Migrating All Instances

The following is an example of using the CLI to migrate all instances from Sun ONE Web Server 6.0 or Sun Java System Web Server 6.1 to Oracle iPlanet Web Server 7.0:

wadm> migrate-server [--user=admin-user] [--password-file=admin-pswd-file][--host=admin-host][--port=admin-port][--no-ssl][--rcfile=rcfile][--echo][--no-prompt][--verbose][--search-collection-copy-path=directory][[--log-dir=directory]([--all|[--config=newconfigname[--instance=instancename]) --server-root=path

-all=true
--server-root=6.xwebserver_install_root

where, for example, 6.x webserver_install_root might be/opt/SUNWwbsvr.

Verifying Migration

To verify migration:

Viewing the Migration Log File

Detailed migration information is provided during and after the migration process, listing the settings and configurations that were and were not migrated, warning about changes that need to be made manually, and indicating whether the migration succeeded or failed. This information is recorded in the migration log file. The syntax for the migration log file is as follows:

MIGRATION_yyyymmddhhmmss.log

For example, if the log directory specified during installation (--logdir) is /ws7, and the migration process was started on 01/08/2006 at 11:16 PM, the following file is created under the /ws7 directory: MIGRATION_20060108111600.log. If no log directory was specified during installation, the file with the same name is created under the install-dir/admin-server/logs directory.


Note –

If you select the All Instances Migration option, all the instances migration log are stored in the same migration log file.


Creating a Server Instance from the Migrated Configuration

The create-instance command creates the Web Server instance from the configuration. So if migrate-server creates a configuration called foo, the create-instance command creates the instance https-foo using the configuration install-dir/admin-server/config-store/foo in the specified node. The syntax is create-instance --config=config_name host_name.domain_name.

The migrate-server CLI command removes the prefix https- from the old instance and uses that name as the configuration name, while the create-instance command adds the prefix https- to the configuration name and uses that name as the instance name.

Updating Your Sun Java Enterprise System Installation

For information about upgrading Web Server from a previous Java ES release to Sun Java Enterprise System Web Server (Java ES Release 5), see the Sun Java Enterprise System Upgrade Guide in the Java ES system documentation at http://docs.sun.com/app/docs/prod/entsys#hic.