This page provides general instructions on how to upgrade AIRT. Specific upgrade paths are discussed in more detail.

Specific upgrade instructions

Upgrading from 20080403.1 to 20090112.1

General upgrade instructions

When obtaining a new version of AIRT, install the application as normal. However, instead of creating the new database schema, the schema must be upgraded.

sudo -u postgres pg_dump airt |bzip2 > airt-backup.sql.bz2

Upgrade the database

Begin by obtaining the current version number of your database. This can be achieved by executing the following command on a shell prompt.

echo "select value from versions where key='airtversion'" |psql airt airt

Make sure that the user executing the command is authorized to connect to your database. You may have to replace the psql arguments with your database name, respectively the database user.

The output should look something like:

kees@airt-test:/opt/airt/src/airt-20090121.1$ echo "select value from versions where key='airtversion'"|psql airt airt
   value
------------
 20080403.1
(1 row)

Next, check which database patches are available. To do this, make sure that you are in the doc/database subdirectory of the source branch that you are upgrading.

kees@airt-test:/opt/airt/src/airt-20090121.1$ cd doc/database
kees@airt-test:/opt/airt/src/airt-20090121.1/doc/database$ ls 200[89]*
20080128.1.sql  20080328.2.sql  20080731.1.sql       20081219.1.schema.sql
20080201.1.sql  20080402.1.sql  20080906.1.sql       20081231.1.sql
20080215.1.sql  20080403.1.sql  20080924.1.sql       20090121.1.sql
20080229.1.sql  20080523.1.sql  20081031.1.sql
20080328.1.sql  20080730.1.sql  20081219.1.data.sql

All patches between the current version and the version to which you are upgraded must be installed in sequence. If the filename contains the phrases schema and data, the patches must be applied by the schema owner, respectively the airt user. Apply the schema changes before the data changes.

Check configuration file changes

Once the database schema has been upgraded, cd to the configuration file directory and check if there are any new command directives:

kees@airt-test:/opt/airt/src/airt-20090121.1/doc/database$ cd /opt/airt/etc/airt/
kees@airt-test:/opt/airt/etc/airt$ diff -U1 airt.cfg airt.cfg.dist
--- airt.cfg    2009-01-25 08:14:43.000000000 -0500
+++ airt.cfg.dist       2009-01-25 08:32:17.000000000 -0500
@@ -21,3 +21,3 @@
  *
- * $Id: airt.cfg.dist.in 1153 2007-07-31 09:23:11Z kees $
+ * $Id: airt.cfg.dist.in 1381 2008-12-05 19:11:07Z kees $
  */
@@ -47,2 +47,7 @@
    $SETTINGS['libdir'] = '/opt/airt/lib';
+
+   // identify clients by X509 certificates? Note: web server is
+   // expected to ensure the validity of the certificate. AIRT will
+   // look for the subject name.
+   $SETTINGS['x509client'] = true;

@@ -111,2 +116,5 @@

+   // instance name
+   $SETTINGS['incident_name'] = "Example AIRT Site";
+
    // local customization can be found in this file. If undefined, no local

In this case, there are two new configuration directives: x509client and incident_name. Make sure to reflect these changes in your current configuration.

You should now be all set.