OPS335 Lab 5

OBJECTIVE & PREPARATION

In this lab, we will look at several separate technologies that are used with the Apache web server to install, configure and run web applications.

The basic purpose of the Apache web server is to serve text pages, images, and other static files. You can format those web-pages to appear nice, but they would lack dynamic functionality (i.e. the ability to change colors or font-size when the mouse moves over a link, button, etc). In other words using Apache web-server as a sole application would not make your web-pages more interesting.

If we want to add more features for our web-page (eg. dynamic functionality, security, e-commerce, etc), your webserver would need additional help. To provide additional help requires several resources - more than just the web server itself. A popular acronym to represent these foundations and servers is referred to as LAMP. It stands for Linux, Apache, MySQL, and PHP (or Python).

In your previous OPS235 course, your second assignment may have required you setup a similar series of services in order to run a Wiki on one of your virtual machines. In this lab, we will set up another example of a "LAMP solution" that will allow the user to run webmail in a web-browser to send and receive e-mail messages.

Online Resources

• (Course Notes on the Apache Web Server)
• Apache Resources
• Installing Apache Webserver on Centos7
• PHP Tutorial (w3schools.com)
• MySQL / SQL Language Resources (w3schools.com)

INVESTIGATION 1: SETTING UP A LAMP SOLUTION

Install, Configure & Run a Webserver (Apache)

Next we need to install, configure and run a webserver on one of our Linux VMs.

Apache Webserver Resources
Apache web-server configuration can be a very complex topic (covering an entire course!). Although this lab focuses only on one small application of a web-server, you can refer to the following link to refer to additional configuration help: Apache Resources.

Perform the following steps:

1. Make certain you are in your VM1 machine.
2. Install the Apache package (the name of the package is: httpd).
3. Start the httpd service, and enable this service to start automatically upon system startup.
4. Using a text browser such as lynx on vm1 go to localhost. You should get the "Fedora Test Page" which indicates your web server is running on the local virtual machine.
5. Make certain to configure your firewall to allow access to the httpd service (i.e. the Apache serves HTTP traffic which goes over TCP port 80) and to update the firewall_restore script to include it.
6. Open a web-browser in your host machine and enter the following URL: vm1.youruserid.org.
   If you setup your Apache webserver correctly, you should be able to view the Apache Test page.
7. Although we will not be exploring webservers in depth, we will have you create a simple webpage for testing purposes, then later setup a web resource for webmail.
8. The termDocumentRoot specifies where the Apache webserver will search for documents to serve. Create the file index.html in your DocumentRoot directory with the following contents (replace the date with the current one):

Hello, this is a web page on vm1.yourid.org and the current time is Mar 28 22:16:27 EDT 2016!

9. If you refresh your web-browser page in your browser, you should see the contents of your index.html document. If you wish, you can specify the filename index.html in the address, but it is not necessary, since the file index.html is automatically loaded by default when the URL refers to that directory containing that file.

