(Apache 2.2.19 Page 2 of 3)

Prepare for Apache 2.2.19 installation :

Before we begin our Installation of Apache HTTP server 2.2.19, as we do with other major programs like PHP or MySQL that we intend to install along side Apache, we should note some system specific steps according to our Operating System.

For Vista, 2008 & 7, updating key configurations may be ignored if you have not set your permissions correctly for use with User Account Control (UAC). If you use UAC, configuration changes may be stored in the hidden user folder C:\ProgramData which the program expects to be made to files in C:\Program Files, C:\Windows etc. Config files in this folder can also cause problems when re-installing software. You should either know how to use UAC to grant the safest highest Privilege Levels or totally disable UAC by sliding the level controller into the Never Notify position. If you suspect UAC is causing you grief, this is a good simple UAC troubleshooting guide from Microsoft.com.

Most can skip this Port:80 check unless you have a problem testing your install at the end of this tutorial. Apache does not share the same TCP/IP port as other applications on the Windows Operating System. Other programs listening on port 80 (such as Skype or IIS) need to be stopped, uninstalled or have their configuration changed to an alternative port. To see what ports are in use, you can call up the command prompt [a Dos Box (Fig 00)] and type: netstat -n -a -b [press enter]. The resulting list informs you which port numbers are in use under the Local Address column (next to the name of the program which owns it). Type exit [then press enter] to close the DOS window.

Checking for Port :80 Conflicts
(Fig. 00)

The install package does offer an alternative (port:8080) which will get around the port conflict issue as discussed in the "server information" section. If you chose this route, you will need to ensure you specify :8080 in your target urls. (eg. http://localhost:8080/index.html etc.)

You should have now downloaded your install file, and be ready to proceed to the next step and begin the software installation part of this tutorial.

Begin the installation:

Start your downloaded file: httpd-2.2.19-win32-x86-no_ssl.msi (double click or right click/run) and this training module will help step you through the data input selections the wizard will ask of you. The wizard starts with the following start-up screen (Fig. 01):

Starting the Apache HTTP Server 2.2 installation wizard
(Fig. 01)

The Administrator will be wise to note that this same installer file can also be started to modify/repair/remove an existing installation. As this is our first installation, the only option we will be presented with is to install the server software. Select next to move to the next part of our Apache HTTP server 2.2 installation.

Accepting the License Agreement:

The second window loads the License agreement into the viewing panel (Fig. 02). The provided scroll bar enables you to view the entire contents of the agreement. Check over the details to be sure you are happy and willing to comply and accept the conditions as laid out for your use of the software. If all is acceptable, select the radio button in front of the phase I accept the terms in the license agreement and then choose next to continue the installation process.

Apache HTTP Server 2.2 License Agreement Screen
(Fig. 02)

The Apache user community:

Our next window (Fig. 03) is quite brief and will give us some useful information like where to subscribe should there be desire to keep abreast of new code releases, bug fixes, security fixes and other general news or information for your Apache server. Visit, bookmark or subscribe to anything of interest and then choose next to move to the next stage of the installation process.

Introducing the Apache HTTP Server community
(Fig. 03)

Entering your Server Information:

Our next window (Fig. 04) is of extreme interest to the Website Administrator as it defines our exact network location in terms of our DNS domain.

If we were establishing a www set-up, this step would be of elevated importance and would look something like this: server.mydomain.com. This full name would be our Server Name (The second line in our form in Fig. 04).

mydomain would of course be replaced with the duly registered domain name of your website (or that of your dns server).

Our network name is the last part of this address: i.e. mydomain.com (This becomes the first line in our form in Fig. 04).

Notes: Configuring your Apache Server at Home or Home Office For the Web. A DNS (Domain Name Server) is like a large telephone book which computers on the internet use to locate a website address. Most people like names better than a bunch of numbers. For example, if you go to 72.14.213.99 in your web browser, you will see you have arrived at Google.com. Most people would rather remember www.google.com over a series of dots and numbers anyday. Having a DynDNS can assist in resolving this issue and the next.

Many home users have an ISP (internet service provider) connection that regularly changes their IP number. The full DNS number also changes and so the home-based web server can not be found at a single constant address for an extended length of time. The home http server needs to be re-configured with the new number each time a change happens. And because the website link has changed, they must also follow up each friend or client and give them this new numbered address. Some ISP's will supply a permanant IP at extra cost but this is not quite the same thing as owning an IP number. If you decide to change the ISP, this IP number will change too.

However, now home users can get a personal free DynDNS (see link below) that will solve this problem. This is very easy to configure and much like the instructions we just discussed. To make it easy to get started, get a domain name from a domain name supplier that caters for this type of setup (you can do this through the link in the next paragraph) and simply request that your free DynDNS service be activated on the domain name you have chosen. This will become your permanent website address. You can then setup and run that website address with Apache HTTP Server from your home (or office) computer. Then your friends and customers will always be able to find you.

Some people also like to get their website name in as many different domains as possible (.com, .net, .co.uk, .it etc. ) because Google's SEO formula can be dependant on the website's geographical Domain Name location. This also helps stop other people from stealing your brand name or idea. You can search and register Domain names (with or without DynDNS) here. (Europe, Asia, Oceania, America etc. etc.)

And as the purpose of this tutorial is to place a server setup on a local network to further familiarize the website administrator with Apache, we will gloss over this point for now and define our DNS domain as a local domain only.

Entering the DNS domain details of our Apache HTTP Server
(Fig. 04)

We enter "localhost" as our Network Domain, and we also enter "localhost" as our Server Name. You can name any email address you like as the administrator's email. If we wanted to secure a domain first, or use DynDns, we used the link above and can either use the data now, or we can add them after we have setup apache.

Next we want to ensure our network users can find our server and we setup their shortcuts by choosing the radio button marked for All Users, on Port 80, as a service -- Recommended and select next to continue with the installation process. Note: If you select Port 8080, you will need to stipulate this port when calling your network. eg. http://127.0.0.1:8080/ or http://localhost:8080/index.html

Some Vista Operating System users may opt to use port 8080 if they are unable to resolve any port 80 conflicts as mentioned in page 1 of this guide.