Requirements for the Astro-Grid-D Globus standard installation (GACSI)
This text describes which Unix programs are required for a successful installation and which updates are recommended. These guides have been tested for Scientific Linux 4.3 (Redhat Enterprise Edition). There can be slight deviations for different Debian distributions.
Annotation of the table:
The first column contains links to the general pages of the projects. The second column marks ("!") the programs for which an installation or update is required for Scientific Linux 4.3. The version number give minimum requirements or recommended versions. The links in the second column directly lead to the download of the required file (Deviations can occur for processor-dependent distributions, e.g., for 64-bit architecture, or of course more recent versions). Under "directory", the real destination directory of the program is recommended as well as the expected link for the GACSI (in case the program is not given in the path anyway). Next is the system variable describing the directory as well as the program call to check for the version number if the program has been installed at all. Finally, the name of the binary distribution or the source codes are given.
||Version number (or higher)||Directory
||system variable||Check||File name (version-dependent)|
|Java Development Kit||
||1.4.2 (better: JDK5 = J2SE 1.5)||/opt/jsdk-xx/jdk||
||$JAVA_HOME||java -version||jdk-1_5_0_08-linux-i586.bin (or processor specific)
3.2.1, 2.95.x tested (V3.2 not appropriate); 4.1
||1.2.3|| /usr/lib/ (/usr/local/lib)
||-||/sbin/ldconfig -v | grep libz
ls /usr/lib | grep libz
|GNU tar, sed, make, bzip2 etc.; sudo||
(for tar, sed, ..., correspondingly)
The Leibniz-Rechenzentrum offers a perl script to test the requirements.
If the program is missing in the distribution or the version is too old, the problem has to be solved before Globus is further installed. In this case, download the program and install it.
Anyway, the directories given in the column "linked" should be installed, e.g., using
mkdir /usr/local/jdkln -s /opt/jdk /usr/local/jdk/jsdk
or with the corresponding directories for tomcat and ant.The commands to unpack under Unix are:
- .tar.gz: tar xfz <file>
- .tar.bz: tar xfj <file>
- .bz2: bunzip2 <file>
- .bin: sh -x <file> (archive with integrated installation script)
An alternative installation directory for the Globus toolkit is "/opt". Alternatively, the Globus user directories can be installed in a separate partition which also determines the available memory space.
Considerations about the file system
Note that the PostGres daemon might use a lot of space, so that the partition "/var" has to be installed with sufficient size (about 10 GB). Globus programs on workstations are moved to the "swap" section of the file system during the day and while the main usage. Therefore, a sufficient swap space of 2*RAM is recommended (e.g., 4 GB swap for 2 GB RAM),
The complexity of the different versions and version numbers in Java is remarkable.
Java Development Kit
For Globus, just one Sun java compiler is required which is included in the "Java Development Kit (JDK)" that is available separately, e.g., as "JDK5.0 Update 8". There are "bundles" with other applications which always have different numbers and descriptions.
It makes sense for an installation to install a separate current version of the SDK indepedant of the versions being installed on the operation system already, and to use these for the compilation of the GTK.
If the data base has to be compiled, the configure setting of the globus helper may be used (~globus/globus-helper/globus-install/pgsql.cfg).
If the data base management is no working although it has been installed (e.g., saying "Postmaster is stopped"), it possibly is not started automatically. In this case, execute the following lines:
/etc/init.d/postgresql start# is the data base starting?
chkconfig postgresql on# autostart in init levels 2-5
If possible use gcc4 which also acts as Fortran compiler.
In Scientific Linux, zlib (libz.so) is only installed as version 184.108.40.206 which has a potential security gap.
For1.2.3, there are different source versions.
The direct download should be:
Update of zlib
The program is then installed by
In this installation version, the old version is kept and can be used simultaneously for compatibility reasons (e.g., for Acrobat Reader).
mv /work1/zlib-1.2.3.tar.gz /work1/build/
tar xfz zlib-1.2.3.tar.gz
ldconfig -v |grep libz # installation testen
libz.so.1 -> libz.so.1.2.3
libz.so.1 -> libz.so.220.127.116.11