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.
| | The drivers have been replaced due to vulnerabilities from third-party libraries. Update your data sources to use the new drivers |
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.
| 1. | Add the following files to the <js-install>/WEB-INF/lib directory: |
| • | Curator-client-2.6.0.jar |
| • | Curator-framework-2.6.0.jar |
| • | Curator-recipes-2.6.0.jar |
| • | Hive-metastore-1.2.2.jar |
| • | Hive-service-1.2.2.jar |
| • | Impala-jdbc4-1.0.44.1055.jar |
| • | Libfb303-0.9.3.jar |
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.
| 1. | Add the following files to the <js-install>/WEB-INF/lib directory: |
| • | Curator-client-2.6.0.jar |
| • | Curator-framework-2.6.0.jar |
| • | Curator-recipes-2.6.0.jar |
| • | Hive-metastore-1.2.2.jar |
| • | Hive-service-1.2.2.jar |
| • | Spark-jdbc4-1.1.1.1001.jar |
| • | Libfb303-0.9.3.jar |
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 TIBCO MongoDB Query Language
The TIBCO MongoDB Query Language has been updated to reflect changes in the MongoDB driver:
| • | All aggregate commands must be updated to the new API-driven query syntax. |
| • | All other command-driven queries (queries that use runCommand) are deprecated. If you want to use your queries in a future release, you should update them to the new syntax. |
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:
| 1. | Before starting, back up your original 7.5 server. |
| 2. | Then export everything from your running 7.5 server with the following command: |
This encrypts the export with the key that is displayed on the console output:
| 3. | Proceed with the upgrade and installation of the new server, but without migrating your data. |
| 4. | Import the key into your upgraded server with the following command. |
| 5. | Proceed with the migration of your data to the upgraded server, or manually import your catalog to the upgraded server. As the data is imported, it is decrypted with the given key, and re-encrypted with the server's new keys. |
| 6. | Once the server is ready for production, back up your data and new keystore once again. |
For more information and procedures for importing keys, see the TIBCO 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
| Element | Classname and Modifications | File | Notes |
|---|---|---|---|
| Banner |
Changed | containers.css | Default value:
|
| Body |
Changed the | containers.css | Default value:
|
| Banner Logo |
Changed Responsive behavior was added to the banner. There is now a breakpoint at which the logo shrinks in size (1100px) and a breakpoint at which it becomes hidden (980px). | theme.css | Default values:
Breakpoint from 981-1100px:
980px and below:
|
| Banner Main Navigation home icon |
New sprites for | containers.css | Default value:
High resolution value:
|
| Banner Main Navigation Item text |
Enlarged | containers.css | Default values:
|
| Banner Main Navigation Item arrow icon |
New sprites for | containers.css | Default values: background-image: url(images/disclosure_icons_sprite@1x.png) High resolution value: background-image: url(images/disclosure_icons_sprite@2x.png) |
| Banner Metadata container | #metalinks Changed With the addition of responsive behavior, the | theme.css | Default values: height: Breakpoint from 821-1100px:
Breakpoint from 751-820px:
|
| Banner Metadata text |
Enlarged | theme.css | Default values: font-size: 14px |
| Banner Search container |
Increased Responsive behavior was added to the banner. There are now breakpoints at which the search container shrinks in width and a breakpoint at which it becomes hidden. | controls.css | Default value:
Breakpoint from 821-1100px:
Breakpoint from 751-820px:
750px and below:
|
| Banner Search input wrapper |
Increased | controls.css | Default values: height: 28px |
| Banner Search input |
Responsive behavior was added to the banner. There are now breakpoints at which the search input shrinks in width and a breakpoint at which it becomes hidden. | controls.css | Default value:
Breakpoint from 821-1100px:
Breakpoint from 751-820px:
750px and below:
|
| Banner Search button icon |
New sprites for | controls.css | Default value:
High resolution value:
|
Recommended Comments
There are no comments to display.