Project

General

Profile

Installation

Before start with the installation process, you probably want to checkout the sources and build a release directly from them, so you could visit the checkout section.

In order to install jTReqS, it is necessary to have installed:

  • Java 6 sdk 64 bits[[http://www.java.com/en/download/linux_manual.jsp]] It is important to have 64 bits in order to use the Native part that communicates with HPSS.
  • Maven 2.2 [[http://maven.apache.org/download.html]] to invoke the project life cycle. It is necessary to configure M2_HOME, M2, JAVA_HOME and PATH (Check at the end of the download page, the section "Installation Instructions").
  • HPSS API installed, in order to compile the native part and to execute the application.

In order to execute, it is necessary to define the next variables:

  • export JAVA_HOME=${JAVA_HOME:-/user/jdk} This has to reference to the valid Java 6 64 bits.
  • export HPSS_ROOT=${HPSS_ROOT:-/opt/hpss}

The file of the release can be obtained as a product from a checkout or it can be downloaded from this forge, from the https://forge.in2p3.fr/projects/treqs/files section.

You just have to extract the tar.gz file in the desired location, and configure the files that can be found at

./jtreqs/etc

The bin directory contains the executables such as jtreqs.sh, the daemon and the watchdog.
The etc directory contains the configuration files for jtreqs, for the logger, and for the cron.
The doc directory holds the files that describe some extra documentation that could be uselful if having problems.
And finally, the repo directory keeps all the libraries that are necessaries to execute jTReqS, including the generated NativeBridge.so.

Now that you understand the structure of the directory tree of jTReqS, you can create a symbolic link in /etc/init.d/jtreqsd that points to the daemon in the bin directory.
You can put a cron that activates the Watchdog periodically. The cron could be configurated according to the cron file in the etc directory.

For more information, take a look at the README.txt file, in the root directory of the sources or of the distribution file.