Page History

...

• 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.on the port 2001.

NOTE: After you launch oodt (the fourth command), you may observe the following output:

Using CLASSPATH:       
-e Starting OODT File Manager [  Failed  ]
-e Starting OODT Resource Manager [  Failed  ]
-e Starting OODT Workflow Manager [  Failed  ]

Don't be confused. In order to see whether the oodt is running, open a browser to 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..  Click on PCI Status link to get detailed information about running processes. A green arrow in front of a manager name indicates that the corresponding process runs correctly.

Image Added

Alternatively one may run the following command and get list of relevant processes and assigned ports.

ps -aux | grep "java"

NOTE: The "oodt start" command should return quite quickly. This is normal. If, however, the OpsUI link http://localhost:8080/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/logs/oodt.out"

...