...

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

...

<mime-info>
    <mime-type type="metadata/cas_pushpull">
        <glob pattern="*.info.tmp"/>
    </mime-type>
    <mime-type type="metadata/cas_metadata">
        <glob pattern="*.cas"/>
        <glob pattern="*.met"/>
    </mime-type>
    <mime-type type="product/TESLevel2CO2">
        <_comment>Level 2 - CO2 Retrivals from TES</_comment>        
        <glob pattern="TES-Aura_L2-CO2-Nadir_r\d{10}\w{2}\d{2}\w\d{2}\.he5" isregex="true"/>
    </mime-type>
</mime-info>

...

<remoteSpecs>
    <aliasSpecs>
        <aliasSpec file="[CAS_PP_HOME]/etc/examples/ExternalSources/ExternalSources.xml"/>            
    </aliasSpecs>
    
    <daemons>
        <daemon alias="TESL2CO2" active="yes">
            <runInfo firstRunDateTime="2011-12-01T00:00:00Z" period="3m" runOnReboot="yes"/>
            <propInfo dir="[CAS_PP_HOME]/etc/examples/DirStructXmlParserFiles">
                <propFiles regExp="TESL2CO2\.xml" parser="org.apache.oodt.cas.pushpull.filerestrictions.parsers.DirStructXmlParser"/>
            </propInfo>
            <dataInfo stagingArea="TESL2CO2" deleteFromServer="no"/>
        </daemon>
    </daemons>
</remoteSpecs>

...

<root>
    <dirstruct starting_path="/TES/TL2CO2N.005">
        <nofiles/>
        <dir name="\d{4}\.\d{2}\.\d{2}"> <!-- regex matching '2004.09.20' -->
            <nodirs/>            
            <!-- regex matching TES-Aura_L2-CO2-Nadir_r0000002147_F06_09.he5 -->
            <file name="TES-Aura_L2-CO2-Nadir_r\d{10}\w{2}\d{2}\w\d{2}\.he5"/>
        </dir>  
    </dirstruct>
</root> 

Launching the PushPull Daemon

Located within the $CAS_PP_HOME/bin directory there is a shell script that you can use to launch the PushPull daemon process. You will either need to edit the pushpull file directly to make the proper adjustments or export 2 environment variables. The following steps will assume that we are starting the daemon to run using the configs listed above.

1. cd $CAS_PP_HOME/bin
2. The two options listed below: Edit the 'pushpull' shell script making sure to replace the key variables as shown below:
   1. Export 2 env vars
   2. Replace the CAS_PP_RESOURCES and DAEMONLAUNCHER_PORT with static values

   1. Code Block
      title [CAS_PP_HOME]/bin/pushpull borderStyle dashed
      line 25 ${JAVA_HOME}/bin/java \ 26 -cp ${LIB_DEPS} -Dcom.sun.management.jmxremote \ 27 -Djava.util.logging.config.file=../etc/logging.properties \ 28 -Djavax.net.ssl.trustStore=${CAS_PP_RESOURCES}/jssecacerts \ 29 org.apache.oodt.cas.pushpull.daemon.DaemonLauncher \ 30 --rmiRegistryPort ${DAEMONLAUNCHER_PORT} \ 31 --propertiesFile ${CAS_PP_RESOURCES}/push_pull_framework.properties \ 32 --remoteSpecsFile ${CAS_PP_RESOURCES}/examples/RemoteSpecsFiles/RemoteSpecs.xml

   1. # You can leave this file unchanged by merely exporting the following env vars (bash shell) export CAS_PP_RESOURCES=$CAS_PP_HOME/etc export DAEMONLAUNCHER_PORT=9012 # Or you can always use this config and not setup env vars line 25 ${JAVA_HOME}/bin/java \ 26 -cp ${LIB_DEPS} -Dcom.sun.management.jmxremote \ 27 -Djava.util.logging.config.file=${CAS_PP_HOME}/etc/logging.properties \ 28 -Djavax.net.ssl.trustStore=${CAS_PP_HOME}/etc/jssecacerts \ 29 org.apache.oodt.cas.pushpull.daemon.DaemonLauncher \ 30 --rmiRegistryPort 9012 \ 31 --propertiesFile ${CAS_PP_HOME}/etc/push_pull_framework.properties \ 32 --remoteSpecsFile ${CAS_PP_HOME}/etc/examples/RemoteSpecsFiles/RemoteSpecs.xml
3. ./pushpull

That should be about it. The daemon should start up on port 9012 (given this config)

...