awips2

xan/awips2

History

Roger Ferrel 9b7715e5e0 Issue #2838 Archive binary feeder creation. Change-Id: I4e431d62e3d27565af75d52012fe042a18fd1f9c Former-commit-id: 16c38960863df2f993c6ee7e18de31824cbdbb08		2014-02-27 07:45:40 -06:00
..
.settings	Issue #2838 Archive binary feeder creation.	2014-02-27 07:45:40 -06:00
META-INF	Issue #2838 Archive binary feeder creation.	2014-02-27 07:45:40 -06:00
res/spring	Issue #2838 Archive binary feeder creation.	2014-02-27 07:45:40 -06:00
resources	Issue #2838 Archive binary feeder creation.	2014-02-27 07:45:40 -06:00
src/com/raytheon/uf/edex/archive/feeder	Issue #2838 Archive binary feeder creation.	2014-02-27 07:45:40 -06:00
.classpath	Issue #2838 Archive binary feeder creation.	2014-02-27 07:45:40 -06:00
.project	Issue #2838 Archive binary feeder creation.	2014-02-27 07:45:40 -06:00
build.properties	Issue #2838 Archive binary feeder creation.	2014-02-27 07:45:40 -06:00
README.txt	Issue #2838 Archive binary feeder creation.	2014-02-27 07:45:40 -06:00

README.txt

The com.raytheon.uf.edex.archive.feeder plugin is not part of the standard EDEX deploy.
It is a tool for debugging the binary files generated for archiving.

The easiest way to generate this plugin jar is to add the following to
com.raytheon.edex.feature.uframe/feature.xml:
	
   <includes
         id="com.raytheon.uf.edex.archive.feeder.feature"
         version="0.0.0"/>

Then run the build.edex	deploy-install.xml. This will create the plugin jar file:
/awips2/edex/lib/plugins/com.raytheon.uf.edex.archive.feeder.jar

the needed configuration file:

/awips2/edex/conf/resources/com.raytheon.uf.edex.archive.feeder.properties

By placing these two files in the corresponding locations on the desired EDEX server and
restarting EDEX will start the clusteredArchiveBinaryFeederProc.  You can then drop the
binary files into the archive.feeder.directory, default /tmp/archive-feeder.