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 easily be changed to use your preferred DBMS. These databases have been tested as supported for the server database: Apache Derby, HSQLDB, MySQL, Microsoft SQL Server, IBM DB2, Oracle, Sybase, PostgreSQL, and Informix.
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.
When you install JReport Server, a dbconfig.xml file is automatically created in the directory <install_root>\bin. The database configuration information is stored in this configuration file. You can also configure your database by using the dbconfig.xml file.
This section presents the ways of configuring the server database as follows:
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
See also Managing Server Data for information about working with the data in the server databases.
Notes: