CTarchive subscribes to one or more channels in a DataTurbine source and converts the data to CloudTurbine format files.
java -jar CTarchive.jar -h
Usage: java CTarchive
-h print this usage guide
-a <rbnb host:port> default: localhost:3333
-n <sink name> default: CTarchive
-p <pickup channel> default: Fdrop/*
-d <drop folder> default: CTarchive
-o fetch from oldest available data (fetch from newest w/o this flag)
-f <flushTime (sec)> default: 5.0
-t <trimTime (sec)> default: 0 (open-ended)
The “-a” option specifies the address of the DataTurbine server to connect to.
The “-n” option specifies the name of the sink connection this program makes to the DataTurbine server.
Use the “-p” option (with optional wildcard) to specify the DataTurbine channels that CTarchive will fetch data from. For example, consider a DataTurbine source named “rbnbSource” which is streaming 5 channels of data to a DataTurbine server named “c0”, “c1”, “c2”, “c3”, and “c4”. CTarchive can fetch all of this data by specifying “-p rbnbSource/*” or it can fetch only data from channel “c3” by specifying “-p rbnbSource/c3”.
The “-d” option specifies the name of the CloudTurbine output source folder.
Use the “-o” flag to fetch all data from the DataTurbine source (i.e., from oldest available). Without this flag, CTarchive will fetch from the newest available data forward.
The “-f” option specifies how frequently data will be flushed to the output CloudTurbine source. Data is saved in ZIP files, and thus this flag specifies how much data is stored in each ZIP file and how frequently the ZIP files are flushed to disk.
Use the “-t” flag to only maintain a certain amount of data in the CloudTurbine source.