Sun Java System Web Proxy Server 4.0.8 Installation and Migration Guide

Migrating Settings and Data

Caution – Caution –

Shut down the server instance that you want to migrate. The port number of this server instance is migrated.

ProcedureTo migrate the server instance

  1. In the Administration Server page, click the Server tab.

  2. Click Migrate Server.

  3. Enter the server root of the server from which you want to migrate, and click Search.

    For example:


    Proxy Server detects whether there are server instances installed in the directory you specified, and displays the servers you can migrate in the section called Installed Servers.

    Note –

    The Administration Server cannot be migrated. Direct migration from a Proxy Server version lower than 3.6 is not supported. You must first migrate your legacy server to Proxy Server 3.6, and then to Proxy Server 4.

  4. Select a server from the drop-down list, and click Migrate.

    The Migration parameters page is displayed. The sections that are displayed depend on the features Proxy Server is using and which components you installed. The following sections of parameters are possible:

    • General. This section allows you to specify the server name and the UNIX user name.

      • Server name. Specify the name of the new Proxy Server instance.

      • User. (UNIX) Specify the UNIX user name that runs the new server instance. The default is the user name of the server instance as specified in the magnus.conf file of the old server if the administration user of the Proxy Server 4 installation is root. Otherwise, it is set to the Proxy Server 4 administration user name.

      Users and Groups. The migration tool checks in the dbswitch.conf file whether a local database is configured for the 3.6 instance and displays this section. You can export the local database to LDIF using the following option:

      • Export Localdb to LDIF File. Specify whether you want your local database exported to an LDIF file.

      Keys and Certificates. This section is displayed only if security (SSL) is enabled on the Proxy Server 3.6 instance. Certificates are migrated from the 3.6 versions to the supported NSS format. The old key password has to be provided.

    • Cache Settings. You can specify the cache directory and capacity.

      • Cache directory. Specify a new cache directory for the migrated server. The value <default> corresponds to ProxyServer4_installroot/ProxyServer_name/cache.

      • Cache capacity. Specify the capacity of the cache to be configured on the server. The cache size can range between 125 MB to 32000 MB. The default value of the cache capacity field on UNIX is the capacity of the Proxy Server 3.6 instance that is being migrated whereas on Windows the field displays 125 MB.

  5. Click the Migrate button.

    The Migration Log page appears. It shows the results of the migration, whether the migration succeeded or failed. It includes the parameters successfully migrated and the parameters you need to migrate manually. It also includes information about database settings and configuration file creation and shows any features of the 3.6 server that are not supported in the new version.

    The log page displays Assimilation Complete if the migration succeeded. The new server was created, but not started. To run the old instance in parallel with the new server instance, change the port number of the new server before starting it. To configure the migrated server using the Server Manager interface, click the Configure Migrated Server button.

    The log page displays Assimilation Failed if migration failed. If an error is encountered at any stage of the migration process, migration stops. Error messages provide information that will help you diagnose and fix any problems, so you can then retry migration.