TIBCO JasperReports (R) Server 6.3.2 Release

Table of Contents

1. Introduction2. What’s New3. Installation Overview4. Login5. Starting and Stopping6. Upgrade Notes7. Security Fixes 8. Known Issues9. Release Distributions10. End of Support Notices11. Evaluation License

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−1. Introduction

JasperReports Server is a high−performance standalone orembeddable Business Intelligence (BI) platform that providesrich reporting and integrated in−memory analysis capabilities.

These release notes describe the installation and availablefunctionality at a high level; for details, please refer to theonline help. Please also refer to the documentation, which isavailable at: http://community.jaspersoft.com/documentationor at <js−install>/docs after installation. In particular,refer to the Installation Guide for instructions about runningthe installer, creating and updating the database, and deploying the WAR file; refer to the Upgrade Guide for instructions on upgrading from previous versions.

Note: JasperReports Server is governed by a License Agreement,the text of which is found at <js−install>/Jaspersoft−Subscription−Services−Agreement.txt. Please read it before youlogin to JasperReports Server for the first time. If youinstalled the server using the installer binary (rather thandeploying a WAR file), you have already agreed to this license.

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−2. What’s New

JasperReports Server 6.3.2 is a maintenance release that includes improvements requested by customers. For information about the status of specific cases, please visit the Tibco Jaspersoft Support Portal.

In addition, this release includes an option to restrict the access granted to Groovy, which is distibuted with the server.By default, Groovy is given broad access within your application server, which is a good approach to certain design, testing, and evaluation tasks. However, some production systems should be configured to restrict Groovy to more limited access.

To enable the restriction, edit:

.../WEB−INF/applicationContext−semanticLayer.xml to uncomment the groovyCustomizerFactory property in the groovyRunner bean. .../WEB−INF/applicationContext−datarator.xml to set the

preprocessGroovy property (in the defaultPreprocessor bean ) to true. (Optionally) .../groovy/com/jaspersoft/commons/groovy/GroovyCustomizerFactoryImpl.groovy to add classes that Groovy should access by adding them to the GroovyCustomizerFactoryImpl When you enable and configure the whitelist, be sure to test your JasperReports Server environment thoroughly.

