Now that the services are running on nodeB and there is a generic user on nodeA that has a valid certificate, you can proceed with basic testing of the services on nodeB.

The first thing to do is add user jane's credentials to the grid-mapfile on nodeB so that the services on nodeB accept the credentials and user jane can authenticate to those services.

Use the 'grid-cert-info' command as user jane with the '-subject' flag on nodeA to determine the full certificate name or subject for user jane's credentials:

[jane@nodeA ~]$ grid-cert-info -subject
/O=Grid/OU=GlobusTest/OU=ps.univa.com/CN=Jane User

Go back to nodeB and add this user to the grid-mapfile. Be sure to put the certificate name in double quotes as shown, and be sure to add the UNIX account name after the certificate name as shown:

[globus@nodeB ]$ cat /opt/globus-4.0.1/etc/grid-mapfile
"/O=Grid/OU=GlobusTest/OU=ps.univa.com/CN=Jane User" jane

Now back as user jane on nodeA create a proxy certificate for user jane by running 'grid-proxy-init'. When prompted enter the pass phrase that protects user jane's private key:

[jane@nodeA ~]$ grid-proxy-init
Your identity: /O=Grid/OU=GlobusTest/OU=ps.univa.com/CN=Jane User
Enter GRID pass phrase for this identity:
Creating proxy .................................... Done
Your proxy is valid until: Thu Feb 23 23:41:02 2006

You can use the 'grid-proxy-info' command with the '-all' flag to see the details of the proxy:

[jane@nodeA ~]$ grid-proxy-info -all
subject : /O=Grid/OU=GlobusTest/OU=ps.univa.com/CN=Jane User/CN=1947642770
issuer : /O=Grid/OU=GlobusTest/OU=ps.univa.com/CN=Jane User
identity : /O=Grid/OU=GlobusTest/OU=ps.univa.com/CN=Jane User
type : Proxy draft (pre-RFC) compliant impersonation proxy
strength : 512 bits
path : /tmp/x509up_u101
timeleft : 11:59:53

The first thing to test is to see if user jane can authenticate to the globus-gridftp-server running on nodeB and move a file from nodeB to nodeA:

[jane@nodeA ~]$ globus-url-copy -vb gsiftp://nodeb.ps.univa.com/etc/issue file:/tmp/foo
Source: gsiftp://nodeb.ps.univa.com/etc/
Dest: file:/tmp/
issue -> foo

[jane@nodeA ~]$ cat /tmp/foo
Fedora Core release 4 (Stentz)
Kernel \r on an \m

The next thing to test is submitting a simple job to the GRAM WS running on nodeB. Note that we will only use the 'fork' jobmanager for now. We will not be using PBS:

[jane@nodeA ~]$ globusrun-ws -submit -streaming -F https://nodeb.ps.univa.com:8443/wsrf/services/ManagedJobFactoryService -c /usr/bin/whoami
Delegating user credentials...Done.
Submitting job...Done.
Job ID: uuid:9ea53924-a49c-11da-8a6e-0011d8b1eb22
Termination time: 02/24/2006 18:45 GMT
Current job state: Active
Current job state: CleanUp-Hold
jane
Current job state: CleanUp
Current job state: Done
Destroying job...Done.
Cleaning up any delegated credentials...Done.

Note the single line of output 'jane'. That is the output from the actual '/usr/bin/whoami' command that was run on nodeB remotely.

Try running the '/bin/date' command remotely:

[jane@nodeA ~]$ globusrun-ws -submit -streaming -F https://nodeb.ps.univa.com:8443/wsrf/services/ManagedJobFactoryService -c /bin/date
Delegating user credentials...Done.
Submitting job...Done.
Job ID: uuid:d069feea-a49c-11da-84e9-0011d8b1eb22
Termination time: 02/24/2006 18:47 GMT
Current job state: Active
Current job state: CleanUp-Hold
Thu Feb 23 12:47:19 CST 2006
Current job state: CleanUp
Current job state: Done
Destroying job...Done.
Cleaning up any delegated credentials...Done.

< Back Next >