Preparing Fedora Core 4

Installing the Fedora Core 4 Operating System

If you feel confident in installing the server installation of Fedora Core 4, you may skip this section but make sure to install the pre-requisites otherwise GRIA war will fail to function correctly.

N.B. There are several ways to install and configure Fedora, so you are advised to consult your system manager and setup the system according to your needs. The following notes describe a simple way to install and configure a headless Fedora system for GRIA war.

Having satisfied the above, the installation process is as follows:

Place the Fedora Core 4 CD1 into the CD-ROM drive and boot the system from the CD, pressing enter at the boot prompt (install in graphical mode).
Test the CD media (optional).
Click Next on the Welcome to Fedora Core screen.
Choose language (e.g. English) on the Language Selection screen.
On the Keyboard Configuration screen choose keyboard, e.g. United Kingdom.
On Upgrade/Install Examine screen choose Install Fedora Core.
On the Installation Type screen choose Server.
According to your needs and system settings, choose automatic or manual configuration for the Disk Partitioning Setup screen. Then follow the instructions accordingly, e.g. for the Disk Setup and Boot Loader Configuration screens.
Enter the appropriate settings for the Network Configuration screen. If you do not have a DHCP server, enter the hostname, etc manually.
On the Firewall Configuration screen, select Enable firewall and choose SSH and Web Server services. You may want to disable SELinux by selecting this option in the drop down menu.
Set the correct time zone in the Time Zone Selection screen.
Set the root password in Set Root Password screen.
The machine will reboot at the end of the installation.

After the installation from CD is complete, we recommend updating the system with the latest patches. This may be done using the yum command (this may take some time):

# yum update

This completes the installation of the operating system.

Installing the Software Pre-requisites

Having installed the operating system, the following lists the pre-requisites which must be installed if GRIA war is to function correctly. It is important to install any dependencies which may also required by these software pre-requisites:

Sun Java JDK v1.5.0 or higher
Jakarta Tomcat v5.0.28
Apache HTTP server v2.0 (an optional package to provide secure access)
- httpd-2.0.xx.x
Perl v5.6 or higher (only required for the GRIA Basic Application Services package)
A sample, test application: ImageMagick(only required for the GRIA Basic Application Services package)
An Internet browser, e.g. Mozilla Firefox (which may be installed on a different machine)
Optional utility packages:
- zip and unzip
- tar, etc.

We recommend using tomcat v.5.0.28 as this version is the one that has been most comprehensively tested with GRIA. However, GRIA has also been used with v5.5.17 so it is possible to employ that version (or higher).

If you have followed the installation instructions above then your system already has Apache and Perl installed. The Fedora Core 4 distribution CDs include RPM packages for Tomcat and for GNU Java. However, to use GRIA you must install Sun Java. Unfortunately, it is very difficult to configure the pre-packaged Tomcat to use Sun Java, so Tomcat must also be manually installed by following the instructions below.

First, download the Java binary JDK selecting the "Linux self-extracting file" (e.g. jdk-1_5_0_05-linux-i586.bin) and Tomcat packages and place them into /tmp directory on the Fedora Core 4 machine. You may find it easiest to do this by downloading the packages to your desktop machine and copying them to the server. Finally, log in to the server machine as the root user ready to install the software.

Install Java

In order to install Java in the /opt directory the following must be done (adjusting the version number to your particular package):

Move to /opt:
```
# cd /opt
```
Unpack the binary from the temporary directory:
```
# sh /tmp/jdk-1_5_x_xx-linux-i586.bin
```
Create a symbolic link within this directory:
```
# ln -s jdk1.5.x_xx java
```

Install Tomcat

The following must be done in order to install Tomcat successfully (adjusting the version number to your particular package):

Tomcat will be installed under the /opt directory, therefore move to this directory with:
```
# cd /opt
```
Unpack the Tomcat tarball from the temporary directory:
```
# tar xvfz /tmp/jakarta-tomcat-5.0.28.tar.gz
```
Create a symbolic link for Tomcat
```
# ln -s jakarta-tomcat-5.0.28 tomcat
```
Tomcat will be most secure if it is not run by root, therefore create a user for the tomcat server to run as e.g. "tomcat" with the user's home directory set to /opt/tomcat:
```
# useradd -d /opt/tomcat tomcat
```
Alter the ownership of the directory to the tomcat user created above:
```
# chown -R tomcat:tomcat tomcat
```

