Page History

...

The archetype is available at maven central. Here is the set of commands you would typically run.

prompt> mvn archetype:generate -DarchetypeGroupId=org.apache.oodt -DarchetypeArtifactId=radix-archetype -DarchetypeVersion=0.6 -Doodt=0.6 -DgroupId=com.mycompany -DartifactId=dms -Dversion=0.1-SNAPSHOT
prompt> cd dms; mvn package
prompt> mkdir ../oodt-deploy; tar -xvf distribution/target/dms-distribution-0.1-SNAPSHOT-bin.tar.gz -C ../oodt-deploy
prompt> cd ../oodt-deploy; ./bin/oodt start

• The first command is the running of a maven archetype to make an oodt project. 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.

source <(curl -s http://svn.apache.org/repos/asf/oodt/trunk/mvn/archetypes/radix/src/main/bin/radix)

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.

...

If you want to manage your OODT RADiX distribution with Subversion.

prompt> svn import <dataSystemName> http://your_repo_path/<dataSystemName>/trunk -m "Initial OODT Import"

...

In order for the easy installation to work properly we will need to settle on a default deployment layout structure. Below is our plan of how we want to layout the deployment when the project is built. First we will list out an overview, then we can detail each path and what files are going to be saved into each.

/$DEPLOYMENT_BASE_DIR
  /bin
  /crawler
    /bin
    /etc
    /policy
    /lib
  /filemgr
    /bin
    /etc
    /policy
    /lib
  /workflow
    /bin
    /etc
    /policy
    /lib
  /extensions
    /bin
    /etc
    /lib
  /tomcat
  /data
     /archive
     /staging
     /work
     /met
     /failure
     /catalog

...

Manipulate a single component

_./oodt  [start,stop, restart] [crawler OR filemanager OR workflowmanager]_

...

oodt.properties

crawler_port=9020

filemanager_port=9000

workflowmanager_port=9001

resmgr_port=9002

batchstub_port=2001

...

FILEMGR_PORT=9000
export FILEMGR_PORT

...

WFMGR_PORT=9001
export WFMGR_PORT

Default Source Structure

/$DEPLOYMENT_BASE_DIR
  /crawler
    /policy
    /bin
    /etc
  /filemgr
    /policy
      /oodt
    /bin
    /etc
  /workflow
    /policy
    /bin
    /etc
  /webapps
    /fmprod
    /fmbrowser
    /wmonitor
    /curator
  /extensions
    /src/main
      /java
        /<package>
          /extractor
          /versioner
          /task
          /action
      /python
  /distribution
    /bin
      /oodt
    /etc
      /oodt.properties

...