![]() | |
Sun Java System Web Proxy Server User Interface |
The Servers Tab
The Servers tab is used to manage, add, remove, and migrate Proxy Server instances. The tab contains the following pages:
The Manage Servers PageThe Manage Servers page is used to view and administer the server instances that are installed on your system.
The following elements are displayed:
Instance. Lists all Proxy Server instances. Click an instance to access the Server Manager and manage server settings.
Status. Shows whether an instance is started or stopped.
HostName. Shows the host name of the server.
DNS. Shows whether the server performs DNS lookups on clients’ IP addresses that access the server. DNS lookups can be resource intensive and can slow performance. DNS resolution is off by default.
User. (UNIX/Linux) Shows the user name under which the server runs. The server user should have restricted access to system resources. A user named nobody can often be used, but on some systems is not a valid name. You may not want to give nobody group access to all files. If you do not use nobody, create a new UNIX/Linux user such as adm to be the server user.
The Add Server PageThe Add Server page is used to install additional server instances without re-running the installation program. Each server instance can run on any TCP/IP port on your system, but two Proxy Servers cannot be run on the same port at the same time unless they are configured to respond to different IP addresses. For more information, see "Running Multiple Proxy Servers" in the Proxy Server Administration Guide.
The following elements are displayed:
Server Name. Specify the fully qualified host name of the server (for example, www.example.com).
Server Port. Specify the port number to be used for servicing HTTP requests. The default is 8080. Legal values are 1-65535. On UNIX®, creating sockets that listen on ports 1-1024 requires superuser privileges.
Server Identifier. Specify the server identification to be used for this server instance (for example, marketing_server). The server identifier cannot start with a digit. Only ASCII characters are supported.
Server User. (UNIX/Linux) Specify the user name under which the server runs. The server user should have restricted access to system resources. A user named nobody can often be used, but on some systems is not a valid name. You may not want to give nobody group access to all files. If you do not use nobody, create a new UNIX/Linux user such as adm to be the server user.
OK. Creates a new Proxy Server instance.
Reset. Erases your changes and resets the elements in the page to the values that they contained before your changes.
The Remove Server PageThe Remove Server page is used to remove server instances from your system. For more information, see "Removing a Server Instance" in the Proxy Server Administration Guide.
The following elements are displayed:
Select a Server. From the drop-down list, select the server you want to remove.
Confirming Server Removal. Select this checkbox to confirm removal of the server and its associated files.
OK. Removes the Proxy Server instance.
Reset. Erases your changes and resets the elements in the page to the values that they contained before your changes.
The Migrate Server PageThe Migrate Server page is used to migrate a Proxy Server 3.6 server instance to Proxy Server 4.0. For more information about migrating a server and its settings, see the Proxy Server Installation and Migration Guide.
Note the following:
- Before migrating settings, stop the server you are migrating.
- 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.0.
- Migration preserves your old server instance and creates a 4.0 instance with the same configuration.
The following elements are displayed:
Migrate Server
Server Root. Specify the path to the root directory of the Proxy Server 3.6 instance that you want to migrate. For example:
/usr/netscape/suitespot
C:\netscape\suitespot
Search. Click this button after entering a server root. Version 3.6 server instances that are available for migration are displayed under Installed Servers.
Installed Servers
Select a Server to Migrate. Lists all server instances that are installed in the server root specified in the Server Root field. From the drop-down list, select the server you want to migrate.
Migrate. Click this button to migrate the specified server. The Migration Parameters page displays.
The Migration Parameters PageThe Migration Parameters page contains the parameters for migrating a Proxy Server 3.6 instance to Proxy Server 4.0. The parameters that display are based on the configuration of the server instance being migrated. For more information about server migration, see the Proxy Server Installation and Migration Guide.
The Migration Parameters page has the following sections:
- Server and user fields. These settings always display:
- Users and groups. This section displays only if a local database, not an LDAP-based directory service, is configured on the Proxy Server 3.6 instance.
- Keys and certificates. This section displays only if security (SSL) is enabled on the Proxy Server 3.6 instance. Certificates are migrated from the 3.6 versions to the supported Network Security Services (NSS) format.
- Cache settings. These settings always display.
- Buttons. These buttons always display.
- Migrate. Migrates parameters. The Migration Log page displays, showing what has and has not been migrated, and if the migration was successful.
- Reset. Erases your changes and resets the elements in the page to the values that they contained before your changes.
- Cancel. Cancels migration and returns you to the Migrate Server page.
The Migration Log PageThis page shows the results of your migration, listing the settings and configurations that were and were not migrated, and whether the migration succeeded or failed. The elements displayed on this page depend on the configuration of the server instance being migrated, and include information about database settings, configuration file creation, and so on. The following elements also display to indicate whether migration succeeded or failed:
Assimilation complete. Migration succeeded. The new server was created, but not started. You should either stop the 3.6 server and start the newly created one, or 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.
Assimilation failed. 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.