- Grid Computing and Middleware
- Prerequisites
- Globus Toolkit Installation
- Globus Toolkit Configuration and Testing
- Testing Globus Toolkit Services
- Sun N1 Grid Engine Software Installation
- Integrating Sun N1 Grid Engine Software With Globus Toolkit
- Integration Testing
- Troubleshooting
- About the Authors
- Related Resources
- Ordering Sun Documents
- Accessing Sun Documentation Online
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Testing Globus Toolkit Services
This section provides instructions for testing the Globus Toolkit services.
To Create a Proxy Certificate
Log in as a user who owns a certificate signed by a trusted CA.
Create a proxy certificate by entering the following command:
To check the validity of your proxy, use the following command:
Make sure that your PATH environment variable contains the $<GLOBUS_LOCATION>/bin directory and that the LD_LIBRARY_PATH environment variable contains the $<GLOBUS_LOCATION>/lib directory.
$ grid-proxy-init –debug –verify
This proxy certificate will be used for the tests described in the remainder of this section.
$ grid-proxy-info
Testing Globus Toolkit 2.4 Services
This section describes how to test Globus Toolkit version 2.4 services.
Make sure that you have a proxy certificate, created as described earlier in this section.
To Test GRAM
To test the GRAM service, run the following command:
$ globus-job-run <hostname>:<port>/jobmanager /bin/date
where <hostname> and <port> identify the machine and port number the globus-gatekeeper daemon runs on (port number defaults to 2119). For example:
$ globus-job-run solaris.ddns.comp.nus.edu.sg/jobmanager /bin/date
You should get the output of the date command. If you get an error, check the $<GLOBUS_LOCATION>/var/globus-gatekeeper.log file.
To Test GRIS and MDS
To test the GRIS server running at your Globus Toolkit site, run the following command:
$ grid-info-search -h <hostname> -p <port> -anonymous –L
where <hostname> and <port> identify the machine and port number the GRIS daemon runs on (port number defaults to 2135). For example:
$ grid-info-search -h solaris.ddns.comp.nus.edu.sg -anonymous –L
You should see an output of the directory service contents from the GRIS server.
To Test GridFTP
To test the gsiftp server running at your Globus Toolkit site, run the following command:
Verify that the destination file has been created, and that it is identical to the source file.
$ globus-url-copy -s "´grid-cert-info -subject´" \ <source_url> <dest_url>
where the <source_url> and <dest_url> allow the gsiftp and file protocols. For example:
$ globus-url-copy -s "´grid-cert-info -subject´" \ gsiftp://localhost:2811/tmp/src file:///tmp/dst
Testing Globus Toolkit 3.x Services
This section describes how to test Globus Toolkit version 3.x services.
Make sure that you have a proxy certificate, created as described earlier in this section.
To Test MMJFS
From the grid user account, execute the following command:
Check the container output for errors.
$ managed-job-globusrun -factory \ http://<hostname>:<port>/ogsa/services/base/gram/MasterForkManagedJobFactoryService -file $<GLOBUS_LOCATION>/etc/test.xml
For example:
$ managed-job-globusrun -factory \ http://solaris.ddns.comp.nus.edu.sg:8080/ogsa/services/base/gram/MasterForkManagedJobFactoryService -file $<GLOBUS_LOCATION>/etc/test.xml
In the home directory of the local user account mapped to your grid user DN, in the grid-mapfile file, you should find two files, stderr and stdout, corresponding to the execution of the submitted job. You can submit your own job description file to start a different job. The file must be in the Resource Specification Language (RSL) format. The file used in the previous example ships with the Globus Toolkit 3.x distribution.
NOTE
It is possible for the container to dump a set of exceptions, but the submitted job still finishes correctly. This action is not abnormal, and it is caused by the fact that services are instantiated on-the-fly. Additionally, it is possible that a service request is issued before the service has completed initialization.
To Test Index Services
Use the ogsi-find-service-data client utility provided by the Globus Toolkit 3.x distribution to run the following command:
$<GLOBUS_LOCATION>/bin/ogsi-find-service-data
where <GLOBUS_LOCATION> is the actual location of Globus Toolkit 3.x on your system; and you receive output from the index services for the http://localhost:8080/ogsa/services/base/registry/ContainerRegistryService service.
If you want to obtain information about other services or learn more about the ogsi-find-service-data utility, go to http://www.globus.org/ogsa/releases/final/docs/infosvcs/querysvcdata.html.
To Test RFT Services
Use the RFTClient utility that ships with Globus Toolkit 3.x.
RFTClient is a Java™ class that you can invoke from your Java Virtual Machine for the Java platform (JVM™). Documentation and usage examples for RFT are available at http://www-unix.globus.org/toolkit/reliable_transfer.html.