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 the following updates to the Tomcat environment:
| 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. |
| All platforms: lib | Adds JDBC drivers for databases 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.
Installing a New License File
By default, JasperReports Server is installed with an evaluation license that expires a number of days after installation. After the license expires, you can start the server, but you can't log in.
To obtain a commercial license, contact Technical Support or your sales representative.
To upgrade the evaluation license to a commercial one, copy the commercial license file over the evaluation license file.
Application servers have work directories where JSP files are compiled and cached and other objects are stored. These directories can cause errors when upgrading a license. To avoid errors, clear the work directory before upgrading your license. For instance, if you’re using Tomcat:
| 1. | Change directory to <tomcat>/work |
| 2. | Delete all the files in the directory |
After changing to a commercial license, make sure you stop the server before replacing the license file:
| 1. | Stop the server |
| 2. | Replace the license named jasperserver.license in the deployed JasperReports Server root directory with the new license file |
The file name should be jasperserver.license
| 3. | Restart the server |
By default, the license is in the <js-install> directory, but can be located elsewhere. You need to define the ‑Djs.license.directory Java Environment Variable in the Tomcat startup scripts to point to the license location. The name of the license file is jasperserver.license. Make sure the new license file has this name.
Restart JasperReports Server and log in to see if the license grants access. For information about license errors, see the troubleshooting section License-related Errors.
For additional license configuration options, refer to Setting Up the JasperReports Server License.
License File for Existing Tomcat as Windows Service
If you installed JasperReports Server into an existing Tomcat installation on a Windows system running as a Windows Service and the license file is not in the default location, because you didn't choose the default <js-install> installation directory (Choosing Installation Type), manually configure Tomcat to locate the license file.
Follow these steps to examine and update the license location:
| 1. | Open the Tomcat configuration tool by right-clicking the Tomcat icon in your quick-launch bar (usually in the lower-right corner of your desktop) or from the Windows 7 menu, expand Start > All Programs > Apache Tomcat. Right-click Configure Tomcat and select Run as administrator. |
| 2. | Select the Java tab. |
| 3. | At the bottom of the Java Options field, enter the following option: |
-Djs.license.directory=<js-install>
For example:
-Djs.license.directory=C:Jaspersoftjasperreports-server-6.1
| 4. | Stop and restart the application server. |
You should now be able to run JasperReports Server.
Checking your Java JVM Options
Whether you're using the bundled Tomcat or an existing Tomcat, the installer attempts to set Java JVM options to help with memory allocation. You can double-check the values set to see if they are appropriate for your installation. If you installed the bundled version of Tomcat, 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 |
Recommended Comments
There are no comments to display.