Versions Compared

Old Version 51

changes.mady.by.user Chris Mattmann

Saved on

compared with

New Version 52

changes.mady.by.user Paul Ramirez

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Archetype will only support a single version for all components. No mixing versions of individual components
  • Maven Archetype process will be completed using 5 commands or lessas few commands as possible

Prerequisites:

  • Submit INFRA ticket to create a place to put all Maven Central artifacts
  • Load/Install artifacts to Maven Central

The

...

Commands

Requires Maven 2.x and Java 1.5+

Until the archetype is made available at maven central you will need to run the following that will install the radix archetype locally.

Code Block
prompt> svn wgetco httphttps://wwwsvn.apache.org/repos/distasf/oodt/trunk/mvn/archetypes/radix-0.4.tgz
prompt> tarcd -xzvf radix-0.4.tgz
prompt> export PATH=${PATH}:<downloadDirectory>/radix
prompt> oodt-radix create-dms <dataSystemName> <packageName>
prompt> ./<dataSystemName>/deploy/bin/oodt start
mvn install
{/code}

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

Version Control

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

...

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

...

Path

Description

/data/archive

This is the root of where the filemgr will store its archived products

/data/staging

This directory will be monitored by the crawler. Products to be ingested should be placed here

/data/catalog

In a configuration that uses Lucene as a back end this directory holds the contents of that index

/data/work

...

/data/failure

Any products that have failed ingestion will be placed here along with any metadata files.

/bin

Contains system level scripts to start, stop, restart the OODT infrastructure

/components

The guts of what make the data management system work

/components/crawler

The crawler deployment for your data management system (i.e. policy, scripts, and configuration). This component is responsible for monitoring the staging area

/components/filemgr

The filemgr deployment for your data management system (i.e. policy, scripts, and configuration). This component catalogs and archives products into the archive area.

/components/workflow

The workflow deployment for your data management system (i.e. policy, scripts, and configuration). This component orchestrates any processing that may need to be done on your products

/components/extensions

This is a sandbox area to test out metadata extractors, versioners, actions, etc. that you have developed to extend the functionality of the existing OODT framework.

/etc

System wide configuration

...