AGINAB allows you to install and configure a standard set of Astrogrid components on any Un*x machine. All Astrogrid developers should have their own local copy for testing work, and reinstall it frequently.
Checkout astrogrid/integrationTests/auto-integration from CVS
Checkout astrogrid/maven-base from CVS
Create a file ~/build.properties and edit the following properties to be appropriate for your local set up:
If you have previously installed Astrogrid execute:
then stop and restart Tomcat (it leaks memory when undeploying web applications so you have to restart it to avoid memory shortage).
To install a new set of components execute:
To test the installation execute:
You can access your installed portal at http://127.0.0.1:8080/astrogrid-portal/ and use the pre-installed user "frog", pw "qwerty", community "org.astrogrid.localhost"
AGINAB downloads a number of large files. Make sure you're on a fast network the first time you run it
If you have installed Astrogrid once and wish to reinstall it without a new set of downloads then execute maven with the -o switch
To install a single component such as the portal, execute
maven init portal-deploy
maven init X-deploy/X-undeploy where X=myspace/jes/apps/reg/myspace-store/pal/portal/community
Configuration properties you may wish to play with can be found in webapps/astrogrid-configuration/AstroGridConfig.properties . These should be edited before AGINAB is run (you may edit them afterwards by tracking down the deployed properties file in your Tomcat installation.)
Sometimes Tomcat does not clean up after itself properly when the undeploy-all goal is run. To make doubly sure that you are starting clean, shut down Tomcat and execute
If Community fails to set itself up following a clean installation of Tomcat, it could be because it has failed to find the hsqldb database driver jar. Stop/start Tomcat and repeat the maven deploy-all command.
Major fixes to a component should be integration tested before being committed to CVS. This is straightforward to do:
cd to the root AGINAB folder
This will remove any existing components, and download the latest component binaries from Uluru to your local repository. The second call to maven is simply a hack to force it to download the binaries that are later needed for the testing stage.
cd to the root of the component you wish to test
This installs a copy of the component with your fixes in your local repository.
cd to the root AGINAB folder
maven -o deploy-all
maven -o astrogrid-build-site
The -o (offline) switch prevents maven overwriting your updated component with any newer one that may have been built by Uluru in the meantime.
Compare the tests generated in your target/docs directory with that published on the Astrogrid site. In particular, examine the regression report at junit-full/index.html which will allow you to compare the tests in your builds against recent baselines, and thus track down any unexpected test failures.
At the moment running deploy-all on a vanilla tomcat, it will fail at setting up community due to a commonly used jar file (hsqldb-1.7.1.jar) need to be copied into under tomcat/common/lib, one can get around this by running maven setup after running maven deploy-all
This documentation was generated using Maven's html2xdoc goal.
John Taylor 19th June 2004, updated by CLQ 24 May 2005