Changes in 7.2 That May Affect Your Upgrade

Removal of Legacy Dashboards

JasperReports Server 7.2 removes support for legacy dashboards, created in JasperReports Server version 5.6.2 and earlier. If your JasperReports Server repository contains any legacy dashboards, a warning message will appear during the upgrade. If you continue with the upgrade, your legacy dashboards will be permanently deleted. You cannot roll back this operation after it's done.

If you have any legacy dashboards you want to keep, you should recreate them as new dashboards before upgrading. For information on creating new dashboards using the Dashboard Designer, see the TIBCO JasperReports Server User Guide.

Changes to the Login Page

The layout of the login page changed in JasperReports Server 7.2. There were no changes to the CSS classes, but some default values were changed. If you have customized the login page, test your customizations to ensure they have the desired effect in 7.2, and make any necessary changes. If you haven't customized the login page, this change doesn't affect you.

Spring Security Upgrade

JasperReports Server uses the Spring Security framework to implement security throughout the product. In JasperReports Server 7.2, the Spring Security framework was updated to Spring Security 4.2. For many users, this upgrade will have no impact. However, you may need to make some changes if you have implemented the following:

External authentication – If you have implemented external authentication or single sign-on in your server implementation, you need to update your implementation:
     If you implemented external authentication using one of the sample files included in the project, you need to re-implement your changes in the updated sample files included in JasperReports Server 7.2.
     If you implemented a custom external authentication solution, you need to migrate your solution to the new framework.
Customizations – If you have customized the server using Spring Security classes, you need to migrate your solution to the new framework.

Migrating External Authentication Sample Files

If you have implemented external authentication using one of the sample-applicationContext-<customName>.xml files located in the <js‑install>/samples/externalAuth-sample-config directory, migrate your changes to JasperReports Server 7.2 as follows:

1. Prior to upgrade, back up your existing applicationContext-<customName>.xml (for example, applicationContext-externalAuth-LDAP.xml), located in the <js-webapp>/WEB-INF directory of your previous version of JasperReports Server.
2. Update your server installation to JasperReports Server 7.2, as described in the TIBCO JasperReports Server Upgrade Guide.
3. In the new installation, locate the sample file that corresponds to the file you implemented previously. For example, if you implemented applicationContext-externalAuth-LDAP.xml, locate <js‑install-7.2>/samples/externalAuth-sample-config/sample-applicationContext-externalAuth-LDAP.xml.
4. Rename the JasperReports Server 7.2 sample file to remove the sample- prefix. For example, rename sample-applicationContext-externalAuth-LDAP.xml to applicationContext-externalAuth-LDAP.xml.
5. Configure the properties in the new sample file to match the properties in your existing sample file. To do this:
a. Locate each bean you have modified in the previous version.
b. Find the same bean in the JasperReports Server 7.2 sample. The names of the beans have not changed between versions.
c. Copy or re-enter the properties you need for your server, taking care not to copy over class names or class packages.

Although the bean names are the same in the JasperReports Server 7.2 sample files, the name and package of the class in many bean definitions have changed. Make sure not to overwrite the new names with the old ones.

d. Save the JasperReports Server 7.2 sample file.
e. Rename the JasperReports Server 7.2 sample file to remove the sample- prefix. For example, rename sample-applicationContext-externalAuth-LDAP.xml to applicationContext-externalAuth-LDAP.xml.
f. Place the modified file in the <js-webapp-7.2>/WEB-INF directory.

Migrating Customizations

The Spring Security codebase was significantly restructured from 3.x to 4.x. Many classnames have changed and other classes were moved to different packages. In addition, many classes were deprecated. At a minimum, you need to update the names and paths of the Spring Security classes you reference in any customizations you have made to JasperReports Server For information on updating your customizations see the Spring Security migration guide:

https://docs.spring.io/spring-security/site/migrate/current/3-to-4/html5/migrate-3-to-4-xml.html

For specific information about migrating from deprecated classes in 4.x, see the Deprecations topic in the same document.

Version: 
Feedback