::SAGA DOCUMENTATION FILE::

:ADAPTOR NAME:

  Globus GRAM2 Job Adaptor
  
:AUTHORS:

  Copyright (c) 2006-2008 Ole Weidner (oweidner@cct.lsu.edu)

:LICENSE:

  Distributed under the Boost Software License, Version 1.0.
  
:ADAPTOR LIBRARY NAME:
  
  globus_gram_job_adaptor.so (dylib)

:IMPLEMENTS PACKAGE:
 
  - saga_package_job

:DESCRIPTION:

  The adaptor allows (remote) job submission/control/monitoring using the Globus
  GRAM2 (preWS) protocol. 

:URL SCHEMES:

  - gram://

:REQUIRES:

  In order to build and use the adaptor, the Globus Toolkit including the 
  development headers/libraries must be installed.

:CONFIGURE OPTIONS:

  | 
  | --with-globus-location=<dir>  use globus at <dir> (default=auto)         |\\
  | --with-gpt-location=<dir>     use gpt at <dir> (default=auto)            |\\
  | --with-globus-flavor=<flavor> use globus flavor <flavor> (default=auto)  |\\
  |                                                                          |\\
  |  GLOBUS_LOCATION              Globus installation directory              |\\
  |  GPT_LOCATION                 GPT installation directory                 |\\
  |  GLOBUS_FLAVOR                Globus installation flavor                 |\\

:INI FILE:

  globus_gram_job_adaptor.ini

:INI OPTIONS:

  none

:KNOWN ISSUES:

  I/O redirection will most likely not work if you're behind a firewall. The
  run_job(), get_stdout() and get_stderr() calls will fail:

  globus_gram_job: Unable run the job because: [Globus GRAM] the job manager \
                   failed to open stderr (74)

  This is a Globus issue and *not* a SAGA problem but it's still annoying. Check
  out the Globus Firewall Requirements document for more information:

  http://globus.org/toolkit/security/firewalls/Globus-Firewall-Requirements-9.pdf