Globus Toolkit 3.2: Installation Guide
Overview
Before You Begin
Support Software
Installing GT 3.2
Configuring
>Testing
Troubleshooting
Testing Your Installation
Starting
the container |
|
| After following instructions for installing and configuring the Globus Toolkit 3.2, you should be able to start the standalone container that is automatically installed. | |
| 1 | If you installed GT3.x core only, run globus$ grid-proxy-init to create a proxy certificate for use by the container. If you have a full install with a host certificate and have run setperms.sh, a proxy of the host certificate will automatically be created. |
| 2 | To start the container, run: globus$ bin/globus-start-container Note: The container will log to the terminal, and will not return control to the prompt. |
Testing
the OGSA ServiceData Browser GUI |
|
With the container running, a client can access servicedata through a graphic user interface, the ServiceData Browser. | |
| 4 | To test the OGSA ServiceData Browser GUI, run: user$ bin/globus-sdb
In the frame that opens up, you can select a service from the list of services. It will let you inspect the servicedata elements of each service in either raw or tree mode. From a testing perspective, this mainly lets you examine the list of running services. If you're a developer interested in interacting with the samples, see Samples. |