Astrogrid Scripting Client Developer Kit

This project assembles a Client Developer Kit (CDK) for developers that wish to interact with the Astrogrid Scripting Interface. This combines the delegates for accessing the Astrogrid workflow services (JES, CEA) and the core Astrogrid services (Myspace / VoSpace, Registry, Community) with some scripting objects and helper libraries.

The workflow delegates, and the core delegates are also available separately in the smaller Workflow CDK and Core CDK.

Documentation

The scripting environment provided by astrogrid is documented in the Workflow userguide: html, pdf

Configuration

All astrogrid components use a common configuration system. This allows properties to be set using either JNDI (if available), a configuration file, or System properties. The simplest method is to have a file named astrogrid.properties on the classpath. See the javadoc for further details. This CDK requires the following keys to be set:

org.astrogrid.community.ident

The identifier of the local community. For example org.astrogrid.release

org.astrogrid.registry.query.endpoint

Endpoint of the registry query service. For example http://katatjuta.star.le.ac.uk:8080/astrogrid-registry-SNAPSHOT/services/RegistryQuery

org.astrogrid.registry.admin.endpoint

Endpoint of the registry admin service. For example http://katatjuta.star.le.ac.uk:8080/astrogrid-registry-SNAPSHOT/services/RegistryAdmin

jes.job.controller.endpoint

The endpoint of the jes server. For example http://katatjuta.star.le.ac.uk:8080/astrogrid-jes-SNAPSHOT/services/JobControllerService

org.astrogrid.community.default.vospace

Registry key for default myspace service for this community. E.g. ivo://org.astrogrid.release/myspace

Development

It's possible to deploy a mini-astrogrid (Astrogrid in a Box) to a single machine. This provides a convenient target to test clients against. Installation Instructions