This information is for a release that is no longer supported by the Globus Toolkit. The currently supported versions of the Globus Toolkit are 4.2 (recommended) and 4.0.

Globus Toolkit 3.2: Installation Guide

Overview
Before You Begin
>Support Software
Installing GT 3.2
Configuring
Testing
Troubleshooting

Installing Support Software

This topic lets you know which support software you must download as well as other software you may want.

Required

Optional

Java SDK

Since the underlying code of GT3 is written in Java, you must install the Java platform on any machines running the Toolkit.

Required for: GT3 Webservices components

Recommended Versions: 1.3.1 through 1.4.x (1.3.1 may be incompatible with certain services - see Important Notes)

Download Link: http://java.sun.com/j2se

Important Notes:

  • JAAS library is required as a separate download if you are using JDK 1.3.1
  • Some higher level services like the Index Service and Execution Services use Xindice, which is not compatible with version 1.3.1 on some platforms. Please see the Xindice FAQ for more details.
  • 3.2.0 has bug 1596 that restricts the Java GRAM to using version 1.4.x. This will be fixed in an update package.

  • If you don't need to build any source, you may use JRE instead.
  • If you are using Sun's JDK, the safest version to use is JDK 1.4.2. Version 1.4.1 sometimes hangs during compilation for unknown reasons.
  • The MMJFS component (part of GRAM) might not properly work with the IBM JDK on Linux.

Installing JDK

  1. Follow either Sun or IBM's instructions for installing JDK. The current distribution as of this writing is 1.4.2.
     
  2. Set the JAVA_HOME environment to the installation directory
     
  3. Add $JAVA_HOME/bin to your PATH environment.
     

Ant

Ant is a Java-based build tool required for the GT3 installation. The toolkit is composed of many Java classes that need to be combined or built to form a functioning program. Ant is used to execute an Ant-based build script that automates the build process (if the toolkit needs to be re-buit at any point, Ant can skip actions that have already been completed.)

Required for: Webservices installation

Recommended Version: 1.6.1

Download Link: http://jakarta.apache.org/ant

Important Note:

You can continue to use Jakarta Ant 1.4.1 if you replace crimson.jar in your $ANT_HOME/lib directory with the xerces.jar that comes with our distribution.

Installing Ant:

  1. Follow Jakarta's instructions for installing Ant 1.6.x. The current distribution as of this writing is 1.6.1.
     
  2. Set the ANT_HOME environment to the installation directory.
     
  3. Add $ANT_HOME/bin to your PATH environment.
     

Junit

Junit is a Java-based testing framework that facilitates regression tests. If you run tests from source, the junit.jar class must be included with Ant for the GT3 installation.

Required for: Gridservices (however it is optional if you are only installing the GT3 Core component)

Recommended Version: 3.8.1

Download Link: http://www.junit.org

Installing Junit:

  1. Follow Junit's instructions for installing Junit 3.8.1.
     
  2. Copy junit.jar to the $ANT_HOME/lib or put it on the $CLASSPATH. 

C compiler

Required for: Any C code. The only components that do not require this are the GT3 core component and the Higher-level GARs.

Recommended Version: Anything except gcc 3.2 (the RedHat 8 default compiler). gcc 3.2 triggers bug 488, our most-reported bug.

Download Link: http://www.gnu.org/software/gcc/ for GCC. Vendor compilers also work.

YACC (or Bison)

Required for: building C bindings and the ogsi-find-service-data client from source.

Recommended Version: the latest version

Download Link: http://www.gnu.org/software/bison/bison.html

Important Notes:

Your compiler probably already has this installed. Otherwise, you can download the GNU version.

Installing YACC (or Bison):

Follow the instructions from the website.

GNU Tar

Required for: Unpackaging software

Recommended Version: The latest version

Download Link: http://mirrors.kernel.org/gnu/tar/

Important Note:

If you are running Linux, your system comes with GNU Tar. If you are running solaris, /usr/bin/tar is not GNU Tar and you will need to install it.

Installing GNU Tar:

Follow the instructions from the INSTALL file inside the file download.

Jakarta Tomcat

Used for: your web service container. This is optional because the GT3 installation provides a standalone web service container for testing purposes.

Recommended Version: 4.1.24 (4.0.6 has also been tested to work)

Download Link: http://jakarta.apache.org/tomcat

Installing Tomcat:

Follow the instructions from the website.

Microsoft .NET Framework and/or Visual Studio .NET

Microsoft .NET Framework 1.1, and/or Visual Studio .NET 2003 (April 2003 release)

Java Database Connectivity (JDBC) compliant Database

JDBC is an API for Java that allows access to a wide range of SQL databases. JDBC is similar to the open standard API Open Database Connectivity (ODBC), which is aligned with The Open Group.

Used for: the Reliable File Transfer (RFT) service and Replica Location Service (RLS), which require a database backend. For licensing reasons, we ship the PostgreSQL JDBC driver, but other JDBC compliant databases should be compatible.

Recommended Version: not applicable

Download Link: http://www.postgresql.org

Installing a JDBC compliant database:

In this example, we'll use PostgreSQL. If you're familiar with other JDBC databases, like MySQL, you can adapt these instructions. PostgreSQL consists of 11 RPMs, but only three of them are required to install a functioning database.  This procedure installs all of the RPMs and edits two configuration files:

Note: This installation creates the user postgres. This user will be used during the creation of the database.

  1. Download Postgresql from http://www.postgresql.org/ and install RPMs.
     
  2. Allow clients to connect via TCP/IP-based connections:

    a) As root, edit /etc/init.d/postgresql.

    b) Find the line that starts with the postmaster command.

    c) Add the -i flag after the -o flag.

    d) Remove -p ${PGPORT}.
     
  3. Tell the database to listen for requests on the host machine by modifying the host-based authentication file, pg_hba.conf.

    a) As root, edit /var/lib/pgsql/data/pg_hba.conf.

    b) Find the host stanza (or record) and enter it with the IP address for any users from any machines that should have access to the database (the default value is 127.0.0.1)

    c) Remove the # character from the beginning of the line.
     
  4. After saving the file, start the database by running: 
    /etc/init.d/postgresql start

Next page >> Installing GT 3.2