Migration and Compatibility
This section includes:
| • | Upgrade Paths |
| • | Upgrade File |
| • | Database Changes |
| • | Upgrade from Community Project |
| • | Important Upgrade Information |
Upgrade Paths
Your current version determines your upgrade path:
|
|
You can upgrade directly to 8.2.0 if your instance is the following:
| Version 8 |
8.0.x |
8.1.x
|
Note: If your instance is JasperReports Server 8.0 Compact, you can only upgrade to 8.1 Compact. If your instance is JasperReports Server 8.0 Split, you can only upgrade to 8.1 Split.
If your instance is one of the versions listed below, you must first upgrade to the latest version of 8.0.x before upgrading to JasperReports Server 8.2.0:
| Version 7 | 7.1.x | 7.2.x | 7.5.x | 7.8.x | 7.9.x |
If your instance is one of the versions listed below, you must first upgrade to the latest version of 7.1.x, then upgrade to 8.0.x, before finally upgrading to 8.2.0:
| Version 6 |
6.0.x |
6.1.x |
6.2.x |
6.3.x | 6.4.x |
If your instance is one of the versions listed below, you must first upgrade to the latest version of 6.4.x, then upgrade to 7.1.x, then upgrade to 8.0.x, before finally upgrading to 8.2.0:
| Version 5 |
5.0 |
5.1 |
5.2 |
5.5 |
5.6.x |
| Version 4 |
4.5.x |
4.7.x |
If your instance is one of the older versions listed below, you must first upgrade to the latest version of 6.3.x, then upgrade to 7.1.x, before finally upgrading to 8.2.0:
| Version 4 |
4.0 |
4.1 |
4.2.x |
| Version 3 | 3.7.x |
Upgrade File
To upgrade, start with the WAR File Distribution ZIP: TIB_js-jrs_8.2.0_bin.zip
Downloaded it from
The recommended upgrade procedures are fully described in the JasperReports Server Upgrade Guide.
Database Changes
Between certain versions of the server, we have changed the repository database in order to add new functionality. There are changes between 6.4.x, 7.1.x, 7.2, 7.5, 8.0, 8.1 and 8.2.
Upgrade from Community Project
If your current instance is the Community version, you can follow Chapter 6 of the JasperReports Server Upgrade Guide to upgrade to the Commercial version.
Important Upgrade Information
This section touches on special considerations for upgrading to this release. These considerations are explained more thoroughly in the JasperReports Server Upgrade Guide.
| • | Changes in the 8.2 Release. |
| • | Users are able to upgrade from 8.1 Compact to 8.2 Compact using samedb and newdb. |
| • | Users are able to upgrade from 8.1 Split to 8.2 Split using samedb and newdb. |
| • | Users will not be able to upgrade: |
| • | From 8.1 Compact to 8.2 Split. |
| • | From 8.1 Split to 8.2 Compact. |
If users need 8.2 Split installations but they are on 8.1 Compact, the required upgrade path is to:
1. Upgrade 8.1 Compact to 8.2 Compact.
2. Then, migrate from 8.2 Compact to 8.2 Split.
For more information on these installation options, see the Installation and Upgrade guides.
| • | Newdb Upgrade Note. |
Currently, the js-upgrade-newdb.sh/bat script does not import the access, audit, monitoring data when upgrading. However, once the upgrade process has completed, you can use the JRS UI - Import page to re-import the JRS export file that was passed in with the newdb script and select the check boxes for including access, audit and monitoring data. Once this import has completed, then the access, audit, monitoring data will exist in the new database/release.
| • | UI Customizations Note. |
If you had any customizations done for your UI (JavaScript and CSS files), you will have to first perform the JasperReports Server upgrade, then get the JasperReports Server Source Packages, apply customizations in the UI source files, rebuild them and publish into the upgraded JasperReports Server.
| • | Simba Driver Removal. |
As of release 8.0.4, Simba drivers are removed from JasperReports Server.
If you have any resources that use or depend on any of the following Simba Drivers:
| • | athena-jdbc42 2.0.33.1003 |
| • | cassandra-jdbc42 2.0.13.1014 |
| • | impala-jdbc42 2.6.26.1031 |
| • | neo4j-jdbc42 |
| • | spark-jdbc42 2.6.22.1040 |
then you must manually install publicly available drivers (for example, Athena and Cassandra have the same Simba drivers publicly available). For other drivers, you must obtain the drivers which are recommended by the database vendor. After installing new drivers, update the resources in JasperReports Server to use the new drivers.
| • | Changes in the 8.1 Release. |
| • | Users are able to upgrade from 8.0 Compact to 8.1 Compact using samedb and newdb. |
| • | Users are able to upgrade from 8.0 Split to 8.1 Split using samedb and newdb. |
| • | Users will not be able to upgrade: |
| • | From 8.0 Compact to 8.1 Split. |
| • | From 8.0 Split to 8.1 Compact. |
If users need 8.1 Split installations but they are on 8.0 Compact, the required upgrade path is to:
1. Upgrade 8.0 Compact to 8.1 Compact.
2. Then, migrate from 8.1 Compact to 8.1 Split.
For more information on these installation options, see the Installation and Upgrade guides.
| • | Changes in the 8.0 Release. JasperReports Server is now available as Compact (default) or Split installations (for more information on these installation options, see the Installation and Upgrade guides). This release introduces a new Docker/Kubernetes support for JRS deployment, which customers should migrate to as soon as possible to enable all available features (For more information, see https://github.com/TIBCOSoftware/js-docker.) There are database changes in this release. |
| • | Changes in the 7.9 Release. There are database changes in this release. |
| • | Changes in the 7.8 Release. JasperReports Server now uses the Chromium JavaScript engine to export reports and dashboard to PDF and other formats. PhantomJS/Rhino support has been removed. For information, see Changes in 7.8 that May Affect Your Upgrade in the JasperReports Server Upgrade Guide. |
| • | Changes in the 7.2 Release. Legacy dashboards are no longer available to view or edit starting in the 7.2 release. For more information, please refer to the latest 7.2.x upgrade guide. |
Recommended Comments
There are no comments to display.