Installing the Apache server using the Red Hat distribution is not officially supported by our team but it has been done successfully and works.

Installing the module

The following is a general set of steps to put the module in place. It is assumed that the reader has extensive linux knowledge. This assumes that you have 32 bit apache 2.2 installed. This has been tested with 2.2.15.

• download the binary file that contains mod_tm.so and tm.conf and unzip
• copy the file in the previous step to /usr/lib/httpd/modules and make sure the permissions are ok. e.g. owner root:root, mode 755
• The mod_tm module needs a "data" directory in ServerRoot, on RedHat this is in /etc/httpd. As you don't normally want to write data into /etc the RedHat way of dealing with this would be to create an /etc/httpd/data symlink pointing to somewhere more appropriate, /var/www/data, for example. So:
  • mkdir the "data" directory
  • set permissions, owner apache:apache and mode 750
  • and then create a symlink in /etc/httpd pointing there.
• The normal RedHat way of accomodating module configuration needs is not to edit the main httpd.conf file directly but to drop a module-specific config file in /etc/httpd/conf.d. Put the included tm.conf file there and set permissions should be root:root, mode 644. You may also want to disable other module config files if they may interfere with TM - any file ending in ".conf" in that directory will be included in the apache configuration - so simply renaming a config file something.conf to something.conf.bak is enough to stop it being included. (Better yet remove unnecessary modules from the system using rpm or yum.)
• RedHat puts web pages in /var/www/html so download the web pages and replace the content of the htdocs directory with the downloaded pages.
• Test the listener as per below
• when working, add in mod_ssl and the ssl certificates to make sure it works with https.

Testing the module

Step 1

Restart and test the apache server by Starting a web browser like Firefox Type 'http://localhost/TheatreManager/1/login&event=0 You should see a page like the one above If so, then it means that the apache module and configuration are correct. You should also see at least files created in the 'data' directory that contain the state of the active listeners. If not, it means that you may need to look at the apache logs to determine what the issue is and/or redo the process from the start.

Step 2

Refer to any PCI consideration for installing Apache for late breaking security patches