Changes in 7.5 That May Affect Your Upgrade

Driver Updates

In the 7.5 release, the Simba JDBC drivers for Spark and Impala have been updated. By default, the new release supports the new JDBC drivers, and the old drivers cannot be used. You should update your data sources to use the new driver. For more information, see the JasperReports Server Community Project Administrator Guide.

Using the Old Impala Driver

If you want to continue using the Impala driver that was previously available from the community website, modify the install as described below.

If you do not add the files listed, data sources that use the old Impala driver will cause errors when running reports that rely on them.

Using the Old Spark Driver

If you want to continue using the Spark driver that was previously available from the community website, modify the install as described below.

If you do not add the files listed, data sources that use the old Spark driver will cause errors when running reports that rely on them.

Changes to the Cloud Software Group MongoDB Query Language

The Cloud Software Group MongoDB Query Language has been updated to reflect changes in the MongoDB driver:

See the language reference for more information.

Encryption Keys

JasperReports Server 7.5 streamlines how it manages the encryption keys it uses to protect sensitive data inside and outside of the server. There is no more any need to configure the encryption keys because all keys are generated automatically during the installation and stored in a central keystore. The keys are used transparently whenever the server stores passwords internally or exports sensitive data. And as long as the same user performs the upgrade, the upgrade scripts have access to the same keys in the keystore.

The new keys are backward compatible with the default keys from previous servers. However, there are possible cases when you need to manage keys during an upgrade. For example, if you do not have access to the user who installed the 7.5 instance, you may not be able to access the keystore anymore.

If you are in this situation, you should plan your upgrade as follows:

cd <js-install-7.5>/buildomatic
js-export.sh --everything --output-zip js-7.5-export.zip --genkey

This encrypts the export with the key that is displayed on the console output:

Secret Key: 0xb1 0x44 0x72 0x0a 0xe9 0x5b 0x39 0xf5 0x87 0x5c 0xa9 0x1b 0x99 0x9d 0x14 0x4c
Key Alias (UUID): 9e41cd54-31da-43aa-84c2-638a7d0b47b8

./js-import.sh --input-key "0xb1 0x44 0x72 0x0a 0xe9 0x5b 0x39
                 0xf5 0x87 0x5c 0xa9 0x1b 0x99 0x9d 0x14 0x4c"
               --keyalias 9e41cd54-31da-43aa-84c2-638a7d0b47b8
               --keyalg AES --keypass NewKeyPassword

For more information and procedures for importing keys, see the JasperReports Server Security Guide.

Theme Changes

The look and feel of the JasperReports Server web interface has been redesigned to modernize the application's appearance. To accomplish this, markup and styles have been modified. As a result of these modifications, custom themes developed for the previous interface will need to be updated for the new interface. The main changes are in the banner, body, and home page.

The following table lists the changes made to the user interface, except for the changes to the home page. The changes to the home page are extensive. Instead of attempting to update an existing home page, you should re-implement the home page in the new default theme.

If you have not customized the user interface, these changes will not affect you.

Banner