Advanced Version Topics
The following sections cover advanced version topics for administrators. It will give you an understanding of version structure in depth. Developers can also use API to manage the resource versions.
Information about versions, folders, nodes, the security system, the completed table, and server runtime performance are all stored in the specified database of Logi Report Server. For production systems it is recommended to use the same DBMS as your database application so the server data will be backed up with the rest of the application.
To open the Derby database, use Apache toolkit ij. ij is Derby's interactive JDBC scripting tool. It is a simple utility for running scripts or interactive queries against a Derby database. ij is a Java application that you start from a command window such as an MS-DOS Command Window or the Unix shell. ij provides several non-SQL commands for use in accessing a variety of JDBC features for testing.
To open the defaultRealm.* files:
- Start ij.bat in
- Connect to the database. To connect to a Derby database, you need to perform a valid database connection URL. ij automatically loads the appropriate driver based on the syntax of the URL. The following example shows how to connect defaultRealm using the Connect command and the client driver:
ij version 10.5
ij> connect 'jdbc:derby://localhost:8886/defaultRealm';
- After connected to the database successfully, ij allows the execution of Derby SQL statements interactively or via scripts.
Note: All statements must be terminated with a semicolon.
Example 1: Finding result version information from the database
Execute the command
SELECT * FROM RESULTVERSION_3 WHERE CREATOR='admin';to retrieve result versions which were created by the user 'admin'.
Example 2: Finding catalog version information from the database
Execute the command
SELECT * FROM CATALOGVERSION_4;to fetch all catalog versions.
- For more information about Derby and ij, please visit Apache website http://db.apache.org/derby/.
Note: Do not delete, update or insert data into the database. It is recommended that all modifications to the database be done from Logi Report Server instead of in the DBMS tools. Otherwise, it may result in Logi Report Server crashing if invalid data is found.
A working directory
<install_root>\history has been defined for use by the system database. Rather than store all the actual resources in the DBMS, the DBMS stores only pointers to the actual files. Logi Report Server uses this folder to store all of the resources including parameter information and version files. By default, Logi Report Server creates 100 folders in this history folder, and each of these folders can contain a further 3000 subfolders. These subfolders however cannot hold any further subfolders.
First, Logi Report Server puts the history information, such as archive versions and parameter files in folder 1. When the amount of subfolders in folder 1 reaches the maximum subfolder amount, it starts to put files in folder 2. When folder 2 is filled up, folder 3 will be used, then folder 4, folder 5, and so on, until all 100 folders have been filled up.
When all the 100 folders have been filled up with subfolders, Logi Report Server will then create another 100 folders, named 101 to 200, and will continue to store the history information in these folders, starting from folder 101. When the second 100 folders are full, another 100 folders will be created, and so on.
Changing the storage folder
You can specify another folder other than
<install_root>\history to store the version files by the servlet.jrserver.initArgs property in the servlet.properties file in
<install_root>\bin. For example, set
servlet.jrserver.initArgs=D:\ServerData to save version files to
For a Logi Report Server Cluster, you can also use the resource.share.hist.dir property in the server.properties file to change the storage folder