The Servers Tab

The Servers tab allows you to configure server preferences, control who accesses the files on your web site, and use Secure Sockets Layer (SSL) to ensure privacy when communicating with other SSL-enabled products. The Server tab contains the following pages:

• The Manage Servers Page

• The Add Server Page

• The Remove Server Page

• The Migrate Server Page

The Manage Servers Page

---

The Manage Servers page allows you to set up the basic server configuration.

The following elements are displayed:

Select a Server. Lists all the servers.

---

Note	To display the Server Management tabs, choose a server from the drop-down list and click Manage.

---

The following information is displayed about the selected server:

Server Root. Displays the absolute path where the server's scripts, icons, and configuration files are stored.

Hostname. Displays the fully qualified host name of this server (for example, www.mozilla.com).

Error Log. Displays the directory path to the server error log. The error log contains all the errors the server has encountered; it also contains informational messages about the server, such as when the server was started, and any incorrect user authentication.

User (Unix/Linux). Specifies the user name under which the server runs. The server user should have restricted access to your system resources. You can often use a user named nobody in this situation. On some systems, however, nobody is not a valid user name. You may not want to give the user 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.

DNS. Displays whether DNS lookup of the IP address of the resource making a CGI request is enabled. DNS lookups can be resource intensive; therefore, allowing DNS lookups can slow performance, especially on a server that uses extensive CGI.

Help. Displays online help.

The Add Server Page

---

The Add Server page allows you to install multiple server instances and creates configuration files for each server instance on your system without going through the installation program. Each server instance can run on any TCP/IP port on your system, but you cannot run two web servers on the same port at the same time unless they are configured to respond to different IP addresses.

For more information, see Running Multiple Servers.

The following elements are displayed:

Server Name. Specifies the fully qualified host name of this server (for example, www.mozilla.com).

Server Port. Specifies the port number servicing HTTP requests. The default is port 80.

Server Identifier. Specifies the server identification that the Administration Server will use for this server instance (for example, marketing_server). The server identifier cannot start with a digit. Only Latin-1 characters are supported.

Server User (Unix/Linux). Specifies the user name under which the server runs. The server user should have restricted access to your system resources. You can often use a user named nobody in this situation. On some systems, however, nobody is not a valid user name. You may not want to give the user 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.

MTA Host. Specifies the name of the mail server that this server uses to send mail.

Always Attempt to Resolve IP Addresses into Host Names. Specifies whether to match IP addresses with corresponding host names. The server has the client IP address for a given client request. Some sites may wish to log all requests with their resolved DNS name instead of the IP address. Most of the time, a server does not need the DNS name.

Attempt to Resolve IP Addresses Only for Access Control and CGI. Specifies whether to match IP addresses with corresponding host names for access control lists (ACLs) and CGI. Sometimes, a site may want to use domain names instead of IP address in ACLs and CGI. Most of the time, a server does not need the DNS name.

Never Attempt to Resolve IP Addresses into Host Names. Specifies never to match IP addresses with corresponding host names.

Document Root. Specifies the directory path to the location of the server's web documents.

OK. Saves your entries.

Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

Help. Displays online help.

The Remove Server Page

---

The Remove Server page allows you to remove a server instance from your system. This process deletes the server's configuration files, and the directory server_root/servertype-id and its subdirectories.

For more information, see Removing a Server.

The following elements are displayed:

Select a Server. Specifies the server you want to remove. Removing the server will delete all the server's configuration files.

Yes, I Really Do Want to Remove This Server. Verifies that you want to delete the server.

OK. Saves your entries.

Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

Help. Displays online help.

The Migrate Server Page

---

The Migrate Server page allows you to migrate an Enterprise Server version 4.x instance to an iPlanet Web Server version 6.0.

---

Note	The migration preserves your old server instance, and creates a 6.0 server instance with the same configuration. You should stop the old server before migrating settings.

---

For more information, see the migration information in the iPlanet Web Server Installation and Migration Guide.

The following elements are displayed:

Migrate Server

Server Root. Specifies the directory path of the server instance from which to import the server's scripts, icons, and configuration files.

Search. After entering a server root, click Search. The server instances available in the server root you entered appear under Installed Servers.

Installed Servers

Select a Server to Migrate. Lists all the server instances installed in the server root specified above. Click Migrate to migrate the selected server instance.

Help. Displays online help.

The Migration Parameters Page

---

The Migration Parameters page contains the parameters for migrating an Enterprise Server 4.x instance to an iPlanet Web Server 6.0 instance.

The parameters you see depend on the configuration of the server instance you are migrating. The page is divided into the following possible sections:

• General Migration Parameters

• Users and Groups

• Keys and Certificates

• Document Root

• Search Collections

• Search Pattern Files

Click Migrate when you entered information in the parameter fields.

For more information, see the migration information in the iPlanet Web Server Installation and Migration Guide.

General Migration Parameters

These parameters always appear.

Server Name. The name of the new iPlanet Web Server 6.0 instance. It defaults to the name of the server instance from which you are migrating.

Run Server As (Unix/Linux). The Unix/Linux user name that runs the new server instance. The default is the username from the Administration Server 6.0.

Users and Groups

If you were using Users and Groups in a local database with Enterprise Server 4.x, you see the Users and Groups parameters. Export localdb to an LDIF file. Select this box if you want to migrate the user and group information in your local database. Selecting this box will export your database to an LDIF file. After you migrate your server, you need to import this file into the Directory Server.

Keys and Certificates

This section appears if you have security enabled. If security is not enabled, and you still want to migrate your certificate, you can do that using the Server Manager. See iPlanet Web Server Administrator's Guide for more information.

Key " ". This field name shows the name of the old server instance's key in quotes. Enter the key's password to migrate the key and certificate.

Document Root

This section always appears.

Use the same document root as the old server. Select this radio button if you want to use the old document root as your 6.0 document root. Choosing this option makes the documents from the old server visible on the 6.0 server. You must choose this option if you use web publishing or Netshare, otherwise you will lose all your web publishing and Netshare settings and data.

Use the new server's document root. Select this radio button to use the new server's document directory. If you want to see the old server's documents on your new server, you must manually copy them to the new location if you use this option.

Search Collections

This section appears if you have web publishing turned on and if you are using search collections. Your collections from the old server instance are listed. Select the box next to the name of each collection you want to migrate to 6.0.

Search Pattern Files

This section appears if you have web publishing turned on. Use the search pattern files to customize the search user interface. Only migrate pattern files if your old server's pattern files are customized. Click the Yes or No radio button.