Updates Made by the Installer During Installation
This section lists the standard updates that the installer makes to your local environment if you install to existing applications. When the installation completes, you can check that the updates, or corresponding changes, were successful.
Updates made to the application server
If you installed to an existing Tomcat, the following modifications to the Tomcat environment were attempted:
|
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) |
|
Windows: bin/setenv.bat Linux and Mac OSX: bin/setevn.sh |
Creates this file. Sets increased Java memory allocation values to JAVA_OPTS. For additional settings, refer to Setting JVM Options for Application Servers. |
|
Tomcat 5: common/lib Tomcat 6 and 7: lib |
Adds PostgreSQL JDBC driver to this directory. As of 5.1, add additional JDBC drivers for other databases. |
Updates made to the PostgreSQL database
If you installed to an existing PostgreSQL database, new schemas and users are created 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.
Checking your Java JVM Options
For both the bundled Tomcat and the existing Tomcat, the installer attempts to set Java JVM options to help with memory allocation. You can double-check the values set to see that they are appropriate for your installation. If you installed a bundled version of Tomcat from the installer, these are the default Java JVM options for heap memory allocation:
|
Installer Type |
Setting |
File Location |
|
32 bit (x86) Linux |
-Xms512m -Xmx1024m -XX:MaxPermSize=512m |
<js-install>/apache-tomcat/scripts/ctl.sh |
|
64 bit (x64) Windows |
-Xms1024m -Xmx2048m -XX:MaxPermSize=512m |
<js-install>/apache-tomcat/bin/service.bat |
|
64 bit (x64) Linux and Mac OSX |
-Xms1024m -Xmx2048m -XX:MaxPermSize=512m |
<js-install>/apache-tomcat/scripts/ctl.sh |
