Configuring the Server Database
Logi Report Server needs to read and write to a DBMS system to store information about the server and the reports and report versions. By default the DBMS is the 100% Java Apache Derby DBMS embedded in Logi Report, which is provided only for testing and evaluation purposes. It can be easily changed to your preferred DBMS. These databases have been tested as supported for the server database: Apache Derby, HSQLDB, MySQL, SQL Server, IBM DB2, Oracle, Sybase, PostgreSQL, Informix, MariaDB, InterSystems IRIS, InterSystems Caché, and EnterpriseDB (EDB).
Logi Report Server supports connecting a DBMS to access its system data via JDBC. The JDBC configuration information is stored in the file dbconfig.xml located in
<install_root>\bin, which can be used for configuring a database connection too. When Logi Report Server runs in an integrated environment, it can also access a DBMS via JNDI.
There are three logical databases in Logi Report Server: system, realm, and profiling. The system database holds resources of the global server scope, such as server.properties, global NLS, and so on. The realm database holds information of folders, nodes, versions, the security system, and the completed table. The profiling database holds server runtime related information. The system and realm databases are necessary in order to run Logi Report Server. The profiling tables are optional. In most cases you can use the same physical database for all 3 sets of tables.
Logi Report also provides completed SQL files to create tables for all databases supported. They reside in
Select the following links to view the topics:
- Configuring in a Standalone Environment
- Configuring in an Integrated Environment
- Creating Tables in a Specified Tablespace
- Initializing the Database System as a Non-admin Database User
- Specifying Schemas
See also Managing Server Data for information about working with the data in the server databases.
- ODBC is not supported.
- If you are using MySQL, make sure it is of version 5 or above; for Sybase, the driver should be of version jConnect 7.0.7 or above.
- When using Microsoft SQL Server 2000 as the server database, the driver should be jtds.jar, otherwise the Schedule feature cannot work.
- If your server database uses DB2 and the charset is DBK, there will be the exception of encoding not supported.