GT 4.0 C WS Core : System Administrator's Guide

1. Introduction

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

[Important]Important

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

2. Building and Installing

In order to build and install the C WS-Core component from an official release:

Table 1. Building C WS Core from installer

1

Obtain the latest GT 4.x.x release tarball installer from the Download webpage.

2

Untar the tarball:

 tar xvfz gt<version>-all-source-installer.tar.gz

3

Change to the installer directory:

 cd gt<version>-all-source-installer

4

Run:

./configure -prefix=<path to install>

5

Run:

make wsc

6

Run:

make install

In order to build C WS Core from CVS:

Table 2. Building C WS Core from CVS

1

Obtain the source code for C WS Core from CVS:

  1. To get the latest source from CVS execute:

     cvs -d :pserver:anonymous@cvs.globus.org:/home/globdev/CVS/globus-packages \
         checkout packaging

  2. Change into the packaging directory.

     cd packaging

2Set the GLOBUS_LOCATION environment variable to the absolute path of the target directory of your installation.

On Unix/Linux:

 setenv GLOBUS_LOCATION /soft/gt4/

or

 export GLOBUS_LOCATION=/soft/gt4/

3

Run make-packages.pl

 ./make-packages.pl -bundles=gt4-c-ws-core -deps -install=$GLOBUS_LOCATION

3. Configuring

3.1. Configuration overview

The C WS-Core component does not provide global configuration functionality.

4. Deploying

The C WS-Core does not require configuration/deployment steps. All parameter configuration is done programmatically at present.

5. Testing

The C WS-Core has a test suite that tests a number of different packages included in the component. The tests can be built using either the wsctests target to make in the installer of a release, or they can be built using the gt4-c-ws-core-test bundle in the ./make-packages.pl command mentioned previously.

The tests are installed into $GLOBUS_LOCATION/test, and can be run from the appropriate sub-directories.

6. Security Considerations

C WS-Core supports secure transport (https) and secure message (just X509 signing, not encryption).

6.1. Secure Transport

With secure transport, the entire container must be run over an https transport. This is done by default for the C container. If the user does not want security in the container, or wants to use secure message instead of secure transport, they should use the -nosec argument to globus-wsc-container.

For clients, the secure transport is enabled if the contact URI contains the 'https' scheme instead of 'http', so the client doesn't have to enable or disable it explicitly.

7. Troubleshooting

This is a new component. If you are having trouble using it, please let us know!

8. Usage statistics collection by the Globus Alliance

The following usage statistics are sent by C WS Core by default in a UDP packet :

  • Component identifier
  • Usage data format identifier
  • Time stamp
  • Source IP address
  • Source hostname (to differentiate between hosts with identical private IP addresses)

It sends it at container startup (globus-wsc-container) and receipt of that packet tells us that the container started.

If you wish to disable this feature, you can set the following environment variable before running the C container:

export GLOBUS_USAGE_OPTOUT=1

By default, these usage statistics UDP packets are sent to usage-stats.globus.org:4180 but can be redirected to another host/port or multiple host/ports with the following environment variable:

export GLOBUS_USAGE_TARGETS="myhost.mydomain:12345 myhost2.mydomain:54321"

You can also dump the usage stats packets to stderr as they are sent (although most of the content is non-ascii). Use the following environment variable for that:

export GLOBUS_USAGE_DEBUG=MESSAGES

Also, please see our policy statement on the collection of usage statistics.