Java CoG Kit Command Line Programs

This document includes the command line tools that are distributed as part of the Java CoG Kit.

1.1 Reproduction

The material presented in this document can not be published, mirrored, electronically or otherwise reproduced without prior written consent. As you can link to this document, this should not pose much of a restriction.

1.2 Viewing

The best way to read this document is with Adobe Acrobat Reader. Please make sure you conﬁgure Adobe Acrobat Reader appropriately so you can follow hyperlinks. This is the case if you follow the default installation. Acrobat Reader is available at http://www.adobe.com/products/acrobat/readermain.html. Because the hyperlinks are not available in the printed form of this manual and we support saving our environment we strongly discourage printing this document.

We recommend that you save this manual locally on your machine and use Acrobat Reader. This has the advantage that you do not lose your anchor points while switching back and forth between different hyperlinks. An HTML version of this manual is planed, but not available yet.

1.3 Format

We have augmented the document with some comments at places where we found issues. Our intend is to address these issues in a future release. The comments are marked by the icon to do and the name of the person that will work on the removal of the issue.

2 Registration

Please be a team player and support us indirectly by registering with us or reporting your use of the Java CoG Kit. Although this software is free, we still need to justify to our funders the usefulness of the projects. If you want to help us with our efforts please take a few seconds to complete this information. We do not use this information for other purposes. If you have special needs or concerns please contact gregor@mcs.anl.gov. The registration form can ﬁlled out in a variety of formats. The online form can be found at

3 Introduction

4 Compilation

4.1 build

  NAME
      ant - the Java CoG Kit build process

  SYNOPSIS

      ant [help] [dist] [jar] [javadoc]
          [clean] [distclean] [cleanall]
   [all] [dist.joint]
          [eclipse.modules] [eclipse.all] [eclipse.clean]
   -f buildfile.xml

  DESCRIPTION

      The Java CoG kit preferd compilation process is controled by ant.

  OPTIONS

      help:
                 prints out this help message

      -f buildfile.xml
                use an alternate xml build file

      dist:
                 creates a distribution directory of the Java CoG
                 Kit. Compiled classes from different modules will be in
                 different jars. Use dist.joint to put everything into
                 one jar file.

      jar:
                 creates a jar file for the ${project} ${long.name}
                 named ${jar.filename}

      javadoc:
                 creates the documentation

      clean:
                 removes the compiled classes

      cleanall:
                 removes the compiled classes including the ones in
                 the modules

      distclean:
                 deletes the distribution directory

      all:
                 dist and javadoc

      dist.joint:
                 does a dist for all modules, and puts all compiled
                 classes into one jar file

      eclipse.modules:
              creates Eclipse project files for each module in the
                 modules directory. Each module can then be imported
                 into Eclipse as a project. The project dependencies,
                 source directories, and libraries will be automatically
                 set-up

      eclipse.all:
                 creates one Eclipse project, in the cog directory,
                 which includes all of the Java CoG Kit modules.  This
                 makes it more convenient to import the CoG into Eclipse
                 (since there is just one project).  However, the
                 advantages of modularity are gone.

      eclipse.clean:
                 cleans all Eclipse related files from the CoG source
                 tree. This works as a complement to eclipse.modules and
                 eclipse.all. If Eclipse projects were created
                 otherwise, the build directory may not be deleted.

5 Security

5.1 grid-proxy-init

  NAME
      grid-proxy-init

  DESCRIPTION
      TBD

  SYNOPSIS
      grid-proxy-init [options]
      grid-proxy-init -help

  OPTIONS
      -help | -usage
          Displays usage.

      -version
          Displays version.

      -debug
          Enables extra debug output.

      -verify
          Performs proxy verification tests (default).

      -noverify
          Disables proxy verification tests.

      -quiet | -q
          Quiet mode, minimal output

      -limited
          Creates a limited proxy.

      -independent
          Creates a independent globus proxy.

      -old
          Creates a legacy globus proxy.

      -hours <hours>
          Proxy is valid for H hours (default:12).

      -bits <bits>
          Number of bits in key {512|1024|2048|4096}.

      -globus
          Prints user identity in globus format.

      -policy <policyfile>
          File containing policy to store in the ProxyCertInfo
          extension

      -pl <oid>
          OID string for the policy language.

      -policy-language <oid>
          used in the policy file.

      -path-length <l>
          Allow a chain of at most l proxies to be generated
          from this one

      -cert <certfile>
          Non-standard location of user certificate

      -key <keyfile>
          Non-standard location of user key

      -out <proxyfile>
          Non-standard location of new proxy cert.

      -pkcs11
          Enables the PKCS11 support module. The -cert and
          -key arguments are used as labels to find the
          credentials on the device.

  SEE ALSO
      ProxyInit

5.2 visual-grid-proxy-init

  NAME
      vizual-grid-proxy-init

  SYNOPSIS

  DESCRIPTION

  OPTIONS

  BUGS
      no -help

5.3 grid-proxy-info

  NAME
      grid-proxy-info

  SYNOPSIS
      grid-proxy-info [options]
      grid-proxy-info -help

  DESCRIPTION
      TBD

  OPTIONS
      -help | usage
              Displays usage.
      -file <proxyfile>  (-f)
              Non-standard location of proxy.
      [printoptions]
              Prints information about proxy.
      -exists [options]  (-e)
              Returns 0 if valid proxy exists, 1 otherwise.
      -globus
              Prints information in globus format
       [printoptions]
      -subject
              Distinguished name (DN) of subject.
      -issuer
              DN of issuer (certificate signer).
      -identity
              DN of the identity represented by the proxy.
      -type
              Type of proxy.
      -timeleft
              Time (in seconds) until proxy expires.
      -strength
              Key size (in bits)
      -all
              All above options in a human readable format.
      -text
              All of the certificate.
      -path
              Pathname of proxy file.
       [options to -exists] (if none are given, H = B = 0 are assumed)
      -hours H     (-h)
              time requirement for proxy to be valid.
      -bits  B     (-b)
              strength requirement for proxy to be valid

  SEE ALSO
      ProxyInfo

5.4 grid-proxy-destroy

  NAME
      grid-proxy-destry - TBD

  DESCRIPTION
      TBD

  SYNOPSIS
      grid-proxy-destry [-dryrun] [file1...]
      grid-proxy-destry -help

  OPTIONS
      -help | -usage
   Displays usage
      -dryrun
   Prints what files would have been destroyed
      file1 file2 ...
   Destroys files listed

  SEE ALSO
      ProxyDestroy

5.5 grid-cert-info

  NAME
      grid-cert-info - TBD

  SYNOPSIS
      grid-cert-info [-help] [-file certfile] [-all] [-subject] [...]

  DESCRIPTION

      Displays certificate information. Unless the optional
      file argument is given, the default location of the file
      containing the certficate is assumed:

      C:\Documents and Settings\username\.globus\usercert.pem

      under unix it is

      ~/.globus.usercert.pem

  OPTIONS
      -help | -usage
              Display usage.

      -version
              Display version.

      -file certfile
              Use ’certfile’ at non-default location.

      -globus
              Prints information in globus format.

       Options determining what to print from certificate

       -all
              Prints the whole certificate.

      -subject
              Prints the subject string of the cert.

      -issuer
              Prints the issuer.

      -startdate
              Prints the validity start date of the cert.

      -enddate
              Prints the validity end date of the cert.

  SEE ALSO
      CertInfo

      myproxy

      the new cog ca

5.6 grid-change-pass-phrase

  NAME
      grid-change-pass-phrase - TBD

  SYNOPSIS
          grid-change-pass-phrase [-help] [-version] [-file private_key_file]

  DESCRIPTION

      Changes the passphrase that protects the private key. If
      the -file argument is not given, the default location of
      the file containing the private key is assumed:

      C:\Documents and Settings\username\.globus\userkey.pem

      under unix it is

      ~/.globus/userkey.pem

  OPTIONS

      -help | -usage
   Display usage.

      -version
   Display version.

      -file location
   Change passphrase on key stored in the file at
   the non-standard location ’location’.

  SEE ALSO
      ChangePassPhrase

5.7 globus2jks

  NAME
          globus2jks - converts globus user credentials to jks

  SYNOPSIS

          globus2jks [-help|-usage] [-version] [-debug]
                     [-cert filename] [-key filename]
                     [-alias alias] [-password passwd]
                     [-out keystorfile]

          globus -help

           Converts Globus credentials (user key and
           certificate) into Java keystore format (JKS
           format supported by Sun).

  OPTIONS
          -help | -usage
                   Displays usage.
          -version
                    Displays version.
          -debug
                    Enables extra debug output.
          -cert     certfile

                    Non-standard location of user certificate.

          -key      keyfile
                    Non-standard location of user key.
          -alias    alias
                    Keystore alias entry. Defaults to ’globus’
          -password password

                    Keystore password. Defaults to ’globus’

          -out      <keystorefile>

                    Location of the Java keystore
                    file. Defaults to ’globus.jks’

  SEE ALSO

      KeayStoreConvert

5.8 myproxy

  NAME
      myproxy -

  SYNOPSIS
      myproxy [common options] command [command options]
      myproxy -version
      myproxy -help

  DESCRIPTION
      TBD

  OPTIONS
      -help
              Displays usage

      -v | -version
              Displays version

      -h <host> | -host <host>
              Hostname of the myproxy-server

      -p <port> | -port <port>
              Port of the myproxy-server
              (default 7512)

      -s <subject> | -subject <subject>
              Performs subject authorization

      -l <username> | -username <username>
              Username for the delegated proxy

      -d | -dn_as_username
              Use the proxy certificate subject (DN) as the
              default username instead of the "user.name"
              system property.

      COMMANDS
           put     - put proxy
           get     - get proxy
           anonget - get proxy without local credentials
           destroy - remove proxy
           info    - credential information
           pwd     - change credential password

           Specify - help after a command name for
                     command-specific help.

  SEE ALSO

6 Job Management

6.1 cogrun

  NAME
      cogrun - Submits a task for remote Grid execution

  SYNOPSIS
      cogrun -s hostname -p provider -e executable
              [-jm <jobmanager>][-args <arguments>] [-b] [-r] [-stdout <file>]
              [-a <attributes>] [-env <env variables>] [-d <dir>][-c <checkpointfile>] [-stderr <file>] [-v]
      cogrun -help

  DESCRIPTION
      This command submits a user-specified executable for remote
      execution. The user can specify the service contact for the job
      manager, the provider, the executable, and the optional
      arguments. Several other optional parameters control the behavior
      of the execution. The user can execute this job as a batch job,
      whereby the job status will not be updated on the client side. The
      user can also redirect the job output and error to a user-supplied
      file, either on the remote machine or on the local machine.

  OPTIONS
      -name <taskName> | -n <taskName>
        Task name

      -service-contact <host> | -s <host>
        Service contact of the remote job manager

      -job-manager <jobmanager> | -jm <jobmanager>
        Execution JobManager (fork, pbs, etc)execution environment,

      -provider <provider> | -p <provider>
        Provider; available providers: [gt2ft, gsiftp, file, gt4.0.0,
      gt3.0.2, ssh, gt4ft, gridftp, local, gsiftp-old, http, gt3.2.1,
      gt2, gt3.2.0, gridftp-old, ftp, webdav]

      -executable <file> | -e <file>
        Executable file. Should be available on the remote machine

      -arguments <string> | -args <string>
        Arguments. If more than one, use quotes

      -environment <string> | -env <string>
        Environment variables for the remote execution environment,
        specified as "name=value[,name=value]"

      -directory <string> | -d <string>
        Target directory

      -batch | -b
        If present, the job is run in batch mode

      -redirected | -r
        If present, the arguments to -stdout and -stderr refer to local
        files

      -stdout <file>
        Indicates a file where the standard output of the job should be
        redirected

      -stderr <file>
        Indicates a file where the standard error of the job should be
        redirected

      -attributes <string> | -a <string>
        Additional task specification attributes. Attributes can be
        specified as "name=value[,name=value]"

      -checkpoint <filename> | -c <fileName>
        Checkpoint file name. The task will be checkpointed to this
        file once submitted

      -verbose | -v
        If enabled, display information about what is being done

      -help | -h
        Display usage


  SEE ALSO
      cog-file-transfer

6.2 cog-job-submit

  NAME
  cog-job-submit - Submits a task for remote Grid execution

  SYNOPSIS
      cog-job-submit -s hostname -p provider -e executable
                     [-args <arguments>] [-b] [-r] [-stdout <file>]
      [-stderr <file>] [-v]
      cog-job-submit -help

  DESCRIPTION
      This command submits a user-specified executable for remote
      execution. The user can specify the service contact for the job
      manager, the provider, the executable, and the optional
      arguments. Several other optional parameters control the behavior
      of the execution. The user can execute this job as a batch job,
      whereby the job status will not be updated on the client side. The
      user can also redirect the job output and error to a user-supplied
      file, either on the remote machine or on the local machine.

  OPTIONS

       -name <taskName> | -n <taskName>
        Task name

      -service-contact <host> | -s <host>
        Service contact of the remote job manager

       -job-manager <jobmanager> | -jm <jobmanager>
        Execution JobManager (fork, pbs, etc)

      -provider <provider> | -p <provider>
        Provider; available providers: [gt2ft, gsiftp, file, gt4.0.0,
        gt3.0.2, ssh, gt4ft, gridftp, local, gsiftp-old, http, gt3.2.1,
        gt2, gt3.2.0, gridftp-old, ftp, webdav, condor]

      -executable <file> | -e <file>
        Executable file. Should be available on the remote machine

      -arguments <string> | -args <string>
        Arguments. If more than one, use quotes

      -environment <string> | -env <string>
        Environment variables for the remote execution environment,
        specified as "name=value[,name=value]"

      -directory <string> | -d <string>
        Target directory

      -batch | -b
        If present, the job is run in batch mode

      -redirected | -r
        If present, the arguments to -stdout and -stderr refer to local
        files

      -stdout <file>
        Indicates a file where the standard output of the job should be
        redirected

      -stderr <file>
        Indicates a file where the standard error of the job should be
        redirected

      -attributes | -a) <string>]
        Additional task specification attributes. Attributes can be
        specified as "name=value[,name=value]"

      -checkpoint | -c) <fileName>]
        Checkpoint file name. The task will be checkpointed to this file
        once submitted

      -verbose | -v
        If enabled, display information about what is being done

      -help | -h
        Display usage


  SEE ALSO
      cog-file-transfer, cog-file-operation

6.3 cog-checkpoint-submit

  NAME

     cog-checkpoint-submit - Reconnects to a previously checkpointed task

  SYNOPSIS

     cog-checkpoint-submit -c checkpointfile [-v] [-h]

     cog-checkpoint-submit -help

  DESCRIPTION

     This command allows the user to submit a checkpoint file
  (created by the cogrun, cog-job-submit, or cog-task2xml
  commands). Upon submission, the client re-connects to the remote
  execution service and actively monitors the status updates.

  OPTIONS

      -checkpoint <fileName>| -c <fileName>
        Input checkpoint file

      -verbose | -v
        If enabled, display information about what is being done

      -help | -h
        Display usage

  SEE ALSO
  cog-checkpoint-status, cog-job-submit, cogrun, cog-task2xml

6.4 cog-checkpoint-status

  NAME

    cog-checkpoint-status - checks the status of a long running task

  SYNOPSIS

    cog-checkpoint-status -c checkpointfile [-v] [-h]
    cog-checkpoint-status -help

  DESCRIPTION
    This command allows the user to check the status of a long
  running task. The task is represented by the checkpoint file
  (created by the cogrun, cog-job-submit, or cog-task2xml
  commands). Upon submission, the client re-connects to the remote
  execution service and retrieves the latest execution status.


  OPTIONS

      -checkpoint <fileName> | -c <fileName>
        Input checkpoint file

      -verbose | -v
        If enabled, display information about what is being done

      -help | -h
        Display usage

  SEE ALSO
  cog-checkpoint-submit, cog-job-submit, cogrun, cog-task2xml

6.5 cog-task2xml

  NAME

     cog-task2xml - translates the given task into XML format.

  SYNOPSIS

     cog-task2xml -c checkpointfile -s hostname -e executable
     [-n taskName] [-jm jobmanager] [-p provider] [-env environment]
     [-d dir] [-b] [-r] [-stdout outfile] [-stderr errfile]
     [-a attributes] [-v] [-h]

     cog-task2xml -help

  DESCRIPTION
     This command simply translates the given task into an XML
     format without actually submitting the task. The user can
     specify the service contact for the job manager, the
     provider, the executable, and the optional arguments. Several
     other optional parameters control the behavior of the execution. The user can
     execute this job as a batch job, whereby the job status will
     not be updated on the client side. The user can also redirect the
     job output and error to a user-supplied file, either on the
     remote machine or on the local machine.


  OPTIONS

      -checkpoint <fileName> | -c <fileName>
        Checkpoint file name. The task will be checkpointed to this file

      -name <taskName> | -n <taskName>
        Task name

      -service-contact <host> | -s <host>
        Service contact

      -job-manager <jobmanager> | -jm <jobmanager>
        Execution JobManager (fork, pbs, etc)

      -provider <provider> | -p <provider>
        Provider; available providers: [gt2ft, gsiftp, file, gt4.0.0,
        gt3.0.2, ssh, gt4ft, gridftp, local, gsiftp-old, http, gt3.2.1,
        gt2, gt3.2.0, gridftp-old, ftp, webdav]

      -executable | -e <file>
        Executable

      -arguments | -args <string>
        Arguments. If more than one, use quotes

      -environment <string> | -env <string>
        Environment variables for the remote execution environment,
        specified as "name=value[,name=value]"

      -directory | -d <string>
        Target directory

      -batch | -b
        If present, the job is run in batch mode

      -redirected | -r
        If present, the arguments to -stdout and -stderr refer to local
        files

      -stdout <file>
        Indicates a file where the standard output of the job should be
        redirected

      -stderr <file>
        Indicates a file where the standard error of the job should be
        redirected

      -attributes <string> | -a <string>
        Additional task specification attributes. Attributes can be
        specified as "name=value[,name=value]"

      -verbose | -v
        If enabled, display information about what is being done

      -help | -h
        Display usage

  SEE ALSO

  cog-checkpoint-submit, cog-checkpoint-status, cog-job-submit

