The zip archive should be unpacked in the Libelle Mail Archive user's home directory. It contains a set of files that will unpack into the same directory as the zip archive and one directory which contains SQL scripts.
All the files in this directory must be owned by the Libelle Mail Archive user.
These should work without modification. Their use is described later.
These files should be left in the directory where the loader and backup programs will be run.
The three Libelle Mail Archive configuration files, which have .conf extensions will need to be customised for your installation. All are extensively commented:
All parameters must be set to suit your installation. The first group are used by all Libelle Mail Archive programs to access the database that stores the archive.
The remaining parameters are used by the archive search program, MASearch.
This file controls the backup program, MABackup. You only need to edit this if you intend to do incremental backups rather than use your RDBMS backup utilities. The only parameters that should normally be changed are:
|maloader.conf||This file controls MALoader, which adds messages to the archive. Every parameter is described in the comments that immediately precede it in the file. Edit the file to define the way that MALoader will operate during a normal mail archiving run.|
|These files configure packages that MALoader and MABackup are dependent on. They should not need any changes. Put copies of them in the directory that contains the jar files.|
The remaining files are shell scripts. All of them must be edited to customise them for your environment.
|Edit the second 'launcher' definition to set
the absolute pathname of the MailArchive.jar file to match
These are are all wrapper scripts that run MABackup, MAFixMessages, MALoader, MAParm, MASearch, MASetConfig, MATestConfig and MAUpdate respectively.
This script updates the copy of mailarchive.conf in MailArchive.jar.
The mailarchive.conf file is only used during development when Libelle Mail Archive is not run from a jar file. This provides an easy way to use separate databases for development and production.
The options for runSetConfig must be given the same values as you used in mailarchive.conf. The script as issued contains the values used in my testing environment. Change them as shown below:
These files should be on the search path of all users who have permission to run them. runSearch will be used by anybody who is allowed to search the archive and retrieve mail messages from it. The rest will not normally be used by anybody except the archive administrator.
The three jar files must be placed in the same directory. This must also contain the prerequisite jar files or symbolic links to them.
The site-specific changes to mailarchive.conf must be applied to MailArchive.jar, preferably after the jar file has been installed alongside the other prerequisite jar files. Apply the site-specific changes by changing your current directory to the one holding the jar file and running