This chapter describes the recommended procedure for upgrading from JasperReports Server:

5.5 or 5.6

to JasperReports Server 5.6.1.

The examples describe how to use the js-upgrade shell scripts to carry out the upgrade operation.

This chapter contains the following sections:

Upgrade Steps Overview

These are the general steps used in this section:

If your current instance of JasperReports Server has any custom modifications or extensions, keep track of these and re-integrate them into your 5.6 instance after upgrading.

Back Up Your JasperReports Server Instance

First you must backup your JasperReports Server WAR file and jasperserver database so that they can be restored in case there is a problem with the upgrade. These steps are performed from the command line in a Windows or Linux shell.

The following backup example is for Tomcat with the PostgreSQL or MySQL database. For other databases, consult your DB administration documentation for back up information.

Back up your JasperReports Server WAR File:

Back up your Jasperserver Database:

cd <path>/JS_55_BACKUP

pg_dump --username=postgres  jasperserver  >  js-db-5.5-dump.sql

cd <path>/JS_55_BACKUP

mysqldump --user=root --password=<password> jasperserver > js-db-5.5-dump.sql

                cd <path>/JS_55_BACKUP                mysqldump --user=root --password=<password> --host=127.0.0.1 jasperserver > js-db-5.5-dump.sql[/code]        

Preparing the JasperReports Server 5.6.1 WAR File Distribution

Use the buildomatic js-upgrade scripts included in the 5.6.1 WAR file distribution ZIP release package to carry out the upgrade. Follow these steps to obtain and unpack the WAR file distribution ZIP file:

After you unpack the WAR File Distribution Zip, the resulting location will be known as:

<js-install-5.6>

Configuring Buildomatic for Your Database and Application Server

This upgrade procedure uses the js-upgrade-samedb shell script.

This section shows example configurations for the PostgreSQL, MySQL, and Oracle databases. Other databases are similar.

Example Buildomatic Configuration

The upgrade configuration is handled by the default_master.properties file. Jaspersoft provides a sample configuration file for each database. You must specify your database credentials and your application server location, and rename the file to default_master.properties.

PostgreSQL Example

This example shows how to configure default_master.properties for PostgreSQL.

MySQL Example

This example shows how to configure default_master.properties for MySQL.

Upgrading to JasperReports Server 5.6.1

Now that your buildomatic scripts have been configured, you can complete the upgrade.

js-upgrade Test

You can run the js-upgrade scripts in test mode using the test option. For example, in Windows enter:

cd <js-install-5.6>/buildomatic

js-upgrade-samedb.bat test

In test mode, the js-upgrade scripts check your default_master.properties settings. The application server location is validated and the capability to connect to the specified database is validated. Using test mode can help debug issues, such as an incorrect database password. Your system is not altered when executing the script in test mode.

Output Log Location

The js-upgrade script creates an output log that captures standard output and error output. If there are any problems during the execution of the script or if you want to remember which options you chose, you can open the output log file.

The output log file is located here:

<js-install-5.6>/buildomatic/logs/js-upgrade-<date>-<number>.log

Errors

If you encounter errors during the js-upgrade script execution, first look at the output log to see if you can spot any errors. Additionally, you should refer to the Troubleshooting appendix of the JasperReports Server Installation Guide. The information in this appendix applies to both js-upgrade scripts and the js-install scripts.

If you need to modify values in your default_master.properties file, you can simply edit the file. When the js-upgrade script is run again, the new values will be used.

Starting and Logging into JasperReports Server 5.6.1

Start your application server. Your database should already be running.

Clearing Your Browser Cache

Before you log in, make sure you and your end users clear the browser cache. JavaScript files, which enable the UI elements of JasperReports Server, are typically cached by the browser. Clear the cache to ensure that the newer files are used.

Logging into JasperReports Server

Log in using the following URL, user IDs, and passwords:

URL: http://localhost:8080/jasperserver-pro

Your JasperReports Server instance has now been upgraded to 5.6.1. In the event of startup or login problems, refer to the Troubleshooting appendix of the JasperReports Server Installation Guide.

Additional Tasks to Complete the Upgrade

The tasks described below should be done when the application server is shutdown.

Clearing the Application Server Work Folder

Application servers have work folders where JasperReports Server files are compiled and cached and other objects are stored. When you update the WAR file or license, the buildomatic deploy-webapp-pro target should automatically clear the application server’s work directory, but it’s a good practice to double-check. A permission problem, or some other problem, could prevent the clearing of the work folder.

To clear the work folder in Tomcat:

Clearing the Application Server Temp Folder

JasperReports Server uses caching to speed operations within the application. In the application server, caching files are created and stored for this caching functionality. Typically, these cached files are stored in a temp folder. Clear this temp folder to avoid any conflicts after the upgrade is complete. For Apache Tomcat the temp folder is <tomcat>/temp. (In general, the temp folder used by an Application Server corresponds to the path pointed at by the java.io.tmpdir Java system property.)

To clear the temp folder in Apache Tomcat:

Clearing the Repository Cache Database Table

In the jasperserver database, compiled JasperReports Library resources are cached in the JIRepositoryCache table for increased efficiency at runtime. In some cases, you may encounter errors running reports after an upgrade. Because the JasperReports Library JAR is typically updated with each new JasperReports Server release, old cached items can get out of date and thus cause errors at runtime. If you encounter errors that mention a JasperReports Library “local class incompatible,” check your repository cache table. In summary, you can clear your jasperserver database cache table whether there are errors or not as part of this upgrade process.

To manually clear the repository cache database table, run a SQL command similar to one shown below:

update JIRepositoryCache set item_reference = null;

delete from JIRepositoryCache;

Old Manual Upgrade Steps: 5.5 to 5.6.1

This section has the older, manual upgrade steps that were in place before the js-upgrade shell scripts were implemented in the 4.0 release. These are provided in the following table as a reference, mainly for internal use. The js-upgrade shell scripts execute these buildomatic targets “behind the scenes.” Jaspersoft recommends using the js-upgrade scripts described in the beginning of this upgrade chapter instead of these manual steps.

Older buildomatic upgrade steps for this chapter are the following: