Changes in Functionality

This section describes changes in functionality in the Jaspersoft BI Suite Version 9.0.0 release.

For the list changes in versions 8.x.x, refer to the following list:

Following are the list of changes in JasperReports® Server version 9.0.0:

  • Progress JDBC drivers removed from JasperReports Server

    Progress JDBC drivers have been removed from JasperReports Server.

    If you have any resources that use or depend on any of the following Progress JDBC Drivers:

    • TIautorest-6.0.1.005359.jar
    • TIcassandra-6.0.3.jar
    • TIdb2-5.1.4.000288.jar
    • TIgooglebigquery-6.0.0.001346.jar
    • TIhive-5.14.1.jar
    • TIimpala-5.14.2.jar
    • TImongodb-6.0.2.000510.jar
    • TIoracle-6.0.0.000790.jar
    • TIredshift-5.14.1.jar / TIredshift-6.0.0.000366.jar
    • TIsforce-6.0.0.001533.jar
    • TIsparksql-6.0.1.000124.jar
    • TIsqlserver-6.0.0.000541.jar

    then you must manually install native drivers. After installing new drivers, update the resources in JasperReports® Server to use the new drivers. Note that the migration of SQL Server, Oracle, and DB2 resources from Progress to native database vendor drivers can bring challenges, particularly with the behavior of resources. Post-upgrade, you might encounter situations where resources either stop functioning or display changed behaviors. This discrepancy is caused by the variance in how Progress JDBC drivers and Native drivers interpret certain data types.

    For guidance on resolving such issues, detailed solutions can be found in the Changes in 9.0 That May Affect Your Upgrade section in JasperReports® Server Upgrade Guide

  • AdHoc Component in Reports

    With the introduction of the AdHoc Component feature, every new AdHoc report generated from an AdHoc view automatically activates this functionality. This integration ensures that any modifications made in the AdHoc view are automatically reflected in its associated AdHoc Report. AdHoc Reports created prior to or imported from earlier JasperReports® Server versions maintain their existing behavior and do not dynamically incorporate AdHoc view changes. To use the AdHoc Component feature for your AdHoc Reports, it is a best practice to recreate reports from the AdHoc views in JasperReports® Server 9.0.0.

    The AdHoc Component feature relies on the new report templates included JasperReports® Server 9.0.0, located at /public/templates. It is important to be aware that these templates have the same names as before. And, while importing older resources, there is a risk of overwriting these templates by accident. In such cases, AdHoc reports might get generated and function correctly, based on legacy report templates. To fix this, you can reimport these templates that are included as a part of our export-minimal-catalogs. The templates can be imported using the js-ant import-minimal-pro command (for details, see JasperReports® Server Installation Guide).

If your deployment uses custom AdHoc templates, it is advised to update them to the new format based on the templates found in /public/templates.

  • JasperReports Server and JasperReports Web Studio integration

    The introduction of the latest JasperReports® Web Studio brings a requirement to deploy two additional applications crucial for the normal functioning of JasperReports® Web Studio. These applications can be deployed either on the same application server as JasperReports® Server or remotely.

    Additional memory must be allocated to the application server, to meet the demand of deployment of the two new JasperReports® Web Studio applications. The amount of memory required depends on the usage pattern of JasperReports® Web Studio. Typically, the memory requirements for JasperReports® Web Studio are significantly lower than those for the main JasperReports® Server application.

    For more information, see JasperReports® Server Administrator Guide and JasperReports® Server Installation Guide.

  • Advanced Date Time Calculations

    To support the new calculations, the following Date grouping functions were renamed:

    • Quarter renamed to Quarter and Year (for example, Q1 2024, Q2 2024, Q3 2024, Q4 2024).

    • Month renamed to Month and Year (for example, January 2024, February 2024).

  • Updates to JNDI Data Sources

    With the addition of the JNDI Security feature, you must createJNDI resources even if the feature is disabled. If there are plans to enable this feature, ensure that all resources that are dependent on jdbc/jasperserver transition to jdbc/jasperserverSystemAnalytics. Similarly, resources using jdbc/jasperserverAudit must be migrated to jdbc/jasperserverAuditAnalytics.

    For more information, see JasperReports® Server Installation Guide and JasperReports® Server Upgrade Guide.

  • OAuth with OpenID

    The introduction of OAuth support requires migration of configurations for previous deployments of JasperReports® Server. If your deployment relied on OAuth configurations customized within applicationContext-externalAuth-*.xml, it is required to migrate these configurations to the new format.

    For more information, see JasperReports® Server External Authentication Cookbook.

  • Alerting in Report Viewer

    The Alerting feature in the Report Viewer operates on the Quartz engine, similar to the Scheduler. To support the increased load from Alert executions on the JasperReports® Server system, the configuration of org.quartz.threadPool.threadCount is increased from 2 to 4. If your deployment has modified this property, it is a best practice to increase it by adding additional threads specifically for Alerting tasks. It is important to note that the introduction of new Alerting tasks might result in an additional load on the overall system performance. However, the footprint of Alerting tasks is comparable to Scheduler tasks. It is because Alert executions perform report executions when triggered, similar to how scheduled jobs do it. Adjust the system configuration based on your usage of the Alerting feature to optimize performance. For detailed information, see JasperReports® Server Installation Guide and JasperReports® Server Administrator Guide.

  • Improvements in the existing column names of the Schedules page

    The view of the Schedules page has been improved with updates to the following existing column names:

    Old Column Names New Column Remarks
    Job name Job name/Description Updated
    Resource Resource/URL Updated
    Owner User Updated

    For more information, see JasperReports® Server User Guide.

  • The ability to delete the system user AnonymousUser is now disabled

    The ability to delete the system user AnonymousUser is now disabled. This role is strictly an internal system user that is required for the normal functioning of JasperReports® Server.

  • Due to security reasons, the container element for viz.js should not have script elements

    Due to security reasons when setting a container for viz.js, that container element cannot be a Script Element or an Element that has children script tags.

    For more information, see JasperReports® Server Visualize.js Guide.

  • Configuring Scheduler for Dashboard

    You can use the JasperReports® Server to enable the scheduler and headless browser to load the dashboard on the server side and export it. You need to set the deploy.base.local.url property in the js.config.properties file when detailed is selected during Export.

    For more information, see the Configuring the Scheduler for Dashboards section in JasperReports® Server Administrator Guide.