Software Links
Getting Started
- Doc Structure
- A Globus Primer
- Globus Is Modular!
- Quickstart
- Installing GT
- Platform Notes
- Migrating from GT2
- Migrating from GT3
Reference
- PDF version
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces
- Resource Properties
- Samples
- Glossary
- Performance Studies
Common Runtime
Security
Data Mgt
Information Svcs
Execution Mgt
Table of Contents
Create a user named "globus". This non-privileged user will be used to perform administrative tasks such as starting and stopping the container, deploying services, etc. Pick an installation directory, and make sure this account has read and write permissions in the installation directory.
![[Tip]](/docbook-images/tip.gif)
Tip You might need to create the target directory as root, then chown it to the globus user:
# mkdir /usr/local/globus-4.1.2.1 # chown globus:globus /usr/local/globus-4.1.2.1![[Important]](/docbook-images/important.gif)
Important If for some reason you do not create a user named "globus", be sure to run the installation as a non-root user. In that case, make sure to pick an install directory that your user account has write access to.
Download the required software noted in Software Prerequisites for Installing GT 4.1.2.
![[Tip]](/docbook-images/tip.gif)
Tip Be aware that Apache Ant will use the Java referred to by JAVA_HOME, not necessarily the first Java executable on your PATH. Be sure to set JAVA_HOME to the top-level directory of your Java installation before installing.
Also, check the Platform Notes for GT 4.1.2 if your OS includes ant already. Your
/etc/ant.confis probably configured to use gcj, which will fail to compile the Toolkit.In this guide we will assume that you are installing to
/usr/local/globus-4.1.2.1, but you may replace/usr/local/globus-4.1.2.1with whatever directory you wish to install to.As the globus user, run:
globus$ export GLOBUS_LOCATION=
/usr/local/globus-4.1.2.1globus$ ./configure --prefix=$GLOBUS_LOCATIONYou can use command line arguments to ./configure for a more custom install. Here are the lines to enable features which are disabled by default:
Optional Features: --enable-prewsmds Build pre-webservices mds. Default is disabled. --enable-wsgram-condor Build GRAM Condor scheduler interface. Default is disabled. --enable-wsgram-lsf Build GRAM LSF scheduler interface. Default is disabled. --enable-wsgram-pbs Build GRAM PBS scheduler interface. Default is disabled. --enable-i18n Enable internationalization. Default is disabled. --enable-drs Enable Data Replication Service. Default is disabled. [...] Optional Packages: [...] --with-iodbc=dir Use the iodbc library in dir/lib/libiodbc.so. Required for RLS builds. --with-gsiopensshargs="args" Arguments to pass to the build of GSI-OpenSSH, like --with-tcp-wrappers
For a full list of options, see ./configure --help. For a list of GSI-OpenSSH options, see Optional Build-Time Configuration for GSI-OpenSSH. For more information about our packaging or about choosing a flavor, see Packing Details for Installing GT 4.1.2.
Run:
globus$ make
Note that this command can take several hours to complete. If you wish to have a log file of the build, use tee:
globus$ make 2>&1 | tee build.log
The syntax above assumes a Bourne shell. If you are using another shell, redirect stderr to stdout and then pipe it to tee.
![[Note]](/docbook-images/note.gif)
Note Using make in parallel mode (-j) is not entirely safe, and is not recommended.
Finally, run:
globus$ make install
This completes your installation. Now you may move on to the configuration sections of the following chapters.
We recommend that you install any security advisories available for your installation, which are available from the Advisories page. You may also be interested in subscribing to some mailing lists for general discussion and security-related announcements.
Your next step is to setup security, which includes picking a CA to trust, getting host certificates, user certificates, and creating a grid-mapfile. The next three chapters cover these topics.
With security setup, you may start a GridFTP server, configure a database for RFT, and configure WS-GRAM. You may also start a GSI-OpenSSH daemon, setup a MyProxy server, run RLS, and use CAS. The following chapters will explain how to configure these technologies. If you follow the chapters in order, you will make sure of performing tasks in dependency order.
[For advanced developers: general instructions for building from CVS and then list of branches? just link to existing page...]
[For advanced developers: general instructions for building from source then table with list of packages?]
The following is a list of links to more detailed installation information available for the following components: