OGF25/Usage

This page describes how to quickly test the ARC1 clients. If you are looking for server side configuration follow the instructions: Server install and setup instructions.

The system needs to be able to find the Globus shared libraries. Otherwise warnings will be displayed since all other installed pugins are loaded. To avoid these messages you can do something like:

 export LD_LIBRARY_PATH=/opt/globus/lib

Certificates

To test most of the functionality of ARC you need to have a valid X509 user certificate. If you don't have certificate already, you can generate one using KnowARC instant certificate authority (CA) running at https://vls.grid.upjs.sk/CA. To use the certificate then please make sure that your server recognizes CA that generated the certificate.

There is a short video available that demonstrates use of the instant CA. The generation of certificates for both user and server using web interface is presented in the video.

A-REX service (job submission and management)

• generate your proxy certificate with grid-proxy-init -rfc or with arcproxy utility (see --help for usage).

arcproxy -d VERBOSE -P <path-to-your-proxy>/proxy -C <path-to-your-usercert>/usercert.pem  \
-K <path-to-your-userkey>/cert/userkey-un.pem -c validityPeriod=10000

When using arcproxy the following commands may help to setup the certificate/proxy environment if the command-line options are not preferred:

export X509_USER_CERT=$HOME/.globus/usercert.pem
export X509_USER_KEY=$HOME/.globus/userkey.pem
export X509_USER_PROXY=`mktemp /tmp/x509up.XXXXXX`

• in any case make sure that the X509_USER_PROXY env variable points to the location of your proxy certificate. grid-proxy-init requires the following setting:

 export X509_USER_PROXY=/tmp/x509up.u`id -u`

• create a job description in JSDL form (e.g. http://vls.grid.upjs.sk/arc1/get_hostname.xml) and save it as .xml. Please note that the current release requires that the executable (if locally staged) is explicitly listed as an inputfile.
• submit a job to your A-REX service (you have to know your A-REX endpoint) using arcsub command (see man arcsub for more details)

arcsub -c ARC1:https://example.org:60000/arex your_job.xml  # (a jobID will be returned)

• monitor the status of your job with arcstat (see man arcstat for more details)

arcstat -a
arcstat jobID

• get the results of finished job using arcget command (see man arcget for more details)

arcget -a 
arcget jobID

• clean your job on a cluster using arcclean command (see man arcclean for more details)

arcclean jobID

• kill your running job using arckill command (see man arckill for more details)

arckill jobID

ECHO service

client.xml config file needs to be correctly configured. You can find the example config file in @ARC_LOCATION/share/doc/arc/

arcecho https://example.org:60000/Echo hallo  

If ECHO service was configured without the TLS layer, replace https with http.

HOPI service (simplified HTTP server)

• point your favourite web browser to your HOPI endpoint url (e.g. http://example.org:50000/httpd). You should see the content of /tmp/httpd directory.
• use wget or curl to PUT, GET the files to/from your HOPI service (again use the same endpoint url here)

Storage service

• for this step see detailed description in a Storage service README file

CHARON service (policies)

• for this step see the detailed description in Charon client README and Charon service README
• usage of CHARON service is related to proper configuration of charon_policy.xml which was defined on the CHARON service side
• Notice that to use Charon client a userkey has to be unencrypted