ProCKSI

h1. [[ProCKSI]] Workbench

This section describes the installation and configuration of the server side of the [[ProCKSI]]-Workbench. This includes the configuration of the web server and the database.

The server component (incl. all user data and results) will be installed into the home directory of the user _procksi_. Therefore, make sure that it is on a separate partition / hard disk with much space. In the best case, this will be a RAID system.

*IMPORTANT*: Always test a new release before taking a new version online! 

h2. Preparations for *TEST* and *RELEASE*

Make sure that directories for log and lock files exist, which are shared by all *TEST* and *RELEASE* instances (see below for more information):

<pre>

  mkdir /home/procksi/logs

  mkdir /home/procksi/locks

</pre>

h2. Installation and Configuration of a _TEST_ version

In the following, any test version of the workbench is referred to as _TEST_, which could be either a tagged release or a snapshot of the current development version. _TEST_ should include the current date in order to distingish different snapshots from different days, e.g. _snapshot_2008-08-01_.

Check out the current snapshot of the development version from the SVN repository.

<pre>

  svn co https://psiren.cs.nott.ac.uk/repos/procksi/ProCKSI-Workbench/trunk /home/procksi/TEST

</pre>

Create a softlink from _TEST_ to a generic directory _/home/procksi/test_. The web server and the workbench itself assume that there is always such a generic directory:

<pre>

  ln -s /home/procksi/TEST /home/procksi/test

</pre>

Change into the installation directory, run the setup script once to see the default settings. Running the script _without_ the parameter _-x_ just displays the current configuration.

<pre>

cd /home/procksi/test/install

./setup.pl -i -env test

</pre>

Run the setup script again with adjusted parameters. Parameters that might need adjustment are:

  - _-server_base_: Should be _/home/procksi/test_

  - _-server_name_: URL and port number for this _TEST_ version as given in the _apache_ configuration file

  - _-server_admin_: Email address of the administrator or this _TEST_ version

  - _-database_name_: Database that should be used for this _TEST_ version

In order to execute the installation for the given configuration, you must run the script _with_ the parameter _-x_.

<pre>

cd /home/procksi/test/install

./setup.pl -i -env test -x

</pre>

Check that all links in _/home/procksi/test/bin_ point to the correct files of the operating system.

Having *root privileges*, make sure that all permissions are set to '770', the user is _procksi_ and the group is _procksi_dev_.

<pre>

  cd /home/procksi/test/admin

  ./chall.sh

</pre>

h2. Installation and Configuration of an official *RELEASE*

In the following, the latest official version of the workbench is referred to as _RELEASE_, which could be for instance _procksi_8-6-1_.

Check out the latest _RELEASE_ from the SVN repository:

<pre>

  svn co https://psiren.cs.nott.ac.uk/repos/procksi/ProCKSI-Workbench/tags/RELEASE /home/procksi/RELEASE

</pre>

Create a softlink from _RELEASE_ to a generic directory _/home/procksi/latest_. The web server and the workbench itself assume that there is always such a generic directory:

<pre>

  ln -s /home/procksi/RELEASE /home/procksi/latest

</pre>

Change into the installation directory, run the setup script once to see the default settings. Running the script _without_ the parameter _-x_ just displays the current configuration.

<pre>

cd /home/procksi/latest/install

./setup.pl -i -env latest

</pre>

In order to execute the installation for the given configuration, you must run the script _with_ the parameter _-x_.

<pre>

cd /home/procksi/test/install

./setup.pl -i -env latest -x

</pre>

Check that all links in _/home/procksi/latest/bin_ point to the correct files of the operating system.

Having *root privileges*, make sure that all permissions are set to '770', the user is _procksi_ and the group is _procksi_dev_.

<pre>

  cd /home/procksi/latest/admin

  ./chall.sh

</pre>