THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Code Block |
|---|
prompt> svn co https://svn.apache.org/repos/asf/oodt/trunk/mvn/archetypes/radix
prompt> cd radix
prompt> mvn install
{/ |
| Code Block |
|---|
} 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 |
...
h4. Version Control |
...
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"
...
Default Deployment Structure
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 |
|---|
h2. Default Deployment Structure
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
...
| Code Block |
|---|
h4. Path Descriptions
||Path||Description||
| |
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 |
...
|/crawler |
...
|The crawler deployment for your data management system (i.e. policy, scripts, and configuration). This component is responsible for monitoring the staging area |
...
| |/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. |
...
| |/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 |
...
| |/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 |
...
Deployment Path Details
configuration| h3. 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. |
...
Manipulate all components (DEFAULT BEHAVIOR) |
...
_./oodt \[start, stop, restart\]_ |
...
Manipulate a single |
...
component \_./oodt \[start,stop, restart\] \[crawler OR filemanager OR workflowmanager\]\_ |
...
*/$DEPLOYMENT_BASE_DIR/components* \- This will contain a single folder for each component. |
...
Initially this will only contain the 3 components we have selected to start this process, but as more components are added they will be added in here. */$DEPLOYMENT_BASE_DIR/etc* \- This will contain configuration and properties files which apply to several components. This should (like the bin dir) give users a single directory they can go into to configure the associate components. |
...
h2. Parameters that can be managed within the conf |
...
directory *{_}oodt.properties |
...
{_}*
|
crawler_port=9020
...
filemanager_port=9000
...
workflowmanager_port=9001
...
resmgr_port=9002
...
batchstub_port=2001
| Code Block |
|---|
JAVA_HOME |
...
h3. Component settings we plan to default |
...
crawler
port
filemanager
| Code Block | ||||
|---|---|---|---|---|
| ||||
*crawler*
port
*filemanager*
{code:title=filemgr | borderStyle=solid}
FILEMGR_PORT=9000
export FILEMGR_PORT
|
...