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 |
Once you have the archetype installed or it is available at maven central. Here is the set of commands you would typically run.
| 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. |
...
- The first command is merely a place where we will put the deployment of oodt for your project after the tarball is built
- The second 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 third 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.
- The fourth command creates the distribution of your OODT project
- The fifth command merely untars the distribution into the given deployment directory made in the first call
- The sixth command moves into the deployment directory
- The last command starts the OODT system.
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.
Version Control
If you want to manage your OODT RADiX distribution with Subversion.
| Code Block |
|---|
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 |
|---|
|
| 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 |
...
|
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 |
...
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.
...
Manipulate
...
all
...
components
...
(DEFAULT
...
BEHAVIOR)
...
| Wiki Markup |
|---|
_./oodt \[start, stop, restart\]_ |
...
Manipulate
...
a
...
single
...
component
| Wiki Markup |
|---|
\_./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.
...
Parameters
...
that
...
can
...
be
...
managed
...
within
...
the
...
conf
...
directory
oodt.properties
| Code Block |
|---|
{_}* crawler_port=9020 |
...
filemanager_port=9000 |
...
workflowmanager_port=9001 |
...
resmgr_port=9002 |
...
batchstub_port=2001 |
...
JAVA_HOME
...
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
|
...