nodeA since that node will serve as the 'client' machine
nodeB since that node will host the Globus GRAM WS that front ends the PBS batch system, along with other Globus grid services.
nodeC since that node will host the Globus GRAM WS that front ends the SGE batch system, along with other Globus grid services.

It is probably easiest to complete all the instructions on nodeB first and then go back and repeat most of the instructions (with the exception of creating a CA) on nodes nodeA and nodeC.

Begin by making a directory for the installation that is owned by globus and in group globus:

[root@nodeB ~]# mkdir -p /opt/globus-4.0.1
[root@nodeB ~]# chown globus.globus /opt/globus-4.0.1
[root@nodeB ~]# ls -alh /opt | grep globus
drwxr-xr-x 2 globus globus 4.0K Feb 20 12:05 globus-4.0.1

Become user 'globus':

[root@nodeB opt]# su - globus
[globus@nodeB ~]$ cd

Download the source for Globus Toolkit 4.0.1. You can download it using the 'wget' command:

Note: The following code appears on multiple lines, but it is 'one' line of code

[globus@nodeB ~]$ wget http://www.globus.org/ftppub/gt4/4.0/4.0.1/installers/
src/gt4.0.1-all-source-installer.tar.bz2

The source tarball should look like this:

[globus@nodeB ~]$ ls -l gt4.0.1-all-source-installer.tar.bz2

Note: The following output appears on multiple lines, but it is 'one' line of output

-rw-rw-r-- 1 globus globus 88609887 Aug 5 2005 gt4.0.1-all-source-installer.tar.bz2

The source tarball should have the following md5 checksum:

[globus@nodeB ~]$ md5sum gt4.0.1-all-source-installer.tar.bz2
398076812364f53d694194320836b8ad gt4.0.1-all-source-installer.tar.bz2

Next >