What You Need to Know
Before you begin to setup a server make sure you understand:
- The role of a DataTurbine server
- Basics of installing and running DataTurbine
- Determined a working network topography for your application.
- Understand Java Memory Allocation
Starting a Server
Starting a server is as simple as running rbnb.jar. From the command line run it as
Disk Space Requirements
The amount of hard drive space required by a server is set by the source. The amount of disk space needed to archive all the channels can be estimated by the following formula:
DataTurbine archives do not pre-allocate space, the specified archive size is an upper limit. No error occurs at the time a source specifies the archive size; only if that archive eventually exceed disk space. Should an open-ended (non-looping) archive be desired, specifying a huge archive is fine and suffers no up front resource penalty.
The overhead is mostly for timestamps. The relative timestamp overhead is highly dependent on how data is sent. E.g. many small data frames have higher relative overhead than fewer large frames. It is possible for the overhead term to be larger than the data term (e.g. double precision timestamps for single-point data frames > single precision data).
Specifying an Archive
By default DataTurbine will dump the files it uses
into your home folder. Storing files this way is hard to manage. Instead it is better practice to create a folder where the files will be archived.
This can be set by the -H command line parameter for rbnb.jar
When specifying an archive path you must first create a folder then start a DataTurbine Server
Making Data Automaticaly Visable
By default if the server is restarted the data is not automatically visible until a source reconects to it. Data can automatically be accessible by specifying the the -F command line parameter for rbnb.jar
Administration
A great tool for administrating DataTurbine is the admin utility.