6.6 globus-personal-gatekeeper

  NAME
      globus-personal-gatekeeper

  SYNOPSIS
      globus-personal-gatekeeper [-version] [-help]
              [-p port | -port port] [-d|-debug]
       [-s service_file]
       [-l log_file]
       [-gridmap gridmap_file]
       [-proxy cretential]
       [-serverKey key]
       [-serverCert cert]
       [-caCertDir cadir]

  OPTIONS
      -help | -usage
   Displays usage
      -p | -port
   Port of the Gatekeeper
      -d | -debug
   Enable debug mode
      -s | -services
   Specifies services configuration file.
      -l | -log
   Specifies log file.
      -gridmap
   Specifies gridmap file.
      -proxy
   Proxy credentials to use.
      -serverKey
   Specifies private key (to be used with -serverCert.
      -serverCert
   Specifies certificate (to be used with -serverKey.
      -caCertDir
   Specifies locations (directory or files) of trusted
   CA certificates.

  SEE ALSO
      Gatekeeper

  BUGS

      The name gatekeeper is incorrectly used in the Globus
      Toolkit. This shoudl be called the term
      execution-service should be used instead.

      The parameters of this command must be reviewed.

7 File Management

7.1 cog-ﬁle-transfer

  NAME
      cog-file-transfer - Transfers a Grid file from one file server to another

  SYNOPSIS
      cog-file-transfer -s source-uri -d destination-uri [-t]
      cog-file-transfer -help

  DESCRIPTION
      This command transfers a file hosted on one file server to another
      file server. If both the file servers are GridFTP servers, then
      the files can be transfered in third party mode.

  OPTIONS
      -source-uri <URI> | -s <URI>
        Source URI: <provider>://<hostname>[:port]/<directory>/<file>

      -destination-uri <URI> | -d <URI>
        Destination URI:
        <provider>://<hostname>[:port]/<directory>/<file>

      -thirdparty | -t
        If present, performs a third party file transfer. Valid only
        between two GridFTP resources

      -help | -h
        Display usage


  SEE ALSO
      cog-job-submit, cog-file-operation

7.2 cog-ﬁle-operation

  NAME
      cog-file-operation - Performs operations on files hosted on remote
   file servers

  SYNOPSIS
      cog-file-operation -s hostname -p provider
      cog-file-operation -help

  DESCRIPTION
      This command initiates a connection with a remote file server and
      allows the user to invoke operations on files hosted on that server.
      On execution, this commands enters a shell-based mode allowing the
      user to invoke file operations.

  OPTIONS
      -service-contact <host> | -s <host>
        Service contact of the remote file server

      -provider <provider> | -p <provider>
        Provider; available providers: [gridftp, ftp, and webdav]

      -verbose | -v
        If enabled, display information about what is being done

      -help | -h
        Display usage


  SEE ALSO
      cog-file-transfer, cog-job-submit

7.3 globus-url-copy

  NAME
      globus-url-copy

  SYNOPSIS
      globus-url-copy [-help]
          [-s subject]
   [-ss source subject]
   [-ds subject]
   [-noopt]
   [-nodcau]
          fromURL toURL

  DESCRIPTION
      TBD


  OPTIONS
      -s  <subject> | -subject <subject>
         Use this subject to match with both the source
         and destination servers

      -ss <subject> | -source-subject <subject>
         Use this subject to match with the source server

      -ds <subject> | -dest-subject <subject>
         Use this subject to match with the destination server

      -notpt | -no-third-party-transfers
         Turn third-party transfers off (on by default)

      -nodcau | -no-data-channel-authentication
         Turn off data channel authentication for ftp transfers
         Applies to FTP protocols only.

  PROTOCOLS SUPPORTED
      - gass (http and https)
      - ftp
      - gsiftp
      - file

  BUGS
      This should in future have a replacement in cog-transfer
      which is not the same as url copy.

  SEE ALSO
      GlobusUrlCopy

7.4 globus-gass-server-shutdown

  NAME

      globus-gass-server-shutdown - shuts down the gass server

  Syntax:

      globus-gass-server-shutdown [-help] [-usage]
                                  [-version] gass_server_url

  DESCRIPTION

      Allows the user to shut down a (remotely) running GASS
      server, started with client-shutdown permissions
      (option -c).

   Options:
   -help | -usage
   Displays usage
   -version
   Displays version

  SEE ALSO
      GassServerShutdown

  BUGS
      option -c is not described

7.5 globus-gass-server

  NAME
      globus-gass-server [-version] [-help]

  DESCRIPTION
      start the gass server

  OPTIONS
      -help | -usage
   Displays usage
      -version
           Dispalys the version
      -s | -silent
   Enable silent mode (Don’t output server URL)
      -r | -read
   Enable read access to the local file system
      -w | -write
   Enable write access to the local file system
      -o
   Enable stdout redirection
      -e
   Enable stderr redirection
      -c | -client-shutdown
   Allow client to trigger shutdown the GASS server
   See globus-gass-server-shutdown
      -p <port> | -port <port>
   Start the GASS server using the specified port
      -i | -insecure
   Start the GASS server without security
      -n <options>
   Disable <options>, which is a string consisting
   of one or many of the letters "crwoe"

  SEE ALSO

      GassServer

8 Workﬂow

8.1 cog-graph-editor

  NAME
      graph-editor - TBD

  SYNOPSIS
      graph-editor <options>
          [-s <port>]
          [(-h | -help)]
          [(-l | -load) <file>]
          [-q | -quit]
          [-r | -loop]
          [(-o | -options) <options>]

  DESCRIPTION
      TBD

  OPTIONS
      -s <port>
          Starts the service on the specified port. If no port
          is specified, 9999 is used.

      -h | -help
          Displays this help message and exits.

      -l | -load <file>
          specifies a file to be loaded on startup

      -t | -target <target>
          Starts on the specified target. If missing, the
          default target (the Swing GUI) will be used

      -q | -quit
          Render the graph and quit. Useful with
          non-interactive targets.  This is the default when
          the -load option is used. In server mode, the
          program will wait for a graph first, render it and
          then quit.

      -r | -loop
          In server mode loop and wait for updates, and render
          them, as opposed to quitting after the graph is
          received.

      -o | -options <options>]
          Pass additional options to various
          sub-components. The value must be quoted and has the
          form [property=value[, property=value[,...]]]. Take
          a look at etc/grapheditor.properties for a list of
          properties.

  SEE ALSO
      TBD

8.2 cog-workﬂow-gui

  NAME
      cog-workflow-gui

  SYNOPSIS
    cog-workflow-gui [-help]
                [-load <file>]
         [-run]

  DESCRIPTION
      TBD

  OPTIONS
      [-load <file>]
        Loads the specified file

      [-run]
        If a workflow specification was loaded, it starts executing it;
        otherwise, it does nothing.

      [-help]
        Displays a usage summary

  SEE ALSO
     gridant

8.3 cog-workﬂow

  NAME
      cog-workflow - TBD

  SYNOPSIS

  DESCRIPTION

  OPTIONS

  BUGS

9 Information Services

9.1 grid-info-search

  NAME
      grid-info-search - TBD

  SYNOPSIS
      grid-info-search [ options ] <search filter> [attributes]

  DESCRIPTION
      Searches the MDS server based on the search filter,
      where some options are:

  OPTIONS
      -help
             Displays this message

      -version
             Displays the current version number

      -mdshost host (-h)
             The host name on which the MDS server is running
             The default is ROBIN.

      -mdsport port (-p)
             The port number on which the MDS server is running
             The default is 2135

      -mdsbasedn branch-point (-b)
             Location in DIT from which to start the search
             The default is ’mds-vo-name=local, o=grid’

      -mdstimeout seconds (-T)
             The amount of time (in seconds) one should allow to
             wait on an MDS request. The default is 30

      -anonymous (-x)
             Use anonymous binding instead of GSSAPI.

       grid-info-search also supports some of the flags that are
       defined in the LDAP v3 standard.
       Supported flags:

        -s scope   one of base, one, or sub (search scope)
        -P version protocol version (default: 3)
        -l limit   time limit (in seconds) for search
        -z limit   size limit (in entries) for search
        -Y mech    SASL mechanism
        -D binddn  bind DN
        -v         run in verbose mode (diagnostics to standard output)
        -O props   SASL security properties (auth, auth-conf, auth-int)
        -w passwd  bind password (for simple authentication)

  SEE ALSO
      TBD

10 Miscellaneous

10.1 sample-launcher

  NAME
      simple-launcher

  BUGS
  java.lang.NoClassDefFoundError: org/globus/cog/example/Class
  Exception in thread "main"

References

[1] G. von Laszewski, I. Foster, J. Gawor, and P. Lane, “A Java Commodity Grid Kit,” Concurrency and Computation: Practice and Experience, vol. 13, no. 8-9, pp. 643–662, 2001. [Online]. Available: http://www.mcs.anl.gov/~gregor/papers/vonLaszewski--cog-cpe-ﬁnal.pdf

[2] “Java CoG Kit Wiki,” 2004. [Online]. Available: http://www.cogkit.org/wiki

[3] “Java CoG Kit Registration,” 2004. [Online]. Available: http://www.cogkit.org/register

Additional publications about the Java CoG Kit can be found as part of the vita of Gregor von Laszewski http://www-unix.mcs.anl.gov/~laszewsk/vita.pdf. Most documents are avalable online if you follow the links. In future we intend to provide this information without Gregors vita data.

Appendix

A Java CoG Kit Guides


Short Title	Description	Format

Guide	A guide to help you ﬁnding out what guides have been written	[PDF] [HTML]

Install	A guide to the different ways of installing the Java CoG Kit	[PDF] [HTML]

Commands	A guide to the command line tools of the Java CoG Kit	[PDF] [HTML]

Workﬂow	A guide to the Gridant/Karajan Workﬂow	[PDF] [HTML]

Abstractions	A guide to the Java CoG Kit abstractions API	[PDF] [HTML]

JavaDoc	The Java API documentation to the Java CoG Kit	[HTML]

Coding	A guide to the Coding rules for the Java CoG Kit	[PDF] [HTML]

Overview	A future guide that will be an overview to the Java CoG Kit	[PDF] [HTML]

B Java CoG Kit Guides Under Construction

More guides are under development. The following guides are not yet completed, but are listed here to help us improving these guides. Please, explore them and send us e-mail about improvement suggestions. If you like to contribute a guide yourself, please contact gregor@mcs.anl.gov.

C Available Downloads

First time users of the Java CoG Kit should read the “Guide to Installing the Java CoG Kit” [PDF] [HTML]. We hope that you will ﬁnd this guide useful to decide which bundles you need. For the more experienced user, we provide the following table.

D Availability of the Document

It is not allowed to reproduce this document or the source. This documentation is copyrighted and is not distributed under the CoG Kit license.

E Bugs

This guide is constantly improved and your input is highly appreciated. Please report suggestion, errors, changes, and new sections or chapters through our Bugzilla system at

F Administrative Contact

The Java CoG Kit project has been initiated and is managed by Gregor von Laszewski. To contact him, please use the information below.

Index

Administrative Contact, 28

build, 4

cog-checkpoint-status, 16
cog-checkpoint-submit, 15
cog-ﬁle-operation, 20
cog-ﬁle-transfer, 19
cog-graph-editor, 23
cog-job-submit, 14
cog-task2xml, 17
cog-workﬂow, 24
cog-workﬂow-gui, 24
cogrun, 12
Command
    build, 4
    cog-checkpoint-status, 16
    cog-checkpoint-submit, 15
    cog-ﬁle-operation, 20
    cog-ﬁle-transfer, 19
    cog-graph-editor, 23
    cog-job-submit, 14
    cog-task2xml, 17
    cog-workﬂow, 24
    cog-workﬂow-gui, 24
    cogrun, 12
    globus-gass-server, 22
    globus-gass-server-shutdown, 22
    globus-personal-gatekeeper, 18
    globus-url-copy, 21
    globus2jks, 10
    grid-cert-info, 8
    grid-change-pass-phrase, 9
    grid-info-search, 25
    grid-proxy-destroy, 8
    grid-proxy-info, 7
    grid-proxy-init, 5
    myproxy, 11
    sample-launcher, 26
    visual-grid-proxy-init, 7
Contact, 28

globus-gass-server, 22
globus-gass-server-shutdown, 22
globus-personal-gatekeeper, 18
globus-url-copy, 21
globus2jks, 10
grid-cert-info, 8
grid-change-pass-phrase, 9
grid-info-search, 25
grid-proxy-destroy, 8
grid-proxy-info, 7
grid-proxy-init, 5

myproxy, 11

Registration, 2

sample-launcher, 26

visual-grid-proxy-init, 7