Sun Java System Web Server 7.0 Update 4 Installation and Migration Guide

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:

The server being migrated and the Web Server 7.0 Administration Server must reside on the same host.
Commit all pending configuration changes made to the Sun ONE Web Server 6.0 and 6.1 instance through the Administration Server console GUI before migrating the instance.
Confirm that the existing Sun ONE Web Server 6.0 and 6.1 instance is working correctly before migrating the instance.
Stop the server you are migrating before the migrating settings.
If migrating from a Web Server version lower than 6.0, you must first migrate your legacy server to Web Server to 6.1, and then to Web Server 7.0. Direct migration from versions lower than 6.0 is not supported. After migrating from iPlanet Web Server 4.0 to 6.1, ensure that Web Server 6.1 works, then migrate to Web Server 7.0.

To Migrate From Non-Supported Linux Version

Sun Java System Web Server 7.0 supports Red Hat 3.0 Enterprise Server, Red Hat 4.0 Enterprise Server, and SUSE 9 Enterprise.

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

Stop the Web Server 6.0 or 6.1 instances.
Upgrade the Linux operating system to one of the Sun Java System Web Server 7.0 supported Linux versions.
Migrate the Web Server 6.0 or 6.1 instances to Sun Java System Web Server 7.0.

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

Archive the Web Server 6.0 or 6.1 installation directory, including all necessary resources like document root, libraries, and web applications.
Extract the archive to the system running Sun Java System Web Server 7.0.
Migrate the extracted Web Server 6.0 or 6.1 instances to Sun Java System Web Server 7.0.

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 Sun Java System Web Server 7.0 Update 4 Administrator’s Guide.

To Migrate Using the Graphical Interface

Access the Administration Server console and click the Configurations tab.

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

The Migrate Instances Wizard displays.

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.

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

The New Instance Wizard displays.

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.

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 Sun Java System Web Server 7.0 Update 4 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] [--passwordfile=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 6.1 to 7.0 using the same name for the migrated configuration as the 6.0 or 6.1 instance :

wadm> migrate-server [--user=admin-user] [--passwordfile=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 6.1 to 7.0 using a different name from the 6.0 or 6.1 instance for the migrated configuration:

wadm> migrate-server [--user=admin-user] [--passwordfile=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 6.1 to 7.0 using a different name from the 6.0 or 6.1 instance for the migrated configuration.

wadm> migrate-server [--user=admin-user] [--passwordfile=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 6.1 to 7.0 using a different name from the 6.0 or 6.1 instance for the migrated configuration.

--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 6.1 to 7.0 using a different name from the 6.0 or 6.1 instance for the migrated configuration. Specify a different log directory for migration logs:

wadm> migrate-server [--user=admin-user] [--passwordfile=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 6.1 to 7.0:

wadm> migrate-server [--user=admin-user] [--passwordfile=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.