Differences

This shows you the differences between two versions of the page.

--- vibreportinganddatabaseserverbeansdocumentation [2022/01/02 17:52] – wikiadmin
+++ vibreportinganddatabaseserverbeansdocumentation [2026/07/24 16:51] (current) – wikiadmin
@@ Line 1: / Line 1: @@
 =====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.
+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, including databases running in the cloud.
+====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:
+[[DatabaseConnectionManagerDocumentation|Database Connection Manager]] - This is a generic connection manager which can be used for any database
+[[HSQLDBConnectionManagerDocumentation|HSQLDB Connection Manager]]
+[[SQLiteConnectionManagerDocumentation|SQLite Connection Manager]]
+[[MySQLConnectionManagerDocumentation|MySQL Connection Manager]]
+====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).
+See [[databasereferencecheatsheet|Database Reference "Cheat Sheet"]] for a compilation of information on various database drivers.
+====Database Servers====
+The Database Servers are the Beans used to send SQL statements to the database to get or send data to the tables. The Beans are listed below with links to more documentation and examples.
+[[DatabaseRawLookupDocumentation|Database Raw Lookup]] - Use to read a single value from the database table
+[[DatabaseRawWriteDocumentation|Database Raw Write]] - Use to write to the database table or to execute other SQL statements which do not return a result set
+[[DatabaseArrayRawLookupDocumentation|Database Array Raw Lookup]] - Use to read an array from a single column of the database table
+[[DatabaseRowArrayLookupDocumentation|Database Row Array Lookup]] - Use to read an array from a single row of the database table
+[[DatabaseRawTableLookupDocumentation|Database Raw Table Lookup]] - Use to read a 2D table from a database table
+[[TriggeredHistoricalDocumentation|TriggeredHistorical]] - Use to write one or more columns of timestamped data to a table
+====Debugging====
+If you are having problems with a database connection or sql transactions, please look at this article for more information and setting debugging levels on the historical/logging components:
+[[historical_debugging | Database Components Debugging]]
+====Analytics====
+[[FeatureExtractorDocumentation|FeatureExtractor]] - transform raw process data into numerical features suitable for Fault Detection and Classification (FDC), troubleshooting, dashboards, reporting, machine learning, and AI-assisted diagnostics.
+====Reporting====
+MIStudio/MIX is compatible with Jasper Reports for a feature rich reporting environment to produce PDF, CSV, or XLS reports from database lookups.