## Configuring the server database

There are three 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 realm database is necessary in order to run JReport Server. For best performance, you may want to configure the realm and profiling databases separately, depending on your environment.

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 configure your database by using the dbconfig.xml file.

These databases have been tested workable as the server database: Apache Derby, HSQLDB, MySQL, Microsoft SQL Server, IBM DB2, Oracle, Sybase, and Informix.

This section presents the ways of configuring a server database for JReport Server in two different environments. Also, you can specify a table space in the database configuration for JReport Server to create tables in it.

- Configuring the server database in a standalone environment
- Configuring the server database when integrating with an application server
- Creating tables in a specified table space
- Schema support
- Configuring JdbcDriversConfig.properties

Notes:

- If you are using MySQL, make sure it is of version 5 or above.
- If your server database uses DB2 and the charset is DBK, there will be the exception of encoding not supported.
- When setting SQL 2000 as the server database, the driver should use jtds.jar, otherwise the scheduling feature cannot work.
- ODBC is not supported.

###### Related topics:

- Managing server data