The CEC web-application can test its own installation and most of its configuration before it is registered. Please run through the following tests.

Testing Axis

The CEC contains the Apache Axis technology for web services. If Axis is not working, then the CEC does not work. You should test Axis as soon as you have the CEC installed.

Run the Axis tests using the "axis check" command from the left-hand side-bar. The test checks for the presence of JARs of code. You need all the core libraries to be present; the optional libraries are not required.

If Axis is not happy, there are three possibilities.

  • The WAR for the web-application may be faulty. Please report a bug to AstroGrid.
  • You may have Axis-related parts installed in your copy of Tomcat. Check the common directories of Tomcat for any JARs with similar names to those in the CEC web-application.
  • Your copy of Java may be broken or may be inapproriate for the CEC. Please make sure that you are using Java 1.4.x and not Java 1.5.x. Check for any JAR files added to the Java installation that may be subverting the web-application.

Testing the installations

When you have the CEC configured you can test the configuration using the installation test link in the left-hand side-bar.

If you get a test-failure here then either your configuration is not quite right (likely) or the WAR that you downloaded from AstroGrid has a bug (less likely but worth considering). If you can't see a problem in the configuration then please contact AstroGrid for support.

Test-running applications

When all is configured, use the "test run application" link from the sidebar. This lets you invoke the configured applications locally. They should all work. However, any applications that produce big output-files won't work gracefully as they will return the output to the browser, not to VOSpace.

If you get a test-failure here, then the problem could be in your configuration or could be a bug in the WAR you downloaded from AstroGrid. The problem could also be in the application itself. Try calling the application directly from the command line to see if it's working.