This guide contains advanced configuration information for system administrators working with GTCP. It provides references to information on procedures typically performed by system administrators, including installation, configuring, deploying, and testing the installation.

	Important
	This information is in addition to the basic Globus Toolkit prerequisite, overview, installation, security configuration instructions in the GT 4.1.1 System Administrator's Guide. Read through this guide before continuing!

2. Building and installing

To install GTCP:

Install the Globus Toolkit.
Set your GLOBUS_LOCATION environment variable to the directory in which the Globus Toolkit has been installed.

Run this command:

    $GLOBUS_LOCATION/sbin/gpt-build gt4-gtcp-0.3-src_bundle.tar.gz

3. Configuring

The following parameters, set in $GLOBUS_LOCATION/etc/globus_telecontrol_gtcp_service/server-config.wsdd, are used to configure GTCP:

Table 1. GTCP configuration parameters

Name	Meaning
gtcpBackendFactory	Name of the desired GTCP plugin class.
isSecure	If `true`, GTCP will allow only users in the gridmap file to perform operations that change system state.
gridMapFile	Name of the gridmap file to be used if `isSecure` is set.

4. Deploying

Once GTCP is installed, no further deployment steps are necessary.

5. Testing

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.

6. Security considerations

In some applications, control of physical equipment carries the risk of serious property damage or injury. These applications should implement operational security procedures and not rely solely on software security.

7. Troubleshooting

If the unit tests fail, double-check the format of the URL specified on the ant line. The test code is somewhat unforgiving; if the trailing "/" is omitted, then the tests will fail.

Prev	Up	Next
GT 4.1.1 Release Notes: Globus Teleoperations Control Protocol (GTCP)	Home	Part . GT 4.1.1 Tech Preview: Workspace Management Service (WMS)