Installing DIAL 1.30

D. Adams

We describe how to install DIAL at a site. FOr OSG sites, it is possible to do a remote installation following the instructions on the OSG installation page.

Add the following variables to your environment:
  OSG_APPDIR - Base directory for OSG apps
  VO_ATLAS_SW_DIR - Base directory for ATLAS apps on LCG
  DIALBASE - Base directory for the DIAL installation

OSG_APPDIR or VO_ATLAS_SW_DIR is used to find installed ATLAS kits and transformations.

Support for multiple platforms
The installation scripts allow sites to run different platforms but assume they are compatible and only install one version of each software package. All must be known variants of RedHat Enterprise 3. Known means known to pkgmgr which presently supports standard RedHat (rhel3), scientific linux (sl3) and CERN scientific linux (slc3). As noted below, some of the steps have to be repeated for each supported platform.

The easiest way to install dial on multiple platforms at a site is to run the following scripts on each platform. In some cases (indicated below) it is possible to specify the target platform.

Install webrun

First create the installation directory and copy the webrun script to the installation run directory:
  > mkdir -p $DIALBASE/scripts
  > wget -O $DIALBASE/scripts/webrun
  > chmod +x $DIALBASE/scripts/webrun

Software installation

All required software may be installed with a single command:
  > $DIALBASE/scripts/webrun install_all
Or it may be installed with the following steps:

Install and configure pkgmgr
The install_pkgmgr script may be used to install and configure pkgmgr, install pkgmgr_util and create the required startup files:

  > $DIALBASE/scripts/webrun install_pkgmgr

Register ATLAS packages
Next we use pkgmgr to register the packages inside the atlas kit that are used by DIAL. This assumes the appropriate kit has already been installed at the site.

  > $DIALBASE/scripts/webrun register_atlas_packages 11.0.4
The argument is the ATLAS release tag. For DIAL 1.30 this should be 11.0.4 and it defaults to that value if missing or blank.

An arguement specifying the pkgmgr platform may be added to perform registration for that platform.

Install DIAL
Next we use pkgmgr_system to install and register DIAL and the non-atlas packages on which it depends.

  > $DIALBASE/scripts/webrun install_dial
This registers packages for the current platform. If you wish to install DIAL for a different platform, rerun the command on a machine with the desired platform.

Set up the DIAL clients
If you wish to make the DIAL clients (dial and dialroot) available to interactive users, then create the usual DIAL setup files with the following command:

  > $DIALBASE/scripts/webrun setup_dial_clients
The setup files are put in $DIALBASE/setup. Users of posix-like shells can set up DIAL with the command
  > . $DIALBASE/setup/
This is not needed to run DIAL services or jobs.

Register ATLAS kits and transformations
In order to run DIAL jobs at a site, it is neccessary to first install the packages required by the transformations used by those jobs. ATLAS releases and transformations installed in the conventional locations for production may be registered with the following command:

  > $DIALBASE/scripts/webrun register_atlas_kits

Site configuration

The DIAL configuration resides in a package dialconf_XXX, e.g. dialconf_atlas for ATLAS. Here is an example. Create a directory containing the file (and optionally fms_filter) and register that directory with pkgmgr.

This can be done with the following command:

  > $DIALBASE/scripts/webrun install_dialconf atlas
Substitute your VO and URL for the arguments. An argument specifying the platform may be added.


The data to be accessed at the site should be resident at the site with files registered in the local replica catalog and datasets in the appropriate dataset catalog.