You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Download and Install

  1. Download a Released tarball from the Downloads page.
  2. Untar it
  3. cd into the apache-oodt-{version}-src folder
  4. mvn package

Now the required Maven artifacts have been downloaded and installed into your local maven m2 repo. Time for deployment to your local machine or to another server.

Deployment

  1. cd into pushpull/target
  2. Copy the tarball (cas-pushpull-{version}-dist.tar.gz) to your deployment location
  3. untar the tarball and you will have folder named cas-pushpull-{version} with the following directory structure

/bin /etc /lib /logs /policy

Configuration

Basic Configuration

This is a set of configuration that must be completed to get the Push/Pull framework setup. These setups are required for even the most basic installations. We will cover deployment specific setup/configuration in the next section.

This documentation has been written assuming the environment variable PUSH_PULL_HOME has been set to the directory where you have untar'd the pushpull component. Several configuration properties require a full file path. Just be sure to replace the PUSH_PULL_HOME with a value that is applicable to your deployment, or export that environment variable and use the following config.

The following Sub-Sections will reference the path to each file that needs to be edited, and each file will be followed by a block showing what changes need to be made

[PUSH_PULL_HOME]/etc/push_pull_framework.properties

line
21   #external configuration files
22   org.apache.oodt.cas.pushpull.config.external.properties.files=[PUSH_PULL_HOME]/etc/default.properties

35   # ingester filemgr url
36   org.apache.oodt.cas.filemgr.url=

61   #protocolfactory specification for protocol types
62   org.apache.oodt.cas.pushpull.config.protocolfactory.info.files=[PUSH_PULL_HOME]/policy/ProtocolFactoryInfo.xml

69   #parser to retrievalmethod map
70   org.apache.oodt.cas.pushpull.config.parser.info.files=[PUSH_PULL_HOME]/policy/ParserToRetrievalMethodMap.xml
71
72   #unique metadata element info
73   org.apache.oodt.cas.pushpull.config.type.detection.file=[PUSH_PULL_HOME]/policy/mimetypes.xml
74
75   #directory below which all data file will be downloaded to
76   org.apache.oodt.cas.pushpull.data.files.base.staging.area=[PUSH_PULL_HOME]/staging

Specific Configuration(s)

Due to the limitless combinations of protocols and remote data archives the following list of example is NOT exhaustive and is intended to give you working examples. Each configuration will begin with a summary description of the problem being solved, then it will be followed with config/setups needed to solve the problem.

Example of Connecting to a Remote FTP Server to Retrieve All *.he5 Files

Connection Protocol: FTP
Root Path: ftp://l4ftl01.larc.nasa.gov/TES/TL2CO2N.005/
Password Required: NO
Download (All or Subset)?: All

Examples of full path:

ftp://l4ftl01.larc.nasa.gov/TES/TL2CO2N.005/2004.09.20/TES-Aura_L2-CO2-Nadir_r0000002147_F06_09.he5
ftp://l4ftl01.larc.nasa.gov/TES/TL2CO2N.005/2005.05.21/TES-Aura_L2-CO2-Nadir_r0000002931_F06_08.he5

[PUSH_PULL_HOME]/policy/mimetypes.xml
  • No labels