Configure tomcat to use Sun Java by editting /opt/tomcat/bin/catalina.sh. Open the file (e.g. in vi) and add the line JAVA_HOME=/opt/java to the top of the file after the file header, e.g.:

# system class path used to start Tomcat.
#
# CATALINA_PID (Optional) Path of the file which should contains the pid
# of catalina startup java process, when start (fork) is used
#
# $Id: fc4-pre.htm 3715 2006-04-10 14:01:19Z ajw $
# -----------------------------------------------------------------------------

JAVA_HOME=/opt/java

# OS specific support. $var _must_ be set to either true or false.
cygwin=false

Install Sample Application

The GRIA Basic Application Services package uses demo applications which require the ImageMagick package. You may already have ImageMagick installed. To test for it, log in as root and type:

# rpm -qi ImageMagick

If you see "package ImageMagick is not installed" then the package must be installed, either from the CDs or by using yum:

# yum install ImageMagick

Setting the System Clock

In order to provide some synchronisation between the clocks on machines that the various GRIA packages are installed on, it is recommended to run an NTP client service that will synchronise your system with an Internet time server.. Fedora comes with an NTP package which is installed by default in the server installation. To see if NTP is installed, log in as root and type:

# rpm -qi ntp

If you see "package ntp is not installed" then install NTP either from the CDs or by using yum:

# yum install ntp

The NTP daemon must be configured using the file /etc/ntp.conf. If you are using DHCP then your DHCP server may automatically configure this file. Further instructions regarding NTP are beyond the scope of this manual.

Configuring the Firewall

The deployed GRIA war (or webapp) should be hosted behind a firewall to ensure that your server can only be accessed on certain ports. You should consult with your systems administrator to determine if you need to run a firewall on the GRIA server machine. If so, configure the firewall as follows:

As root, run:
```
# system-config-securitylevel
```
Enable firewall and continue with Customize (use the TAB key to move fields and the SPACEBAR key to select)
Do not select any "Trusted Devices", e.g. eth0
Allow incoming connections for "SSH", "WWW (HTTP)" and "Secure WWW (HTTPS)"
In the "Other ports" box type: "8080:tcp" to temporarily enable insecure access to Tomcat
Finish firewall configuration by selecting "OK"

Configuring SELinux

SELinux is an option during the installation process. It provides better security than standard linux installations. If you are not sure whether SELinux is installed, then type (as root):

# setsebool

If you get "Command not found" then SELinux is not installed and no configuration is necessary. Otherwise, if you chose to install SELinux then it must be configured to let the Apache web server communicate with the Tomcat web server. To do this, enter the following command as root:

# setsebool -P httpd_can_network_connect=1

May need to set another bool to enable httpd to communicate with the terminal (needed for cert handling)

Setting Up Tomcat Users

In order to deploy the war file, the Tomcat Manager for application deployment will be used. The Tomcat manager functions are disabled by default.

o enable Tomcat administration and management we must add a role and a tomcat user to the tomcat-users.xml file.

Open the $CATALINA_HOME/conf/tomcat-users.xml file with a suitable editor and add this element after the last 'role' element:
```
<role rolename="manager"/>
<role rolename="admin"/>
```
Add this line after the last 'user' element, replacing ADMIN_PASSWORD and GRIA_PASSWORD with appropriate passwords:
```
<user username="tomcat" password="TOMCAT_PASSWORD" roles="admin,manager"/>
```
Save the file

Starting Services

There are two services that need to be started: Tomcat and NTP. NTP is easily managed by the system and may be started with this command:

# service ntpd start

As mentioned above, Tomcat should not be run as root, therefore first switch form being the root user to the tomcat user and then start tomcat:

# su tomcat
$ cd /opt/tomcat/bin
$ ./startup.sh

It is useful to have the NTP daemon start automatically when the server is rebooted. This can be done by typing the following as the root user:

# chkconfig ntpd on

Next Step

Having installed and configured the pre-requisites the following step is to deploy war file in Tomcat. In order to do this make sure the Tomcat service is up and running in your system. Test it with your browser by pointing to your Tomcat server URL, i.e. http://<host IP>:8080 - you should be able to access your Tomcat server home page.

The next step is to deploy the services in Tomcat according to the installation instructions for the package you are installing: