This form allows you to install a second instance of your HTTP server, without running the installation program again. It creates a new directory for the server's configuration files, and shares program binaries with your existing server.

You will choose the initial values for the following variables:

The rest of the values will be set to the defaults, and will be configurable through the administrative interface.

Below is a list of the server binaries you have on your system. You should choose which type of server you wish to install. If the type of server isn't listed, you will need to install that server from the CD. You should choose the fully qualified domain name for your server here. If you are installing the second server for a custom domain, you should use that domain name here.

Remember that when you activate security on your server, the URL used to refer to the server will become https://www.[yourdomain].[dom]/ instead of just http. Next, choose an identifier that the administrative server will use for this server.

Examples:

One of the biggest reasons to install a second server to your machine is to have a single machine answer to multiple IP addresses. If you are doing this, then you need to tell this installation of the server which IP address it should listen to.

Note that you still need to configure your operating system to listen to both IP addresses. If you are not going to use the multiple IP address feature, you may leave this field blank. Another reason to install a second server to your machine is to have it listen to a different port. For example, you may want to run both a secure server and an unsecure server at the same time, on ports 443 and 80, respectively. You should enter the port number that the server will run on here. Next, choose a user that your server will run as. You may use an existing user that your other servers use, or create a new one and enter it here. The server creates a number of processes on your server machine when it starts up. These processes take turns answering requests. You can set the number of processes to achieve a balance between system load and request response time. The number should be determined by the number of requests you expect and the speed of the hardware your system runs on. On a low-demand system, the server may only need ten or twenty processes. On a very high demand system, you may want to use as many as eighty to a hundred processes.

You may set this number as high as you need to, however, if you decide to set it to a number higher than the size of your system's process table then you'll need to increase that.

Remember also that each server you install uses its own set of processes. You should take that into consideration when installing additional servers. If you are having trouble setting this number, consult your Server Reference Guide for more details. Finally, you should choose the document root for the new server. Remember that this is the directory which contains most of the documents for your server.