THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
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.
| Code Block | ||||
|---|---|---|---|---|
| ||||
/$DEPLOYMENT_BASE_DIR
/bin
/crawler
/bin
/etc
/policy
/lib
/data
/archive
/catalog
/failure
/met
/staging
/work
/workflow
/extensions
/bin
/etc
/lib
/filemgr
/bin
/etc
/policy
/lib
/logs
/pcs
/bin
/etc
/lib
/logs
/policy
/run
/pge
/bin
/lib
/policy
/resmgr
/bin
/etc
/lib
/logs
/policy
/run
/tomcat
/LICENSE
/NOTICE
/RELEASE-NOTES
/RUNNING.txt
/bin
/common
/conf
/logs
/server
/shared
/temp
/webapps
/work
/workflow
/bin
/etc
/lib
/logs
/policy
/run |
...
Default Source Structure
| Code Block | ||||
|---|---|---|---|---|
| ||||
/$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
|
...