Updates Made by the Installer During Installation
This section lists the standard updates the installer makes to your local environment when you install to existing applications. 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 Output Log File Location
The installer creates a log during installation that records information as the installation progresses. If you encounter any problems when you install JasperReports Server, it can be helpful to look at the installer log. 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.
Recommended Comments
There are no comments to display.