Administrator Guide

  This Guide covers the installation, configuration, and maintenance of gCore.

Prerequisites

The following software is a prerequisite for the installation of gCore:

• A platform compatible or made compatible with GT requirements.
• J2SE 1.5.08 SDK or greater. Sun's reference implementation is recommended, but versions from IBM, HP, or BEA should work equally well.
• Ant 1.6.5+ to build gCF sources or to develop services with it.
• a SVN client to install gCore from the SVN repository.
• GNU tar to install gCore from archived distributions.
• sudo to execute shell commands with controlled super-user privileges.

Running gCore in a secure infrastructure raises further prerequisites:

• A ntp server to synchronise your clock with other machines' for correct credential validation.
• [coming soon]

Finally, at least static IP address (if not a DNS name) is needed for all but the simplest testing scenarios.

Installation

gCore may be installed from a SVN repository, or else from pre-packaged archives.

In the first case, installing gCore is tantamount to downloading it into a directory of choice, the gCore location. In the second case, installing gCore is simply matter of expanding the downloaded archive into the the gCore location. In either case, proceed to the installation as a a non-privileged user with read and write permissions for the gCore location.

At the end of the process, the gCore location should contain the following structure:

|-bin
|
|-config
|
|-endorsed
|
|-etc
|
|-lib
|
|-libexec
|
|-share

Some folders are of immediate interest to administrators and developers alike:

bin	executables
config	gHN configuration files
etc	container and deployed service configuration files
lib	standard and deployed service libraries
share	build tools, standard and deployed service interfaces/schemas

Configuration

Configuring the installation can be roughly distributed across the following steps: configuring the environment, the container, the gHN associated with a running instance of the container, and the operation of the gHN in a secure infrastructure.

Configuring the environment

Define an environment variable GLOBUS_LOCATION and point it to the installation directory. Assuming a bash shell:

export GLOBUS_LOCATION = ...absolute path to your gCore location...

Adding $GLOBUS_LOCATION/bin to your PATH environment variable is also highly recommended:

export PATH = $PATH:$GLOBUS_LOCATION/bin

Configuring the Container

Specify the hostname of your machine as the value of logicalHost parameter in the container's configuration file $GLOBUS_LOCATION/etc/globus_wsrf_core/server-config.wsdd:

<parameter name="logicalHost" value="..yourhostname..."/>

Configuring the gHN

In the gHN's configuration file $GLOBUS_LOCATION/config/GHNConfig.xml, override wherever appropriate the default values of the following properties:

securityenabled	true if the gHN can operate in a secure infrastructure, false otherwise.
mode	in a development' mode, the gHN does not publish its own profile as well as those of the deployed Running Instances in the infrastructure. In a production mode, it does.
rootVO	the rootVO of the gHN.
defaultVO	the defaultVO of the gHN.
infrastructure	the infrastructure of the gHN.
labels	[coming soon]
rootGHN	[coming soon]
GHNtype	[coming soon]
localProxy	[coming soon]
coordinates	A pair of comma-separated values for the latitude and longitude of the gHN. Coordinates for some popular locations are available here.
country	[coming soon]
location	[coming soon]
updateInterval	[coming soon]

Configuring Security

[coming soon]