Using the index.html file
It is considered to be a "best practice" to create index.html files for newly-created subdirectories within the DocumentRoot (or users' public_html directories) to force a display of a web-page, instead of viewing the directories "index" listing of files (from "curious eyes"): that is why the name of the file is called "index.html".

10. Refresh your web-page by issuing the keycombination: ctrl-r. Notice that the time doesn't change as you refresh the page. This indicates that the page is static (not dynamic) indicating that the page does not change (i.e. boring!).

Creating a PHP Script

In order to allow us to run a webserver application in a web-browser, we need a scripting language that will allow the web-browser to function dynamically (i.e. being able to change frequently, as opposed to being "static" or unchanging). In this section, we will demonstrate how a scripting language (PHP) can be used for the web-browser to react in a more dynamic fashion.

PHP Scripting Language
PHP code is considered to be a language that runs on the web-server (i.e. "server-side programming"). PHP code can be embedded in an HTML document (HTML code), and use the resources on the "server-side" to make the web document or resource more dynamic (eg. database access, etc). Although it is not the purpose of this course to learn about and create PHP documents, here is a quick resource on PHP: PHP Tutorial

Perform the following steps:

1. Copy the index.html file to index.php and modify it to contain:

Hello, this is a web page on vm1.yourid.org and the current time is <?php system("date"); ?>!

2. On your host machine, again refresh your web-browser. Notice that in a web browser the index.php file isn't treated as a default page and the contents don't contain the date, but instead are displaying the text in the php code you entered into the index.php file (refer to above code).
3. The reason this occurs is that the PHP interpreter hasn't been installed on your vm by default.
4. Install the php package on your vm1 machine, and restart your webserver. NOTE: The php package comes with a working default Apache configuration so you don't need to enable it manually.
5. Refresh the webpage for your web-browser on your host machine. You should now notice that you see the date instead of the call to the date command. Refresh your webpage several times to see how the time changes. This is simply a "trivial example" of dynamic web content does it does provide a simple demonstration of how scripting languages can be used to create more dynamic webpages.

Controlling Access to Pages

• Now, as root on your gateway/host, try to forward incoming http connections that arrive on your host to the web server on vm1. Use an iptables command something like this:

iptables -t nat -A PREROUTING -i *yourinterface* -p tcp --dport 80 -j DNAT --to 192.168.X.2

• You will also need to create a rule in the FORWARD chain in the default table to accept connections to port 80.
• To test this setup you'll need to ask a classmate on another PC to try to use a browser to view your web page. S/he'll have to enter your host's external interface IP number in their browser's address window.
• Have them view both index.html and index.php
• create a new directory inside your DocumentRoot and move index.php inside it.
• Have your partner view both files again.
• We will now modify the settings on the web-server to prevent machines outside our network from accessing the private directory.
• Add the following directory statement to your apache configuration (making sure to replace the X with your own network octet):

<Directory "/var/www/html/private">
  AllowOverride None
  Require ip 192.168.X.0/24
</Directory>

• This sets up separate rules and access permissions for that subdirectory.
• Your partner should no longer be able to access any pages in the private directory (or any sub-directories of it), but your other internal machines (including your host) should still have access.

Install, Configure and Run MySQL Database Server

We complete the last piece of the puzzle by installing, configuring and running a database server to support your webmail application that will be installed and setup in a later lab.

MySQL is used to allow storage and retrieval of structured data. SQL is a command language (used by scripting languages such as PHP) to allow programmers to access databases contained within a server (or other servers via a network) to be used within web-based applications via the web-browser.

We won't spend much time learning the details of MySQL configuration but you need a basic server set up. You may remember when setting up MySQL from OPS235 - it is basically the same concept.

MySQL / SQL Language Resources
Again, MySQL can be a complex topic: Seneca has an entire course that concentrates on using SQL commands! Here is a link to MySQL / SQL Language resources: MySQL / SQL Language Resources.

Perform the following steps:

1. Install mariadb-server.
   
   The MySQL and MariaDB are actually two separate projects run by different groups, yet they are compatible; therefore, you can use documentation from one to configure the other.
   
   
2. NOTE: When installing mariadb, make certain that you have not just the client but also the server software.
3. When you start the MySQL service, check the system log file for instructions regarding how to set the root password. Even though we will not configure our MySQL service to be accessible over the network, it is accepted as a "best practice" configuring for network access for each MySQL installation.
4. Note that the MySQL service has two root passwords:
   • For the localhost
   • For external requests
5. Refer to the log file to learn how to run the two commands in order to generate the appropriate passwords.
   
   NOTE: Use a password you make up yourself, but do not generate a secret password, since you will be storing that password in a plain text file for later reference.
6. Start the service and ensure that it will start automatically every time the machine boots.

Test Connection to MySQL Database Server

• While the web server (with php), and MySQL server may be working individually, we need to ensure that they can connect to each other.
• Since this test will involve storing the database password in a plain-text html file, we want to make sure no one else can access it.
• Modify the Directory statement for your private directory to prevent any machine other than your vm1 from accessing it.
• Re-start the web-server and try to access the page from another machine. Make sure that you can not do so before you continue.
• Install the php-mysql module so that the installation of php your web server is using can execute sql statements. You will have to restart the service after installing it.
• Create a page like the one described here to test that your web server can connect to the database (replace the user, password, and database with values appropriate for your machine). Note that only the first connection (using localhost) on that page should be able to connect.
• Once that page shows a successful connection on your VM (Localhost via UNIX socket) this step is complete.
• You have now established that the web server is able to run code which can interract with the database. This will allow dynamic pages to make use of information stored there when providing resources to your users.

Record steps, commands, and your observations on this investigation in your OPS335 lab log-book

COMPLETING THE LAB

You now have a complete LAMP stack and could host a variety of web-pages that could include dynamically generated content and database access.

Depending on your professor you will either be asked to submit the lab in class, or online. Follow the appropriate set of instructions below.

Online Submission

Follow the instructions for lab 5 on moodle.

In Class Submission

Students should be prepared with all required commands (system information) displayed in a terminal (or multiple terminals) prior to calling the instructor for signoff.

Arrange evidence (command output) for each of these items on your screen, then ask your instructor to review them and sign off on the lab's completion:

To be completed by an instructor who uses in-class submissions.

EXPLORATION QUESTIONS

1. What does the term LAMP stand for? Briefly describe the purpose of each of the following items in LAMP.
2. What is the major difference between a static web document and a dynamic document?
3. What does the term "server-side programming" mean?
4. What is the purpose of creating and using an index.html file?
5. What is the purpose of creating and using an index.php file?