Preparation

You'll need to have a suitable tomcat installation in which to deploy the CEA component. See Deploying tomcat for more.

It's best to install the CEA into a completely fresh tomcat (one that has no AstroGrid components installed in it at the moment). If you've done a trial AGINAB deployment, sometimes the "maven CLEANTOMCAT" cleanup command doesn't clean out all the AGINAB webapps from tomcat so it's worth checking in the tomcat manager and manually undeploying any AG webapps that are left behind. See the general installation notes for more on AGINAB and AGINAB cleanup.

You do NOT need to install AGINAB into the tomcat(s) in which you are installing CEA, either manually or using the auto-installer. Doing so (probably) won't break anything, but it may make it harder to debug configuration/connection problems with your CEA component.

Installing CEA with the java-based installer

At present, a java-based installer for CEA is in preparation but is not yet available.

Installing CEA manually

Note: these are short-term instructions until better documentation is available.

Step 1. Download and deploy the required CEA WAR files (current versions given below) :

http://www.astrogrid.org/maven/org.astrogrid/wars/astrogrid-cea-http-0.9-b002a.war (md5)

http://www.astrogrid.org/maven/org.astrogrid/wars/astrogrid-cea-commandline-0.9-b002a.war (md5)

http://www.astrogrid.org/maven/org.astrogrid/wars/astrogrid-cea-server-0.9-b002a.war (md5)

Step 2. Rename the WAR files.

To get user-friendly installation endpoint names in tomcat, I recommend renaming the wars to remove the version numbers - e.g. astrogrid-cea-http.war. (Tomcat will deploy a WAR with a context path based on the WAR's name).

Step 3. Deploy the WAR files.

You will need to deploy these WAR files into your tomcat installation, either by using the tomcat manager or by copying the WARs into the tomcat webapps directory and restarting tomcat.

Step 4. Edit the astrogrid.properties file.

Create a file called astrogrid.properties containing the following entries:

org.astrogrid.registry.admin.endpoint=http://galahad.star.le.ac.uk:8081/astrogrid-registry/services/RegistryUpdate
org.astrogrid.registry.query.endpoint=http://hydra.star.le.ac.uk:8080/astrogrid-registry/services/RegistryQuery
cea.commandline.workingdir.file=/path/to/your/local/working/directory
cea.commandline.description.list.url=file:///path/to/yourlocal/ApplicationConfig.xml
cea.filestore.basedir=/path/to/your/local/file/store/directory
cea.component.manager.class=org.astrogrid.applications.commandline.CommandLineCEAComponentManager

Entries in bold should be customised to your local filesystem paths - you can choose where they go; make sure they're on a disk/partition with plenty of spare space though.

Copy this file to the following location in each of the webapps (to check : does it just need to go in the server app, or all three?):

$TOMCAT_HOME/webapps/<warname>/WEB-INF/classes

Step 5. Create (beg/borrow/steal) an ApplicationConfig^?.xml file

In the astrogrid.properties file above you referenced an ApplicationConfig^?.xml file; this is where all the configuration goes specifying how to connect to / run the "real" system applications that this CEA is providing access to.

A sample is attached to the page which is suitable for the solar movie maker application (with customisation for your local paths); hope to follow soon with an example from Jodrell with lots of apps. Note that the sample file's name in this case is astrogrid-cea-commandline-MSSL.xml; the exact name you use for your installation doesn't matter (I believe) as long as the astrogrid.properties file knows what it is.

Make sure you've put your ApplicationConfig^?.xml file in the place you said it was in the astrogrid.properties file.

Step 6. Restart tomcat

Restart tomcat and make sure you can still see all three webapps.

Step 7. Run a self-registration

Go to the main page of one of the astrogrid-cea-server webapp, and choose "Register" from the LH menu box. This should register your CEA installation and applications in the registry on galahad. Let me know when you have done this (and if it doesn't work); at this stage, we will need to manually convert those registrations up to the 0.10 registry format.

-- KonaAndrews - 22 Mar 2005