caGrid 1.2 Software

caGrid 1.2 Installation Quick Start

Make sure you have the prerequisites installed.
Obtain a software release at: caGrid 1.2 Software Downloads.
Review additional documentation.

Build caGrid

In order to use any feature of caGrid (or to develop applications with it), you must build caGrid. The installer will do this automatically for you, but if you are using the source release, you must build it yourself. After obtaining the prerequisites above, type the following command from the caGrid directory:

ant all

To install caGrid using the installer, you can follow the installer instructions.

Release Layout

The caGrid release is oriented around a number of individual projects and the build process manages inter-project dependencies. After caGrid is built, each of the projects can be used independently. For example, if you are only interested in Introduce, you can safely copy around caGrid/projects/introduce as a standalone copy of Introduce. The same is true for core services; once caGrid is built, all dependencies for each service are copied into the ext directories of the service. Please read the descriptions of each project.

Target Grids

As of caGrid 1.1, the caGrid build process has supported the capability to reconfigure its components that communicate with the grid (for example, Introduce and the GAARDS UI). A simple ant command can be used to make every change that is necessary to work with a new grid. Read about how to change target grids.

Depending on caGrid

caGrid has always been distributed as a source release and as graphical installer. As of caGrid 1.2, a repository of pre-built jar files and other resources are available for download. Those who want to build software that needs caGrid libraries, can either use a caGrid release and locate and copy the libraries needed from that release, or, they make use of the new Ivy-based dependency framework available in caGrid 1.2. The later is strongly-encouraged, since all transitive dependencies are completely formally defined. This addresses the otherwise very difficult problem of determining which libraries you actually need for what you are trying to do. Those who who still do not want to use Ivy can make use of the dependencies reports now generated into each project's "ext" directory. Read about how to use Ivy to depend on caGrid.