MAiN
 
  BAcK to Session
 
  BAcK to Curriculum
 
:: Instructions for certificate installation, conversion, and check


1) Open a window on grid-tutor.ct.infn.it.
Use the secure shell client to ssh onto grid-tutor.ct.infn.it, using the username
and password that you gave when you applied for the certificate.


2) copy <certfile> from your computer to grid-tutor.ct.infn.it
Open file transfer client from the secure shell client; its the 4th icon
from the right. The connection to grid-tutor is made for you, showing your files
on grid-tutor in the right hand window. Copy your certificate by drag-and-drop.


Continue by using the secure shell client:

3) mkdir .globus

4) mv <certfile> .globus

5) cd .globus

6) openssl pkcs12 -nocerts -in <certfile> -out userkey.pem
You will be asked for two passwords: one set when you exported the certificate from
the browser; the other is the password of the certificate.

7) openssl pkcs12 -clcerts -nokeys -in <certfile> -out usercert.pem
You will be asked for the password set when you exported the certificate.

8) chmod 644 usercert.pem
This allows the public key to be read by anyone, but only deleted by the owner.

9) chmod 400 userkey.pem
This allows only the owner to have read-access to the private key.

10) cd ..

NOW, YOU ARE ABLE TO RUN A JOB ON THE GILDA TESTBED
FROM THE COMMAND LINE:.. but if you wish you can jump to follow instructions
in help-myproxy to use GENIUS.

11) grid-proxy-init
Creates a proxy that the UI machine will attach to any job you submit. (The private and
public key are not sent anywhere; this proxy is a "temporary certificate" valid for 12 hours.)
You are asked for your "pass phrase": the password of your certificate.

12) grid-proxy-info
Checks that the proxy exists:

13) edg-job-list-match hostname.jdl
This shows the Computing Elements (CE) that are available for your job, specified
by the .jdl file.

14) edg-job-submit hostname.jdl
Submits the job, NOTE THE URI THAT IS THE JOB-IDENTIER, it looks like a URL but
there is no web page etc, its a unique string.

15) edg-job-status https://grid....<rest of URI>
Gives the status; repeat until the command returns "Done" with "error code=0"

16) mkdir output
Make a directory to keep output away from other files.

17) edg-job-get-output --dir output https://grid....<rest of URI>
Gets your output from the Resource Broker, which holds the output sandbox (so there is no
direct contact with the machien on which the job executed)

BY NOW YOU KNOW WHY GENIUS WAS CREATED...

18) Go help-myproxy to use GENIUS.