4.1. Basic Configuration

The GRIA job service is used to manage jobs. Clients can use the service to create new jobs, upload input data, start the job, monitor progress, and download results.

Each input and output of a job is actually a data stager managed by the local data service (the one in the same .war as the job service). Therefore, you must configure the data service before the job service can be used. Users can run jobs that take input from or send output to other data services by using the normal data transfer features provided by the data service.

To configure the job service you will need to specify:

• The location of the root job directory. The service creates one subdirectory inside this directory for each job.
• The directory containing the platform scripts. These scripts interact with the underlying resource manager, allowing the job service to be used with clusters of machines.
• A list of trusted management services. Normally, you can just click Add to accept the default management service. This is the SLA management service from the GRIA service provider management package. Note that if the GRIA basic application services package is deployed on a different machine to the GRIA service provider management package, some additional access control setup is required. This is described in Links with Other Services in the Service Provider Management user guide. As an alternative to configuring the service to be managed, you can make use of the service unmanaged (free), by clicking the Make service free button.
• A list of applications which users can run using the service. See the Managing applications section for details.

Next: Managing Applications Previous: The Job Service