a47b877f44
Change-Id: I4e431d62e3d27565af75d52012fe042a18fd1f9c Former-commit-id:98bd4174d3[formerlyac03675880] [formerly9b7715e5e0] [formerly98bd4174d3[formerlyac03675880] [formerly9b7715e5e0] [formerly995d962a66[formerly9b7715e5e0[formerly 16c38960863df2f993c6ee7e18de31824cbdbb08]]]] Former-commit-id:995d962a66Former-commit-id:592bbd8241[formerlydae52ad3a0] [formerly 8b2aa969d1f1fe5980fc422623cca4e71e6d36fc [formerly03843090fa]] Former-commit-id: 78ebd5a1d7d77f8dc49f5bbc17e2c05c508f1e9d [formerly40369d124f] Former-commit-id:1b29ee087f
20 lines
No EOL
885 B
Text
20 lines
No EOL
885 B
Text
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. |