...

prompt> curl -s http://svn.apache.org/repos/asf/oodt/trunk/mvn/archetypes/radix/src/main/resources/bin/radix | bash
prompt> mv oodt oodt-src; cd oodt-src; mvn package
prompt> mkdir ../oodt-deploy; tar -xvf distribution/target/oodt-distribution-0.1-SNAPSHOT-bin.tar.gz -C ../oodt-deploy 
prompt> cd ../oodt-deploy; ./bin/oodt start
prompt> ./resmgr/bin/batch_stub 2001

• The first command is the running of a maven archetype to make an oodt project. Inside of the RADIX script downloaded in the curl command is an mvn archetype generation command. That command has a number of parameters that the 1 liner radix script encapsulates. (parameters marked in italics below)
  • The groupId is a place to specify your company's namespace. 
  • The artifactId is a place to specify a short name of your project. 
  • The version indicates the initial version label for your project. 
  • The oodt flag indicates the version of OODT that you want your project to be built on.
• The second command simply moves into the created oodt project directory where your source and configuration can be maintained and later can be placed into version control. Then creates the distribution of your OODT project using "mvn package"
• The third command merely untars the distribution into the created deployment directory
• The fourth command moves into the deployment directory and starts the OODT system.
• The fifth command launches batch stub located in the resource manager directory.

You can now check the installation by opening a browser to http://localhost:8080/opsui or running the various command line programs for the various components.

NOTE: The "oodt start" command should return quite quickly. This is normal. If, however, the OpsUI link above is not functional on your system, one good place to start looking for probable cause is the "oodt.out" log file, which can be found (if you've been following the example above) in "oodt-deploy/logs/oodt.out"

Version Control

...