Previous Page Next Page
JReport 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 JReport, 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, MS SQL Server, IBM DB2, Oracle, Sybase, PostgreSQL, Informix and InterSystems Caché.
JReport 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 JReport Server runs in an integrated environment, it can also access a DBMS via JNDI.
There are three logical databases in JReport 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 JReport Server. The profiling tables are optional. In most cases you can use the same physical database for all 3 sets of tables.
JReport also provides completed SQL files to create tables for all databases supported. They reside in <install_root>\script_files.
This section contains the following topics:
See also Managing Server Data for information about working with the data in the server databases.
Notes: