TIBCO JasperReports® Server 6.2.1 Release
Introduction
JasperReports Server is a high-performance standalone or embeddable Business Intelligence (BI) platform that provides rich reporting and integrated in-memory analysis capabilities.
These release notes describe the installation and available functionality at a high level; for details, please refer to the online help. Please also refer to the documentation, which is available at: http://community.jaspersoft.com/documentation or at <js-install>/docs after installation. In particular, refer to the Installation Guide for instructions about running the 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 you login to JasperReports Server for the first time. If you installed the server using the installer binary (rather than deploying a WAR file), you have already agreed to this license.
What's New
JasperReports Server 6.2.1 includes 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 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 Custom Visualization 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 of JasperReports Library to use for compiling reports. This does not affect reports uploaded to JasperReports Server, which are 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 now 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 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 pick a new workspace location. Once Jaspersoft Studio has launched, you can import your previous projects to the new location. You can also import data adapters, server connections and preferences.
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.
Installation Overview
Binary Installer
To install JasperReports Server, you can use the binary installer, which is available for Windows, Linux, and Mac. This installer optionally puts Tomcat, Java, and PostgreSQL onto your system so that JasperReports Server is ready to run.
Download this installer from http://jaspersoft.com/downloads or from the Support site: http://support.jaspersoft.com: jasperreports-server-6.2.1-<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 scripts if 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 the Installation Guide. To run the js-install scripts, download the WAR File Distribution ZIP file from the Jaspersoft Support site at http://support.jaspersoft.com. The file name is: jasperreports-server-6.2.1-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.
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 also created, including:
| User | Password |
|---|---|
| joeuser | joeuser |
| demo | demo |
CAUTION: For security reasons, always change the default passwords immediately after installing JasperReports Server.
Starting and Stopping
If you installed using the binary installer, refer to this section 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.2.1 > 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.2.1/jasperServerStart.app
/Applications/jasperreports-server-6.2.1/jasperServerStop.app
/Applications/jasperreports-server-6.2.1/jasperServerLogin.app
Alternatively, you can start/stop from the OS X command line:
./<js-install>/ctlscript.sh (start|stop)
Upgrade Notes
6.1 Introduction
You can upgrade directly to 6.2.1 if your instance is one of the following:
|
|
|
To upgrade, start with the WAR File Distribution ZIP: jasperreports-server-6.2.1-bin.zip
It can be downloaded from the Jaspersoft Support site at http://support.jaspersoft.com.
The recommended upgrade procedures are fully described in the Upgrade 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.1, 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.x and 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.
6.2 Upgrade to 6.2.1 (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 original web 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.2.1.zip
To start your overlay upgrade, unzip the package and open a
command shell to the root of the package. Make sure to stop
your 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.2.1
--------------------------------------
To upgrade from 6.x, the recommended procedure is
described in the Upgrade Guide Chapter 3. This procedure is run
from the command line. Here is a summary of the steps used for
this upgrade procedure:
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 the
JasperReports 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 a
summary of the steps used for this upgrade procedure:
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
follow the 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
is replaced 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. We
now use Spring Security 3. 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.
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.5 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.
Security Fixes
* 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, TIBCO Jaspersoft 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
Known Issues
* 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.
* 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 a report 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.
* 31955: In Pro Charts (based on Fusion), Gantt charts do not
support HTML5 output format. We find that this limitation
originates in Fusion, and so have no plans to resolve it.
Fusion may address this issue in a subsequent release.
Since the problem originates in the PostgreSQL installer,
we have no plans to resolve.
* 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
* 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
* 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 the Domain.
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 out of 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.
* 43387: We are aware of a significant performance issue when
the server is run in Tomcat 8.0.15. Because of it, we
recommend that you use an earlier version of Tomcat (any
8.0.x before 8.0.15). We plan to address this issue in a
subsequent release.
* 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.
* 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.
* 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
* 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.
* 44541: When the JasperReports Server installation executable
runs in Windows against an existing Tomcat instance, it
doesn't remove the contents of the WEB-INF/lib directory. This
results in duplicate JAR files, which cause Tomcat to return
errors and fail to initialize.
To work around this issue, delete the contents of the
WEB-INF/lib directory before running the installation
executable.
These defects, which were listed in the release notes of previous
versions, are considered obsolete in this release:
* 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 10.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 previous
versions, 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 (found in
<js-install>apache-tomcatwebappsjasperserver-proWEB-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.
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.14
* Postgres 9.3.9 (32 or 64 bit)
* Oracle JDK 1.8.0_51 (32 or 64 bit)
* 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), 8.1, and 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; 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 7.0, 8.0, and 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 2008 R2, 2012, and 2014
* Oracle 11g R2 and 12c
Java Virtual Machines:
* Oracle JDK 1.7 and 1.8
* OpenJDK 1.6; specifically:
* OpenJDK 1.6.0_20
* OpenJDK RunTime Environment (IcedTea6 1.9.7)
* OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
* OpenJDK 1.7 and 1.8
* IBM JDK 1.7 and 1.8
For more information, refer to the Jaspersoft Platform Support
document, which is available on the Support Portal.
End of Support Notices
TIBCO Jaspersoft is in the process of ending support for several
technologies:
* JasperReports Server no longer supports JDK 1.5.
* 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 old 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 for details.
* 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,
you must 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 version 4.5.x ended on July 2, 2014.
- Support for version 4.7.x ended on November 12, 2014.
- Support for version 5.0.x ended on April 29, 2015.
- Support for version 5.1.x ended on June 28, 2015.
- Support for version 5.2.x ended on October 25, 2015.
* Support for version 5.5.x of our Jaspersoft BI products,
including JasperReports, JasperReports Server, and iReport,
will end on May 28, 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.
Evaluation License
The installer includes several 30 day evaluation licenses that
allow you to run various editions of JasperReports Server.
When the evaluation period expires, you must replace the
evaluation license with a commercial license to enable the
software. Please refer to the JasperReports Server Installation
Guide for information on replacing the license.
If you don't already have a commercial license, you can obtain
one by contacting your Sales representative.
During your evaluation, we invite you to use Evaluation Central
to 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: 0316-JSP62-33
Copyright © 2005-2016, TIBCO Software Inc. All rights
reserved. Printed in the U.S.A. Jaspersoft, the Jaspersoft logo,
Jaspersoft iReport Designer, Jaspersoft Studio, JasperReports
Library, JasperReports Server, Jaspersoft OLAP, and Jaspersoft
ETL are trademarks and/or registered trademarks of TIBCO
Software Inc. in the United States and in jurisdictions
throughout the world. All other company and product names are
or may be trade names or trademarks of their respective owners.
Recommended Comments
There are no comments to display.