This is an old revision of the document!
Table of Contents
Reporting and Historical Servers
The Reporting and Historical Severs are a subset of the components available in the MIStudio and TransSECS Developer packages. These Beans are specifically used with JDBC databases to read from and write to tables in these databases. A Database Connection Manager is used to make the connection to the database, including (but not limited to) SQLServer, SQLite, PostgreSQL, MySQL, MariaDB, DB2, HSQLDB, and others.
Database Connection Managers
The DatabaseConnectionManagers are used to connect to the database. There is one generic DatabaseConnetionManager which can be configured for any database using a JDBC driver. Other database specific mangers are the MySQLConnectionManager, HSQLDBConnectionManager, and the SQLiteConnectionManager. The MIStudio configuration of the specific DatabaseConnectionManagers are found here:
Database Connection Manager - This is a generic connection manager which can be used for any database
JDBC Driver Jars
JDBC drivers are Java “jar” files which contain the code used by our Beans to make the specific database connection and are used by the DatabaseConnectionManager. MIStudio and TransSECS Reporting installations contain the code and driver jar needed for SQLite database connections. Other jars can be downloaded and placed in your MIStudio project's Driver directory. For TransSECS these driver jars are placed in the “addons” directory of the project (but can be placed in an “addons” subdirectory of the TransSECS Builder directory if this driver will be needed for all of your projects).
The documentation from the website where you download the JDBC driver will tell you the name of the JDBC Driver class (for the Database Driver Class Name property of the configuration), and the format of the connection URL (the Database URL property).