You should set the configuration by editing the component's properties, using the editor pages built into the component. This is accessible via the 'administration controls' menu on the left-hand side-bar of the web pages included in the component itself (so you won't see it if you're reading this on the AstroGrid web site). The editor pages include specific instructions for applying the new configuration to a JES running in a Tomcat container. The meaning of the properties is discussed below.
The configuration properties that JES understands are as follows
JES requires a directory in which to store workflow transcripts, and other bookeeping information. Jes will create a series of directories under the direcory given in the jes.jobfactory.file.basedir property. This base directory must be writable by Tomcat (and JES given permission under any security manager you may be running).
The property org.astrogrid.registry.endpoint should contain the URL endpoint of the Registry webservice this JES is to use.
When JES dispatches a step to a CEA service, it needs to tell that service where to send notification of the step execution. The properties jes.monitor.endpoint.url and jes.results.endpoint.url contain the absolute URL endpoints of the callback webservices for this JES server. These always follow the same pattern:
jes.monitor.endpoint.url=http://server.name:port/jes-context/services/JobMonitorService jes.results.endpoint.url=http://server.name:port/jes-context/services/ResultListener
where server.name is the DNS-resolvable name of the machine the Tomcat is running on, port is the port that Tomcat is listening on, and jes-context is the context in Tomcat at which the JES component is installed. The default settings, when the component is first deployed, include localhost as the address. This is not sufficient for normal operation, as an endpoint based on localhost is not meaningful on other computers.
After changing these endpoints it is best to re-run the installation tests: see the menu in the left-hand side-bar. The installation tests check that the endpoints are accessible.
JES also uses the following properties. The defaults are correct by definition, so don't try to change them.
jes.locator=registry jes.store=file
This is how a complete set of JES properties might look if written out in a properties file. You may wish to list your properties in this format (the configuration-editor pages allow this) for comparison.
# file: astrogrid.properties - sample configuration file for a JES Server # Working directory for jes jes.jobfactory.file.basedir=/home/tomcat/jes/jobs #Registry Endpoint - AstroGrid central registry org.astrogrid.registry.query.endpoint=http://galahad.ast.cam.ac.uk:8080/galahad-registry/services/RegistryQuery #Callback Endpoints jes.monitor.endpoint.url=http://my.server.name:8080/astrogrid-jes/services/JobMonitorService jes.results.endpoint.url=http://my.server.name:8080/astrogrid-jes/services/ResultListener #Required Properties. jes.locator=registry jes.store=file