If you have been running your server without this restriction, and then enable and configure it, some functionality may fail. For more information, please see our article on the Jaspersoft community site (http://community.jaspersoft.com). More information is also available in the version 6.4 JasperReports Security Guide.

For more information about Groovy, see Apache’s Groovy web site.

Note: In some cases, documentation may refer to this release as 6.3.0. In such cases, the information applies to both 6.3.0 and 6.3.2.

JasperReports Server 6.3.0 added these improvements:

* Dashboards − New enhancements include: − Dashboard and dashlet exporting. − Text and image dashlets now support hyperlinks. − More formatting options for dashboards and dashlets. − New time and date wildcards for dashlets. − Auto−complete for parameters and time and date wildcards. − Image dashlets have a Browse button for the respository. * Scheduler − New enhancements include: − Support for scheduling Dashboard exports. − Support for SFTP with SSH key authentication as a transfer protocol. − Automatic validation of the path to the repository output folder when clicking Save. − Support for changing the default output folder by editing a configuration file. * Data Connectivity − We continue to improve and refine data access in JasperReports Server. This release adds: − New support for Microsoft SQL Azure. − New driver for Spark. − New Progress driver for Cassandra. − New JDBC driver for MongoDB. − Updated MongoDB Connector. − New Progress driver for Impala. − Updated JDBC driver for MariaDB. * Jaspersoft Studio − New enhancements include: − Support for font sets, which let you group font extensions in supersets that can include several languages or character

sets and control which languages are used for each font in the set.

− Import/export for configuration resources, which lets you migrate global configurations, such as global data adapters,

composite elements, and Jaspersoft Studio preferences between different instances of Jaspersoft Studio.

− Improved interface for editing properties in HTML5 charts. * Performance Improvements − JasperReports Server is faster and uses less memory when working with high−cardinality data in Ad Hoc views or reports based on Ad Hoc views. * Security Improvements − In our on−going effort to improve the security of your data, JasperReports Server implements a new Cross−Site Request Forgery (CSRF) protection mechanism that is more effective and less intrusive. For more information, see the Security Guide. To fully enable CSRF protection, please configure it as described in the JasperReports Server Security Guide.

JasperReports Server 6.2.1 added these improvements:

* Data Connectivity − We continue to improve and refine data access in JasperReports Server. This release adds: − Support for Kerberos Authentication for MongoDB data sources. − New JDBC drivers for Impala and Cassandra data sources. We recommend using the JDBC driver for new Cassandra data

sources and the native Cassandra driver only for existing data sources.

− A driver for Salesforce data sources can be added to JasperReports Server. − Support for these big data solutions: * Hortonworks HDP 1.3−2.3 * CDH 4.5.x− 5.5 * Apache Cassandra 2.0−2.2 * MongoDB 2.6 − 3.0 * Cloudera Impala 1.3 − 2.0 * New Supported Platforms − This release adds support for: − Operating Systems: Microsoft Windows 10; note that Microsoft Edge is also supported with this release. − Application Servers: WildFly 8.2.0

* New Advanced Chart Formatting Options − This release adds support for three−dimensional pie and bar charts, as well as solid gauges. In the Ad Hoc Editor, apply these effects using the Advanced tab of the Chart Formatting dialog. For more information, see: http://community.jaspersoft.com/wiki/advanced−chart−formatting * Jaspersoft (R) Studio − Our advanced report designer has several improvements, including: − Usability and interface improvements, including improvements to crosstabs, particularly when working with row and column groups; improvements to the UI for the Maps and TIBCO Maps

components; improvements to the community−supported CustomVisualization Component.

− Commercial versions of Jaspersoft Studio now include the Simba JDBC drivers for Impala and Cassandra. The Cloudera driver for Impala has been removed from Jaspersoft Studio; it is available as a plug−in on SourceForge. − If you are using your reports with an application you have built using JasperReports Library, you can use the Window >

Preferences > Compatibility Setting to choose the version ofJasperReports Library to use for compiling reports. This doesnot affect reports uploaded to JasperReports Server, whichare still set by configuring the settings for each server.

* Documentation Improvements − To improve the API documentation of JasperReports Server, the Web Services Guide has been redesigned and renamed as the REST API Reference. This book covers the current and complete REST API; the deprecated REST and SOAP APIs have been removed. Use the new REST API Reference to build client applications that access server functionality and embed reporting where your customers need it.

JasperReports Server 6.2.0 added these improvements:

* Organization Export and Import − To simplify administration of JasperReports Server, organization administrators can export and import entire organizations or sub−organizations, making it possible to quickly move or duplicate organization structures and the reports and dashboards they contain, including their dependencies. The new operations are available through the Manage menu and through new options for the import−export scripts. * Ad Hoc Editor − Ad Hoc views support new chart types, including tree charts and semi−pie; the ability to unmerge crosstab cells to show individual rows; and filtering to show the top or bottom values in crosstabs. The new chart types are also available in Jaspersoft Studio. * Dashboard Designer − Dashboards now support image dashlets, streamlined parameter handling, and export. * Scheduler Master View − A new Schedules page lets you view and manage all scheduled jobs that you can access. * Jaspersoft Studio − Our advanced report designer has several improvements, including: − The RCP version of Jaspersoft Studio has been updated to Eclipse 4.5. − An improved interface for the Maps component makes it easier to add markers and paths to Google maps, as well as to authenticate using your API key or client ID. − Enhancements to the custom visualization component let you create your own component UI using a JSON file. − A new grid layout makes it easier to place elements in containers, such as bands, tables, crosstabs, and frames. − Two ready to use custom visualization components: * Figures: This example component lets you add a visualization of stick figures representing a set of

values. Such visualizations are often used in infographics to depict complex information in a format that’s easy to read.

* Radial Progress: This example component lets you add a circular visualization that represents a percentage. Values up to 100% are drawn as a single ring or portion thereof. For values above 100%, additional rings are drawn. For more information on these community−supported features visit community.jaspersoft.com.

− Due to incompatibilities between Eclipse 4.5 and earlier versions of the Jaspersoft Studio workspace, the workspace

format has been updated. Upgrading users are prompted to picka new workspace location. Once Jaspersoft Studio launches, you

can import your previous projects to the new location. You can also import data sdapters, server connections, andpreferences.

* Visualize.js − Our embeddable JavaScript solution now supports dashboards, report search, report bookmarks, and floating headers in tables and crosstabs.

* Data Connectivity − We continue to improve and refine data access in JasperReports Server. Impala and Spark are now supported as JDBC data sources.

JasperReports Server 6.1.1 added these improvements:

* Updated Domain schema − A new schema for Domains, schema_1_2.xsd, adds support for influencing which join paths are used in Ad Hoc views when a Domain includes a circular join. This feature is only available by directly editing the Domain XML file; once the Domain XML is edited, you can’t use the Domain designer to edit the Domain.

* Keyboard Navigation and Improved Accessibility − Keyboard navigation has been improved in the web UI. Accessibility has been improved, including the Easy Access theme, which increases color contrast and highlighting in the web UI. It can improve the user experience of those with visual impairment. For more information on themes, see the JasperReports Server Administrator Guide. For information on keyboard navigation, see the JasperReports Server User Guide. * Data Connectivity − We have improved our support for MongoDB, including support for SSL or X.509 authentication using the native driver. For information on using MongoDB, see the JasperReports Server Administrator Guide. * Performance Improvements − JasperReports Server’s performance has been improved, particularly when adding organizations in an instance with a very large number of organizations. * New Supported Platforms − This release added support for: − Operating Systems: RHEL 7.1 − Databases: PostgreSQL 9.4 − Application Servers: * tcServer 2.5.1, 2.6.5, and 2.9.10 * JBoss EAP 6.3 and 6.4 − Java Development Kits: * Open JDK 1.8 * IBM JDK 1.7 JasperReports Server 6.1.0 added these improvements:

* Dashboard hyperlinking − In the dashboard designer introduced in 6.0, you can now define hyperlink behavior for a chart dashlet, which lets you specify an internal or external URL to be called when a user clicks a dashlet. * Dashboard HTTP Parameters − Dashboards created with the Version 6 Dashboard Designer can be called via HTTP, which now includes the ability to pass parameters into a dashboard.

* Dashboard report self−hyperlinks − In the dashboard designer introduced in 6.0, self−hyperlinks are now supported in report dashlets.

* TIBCO Spotfire 7 Support − Spotfire Infolinks can be used as a data source in Jaspersoft Studio, and the resulting reports can run on the server.

* Visualize.js − New enhancements provide control for report: − Magnification − Save/Save As − Sorting of columns in interactive reports

* Support for TIBCO GeoAnalytics Maps − In this release, you can create reports in Jaspersoft Studio that include map components from GeoAnalytics. Either TIBCO Maps or Google Maps can provide the map image of these multi−layer maps, and paths and markers can be defined using either latitude and longitude or a street address through geolocation. Note that a separate license is required to access TIBCO’s geolocation services.

* Data Connectivity − We continue to improve and refine data access in JasperReports Server. This release adds: − Support for Query based data sources, such as XML/A, JSON, and Remote XML. − Domains partially support custom data sources (users can only view the Display tab in the Domain designer. However, users can apply pre−filters and calculated measures using the

the Domain XML file). − Custom data sources can be included in virtual data sources. − Custom data source deployment has been simplified. For details, see the JasperReports Server Administrator Guide. * Documentation Improvements − In our continuing efforts to improve the security of JasperReports Server, we have reorganized some of our documentation for ease of use. In previous releases, information about securing the application was spread across several documents. In this release, the new security guide describes security concerns and steps you can take to protect your application. Details of data−level security in Jaspersoft (R) OLAP remain in that product’s documentation.

* More Powerful Attributes − A new user interface allows administrators to define attributes easily throughout the server. New permissions on attributes allow administrators to control the visibility and usage of attributes, as well as delegate management to sub−organizations. Attributes are now accessible in Domains and Ad Hoc views so that data access and reports can be easily customized for each user or organization. * Diagnostics − Data/Result Set and Log Capture utilities now help diagnose problems with the Jaspersoft environment. For more information, see the JasperReports Server Administrator Guide. * Updated Default Theme − An updated theme for the web UI improves the server’s look and feel. * Updated version of Groovy − We have updated the version of one of our third−party components; Groovy is used in Domain definitions. We upgraded our Groovy version from 2.0.1 to 2.4.3. * HTML5 Rendering for Fusion components − Fusion−based charts, maps, and widgets in reports are rendered in HTML5 by default starting in this release; if users access Pro Widgets and Maps using IE8, configure the server to use Flash by default,

instead. For more information, see the JasperReports Server Administrator Guide. * We have updated versions of some of the third−party components that are provided in the JasperReports Server installer: − Apache Tomcat 7.0.59 − Postgres 9.1.15 (32 or 64 bit) − Oracle JDK 1.7.0_75 (32 or 64 bit) * New Platform Support − JasperReports Server now supports: − Oracle Java 8 as a JDK − Oracle 12c as a repository database − Oracle RAC as a repository database − New Big Data Support * MongoDB version 2.6 via TIBCO JDBC driver and native drivers * Domains now provide a user interface to create schemas for data stored in MongoDB * Hortonworks 2.2 and Cloudera 5.2 * Impala 2.0 (supported through TIBCO JDBC driver or

Cloudera drivers) * Spark SQL 1.1

* Amazon Redshift (supported through TIBCO JDBC driver) JasperReports Server 6.0.1 added these improvements:

* Custom Visualization Component − This new Jaspersoft Studio Community−supported component lets you leverage third−party JavaScript libraries, such as D3, in Jaspersoft Studio and JasperReports Server. For details, please see: http://tinyurl.com/lvvuaoj Please note that this component is only supported by the Jaspersoft Community (http://community.jaspersoft.com). TIBCO Jaspersoft Technical Support and Engineering do not currently provide support for this feature. The custom visualization component is a powerful and flexible feature, suitable for advanced users of JasperReports. Using the component requires advanced coding skills in the following technologies: − JavaScript − CSS − HTML/DHTML − The third−party library you want to expose in Jaspersoft Studio and JasperReports Server.

* Updated Spring Security − Starting in this release, the server now incorporates a more recent version of the underlying Spring Security framework. We now use Spring Security 3. The new version offers improved application security. If you are upgrading from a previous version of JasperReports Server, you may need to take additional steps to accommodate the file structure of the new version of Spring. This is particularly the case if you have custom LDAP or SSO configured for the server. For more information, refer to the JasperReports Server External Authentication Guide. JasperReports Server 6.0.0 added these improvements:

* New Dashboards − A new web−based dashboard design environment lets you create web responsive dashboards that include new

visualizations, reports, Ad Hoc views, input controls, filters and web pages. Dashlets dragged onto the canvas automatically resize to fit the available space. This is a significant improvement over the legacy dashboard designer that required multiple tools to create content. The new dashboard designer makes it easy to create dashlets with title bars, include formatted text, set advanced properties to control look and feel, and re−wire filters to specific dashlets. In some releases, features available in legacy dashboards aren’t available in the 6+ dashboard designer. See the release for your version for details.

* Visualize.js − With this release, you can now directly embed our new dashboards into web pages through JavaScript, letting web designers leverage the power of our new dashboards, including setting filter values directly from within any web page. This release adds: − New support to run, refresh, and cancel dashboards, including setting filter values. − More support for reports, including report zoom, export to JSON and CSV formats, and the ability to fetch data from the server.

For details, refer to the JasperReports Server Visualize.js Guide (formerly, the JasperReports Server Programming Guide).

* Interactive Reports − The web UI’s report viewer now includes: − Ad Hoc Filter Value Display − Lets report designers create an Ad Hoc Report Template in Jaspersoft Studio that displays Ad

Hoc filter values when viewing an Ad Hoc report. − Workbooks and Tables of Contents − Lets report designers create a JRXML report that contains workbook sections and a

Table of Contents that is displayed as a tabbed report in theserver’s report viewer. The table of contents is also created when the workbook is exported; for example, a PDF would include a table of contents hyperlinked to specific report pages. This eliminates the need for code that wasrequired to consolidate multiple reports and generate atable of contents in previous releases.

− Variable Page Format Support − Lets report designers combine reports that have varying page layout formats within a

single workbook. This lets the designer create highly customized content within a single report.

− Floating Crosstab Headings − When viewing a long crosstab report, headings are displayed and move with your view as you

scroll.

* Ad Hoc Views − Two new chart types have been added to Ad Hoc views: − Heat Map − Lets you visualize color−coded ranges of data across x− and y−axes for a single measure to quickly

highlight outliers. − Time Series Heat Map − Lets you visualize color−coded ranges of data across a combination of a date/time field and

non−date field for a single measure to quickly highlight outliers.

Also, you can control the formatting of legends and various labels to make better use of the chart canvas. This feature is especially valuable when charts are used in dashboards. Jaspersoft Studio also supports the new chart types.

* Domains Complex Joins − We have enhanced our join functionality to include complex operators (listed below). This feature is only available by directly editing the Domain XML file; once the Domain XML is edited, you can’t use the Domain designer to edit the Domain. Complex joins: − Can use constants for comparisons in join expressions. − Support more types of operators beyond equality (=), including !=, >,<,<=,>=, IN, and NOT IN. − Support new specification of join types (inner join, left outer join, and right outer join). − Address a previous issue of OR joins not being recognized properly. * Data Staging − A new configuration of JasperReports Server allows Ad Hoc views and reports to keep and refresh datasets in the Ad Hoc cache indefinitely. This can drastically improve performance for datasets that can be stored in the cache. A new UI setting allows you to select data staging independently in every Domain Topic. * Organization and Server Level Attributes − New profile attributes support hierarchical and categorical attributes at the user, organization, and server levels. You can refer to these attributes while developing reports in Jaspersoft Studio and while defining data sources in JasperReports Server, OLAP access grants, and Domain security files. The new profile attributes make organization management much more flexible and robust. You can define parameter−based data sources using attributes defined at user, organization, and server levels. The values of attributes are replaced only at run time, making it completely dynamic. Reports and data sources can be moved across users, organizations, and servers.

* Expanded Big Data Connectivity − JasperReports Server now supports: − Hive − Hortonworks HDP 1.3, 2.0 (Hive version 0.11x, 0.12x) − CDH 4.5.x− 5.1 (Hive version0.8x−0.13x) − Apache Cassandra 2.0 − MongoDB 2.4.x − Cloudera Impala 1.3.1 Note: if your version of Cassandra is 1.12.18 or higher, JasperReports Server supports authentication when connecting to it.

* New Third−party platforms − JasperReports Server now supports: − JBoss EAP 6.2 − PostgreSQL 9.1.15 − IBM DB2 10.5 − Microsoft SQL Server 2014 − Windows 8.1 − Ubuntu 14

* TIBCO Spotfire Support − JasperReports Server now supports the creation of reports that contain TIBCO Spotfire 6.5 Information Links using Jaspersoft Studio. For information regarding features added to 5.x releases, please

refer to the 5.6.1 release notes.

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−3. Installation Overview

Binary Installer−−−−−−−−−−−−−−−−

To install JasperReports Server, you can use the binaryinstaller, which is available for Windows, Linux, and Mac.This installer optionally puts Tomcat, Java, and PostgreSQLonto your system so that JasperReports Server is ready to run.

Download this installer from http://jaspersoft.com/downloadsor from the Support site: http://support.jaspersoft.com:

jasperreports−server−6.3.2−<osType>−x64−installer.<ext> (64 bit)

Double−click the installer and accept the default installation type to create a default installation. Select the custom installation type to configure your instance. The installer can also be run from the command line.

For more information on JasperReports Server installation,refer to the Installation Guide, which is found at:<js−install>/docs/JasperReports−Server−Install−Guide.pdf

War File Distribution ZIP js−install Script Installation−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

NOTE: You can use the js−install command−line shell scriptsif you are installing to the following databases: * PostgreSQL * MySQL * DB2 * Microsoft SQL Server * Oracle

And the following application servers: * Tomcat * Glassfish * JBoss * WildFly

For information on the js−install scripts, see Chapter 5 of theInstallation Guide. To run the js−install scripts, download theWAR File Distribution ZIP file from the Jaspersoft Support siteat http://support.jaspersoft.com. The file name is:

jasperreports−server−6.3.2−bin.zip

To install, go to the buildomatic folder, create and edit a default_master.properties file, and run js−install.sh/bat:

cd <js−install>/buildomatic cp sample_conf/<dbType>_master.properties default_master.properties

edit default_master.properties (with your app server and db properties added)

./js−install.sh (or js−install.bat)

Then setup increased JAVA_OPT memory options for your application server following instructions from the Installation Guide’s section 6.2.

For example, under Linux with Tomcat:

Add to <tomcat>/bin/setclasspath.sh at the top of the file: export JAVA_OPTS="$JAVA_OPTS −Xms1024m −Xmx2048m −XX:PermSize=32m −XX:MaxPermSize=512m"export JAVA_OPTS="$JAVA_OPTS −Xss2m −XX:+UseConcMarkSweepGC −XX:+CMSClassUnloadingEnabled"

Next, copy your jasperserver.license to your application server user’s home folder:

cp <js−install>/jasperserver.license <path−to−home−folder>

For information on JAVA_OPTS configuration and license configuration, see the Installation Guide sections 6.2 and 6.3.

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−4. Login

To login after installation, use the following URL:

http://<hostname>:8080/jasperserver−pro

During installation, default administrative users are created:

User: Password: superuser superuser jasperadmin jasperadmin

If you install the sample data, sample end−users are alsocreated, including: User: Password: joeuser joeuser demo demo

CAUTION: For security reasons, always change the defaultpasswords immediately after installing JasperReports Server.

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−5. Starting and Stopping

If you installed using the binary installer, refer to thissection for information about starting and stopping the server.For other configurations, refer to the Installation Guide.

Windows:

You can start and stop from the Windows menus:

Programs > JasperReports Server 6.3.2 > Start and Stop > Start Service or Stop Service

Linux:

You can start and stop from the command line:

./<js−install>/ctlscript.sh (start|stop)

Mac OS X:

From Finder, double−click the start, stop, or login apps:

/Applications/jasperreports−server−6.3.2/jasperServerStart.app /Applications/jasperreports−server−6.3.2/jasperServerStop.app /Applications/jasperreports−server−6.3.2/jasperServerLogin.app

Alternatively, you can start/stop from the OS X command line:

./<js−install>/ctlscript.sh (start|stop)

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−6. Upgrade Notes

This section includes:

6.1 Introduction6.2 Upgrade to 6.3.2 (Overlay Upgrade)6.3 Upgrade from 6.x to 6.3.26.4 Upgrade from Older Versions6.5 Upgrade from Community Project6.6 Important Upgrade Information

6.1 Introduction−−−−−−−−−−−−−−−− You can upgrade directly to 6.3.2 if your instance is one of thefollowing: * 3.7.x * 5.0 * 6.0.x* 4.x * 5.1 * 6.1.x* 4.1 * 5.2 * 6.2.x* 4.2.x * 5.5 * 6.3.x* 4.5.x * 5.6.x * 4.7.x To upgrade, start with the WAR File Distribution ZIP: jasperreports−server−6.3.2−bin.zip It can be downloaded from the Jaspersoft Support site athttp://support.jaspersoft.com. The recommended upgrade procedures are fully described in theUpgrade Guide chapters 2, 3, and 4. Note: If you are upgrading from certain version JasperReports Server, such as 4.5 or earlier, 5.6, 6.0, 6.0.1, 6.1, and 6.2.0, the upgrade involves substantial changes that may require you to plan and prepare beforehand. Please refer to the Upgrade Guide’s Appendix A for advice regarding these important considerations. Also, see section 6.6 of these Release Notes.

Database Changes−−−−−−−−−−−−−−−−

There are jasperserver repository database changes between 6.0.xand 6.1.x as well as between 6.1.x and 6.2.0. There are no database

changes between 6.2.0 and 6.2.1. There are database changes between 6.2.1 and 6.3.0.

6.2 Upgrade to 6.3.2 (Overlay Upgrade) (Tomcat Only)−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− The 5.1 release added an improved package for upgrading between versions called the Overlay Upgrade.

This package supports a new procedure for upgrading from JasperReports Server 4.0 and above. It can preserve and give execution−time feedback on modified files and customizations found in your JasperReports Server instance. This allows the upgrade to preserve your customizations and gives you visibility into which files changed.

This new procedure also supports rollback to put your originalweb application instance back in place.

This package is only implemented and certified to work with the Tomcat application server. All certified repository databases are supported.

Start by downloading the Overlay Upgrade package from http://support.jaspersoft.com. The package name is:

jasperreports−server−overlay−upgrade−6.3.2.zip

To start your overlay upgrade, unzip the package and open a command shell to the root of the package. Make sure to stopyour Tomcat instance. Then enter:

overlay install (this initiates the upgrade operation)

You are prompted for a working folder (accept the default) It is assumed that you have a default_master.properties file from your original JasperReports Server installation. You are prompted for the path to this file. Enter the path. The overlay upgrade can now execute.

Once the overlay upgrade is complete (and you have resolved any file conflicts), restart Tomcat.

Additional Supported Commands:

overlay help (this displays all available commands)

For information on the overlay upgrade functionality, see the JasperReports Server Upgrade Guide Chapter 2.

6.3 Upgrade from 6.x to 6.3.2−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− To upgrade from 6.x, the recommended procedure is described in theUpgrade Guide Chapter 3. Run this procedure from the command line. Here is a summary of the steps: cd <unpacked−dir>/buildomatic

cp sample_conf/<dbType>_master.properties default_master.properties

edit default_master.properties (add your app server and db properties)

./js−upgrade−samedb.sh (or js−upgrade−samedb.bat) 6.4 Upgrade from Older Versions−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− This upgrade procedure lets you upgrade from any of theJasperReports Server versions listed in this section’s introduction (starting with version 3.7 through 5.x). The recommended procedure is described in the Upgrade Guide Chapter 3. This procedure is run from the command line. Here is asummary of the steps:

Export your existing JasperReports Server repository data (using the buildomatic/js−export.sh/bat command) (for example: ./js−export.sh −−everything −−output−zip my−export.zip) (Or export directly from the UI as of version 5.0 and later)

cd <unpacked−dir>/buildomatic cp sample_conf/<dbType>_master.properties default_master.properties

edit default_master.properties (add your app server and db properties)

./js−upgrade−newdb.sh <path>/my−export.zip

(or js−upgrade−newdb.bat <path>/my−export.zip)

6.5 Upgrade from Community Project−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− If your current instance is the Community version, you can followthe Upgrade Guide steps in Chapter 6 to upgrade to the Commercial version. 6.6 Important Upgrade Information−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

6.6.1 Changes in the 6.2.1 Release

JasperReports Server provides new and updated drivers for various databases. In this release, the previous connector for Impala that was available on the Jaspersoft community website isreplaced with two new options:* TIBCO Impala JDBC driver (also called Progress)* Simba JDBC driver (Cloudera−endorsed JDBC interface)

For more information, refer to the JasperReports Server Upgrade Guide.

6.6.2 Changes in the 6.1.0 Release

The new look−and−feel of JasperReports Server required several changes to the structure of themes. If you have customized your theme, you must

re−apply those customizations to a new theme. For more information, refer to the JasperReports Server Upgrade Guide.

6.6.3 Changes in the 6.0.x Releases

Starting in this release, the server now incorporates a more recent version of the underlying Spring Security framework. Wenow use Spring Security 3. If you are upgrading from a previousversion of JasperReports Server, you may need to take additional steps to accommodate the file structure of the new version of Spring. This is particularly the case if you have custom LDAP orSSO configured for the server. For more information, refer to the JasperReports Server External Authentication Guide.

6.6.4 Changes in the 5.6.0 Release

The 5.6.0 version included two changes that may require you to take additional steps during upgrade:

* JDBC Drivers: The 5.6.0 version did not include JDBC drivers for some of the typical commercial databases (Oracle, Microsoft SQL Server, or DB2). In 5.6.1 and forward, we have included drivers for these data sources; the manual steps required to add these drivers are no longer necessary. For more information, see the documentation; in particular: − Information on working with drivers during installation is in the JasperReports Server Installation Guide. − Information on working with drivers during upgrade is in the JasperReports Server Upgrade Guide. − Information on working with drivers in the web UI is in the JasperReports Server Administrator Guide.

* Changes to OLAP engine: Due to a change between versions of the OLAP engine, if you use Jaspersoft OLAP’s XML/A functionality to connect to a remote JasperReports Servers XML/A sources in versions previous to 5.6.x, you must take additional steps to complete your upgrade to 5.6.x and later versions. For information, see Known Issue 35986 (in these release notes).

6.6.4 Additional Information on Planning for Upgrade

For additional information on planning for your upgrade, please see Appendix A "Planning Your Upgrade" in the JasperReports Server Upgrade Guide.

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−7. Security Updates

* This version of JasperReport Server includes security measures to better protect against Cross−Site Request Forgery (CSRF). To fully enable CSRF protection, configure the server as described in the JasperReports Server Security Guide.

* JS−24680 (was 36569): SECURITY − CVE−2014−0050. TIBCO Jaspersoft addressed a vulnerability in the Apache Commons FileUpload component. Previously, the server was potentially vulnerable to specially crafted Content−type headers that can allow Denial of Service attacks. In release 5.6.0,we upgraded to Apache Commons FileUpload component version 1.3.1, which addresses this security issue.

For more information on the underlying issue, see: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE−2014−0050

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−8. Known Issues

Note that we have adopted new tracking numbers for our known issues. Issues listed in previous releases’ notes list boththe old and new numbers; new known issues list only the new numbers.

* JA−926 (was 35986): If you use Jaspersoft OLAP’s XML/A functionality to connect to a remote JasperReports Server’s XML/A sources, you must take additional steps to complete your upgrade. You must redefine your XML/A connections to specify the connection string in a new way. For example, in previous versions, the Foodmart XML/A connection specified: Provider=Mondrian;DataSource=Foodmart In the new version, the DataSource portion of the connection string is always JRS when the remote provider is JasperReports Server. For example: Provider=Mondrian;DataSource=JRS

* JRL−242 (was 17824): While Fusion Charts support annotations, JasperReports Server and Jaspersoft Studio don’t support them. Annotations cannot be used in Pro Charts. We plan to address this issue in a subsequent release. * JRS−12507: The documentation for this release may refer to the release as 6.3.0. In such cases, the information applies to both 6.3.0 and 6.3.2. * JS−19100 (was 30018): When an XML/A provider returns data to the Ad Hoc Editor, JasperReports Server sometimes must convert the datatype to string. For example, an XML/A provider may return data of type currency; in an Ad Hoc view, such currency data is a string that displays as a symbol (such as $) and a number. When such an XML/A−based Ad Hoc view is saved as a report, its datatypes are converted again. JasperReports Server attempts to convert the data to their original types, but in some cases, such as currency, no such type is available, and so currency data is converted to type double. In reports created from an Ad Hoc view, XML/A data that was returned with datatype currency is displayed as a number; the currency symbol is omitted. We plan to address this issue in a subsequent release. * JS−20916 (was 32168): Though we don’t strictly support the practice, in previous versions of JasperReports Server, it was possible to create a clone install in JBoss by copying an existing JasperReports Server WAR file and deploying it to a new JBoss instance. With 5.1, Jaspersoft supports JBoss AS7/EAP6, but has uncovered issues with clone installs. For more information, refer to http://tinyurl.com/cv6ta2l * JS−27736 (was 40052): In previous versions of JasperReports Server, field IDs and item IDs in Domains could include spaces. With the addition of calculated fields, these spaces cause JasperReports Server to return errors when the Domain is edited,

or when users open Ad Hoc views and reports that rely on it. For example, this XML was valid in version 5.2:

<item description="customer id" descriptionId="" id="customer id" label="customer id" labelId="" resourceId="orders.customer id" />

But this returns errors in version 5.6.1 and later. In all later versions, IDs can’t include spaces. To work around this issue, edit the Domain design to replace spaces with underscores. For example, you would change the above XML to the following: <item description="customer id" descriptionId=""

id="customer_id" label="customer id" labelId="" resourceId="orders.customer_id" />

If you have a large number of Domains, we recommend that you write a script or application that can automatically make these substitutions. At a high level, you would:

1. In your preferred language, write a script that locates spaces in ID definitions and replaces them with underscores.2. Export your Domains from JasperReports Server, and extract them from the ZIP file if necessary.3. Run your script against the exported, unzipped Domains.4. Examine the Domains’ XML to confirm that your script worked correctly.5. ZIP your Domains into a new archive.

6. Import the Domains ZIP into a test instance of JasperReports Server.

7. Test each Domain and the Ad Hoc view and report that rely on them.

8. Identify and correct any problems you identify in your script.

9. Repeat steps 3−8 until your tests are successful. 10. When you’re sure your script is replacing spaces

correctly, import your Domains into your production JasperReports Server instance.

* JS−30583 (was 43387): Jaspersoft is aware of a significant performance issues when the server is run in certain versions of Tomcat. We recommend 8.0.43 or later. * JS−30677 (was 43514): We have found that earlier versions of PhantomJS may not support or include all the fonts JasperReports Server uses when exporting dashboards. For example: − If a dashboard contains fonts for certain locales (such as Japan and China), the text isn’t rendered properly in the exported dashboard. − If a table in a dashboard has been filtered or sorted, the sort and filter icons aren’t rendered properly in the exported dashboard. Sorted crosstabs exhibit similar

behavior.

If you experience such issues, we recommend that you upgrade your instance of PhantomJS to at least version 2.0. * JS−30847 (was 43707): If a dashboard contains an image dashlet that relies on the repo: syntax to refer to its image,

and superuser exports the dashboard (using the repository’s Export context menu item or the Manage > Server Settings > Export page), the image isn’t exported with the dashboard. We plan to address this issue in a subsequent release.

* JS−31424 (was 44413): When JasperReports Server is hosted by some versions of WebSphere, performance is slow. We have determined that this performance problem is resolved by WebSphere Application Server V8.5.5 Fix Pack 8. Once you apply this fix, your WebSphere version number is 8.5.5.8. for more information, including installation instructions, see IBM’s support article: http://www−01.ibm.com/support/docview.wss?uid=swg24041178

* JS−31493 (was 44499): The new chart types added in 6.2, dual−measure tree map, tree map, parent tree map, don’t currently support the hyperlink functionality when an Ad Hoc view or report is used in a dashboard. We plan to address this issue in a subsequent release.

* JS−32269: There is a security vulnerabilty to XML External Entity (XXE) Attacks when working with a Domain when it specifies a DOCTYPE. We added configurable protection against this threat. By default, this protection is disabled to facilitate upgrade, since the new setting may cause report template files (JRTX) uploaded in previous releases to throw errors. Consider enabling this setting if XXE attacks are a concern.

In the applicationContext.xml, set the skipXXECheck property to false to skip this security validation. When you have updated your JRTX files, enable the property by setting it to true; this properly secures your server.

For more information on this security issue, see: https://en.wikipedia.org/wiki/XML_external_entity_attack These defects, which were listed in the release notes of previous versions, are resolved in this release:

* JRL−648 (was 31955): In Pro Charts (based on Fusion), Gantt charts do not support HTML5 output format. This release includes a version of Fusion that addresses this limitation. Gantt charts can now be rendered in HTML5 output.

* JS−31528 (was 44541): When the JasperReports Server installation executable ran in Windows against an existing Tomcat instance, it didn’t remove the contents of the WEB−INF/lib directory, which resulted in duplicate JAR files that caused Tomcat to return errors and fail to initialize. This issue is resolved in this release. These defects, which were listed in the release notes of previous versions, are considered obsolete:

* 21798: When JasperReports Server is accessed through Microsoft Internet Explorer 8, performance may be impaired. Because this version of IE reached its end of life in January 2016, we consider this defect obsolete.

* 25258: When exporting your repository as part of the upgrade process from version 4.0.x, 4.1, or 4.2.x, an organization’s theme is reset to the server’s default theme. The workaround

is to reset each organization’s active theme. Custom themes may need to be upgraded, as described in the JasperReports Server Upgrade Guide. Because we have ended support for these versions, we consider this defect obsolete. * 32159: When the 64−bit JasperReports Server binary installer is run in some versions of Mac OSX (including Mac OSX 0.8.3), and you select the option to install the bundled PostgreSQL, an error appears if PostgreSQL 9.1 is already installed. Since we no longer certify this version of Mac OSX, we consider this defect obsolete. Note that this version of OSX is considered compatible with this version of JasperReports Server.

* 33003: Export catalogs created through the web UI in JasperReports Server version 5.1.x contained incorrect metadata. When these catalogs are imported into JasperReports Server version 5.2, the objects they contain are created in the wrong location in the repository. Because we ended support for version 5.2, we consider this defect obsolete. For more information about this defect, refer to the 5.2 release notes. * 44576: The release notes of a previous version suggested that JasperReports Server failed to export repository resources when the server was hosted by Glassfish 3 and higher and the web UI is viewed in Internet Explorer 9. We have determined that this issue was caused by incorrect configuration, and does not occur normally. This defect, which was listed in the release notes of previousversions, was resolved in a previous release: * 40543: Jaspersoft uncovered a number of issues while testing this release when deployed in Glassfish 3.1 that prevented us from supporting that specific version of Glassfish with previous releases. We have addressed this issue in this release, though it requires additional configuration steps when Glassfish 3.1.2 is used in a non−clustered environment. To change the configuration: 1. Using a text editor, open the web.xml file (found in <js−install>\apache−tomcat\webapps\jasperserver−pro\WEB−INF 2. Locate and uncomment this line: <!−−<listener−class>com.jaspersoft.jasperserver.core.util.GlassFishRequestContextListener</listener−class−−> 3. Locate and comment out (that is, add <!−− at the beginning of) this line):

<listener−class>org.springframework.web.context.request.RequestContextListener</listener−class> 4. Locate and uncomment these lines: <!−−filter> <filter−name>GlassFishFilter</filter−name> <filter−class>com.jaspersoft.jasperserver.war.GlassFishSessionFilter</filter−class> </filter−−> 5. Locate and comment out these lines): <!−−filter−mapping> <filter−name>GlassFishFilter</filter−name> <url−pattern>/*</url−pattern> </filter−mapping−−> 6. Save the file and restart the server.

For information regarding known issues addressed in 5.x releases, please refer to the 5.6.1 release notes.

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−9. Release Distributions

Installer Distributions:

* Installer General Notes

The installers contain all components needed to run the JasperReports Server web application. Bundled components are: * Apache Tomcat 8.0.43 * Postgres 9.3.15 (32 or 64 bit) * Oracle JDK 1.8.0_121 (32 or 64 bit) * PhantomJS 2.1.1 (Linux and Windows) or 1.9.8 (Mac) * JasperReports Server Web Application (WAR) file

* Installer Supported Operating Systems (32 bit and 64 bit) * Linux Installer: * Red Hat Enterprise Linux 5.4, 5.5, 5.6, 6.1, 6.4, and 7.1 * Novell SUSE Linux Enterprise 11.1 * Ubuntu 10, 11, 12, and 14 * Debian 5.0 and 6.0 * Fedora 19 and 20 * CentOS 5.6, 6.1, and 7

* Windows Installer: * Windows 7 (SP1) * Windows8.1 * Windows 10

* Mac OSX Installer: * Mountain Lion (10.8) * Maverick (10.9) * Yosemite (10.10.1) Note: OSX 32 bit is no longer supported as of version 5.5. * Installer Supported Application Configurations: * Bundled Tomcat with Bundled PostgreSQL * Bundled Tomcat with Existing PostgreSQL * Existing Tomcat with Bundled PostgreSQL * Existing Tomcat with Existing PostgreSQL

* WAR File Binary Distribution:

The War File Binary Distribution zip currently contains sample configurations and repository database setup scripts that support the following applications (file name: jasperreports−server−<ver>−bin.zip): * Application servers: * Apache Tomcat 6.0 and 7.0 (we recommend 7.0.19 and higher), and Tomcat 8 ((we recommend 8.0.43); Tomcat 6.0 is also

supported with the Linux advanced packaging tools (such as apt−get and yum)

* SpringSource tcServer 2.5.1, 2.6.5, and 2.9.10 * GlassFish 3.0 and 4.1 * JBoss 7.1, JBoss EAP 6.2, 6.3, and 6.4

* WildFly 8.2.0 * WebLogic 10.3.6 and 12 * WebSphere 8.5

* Database servers: * PostgreSQL 9.0, 9.1, 9.2, 9.3, and 9.4 * MySQL 5.5 and 5.6 * IBM DB2 9.7, 10.1, 10.5 * Microsoft SQL Server 2012 and 2014 * Oracle 11g R2 and 12c * Java Virtual Machines: * Oracle JDK 1.7 and 1.8 * OpenJDK 1.7 and 1.8 * IBM JDK 1.7 and 1.8

For more information, refer to the Jaspersoft Platform Supportdocument, which is available on the Support Portal.

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−10. End of Support Notices

TIBCO Jaspersoft is in the process of ending support for several technologies:

* JasperReports Server no longer supports JDK 1.5 or JDK 1.6. JasperReports Library, which underlies the server, is now compiled with source and target compatibility set to 1.7. * We have deprecated our Open Flash functionality in favor of HTML5 solutions. In particular, the Flash samples that shipped with previous versions of the server are no longer provided.Also note that the Flash export option has been removed from the report viewer. If you want to re−enable this option, you can uncomment the exporter in a configuration file.

To do so, open the WEB−INF/flows/viewReportBeans.xml file and uncomment this line: <entry key="swf" value−ref="swfExporterConfiguration"/>

* With the completion of the v2 REST API, we announced the deprecation of the original REST API and the end−of−life of the SOAP services. While these services will remain available in the server for the time being, we recommend that you migrate your integration to the latest API available: Jaspersoft v2 REST API. * In previous releases, information about our SOAP and REST APIs was found in the Web Services Guide. In this release, SOAP and v1 REST API are considered deprecated, so that information is no longer a part of the current documentation. The older guide is replaced by a new REST API Reference. If you must still use the older APIs, refer to the 6.2.0 version of the JasperReports Server Web Services Guide. * With the general availability of the commercial edition of Jaspersoft Studio, we announced that iReport is now in maintenance mode. We recommend that you migrate to Jaspersoft Studio, which offers improvements beyond what is available in iReport.

* With the addition of more advanced interactive behavior in the report viewer, JasperReports Server no longer supports interactivity in the xhtml report exporter. If you want your reports to be interactive when viewed in the server, use the default report exporter (html2). For more information, see the JasperReports Server Administrator Guide. * For Mac OSX, we no longer support: * The 32 bit version of Mac OSX * Mac OSX 10.5 In addition, Mac OSX 10.8.3 is no longer certified, but is considered compatible with this version of JasperReports Server. * Microsoft has needed support for some of its products: * In April 2014, Microsoft ended support for its Windows XP operating system. For more information, see:

http://www.microsoft.com/windows/en−us/xp/end−of−xp−support.aspx

* In January 12, 2016, Microsoft ended support for Internet Explorer version 8. Also note that JasperReports Server no longer supports Internet Explorer 7. For more information,

see: https://www.microsoft.com/en−us/WindowsForBusiness/End−of−IE−support

* Support for some versions of our Jaspersoft BI products, including JasperReports, JasperReports Server, and iReport, has ended: − Support for 4.5.x ended on July 2, 2014. − Support for 4.7.x ended on November 12, 2014. − Support for 5.0.x ended on April 29, 2015. − Support for 5.1.x ended on June 28, 2015. − Support for 5.2.x ended on October 25, 2015. − Support for 5.5.x ended on May 28, 2016. * Support for version 5.6.x of our Jaspersoft BI products, including JasperReports, JasperReports Server, and iReport, will end on November 30, 2016. * Version 5.6.1 was the last version that supported Spring Security 2.x. All releases after Version 6.0 support Spring 3.x and may require updates to authentication integration code written to work with prior JasperReports Server releases.

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−11. Evaluation License

The installer includes several 30 day evaluation licenses thatallow you to run various editions of JasperReports Server.

When the evaluation period expires, you must replace theevaluation license with a commercial license to enable thesoftware. Please refer to the JasperReports Server InstallationGuide for information on replacing the license.

If you don’t already have a commercial license, you can obtainone by contacting your sales representative.

During your evaluation, we invite you to use Evaluation Centralto learn about our products: http://www.jaspersoft.com/getting−started

We also offer a guided evaluation experience:https://www.jaspersoft.com/get−started−evaluating

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−Part Number: 0217−JSP63−35

Copyright (C) 2005−2017. TIBCO Software Inc. All Rights Reserved. TIBCO Software Inc.