As of JasperReports Server 5.0, changes to configuration settings in the user interfaces are persistent through server restarts. Previously, upon restart configuration settings would revert to values stored in the configuration files.
To make persistent configuration changes through the JasperReports Server user interface:
| 1. | Log in as system administrator (superuser by default). |
| 2. | Select Manage > Server Settings:  |
| 3. | Choose a category of settings or administrator actions from the left-Settings panel. |
| The User Interface for Configuration Settings |
| |
| 4. | Find the configuration setting you want to change and edit its value. In the case of log levels, the new value takes effect immediately. In the case of other settings, click Change beside the individual setting. |
These settings and administrator actions are documented in their respective sections:
| Settings | Documentation |
| Log Settings | |
| Ad Hoc Settings | |
| Ad Hoc Cache | |
| OLAP Settings | Jaspersoft OLAP User Guide |
| AWS Settings | |
| Import | |
| Export |
Here are some guidelines for modifying the configuration settings that appear in the user interface (Log Settings, Ad Hoc Settings, and OLAP Settings):
| • | The Settings pages display a subset of the settings available in configuration files. Therefore, all settings in the UI also exist in a configuration file. |
| • | By default, the Settings pages display the values of settings that exist in the corresponding configuration file. If you modify the files and restart the server, your new file settings take effect on the server and are visible in the UI. |
| The System Properties Folder Visible to System Admins |
| |
| | Only configuration settings that have a value modified on the Settings pages of the UI are stored and made persistent in the GlobalPropertiesList. |
| • | When the server restarts, the values in the GlobalPropertiesList take precedence over values for the same settings in the configuration files. However, each setting is independent, so a value that's not modified in the Settings UI is read from the configuration files. |
| • | The Settings pages display the values of the settings in effect on the server. Therefore, settings in the GlobalPropertiesList appear on the Settings pages where they can be changed again if necessary. |
| | Be aware that the configuration values that appear on the Settings pages are possibly a mixture of values loaded from configuration files and from the persistent GlobalPropertiesList. |
| • | Right-click the GlobalPropertiesList and select Edit to view the configuration values it stores. If a setting has been modified in the UI, it appears in this list so that the setting is persistent. If you want to reset a setting so that it takes its value from the configuration file instead, click Remove next to that setting and then restart the server. Otherwise, we do not recommend modifying this list of values directly. |
| The GlobalPropertiesList Containing Persistent Configuration Settings |
| |
| • | The GlobalPropertiesList also includes JDBC drivers configured during the installation or through the data source creation wizard. For more information, see Managing JDBC Drivers. |
| • | Storing configuration values in the GlobalPropertiesList in the repository makes it possible to export them to different servers or re-import them after a server upgrade. For more information, see Importing From the Settings, |
Recommended Comments
There are no comments to display.