Software Links
Getting Started
- Doc Structure
- A Globus Primer
- Globus Is Modular!
- Quickstart
- Installing GT
- Platform Notes
- GT Developer's Guide
- GT User's Guide (coming soon)
- Migrating from GT2
- Migrating from GT3
Reference
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces (coming soon)
- Resource Properties
- Samples
- Glossary
- Performance Studies (coming soon)
Manuals
Common Runtime
Security
- Non-WS (General) Security
- WS Java Security
- Message-level
- Authz Framework
- CAS
- Delegation Service
- MyProxy
- GSI-OpenSSH
- SimpleCA
- SGAS
Data Mgt
MDS4
Execution Mgt
To run the GTCP tests, start a Globus container, make sure that $GLOBUS_LOCATION is set and that you have a valid proxy certificate, and then run this command:
ant -f ${GLOBUS_LOCATION}/etc/globus_telecontrol_gtcp_service/build.xml \
-Dweb.server.url=your_container_base_url \
test-installed
where your_container_base_url is the base url of your Globus container
(for example, https://127.0.0.1:8443/wsrf/services/).
If the
test output ends with:
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 16.556 sec
then the tests have passed. Note: because the test code checks that illegal requests fail, it may print some error messages and cause the container to print some error messages and/or stack traces. This is normal; as long as the test output reports that it ran 2 tests with 0 failures and 0 errors, the tests have passed.
If you wish to run these tests with an insecure container, you can set
the isSecure parameter to false in
$GLOBUS_LOCATION/etc/globus_telecontrol_gtcp_service/server-config.wsdd and proceed as above.