SimDb Installation

The AugerDb/SimDb framework is installed in 3 steps:

The Java installation is described in the Java pages. The SRB installation is described in the SDSC pages, the CC ones or the local one (SRB Installation).

Installing SimDb means:

Notes

SimDb is a component of the AugerDb framework. Installing AugerDb installs the SimDb tools.

Installation Step by Step

Unpacking the tarball

The examples are given for the LAL installation - changes the directory path depending of your local configuration.

% cd /exp/auger/AugerSoft/AugerDb
% tar xvfpz AugerDb-7.3.1.tar.gz

A subdirectory 7.3.1 is created in the AugerDb root directory.

Setting up Java and SRB

The configuration of the AugerDb project is done using the augerdb_configure.sh script, distributed in the management/ directory of the project. This step needs the definition of the installation directories of Java and SRB. These directories can be specified using the environment variables JAVA_HOME and SRB_HOME  or using the -java and -srb options of the script.

Example 1: usage of the environment variables

% export JAVA_HOME=/usr/java/jdk1.5.0_05
% export SRB_HOME=/exp/auger/Srb/SRB3.4.2_LinuxSL

% 7.3.1/management/augerdb_configure.sh

Example 2: using options

% 7.3.1/management/augerdb_configure.sh \
 		-java /usr/java/jdk1.5.0_05 \
		-srb /exp/auger/Srb/SRB3.4.2_LinuxSL
Defining alias

Alias can be defined to give generic names to the versions: pro, dev, new, old... By default, the augerdb_env scripts (see below) are searching for the pro alias.

Alias are just symbolic links to the installation directories of the AugerDb version. A scrip, management/setVersion.sh can help to manage the miscellaneous versions and alias.

Setting up the user context

The paths and variables to use the SimDb tools are configured by sourcing the augerdb_env.sh or augerdb_env.csh scripts, depending of the used shell.

By default, the "pro" version is used. This logical version is associated to the real version by a soft link during the installation (see augerdb_configure)

% source augerdb_env.sh
Executing pro specific setup

The user can select a specific version, as shown in the following example:

% source augerdb_env.sh 7.3.1
Executing 7.3.1 specific setup

Minimal checks

The first check is to verify if the SimDb commands are in the user path:

% which SdbVersion
/exp/auger/AugerSoft/AugerDb/7.3.1/bin/SdbVersion

The second minimal check is to control the activation of the simplest command:

% SdbVersion
SdbVersion release: 7.3 (version: 7.3.1, build: 01-Apr-2008 12:00)