Post-Installation Tasks

Installing JasperReports Server automatically generates encryption keys that reside on the file system. These keys are stored in a dedicated Cloud Software Group Jaspersoft keystore. Make sure this keystore is properly secured and backed up, as described in the JasperReports Server Security Guide.

Updates Made by the Installer During Installation

This section lists the standard updates the installer makes to your local environment when you install. When the installation completes, you can check whether the updates, or corresponding changes, were successful.

Updates made to the application server:

If you installed to an existing Tomcat, the installer attempted to make updates to the Tomcat environment, as shown in the following table.

File or Directory	Updates
Windows: bin/setclasspath.bat Linux and Mac OSX: bin/setclasspath.sh	Modifies JAVA_OPTS to add -Djs.license.directory. (Commercial installer only)
All platforms: lib	Adds PostgreSQL JDBC drivers to this directory.

Updates made to the PostgreSQL database:

If you installed to an existing PostgreSQL database, the installer created new schemas and users in your database instance:

PostgreSQL Updates	Description
Database jasperserver created	This is the JasperReports Server repository database. This database holds all of system information, such as users, roles, data sources, and report definitions.
Database user jasperdb created	The JasperReports Server application uses this user to connect to the database.
Sample database foodmart created	(optional) Database created if install sample data option was chosen.
Sample database sugarcrm created	(optional) Database created if install sample data option was chosen.

Installer Log File

The installer creates a log during installation that records information as the installation progresses. If you encounter problems during installation, ensure that your system meets all prerequisites, and then check the installer log for potential problems.

The installer log file captures information such as:

•

Environment details such as the user that invoked the installer, host name, operating system details, and so on

•

List of assemblies installed

•

Information related to the Ant scripts executed by the installer

You can find the installer log at <js-install>/installation.log.

Setting your Java JVM Options

You need to set your Java JVM options. There are number of files where you can do this; refer to Setting JVM Options for Application Servers.

Configuration when Web Server is Run as Root on Linux

The export of reports fails when Tomcat is run as root in the JasperReports Server installation on Linux. The Tomcat log file displays an error, for example:

2020-06-11T17:32:19,031 ERROR SecureExceptionHandlerImpl,http-nio-8080-exec-8:116 - com.github.kklisura.cdt.launch.exceptions.ChromeProcessTimeoutException: Failed while waiting for chrome to start: Timeout expired! Chrome output: [0611/173218.897370:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.

To resolve this you need to set the following property in the jasperreports.properties file:

net.sf.jasperreports.chrome.argument.no-sandbox=true

After setting this property, restart JasperReports Server to enable it.

For information about configuring this property, see the JasperReports Server Community Project Administrator Guide.