AggreGate Server uses a relational database to store persistent data, such as:
| 1. | Information about User Accounts and Device Server Accounts in dedicated tables |
| 2. | Values of all persistent context variables (properties of Alerts, Event Filters, Widgets and other system objects) |
| 3. | History of persistent events |
AggreGate Server communicates with the database engine using a JDBC driver, so it can work with most modern Relational Database Management Systems.
|
JDBC stands for the Java DataBase Connectivity API. It is a standardized way for Java-based applications to interact with a wide range of databases and data sources. JDBC differs from ODBC (Microsoft's Open DataBase Connectivity standard) primarily in the fact that JDBC is written in Java, and thus can be used without modification in cross-platform environments. Additionally, whereas ODBC is a complex standard that is becoming technically out-dated, JDBC is a modern, clean specification for cross-vendor database access. |
The AggreGate Server distribution package includes an embedded database engine (Hypersonic SQL, also known as HSQL) that is used by default. It is ideal for small installations with less than 20-30 devices.
See switching to another database engine for more information on how to change the database used by the server.
A separate group of server global configuration settings controls how AggreGate Server interacts with the database engine.
The embedded database's data is located in /db subfolder of AggreGate Server installation folder.
Some distributions of AggreGate Server include pre-configured MySQL bundle. MySQL is a well-known powerful free database server that can serve AggreGate installations with thousands of devices.
If the bundled MySQL package is selected during installation, will be downloaded from Tibbo website and installed in /mysql subfolder of AggreGate Server installation folder. It is already fine-tuned to be used with the AggreGate Server, so no additional configuration should be necessary in most cases.