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 the Globus Toolkit 3.2

This page will expand on the options you will have when installing the Toolkit. Then the Installing the Globus Toolkit 3.2 - Source Installers topic will cover the install itself.

This page contains the following topics:

Root vs Non-root

As a security precaution, we recommend installing GT3 as a non-root user.

GT3 is designed to run as few components at elevated privileges as possible. As you will see in the Configuration section, there are two files that will be made setuid. One of these needs to be setuid root in order to run a User Hosting Environment as another user. The other needs to be setuid to an account which owns the host certificate. That can either be a separate non-root user, or you could choose to have that be root also. You don't need to make the certificate owner choice right now; it will be covered in the Configuration section.

User ID Group ID Description
root root Super user
globus globus Globus Toolkit environment. For installation and execution of the Toolkit.
user group A user other than root or globus. End user environment for job execution on the Grid.

Note: It is important that the user ID under which you want to run GRAM is a member of the group ID that owns the launch_uhe_setuid program (see Configuring Resource Management .) That will be the case if you both install as user globus and launch the container as user globus.

By Service

Since the Toolkit has many components, you can install only the ones you need. On the Globus Toolkit 3.2 Download page, you will find the following options:

All Services

Installs all pre-web services and web services components.
WS Base Installer

Installs only the web services (WS) components from GT3 and the supporting packages. It gives you WS Core and the base services of WS GRAM, the Index Service, and Reliable File Transfer (RFT) service, as well as a GridFTP server.
Pre-WS Installer

Installs all of the pre-web services (Pre-WS) components and the supporting packages. It gives you Pre-WS GRAM, MDS2, and GridFTP. The RLS bundle is available separately.
WS Core

Installs WS Core. It is crossplatform Java code for any platform that supports a JDK.
WS Gridservice Archives (GARs)

Precompiled java gridservices. They may be installed into the WS core for platforms that don't support the installers, like Windows.

Installing the Globus Toolkit 3.2 - Binary Installers (recommended)

Note: If you plan to run the WS GRAM service we recommend that you install as the user that will run the WS GRAM service.

1 If you haven't already, go to Installing Support Software and follow the instructions for downloading the various required support tools.
2 Go to the Download page and choose the binary installer you want to install. You will have to choose between the all/base/preogsi. For the linux installers, run rpm -q glibc to choose between the glibc2.2/glibc2.3 choices. If the first two digits are "2.3", like "glibc-2.3.2-27.9", then you would use the glibc-2.3 installer. If the first two digits are "2.2", like "glibc-2.2.93-5", then you would use the glibc-2.2 installer.

WARNING: These binaries are only known to work on the distribution used to generate them (RH7.3 for the glibc2.2, and Fedora Core 1 for glibc2.3). We have had bug reports even on machines which report the same Major.Minor.Point release of glibc, but are from a different distribution. If you experience GridFTP errors with the binary installation, please rebuild from source.

3 As globus, untar the binary installer.
4 Make sure that ANT_HOME and JAVA_HOME are set, and that ant and java are on your PATH. If you are using JDK 1.3.1, make sure JAAS is in your CLASSPATH before you run the installer.
5

Run:

./install-gt3-bin /path/to/install

Note: some of the resource management configuration can use the packages under the schedulers/ directory. You may not want to delete the installer directory until after you are done configuring.

Installing the Globus Toolkit 3.2 - Source Installers

Note: If you plan to run the WS GRAM service we recommend that you install as the user that will run the WS GRAM service.

1 If you haven't already, go to Installing Support Software and follow the instructions for downloading the various required support tools. Double-check the Troubleshooting Page to check that you don't have version incompatibilities.
2 Go to the Download page and choose the source package you want to install.
3 As globus, untar the source installer.
4 Make sure that ANT_HOME and JAVA_HOME are set, and that ant and java are on your PATH. If you are using JDK 1.3.1, make sure JAAS is in your CLASSPATH before you run the installer.
5

Run:

./install-gt3 /path/to/install

6

Then run:

./install-gt3-mmjfs /path/to/install

Note: some of the resource management configuration can use the packages under the schedulers/ directory. You may not want to delete the installer directory until after you are done configuring.

Installing the Globus Toolkit 3.2 - GT3 Core

WS Core is installed by the GT3 Base and GT3 All installers. If you use one of those installers, you do not need to follow the steps below, it will automatically be installed when you use the installer. It is offered standalone so that users on non-UNIX platforms can download and install the java-only portions that are available for their platforms. It is also useful for gridservice developers who wish to write new applications, but don't need any of the higher-level services.

1 If you haven't already, go to Installing Support Software and follow the instructions for downloading the various required support tools.
2 For a binary distribution, you merely untar or unzip the .tar.gz or .zip file, then proceed to step 4. For a source distribution, continue to step 3.
3

Untar the core-0.6.tar.gz file. Change directory to core-src/impl/java. Run:

ant dist

Your binary distribution is now in core-src/impl/java/build/ogsa-3.2. Change to that directory now.
4

Now you just need to generate the launcher scripts for your platform. From the binary distribution directory, run:

ant setup

Now you have installed WS Core.

Installing the Globus Toolkit 3.2 - Adding GARs

These GARs are installed by the GT3 Base and GT3 All installers. If you use one of those installers, you do not need to follow the steps below, they will automatically be installed when you use the installer. They are offered standalone so that users on non-UNIX platforms can download and install the java-only portions that are available for their platforms.

1

The GARs require that WS Core has already been installed. Follow the instructions at Installing the Globus Toolkit 3.2 - WS Core if you haven't already.
2

Change to your WS Core install directory, then for each GAR, run:

ant -f build-packages.xml deployGar -Dgar.name=<location of gar>

Installing the Globus Toolkit 3.2 - Bundles

The bundles represent the pre-WS installer broken up into smaller pieces. They're intended for people developing against the pre-WS C APIs who have unusual compiler requirements. If you're not sure what bundles or flavors you want, we recommend using the pre-WS installer instead.

1

First, untar the GPT source package from the download page. cd into the resulting directory and set the environment variable GPT_LOCATION to point where you want it installed. Then run build_gpt.

2

To build the bundles, set the environment variable GLOBUS_LOCATION to point where you would like the bundles installed, then run:

$GPT_LOCATION/sbin/gpt-build [bundle] [flavor]

Replace [bundle] with the name of a bundle, and [flavor] with a GPT flavor label. The pre-WS installer uses a flavor of gcc32dbg for most bundles, and gcc32dbgpthr for the Information Services and Replica bundles. For information on customizing flavor definitions, you can see the Grid Packaging Tools website's globus_core chapter.

Next page >> Configuring GT 3.2