Professional Documents
Culture Documents
TIB JS-JRS-CP 7.1.0 Relnotes-Ce PDF
TIB JS-JRS-CP 7.1.0 Relnotes-Ce PDF
RELEASE NOTES
RELEASE 7.1
http://www.jaspersoft.com
Copyright ©2005-2018 TIBCO Software Inc. All Rights Reserved. TIBCO Software Inc.
This is version 0518-JSO71-33 of the JasperReports Server Community Release Notes.
TABLE OF CONTENTS
Chapter 1 Introduction 5
Chapter 2 What's New 7
2.1 Version 7.1.0 7
Chapter 3 Installation and Basic Usage 11
3.1 Installation 11
3.1.1 Binary Installer 11
3.1.2 War File Distribution ZIP js-install Script Installation 11
3.2 Login 12
3.3 Starting and Stopping 13
3.3.1 Windows 13
3.3.2 Linux 13
3.3.3 Mac OS X 13
Chapter 4 Upgrade Notes 15
4.1 Introduction 15
4.2 Database Changes 16
4.3 Upgrade from 6.4.x to 7.1.0 16
4.4 Upgrade from Older Versions 16
4.5 Important Upgrade Information 17
Chapter 5 Known Issues 19
5.1 Current Known Issues 19
5.2 Known Issues Addressed in this Release 20
Chapter 6 Release Distributions 21
6.1 Installation Executables 21
6.1.1 Operating Systems 21
6.1.2 Components in the Installer 21
6.2 WAR File Binary Distributions 22
6.2.1 Java Virtual Machines 22
6.2.2 Application Servers 22
6.2.3 Database Servers 22
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 an installer binary (rather than deploying a WAR
file), you have already agreed to this license.
• Jaspersoft Studio. Several new features are available in our report designer:
• Spotfire (Version 7.5+) Infolink support. The data adapter for connecting to a Spotfire instance uses the
latest public Spotfire API. Report developer create content from Spotfire data.
• Support for properties in datasets and query executers. Better support for fields and parameters in the
Dataset and Query dialog, including support for field properties on the Fields tab and show and hide
built-in parameters and display, create, and edit parameter properties on the Parameters tab. This lets
you configure your fields and parameters directly in the Dataset and Query dialog.
• Data adapters that connect to a web service. You can now create data adapters that connect to a web
service. You configure these data adapters in the data adapter dialog. When you use this type of data
adapter in a report, you can access them in the Dataset and Query dialog: you can auto-discover fields
from a node you enter in the query dialog and view and manage HTTP parameters on the Data Adapter
tab.
• Enhanced Properties UI. The advanced properties dialog now displays a searchable list of available
properties. You can create expressions, toggle the view to the old Properties dialog, and add properties
for your custom classes. Most elements now support expressions in properties.
• Support for Data Snapshots. Jaspersoft Studio now lets you create a JasperReports data snapshot, which
contains a sample dataset that contains all the data necessary to run the report. Storing the data for a
report makes it easier to develop reports while offline or to share a functional report with other
developers working on the report design.
• New Platforms. Components included in the installer have been updated to:
• PostgreSQL 9.3.20
• Tomcat 8.5.30
• Oracle JDK 8 version 1.8.0_151 (8u151)
• Spring Framework 3.2.18
• New Third-party Software Support. This release adds support for Oracle 12c as a host for the
JasperReports Server repository and WebLogic 12.2.1 as the application server.
You can still create reports and connect to the latest JasperReports Server with previous versions of
Jaspersoft Studio.
• Security Improvement. JasperReports Server implements a new mechanism to protect against clickjacking
attacks. To enable this mechanism, edit a configuration file.
If you use iframes to embed JasperReports Server (including use of Visualize.js), set the
antiClickJackingOption to either SAMEORIGIN (if the embedding host is on the same domain as
JasperReports Server) or ALLOW-FROM (if the embedding host is on a different domain than
JasperReports Server). If you use ALLOW-FROM, also set the antiClickJackingUri property.
Clickjack protection doesn't support cases in which multiple domains embed JasperReports Server.
• Directory Access Control. A new option can deny access to directories in the file system of the
JasperReports Server host using the ResourceForwardingServlet servlet. The servlet forwards requests
from, for example, /runtime/<hex-code>/<my-resource> to the /<my-resource> URL to handle
browser caching.
Access to the WEB-INF and META-INF directories is always denied. In some circumstances, you may want
to deny access to other directories. For example, if you restrict access to certain directories using the
security-constraint tag in web.xml, also restrict access to those directories using the
forwardForbiddenDirectories parameter of the ResourceForwardingServlet servlet. To do so, edit a
configuration file.
<servlet>
<servlet-name>ResourceForwardingServlet</servlet-name>
<servlet-class>com.jaspersoft.jasperserver.war.ResourceForwardingServlet</servlet-class>
<init-param>
<param-name>forwardForbiddenDirectories</param-name>
<param-value>jpivot,fusion,wcf</param-value>
<!-- Comma separated list of any additional directories
(besides WEB-INF, META-INF) that the access is forbidden to-->
</init-param>
3.1 Installation
You can install JasperReports Server either by running an executable installer or deploying a WAR file. For
evaluations, we recommend you use the installer; for most production instances, we recommend you use the
WAR file. Both the executable and the WAR file are available from the Jaspersoft community site
(http://community.jaspersoft.com); download:
• TIB_js-jrs-cp_7.1.0_<osType>-<arch>.<ext>
• TIB_js-jrs-cp_7.1.0_bin.zip
For more information, see the installation guide, which is found at <js-install-ce>/docs/JasperReports-Server-CP-
Install-Guide.pdf.
To install:
1. Go to the buildomatic folder, create and edit a default_master.properties file, and run js-install-ce.sh/bat:
cd <js-install>/buildomatic
cp sample_conf/<dbType>_master.properties default_master.properties
2. Using a text editor, edit default_master.properties to add your application server and database server
properties.
3. Then change the JAVA_OPT memory options for your application server following instructions from the
installation guide. For example, under Linux with Tomcat running on JDK 1.8, add the following to the top
of the <tomcat>/bin/setclasspath.sh file:
4. Next, copy your jasperserver.license to your application server user's home folder:
cp <js-install>/jasperserver.license <path-to-home-folder>
3.2 Login
To login after installation, use the following URL:
http://<hostname>:8080/jasperserver
Always created
jasperadmin jasperadmin
If you install the sample data, these users are also created:
joeuser joeuser
For security reasons, always change the default passwords immediately after installing JasperReports
Server.
3.3.1 Windows
You can start and stop from the Windows menu: click Programs > JasperReports Server 7.1.0 CP > Start
and Stop > Start Service or Stop Service.
3.3.2 Linux
You can start and stop from the command line:
./<js-install>/ctlscript.sh (start|stop)
3.3.3 Mac OS X
From Finder, double-click the start, stop, or login apps:
/Applications/jasperreports-server-cp-7.1.0/jasperServerStart.app
/Applications/jasperreports-server-cp-7.1.0/jasperServerStop.app
/Applications/jasperreports-server-cp-7.1.0/jasperServerLogin.app
4.1 Introduction
Your current version determines your upgrade path:
You can upgrade directly to 7.1.0 if your instance is one of the following:
If your instance is one of the older versions listed below, you must first upgrade to the latest version of 6.4.x
before upgrading to 7.1.0:
For information about upgrading to 6.4.x, please see its release notes.
To upgrade, start with the WAR File Distribution ZIP: TIB_js-jrs-cp_7.1.0_bin.zip
Downloaded it from the Jaspersoft community site (http://community.jaspersoft.com).
The recommended upgrade procedures are fully described in the JasperReports Server Upgrade Guide.
If you are upgrading from certain versions of JasperReports Server, such as 6.0.1, 6.1, or 6.2.0, the
upgrade involves substantial changes that may require you to plan and prepare beforehand. See the
JasperReports Server Upgrade Guide for advice regarding these important considerations. Also, see 4.5,
“Important Upgrade Information,” on page 17.
cd <unpacked-dir>/buildomatic
cp sample_conf/<dbType>_master.properties default_master.properties
2. Using a text editor, edit default_master.properties to add your application server and database server
properties.
3. Run the install .sh or .bat file:
./js-upgrade-samedb-ce.sh
1. Export your existing JasperReports Server repository data, either using the buildomatic/js-export.sh/bat
command (for example, ./js-export-ce.sh --everything --output-zip my-export.zip), or by
exporting directly from the web UI).
2. Change directories to the buildomatic directory (for example, cd <unpacked-dir>/buildomatic).
3. Copy the master properties file (for example, cp sample_conf/<dbType>_master.properties default_
master.properties).
4. Edit the default_master.properties file to add your application server and database properties (for example,
./js-upgrade-newdb-ce.sh <path>/my-export.zip, or /.js-upgrade-newdb-ce.bat <path>/my-
export.zip).
Provider=Mondrian;DataSource=Foodmart
In more recent versions, the DataSource portion of the connection string is always JRS when the remote
provider is JasperReports Server. For example:
Provider=Mondrian;DataSource=JRS
Note that the final steps in this section, those regarding java.io.FilePermission, can be ignored.
• JRS-15525: In the course of testing Wildfly 8.1 with this version of JasperReports Server, we discovered
issues that prevented the server from starting. Because the issues aren't present in Wildfly 8.2, which we
already support, we have ended support for Wildfly 8.1.
• JRS-15530: The UI Samples page for administrators, available in previous releases, has been removed.
When testing themes and other cosmetic changes or customizations to the web UI, please navigate to a web
page with the UI component you're changing rather than viewing the samples page. We may 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. Though Jaspersoft supports JBoss EAP6, we uncovered issues
with clone installs. For more information, see this article on our Community website.
• JS-30583 (was 43387): We are aware of significant performance issues when the server is run in certain
versions of Tomcat. We recommend 8.5.30 or later.
homeFlow&j_username=jasperadmin|organization_1
we now use:
homeFlow&j_username=jasperadmin%7Corganization_1
Note that the related JasperReports Server documentation has been corrected and moved from the
JasperReports Server Security Guide to the JasperReports Server Installation Guide.
• Red Hat Enterprise Linux • Windows Vista (SP2) • Mountain Lion • Solaris SPARC 10
6.1, 6.4, 6.6, and 7.1 • Windows 2008 R1 (10.8) and 11
• Novell SUSE Linux and R2 • Maverick (10.9) • HP-UX 11.23 and
Enterprise 12.1 • Windows 7 (SP1) • Yosemite (10.10.1) 11.31
• Ubuntu 14.04 LTS and • Windows 8 and 8.1 • El Capitan (10.11) • FreeBSD 8.1 and
17.04 • Windows 10 • Sierra (10.12) 10.2
• Debian 8 and 9 • Windows Server • IBM AIX 7.2
• Fedora 22 2012 and 2016
• CentOS 6.4 and 7
During installation, you can choose whether to use an existing instance of Tomcat or create a new one to
host JasperReports Server. Similarly, you can choose whether to use an existing instance of PostgeSQL
or create a new one. These choices are entirely independent; you can use either an existing instance or
create a new instance of either.