NAME

FEI_Watch

Sics a watchdog on an FEI file type.


SYNOPSIS

FEI_Watch [<options>] [-Type] <file type>]


OPTIONS

-Catalog <catalog>

The name of the database catalog to contain the Conductor pipeline tables. The catalog name may be qualified by the <pipeline> name, following a '.' delimiter. Default: HiRISE.

-Pipeline <pipeline>

The name of the Conductor pipeline to receive Source_Pathname entries for new files found in the FEI server file type. Default: The <file type> name.

-Type <file type>

The name of the FEI file type (a.k.a. venue) to watch for HiRISE observation data files. The option switch need not be supplied; a command line argument without a preceeding option switch is taken to be the file type name.

-Start | -After <time>

Files marked with a time after the start time are to be selected by the FEI_Watchdog. The time format is:

YYYY-MM-DD[Thh:mm:ss.fff]

Where:

YYYY - Year number

MM - Month number (01-12)

DD - Day of the month (01-31)

hh - Hour of the day (00-23)

mm - Minute of the hour (00-59)

ss - Second of the minute (00-59)

fff - Fractional second (000-999)

Leading zeros are required if necessary to fill the field width. If the clock time values are optional. Default: The current time.

-Notify <notify list> ...]

A comma delimited list of email addresses which will receive notification messages from the FEI_Watchdog and the downlink pipeline. Multiple uses of this option accumulate to the list of names. Default: The username for whomever is running this procedure.

-[Very_]Verbose | -Quiet

Verbose operation provides details about what is being done. Very verbose operation lists each command that is executed. Quiet operation minimizes messages. Default: Quiet.

-Help

The man page for this procedure is listed.


DESCRIPTION

FEI_Watch is a front-end stetup wrapper for FEI_Watchdog.

The following prerequisites must be met:

The HiRISE_ROOT environment variable must be set to the location of the HiRISE software installation, or /HiRISE must be its location.

The $HiRISE_ROOT/HiDog subsystem software must be present, including the HiDog_Pipeline-Create procedure and the HiDog.conf file if a new configuration file is to be created.

The FEI_HOME environment variable must be set to the location of the FEI client software installation.

The $HiRISE_ROOT/bin/FEI_Watchdog procedure must be present.

The JAVA_HOME environment variable must be set to the location of the Java run time system, or /usr/java must be its location.

The database <catalog> must be present on the database server along with the <pipeline>_Sources and <pipeline>_Procedures tables in it, or the user must have permission on the database server to create them. The user must also have permission to update the <pipeline>_Procedures table with new content. In addition, normal Conductor operations using these pipeline tables must be permissible with the database access specified from the $HiRISE_ROOT/Configuration/HiROC.conf file.

The <file type> is confirmed confirmed as being present on the FEI server. The procedure will abort if this does not succeed.

A $HiRISE_ROOT/Configuration/<pipeline>/<pipeline>.conf file is created if it does not exist. This includes creation of the directory (all segments of the pathname). The configuration file is created from the template $HiRISE_ROOT/HiDog/HiDog.conf configuration file. Parameters marked with a comment, on the same line, containing the single keyword PIPELINE, FILE_TYPE or NOTIFY will have their values replaced with the <pipeline>, <file type> and <notify list> values, respectively, in the new configuration file.

The Conductor pipeline tables - <pipeline>_Sources and <pipeline>_Procedures - are created in the database <catalog> if they don't already exist. The procedures table is loaded with the procedures defined by HiDog_Pipeline-Create. The contents of the sources table remain unchanged.

The <pipeline>_Watchdog.last_time file in the configuration file directory is updated, or created if it doesn't exist, with the start <time> for selecting files to download. However, if a <pipeline>_Watchdog.lock file exists then this indicates that a FEI_Watchdog process is already monitoring the pipeline and a new one for the same pipeline will not be started; only one watchdog should be monitoring any given pipeline.

Now that the appropriate operating environment for the FEI_Watchdog has been established this procedure executes it, passing all the required operating parameters to it.


Exit Status

0 - Success

On shutdown as a result of an external signal.

1 - Bad command line syntax

A command line syntax usage message will be provided.

2 - A system error occured.

This can be of a missing required FEI_HOME environment variable, the fei5list utility, or the inability to create the configuration file.

3 - FEI failure

The availability of the FEI <file type> could not be confirmed.

4 - Pipeline failure

The <pipeline> tables could not be initialized.

5 - Watchdog failure

The FEI_Watchdog could not be started.


Author

Bradford Castalia, UA/PIRL


Copyright

Copyright (C) 2005 Arizona Board of Regents on behalf of the Planetary Image Research Laboratory, Lunar and Planetary Laboratory at the University of Arizona.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License, version 2, as published by the Free Software Foundation.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.


Version

1.7 2006/04/29 04:04:50