Versions Compared

Key

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

...

Code Block
/$DEPLOYMENT_BASE_DIR
  /data
     /archive
     /catalog
     /staging
     /work
     /met
     /failed_ingest_filesfailure
  /bin
  /components
    /crawler
      /bin
      /conf
      /policy
      /lib
    /filemgr
      /bin
      /conf
      /policy
      /lib
    /workflow
      /bin
      /conf
      /policy
      /lib
    /extensions
      /bin
      /conf
      /lib
  /conf

Path Descriptions

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.

/conf

System wide configuration

Deployment Path Details

/$DEPLOYMENT_BASE_DIR/bin- This will contain scripts that will manipulate the underlying components. For example all 3 components can be started, stopped and restarted from this directory. At the same time you can also manipulate a single component at a time from this dir also.

...