Js Jss 9.0.0 User Guide
Js Jss 9.0.0 User Guide
User Guide
Version 9.0.0 | January 2024
Contents
Contents 2
Report Elements 59
Common Element Properties 60
The Palette 60
Element Properties 61
Inserting, Selecting, and Positioning Elements 63
Inserting Elements 63
Selecting Elements 63
Positioning Elements 64
Positioning Elements in Containers 65
Formatting Elements 71
Working with Advanced Properties 74
Example of Using the Properties Dialog 76
Variables in Property Names 79
Adding a Custom Property 81
Setting Properties for XLSX Metadata Export 81
Setting Properties for CSV Metadata Export 82
Graphic Elements 83
Line 83
Rectangle and Ellipse 83
Images 83
Padding and Borders 84
Text Elements 84
Static Text 85
Text Fields 85
Frames 87
Sizing the Frame 88
Inserting Page and Column Breaks 89
Working with Spreadsheet Layout 89
Example of Using Spreadsheet Layout 90
Working with Composite Elements 93
Creating and Editing Composite Elements 94
Exporting and Importing Composite Elements 97
Anchors, Bookmarks, and Hyperlinks 98
Anchors and Bookmarks 99
Hyperlinks 100
Hyperlink Types 104
Creating a Hyperlink 106
Advanced Elements and Custom Components 109
Custom Visualization Component 109
Fields 113
Understanding Fields 113
Registration of Fields from an SQL Query 115
Registration of JavaBean Fields 117
Fields and Text Fields 119
Data Centric Exporters 119
Configuring a Report's Metadata for PDF 508 Tags 120
Configuring a Report's Metadata for Use With the JSON Data Exporter 124
Parameters 128
Working With Parameters 128
Managing Parameters 129
Working with Parameter Properties 132
Default Parameters 135
Using Parameters in Queries 137
Using Parameters in a SQL Query 137
Using Parameters with Null Values 138
IN and NOTIN Clauses 139
Relative Dates 139
Passing Parameters from a Program 144
Parameters Prompt 146
Parameter Sets 148
Variables 154
Defining or Editing a Variable 154
Base Properties of a Variable 155
Other Properties of a Variable 155
Evaluation Time 156
Calculation Function 157
Increment Type 157
Reset Type 158
Incrementer Factory Class Name 159
Built-In Variables 159
Tips & Tricks 160
Expressions 161
Expression Types 162
Expression Operators and Object Methods 163
Using an If-Else Construct in an Expression 165
Using Unicode Characters in Expressions 166
Using Java as a Language for Expressions 167
Fonts 171
Font Extensions Reference 172
The Fonts Page 172
The Font Family Dialog 174
Font Sets 179
Example of Using Font Extensions 181
Creating Font Extensions and Font Sets 182
Using Font Extensions in a Report 186
Deploying Font Extensions to JasperReports Server 191
Glossary 639
Introduction
Jaspersoft® Studio is an Eclipse-based report designer for JasperReports® Library and
JasperReports® Server. It's available as an Eclipse plug-in or as a stand-alone application.
Jaspersoft Studio allows you to create sophisticated layouts containing charts, images,
subreports, crosstabs, and more. You can access your data through a variety of sources
including JDBC, TableModels, JavaBeans, XML, Hibernate, Big Data (such as Hive), CSV,
XML/A, as well as custom sources, then publish your reports as PDF, RTF, XML, XLSX, CSV,
HTML, XHTML, text, DOCX, or OpenOffice.
JasperReports® Server builds on JasperReports® Library as a comprehensive family of
Business Intelligence (BI) products, providing robust static and interactive reporting, report
server, and data analysis capabilities. These capabilities are available as either stand-alone
products, or as part of an integrated end-to-end BI suite utilizing common metadata and
provide shared services, such as security, a repository, and scheduling. The server exposes
comprehensive public interfaces enabling seamless integration with other applications and
the capability to easily add custom functionality.
This section describes functionality that can be restricted by the software license for JasperReports
Server. If you don’t see some of the options described in this section, your license may prohibit you
from using them. To find out what you're licensed to use, or to upgrade your license, contact
Jaspersoft.
The heart of the Jaspersoft® BI Suite is the server, which provides the ability to:
• Easily create new reports based on views designed in an intuitive, web-based, drag
and drop Ad Hoc Editor.
• Efficiently and securely manage many reports.
• Interact with reports, including sorting, changing formatting, entering parameters,
and drilling on data.
• Schedule reports for distribution through email and storage in the repository.
• Arrange reports and web content to create appealing, data-rich Jaspersoft
Dashboards that quickly convey business trends.
For users interested in multi-dimensional modeling, we offer Jaspersoft® OLAP, which runs
as part of the server.
While the Ad Hoc Editor lets users create simple reports, more complex reports can be
created outside of the server. You can either use Jaspersoft® Studio or manually write
JRXML code to create a report that can be run in the server. We recommend that you use
Jaspersoft Studio unless you have a thorough understanding of the JasperReports file
structure.
You can use the following sources of information to learn about JasperReports Server:
• Our core documentation describes how to install, administer, and use JasperReports
Server and Jaspersoft Studio. Core documentation is available in PDF format on the
Product Documentation website. You can also access PDF and HTML versions of
these guides online from the Documentation section of the Jaspersoft Community
website.
• Our Ultimate Guides document advanced features and configuration. They also
include best practice recommendations and numerous examples. You can access
PDF and HTML versions of these guides online from the Documentation section of
the Jaspersoft Community website.
• Our Online Learning Portal lets you learn at your own pace, and covers topics for
developers, system administrators, business users, and data integration users. The
Portal is available online from the Professional Services section of our website.
• Our free samples, which are installed with JasperReports Library, Jaspersoft Studio,
and JasperReports Server, are available and documented online. Please visit our
GitHub repository.
• If you have a subscription to our professional support offerings, please contact our
Technical Support team when you have questions or run into difficulties. They are
available on the web at https://www.jaspersoft.com/support.
JasperReports Server is a component of both a community project and commercial
offerings. Each integrates the standard features such as security, scheduling, a web services
interface, and much more for running and sharing reports. Commercial editions provide
additional features, including Ad Hoc views and reports, advanced charts, dashboards,
Domains, auditing, and a multi-organization architecture for hosting large BI deployments.
Requirements
Software Requirements
Jaspersoft Studio requires the Java Runtime Environment (JRE). To compile the report
scriptlets, a full distribution of Java is required. The JSS installer includes the required
version of Java.
During the JSS download, you must accept the Java license agreement and select the
correct operating system. Jaspersoft Studio is based on Eclipse and supports several
common operating systems. For the versions supported, see the JasperReports Server
Supported Platform Datasheet:
• Windows, 64 bit
• Linux, 64 bit
• MacOS X, 64 bit
To find the version of Eclipse used in Jaspersoft Studio:
1. Select Help > About Jaspersoft® Studio from the main menu.
Hardware Requirements
Jaspersoft Studio needs a 64-bit processor and at least 500 MB of hard disk space. The
amount of RAM needed is dependent on report complexity. A value of 1 GB dedicated to
Jaspersoft Studio is recommended, 2 GB is suggested.
Available Packages
The Eclipse RCP package is available in the following formats for community and
commercial versions.
Commercial versions:
• js-jss_x.x.x_linux_x86_64.tgz
• js-jss_x.x.x_macosx_x86_64.dmg
• js-jss_x.x.x_sources.zip
• js-jss_x.x.x_windows_x86_64.exe
• js-jss_x.x.x_windows_x86_64.zip
x.x.x represents the version number of Jaspersoft Studio.
For community only, unsupported versions for the Eclipse RCP are available as a
convenience for users who are in a restricted environment and cannot download or install
an .exe file:
• js-studiocomm_x.x.x_linux_amd64.deb
• js-studiocomm_x.x.x_linux_x86_64.tgz
• js-studiocomm_x.x.x_macosx_x86_64.dmg
• js-studiocomm_x.x.x_windows_x86_64.exe
• js-studiocomm_x.x.x_windows_x86_64.zip
The community version is also available as an unsupported Eclipse plug-in, called the
Jaspersoft Studio plugin. You can install it from the Eclipse Marketplace or download using
the Eclipse Update Manager. See the following article on the community website for more
information about working with the Jaspersoft Studio plugin.
http://community.jaspersoft.com/wiki/contributing-jaspersoft-studio-and-building-
sources
/LICENSE License Path Path to the license file to use for this installation. The
(optional - license file is copied into the Jaspersoft Studio
commercial installation folder and given the following filename:
versions only) Jaspersoft-JSS.license. If no license is specified,
Jaspersoft Studio looks for the file Jaspersoft-JSS.license
in the installation directory.
Destination
The path of the installation directory for this Jaspersoft
/D Directory
Studio instance.
(Mandatory)
\JASPERSOFT\Installer\TIBCOJaspersoftStudioPro-x.x.x.final-windows-
installer-x86_64.exe /S /LICENSE=C:\Jaspersoft\My
Licenses\jasperserver.license /D=C:\SW\JASPERSOFT\JSS\xxx
The command-line installer looks for the license in the following order:
1. (Optional) If the command is run including the /LICENSE option, the license at the
specified path is copied into the installation folder with the filename Jaspersoft-
JSS.license.
2. Jaspersoft Studio looks in the installation folder for a license with the name
Jaspersoft-JSS.license.
3. If no license is present, the evaluation license is used.
If you are not prompted to update your workspace, you do not need to.
If you are updating from an old version of Jaspersoft Studio, you are prompted to choose a
new workspace when you open Jaspersoft Studio. When you choose a new workspace, a
new, empty workspace is created and set as the workspace for your Jaspersoft Studio
instance. This workspace is used for newer versions. Your previous workspace remains
unchanged and can still be used with older versions.
To update the reports and data from your earlier version of Jaspersoft Studio, you can
import some or all of your projects, server connections, data adapters, and project settings
into your new workspace.
Importing projects
1. (Optional) To import a version of the MyReports project, you must first delete the
existing MyReports folder from your current workspace. You can do this, for
example, if you have just upgraded and have created a new empty workspace. To
delete MyReports in your current workspace, navigate to the workspace location in
your file system and delete or move the MyReports directory.
2. Select File > Import ...
3. Select Existing Projects into Workspace from the General category.
4. Browse to the workspace that you want, click OK, and then click Next.
The Import dialog opens.
5. To work on a copy without modifying the original, select Copy projects into
workspace.
6. Click Finish.
The projects you selected are imported into your current workspace.
Your workspace contains server connections, global data adapters, and your Jaspersoft
Studio preferences in addition to your projects. You must import each type separately.
4. Choose the data adapters that you want. You do not need to import the built-in
adapters (One Empty Record and Sample DB).
5. Click Next.
With JasperReports 3.1, the JRXML syntax moved from a DTD-based definition to an XML-
based schema. The XML source declaration syntax now references a schema file, rather
than a DTD. Based on what we said previously, this is not a problem since JasperReports
assures backwards compatibility. However, many people are used to design reports with
early versions of iReport then generating the reports by compiling JRXML in JasperReports.
This was always a risky operation, but it was still valid because the user was not using a
new tag in the XML. With the move to an XML schema, the JRXML output of iReport 3.1.1
and newer can only be compiled with a JasperReports 3.1.0 or later. All versions of
Jaspersoft Studio produce output that is only compatible with later versions of
JasperReports Library.
For information on exporting or compiling a report to an earlier version of JasperReports
Library, see Setting Compatibility with Earlier Versions of JasperReports Library.
2. Unpack the downloaded package to your local directory using a tool such as 7-zip,
or the following command:
3. Edit the Jaspersoft Studio Professional.ini file appending the following two Java
properties (replace with the proper WebView file location):
-Dorg.eclipse.swt.browser.DefaultType=edge
-Dorg.eclipse.swt.browser.EdgeDir=C:\\dev\\webview
If the Edge browser configuration is missing, the following warning is displayed in the
bottom toolbar of the JRXML editor.
Edge browser engine is not setup. HTML and JRIO Preview will not work fine.
You can view various options available on the Member Login dialog, including:
l Forgot Password: Resets your password.
l Join Now: Opens the Join the Jaspersoft Community page. You can create an
account and join the community by filling the form.
l End User License Agreement: Opens the End User License Agreement (EULA)
document.
l Quit Jaspersoft Studio: Quits Jaspersoft Studio.
l Join the Community: Opens the Join the Jaspersoft Community page. You can
create an account and join the community by filling the form.
l Log in: Logs in to Jaspersoft Studio.
Jaspersoft Studio starts only when the credentials are valid and login is successful.
Before you log into Jaspersoft Studio, you must agree to the End User License
Agreement.
To change the VM
1. Navigate to General > Capabilities page. Additional pages are displayed.
2. View the Java > Installed JREs page.
3. Navigate to the Execution Environments page.
As Jaspersoft Studio is run using a JRE, an error is displayed and the page is not
opened.
Hence, for proper Java development you must use a Java Development Kit (JDK). To
start the application, use a required version of JDK. As far as possible, the JDK
version must be in sync with the JRE bundled.
For example, for Jaspersoft Studio Professional 8.2.0 that contains Adoptium
Temurin OpenJDK 11.0.18, download the latest available JDK 11 LTS from the
Adoptium website: https://adoptium.net/download/
After selecting the proper version (that is Windows x64), you can compress the files
to a directory of your choice of the package (.zip or .tar.gz).
4. Edit the .ini file to modify the configuration for the -vm flag.
For example, for Windows, change
-vm
features/jre.win32.win32.x86_64.feature_11.0.18/adoptopenjdk_jre/bin
to:
-vm
C:/jdk-11.0.21+9/bin
2. Select the Coffee template and click Next. The New Report Wizard shows the Report
file page.
3. Navigate to the folder to which you want the save report and name the report. To
create a folder, see Creating a Project Folder.
4. Click Next.
The New Report Wizard displays the Data Source page. This is where you choose the
data that fills the report. The dropdown menu shows the pre-installed data adapters
as well any data adapters you have added. The following adapters are pre-installed:
• One Empty Record - Empty rows: Data adapter that lets you create a report
without data. You might use this option to define the layout of a report and
connect it to a data source later.
• Sample DB - Database JDBC Connection: Data adapter that connects to an SQL
database provided with the Jaspersoft Studio installation. If you are getting your
data from a JDBC database, you must also supply an SQL query.
You can create a data adapter separately or click New... to create a data adapter
directly from this dialog. Adapters can be created globally (embedded in the workspace)
or local to a specific project. Using a local adapter makes it easier to deploy the report
to JasperReports Server. See Creating and Editing Data Adapters for more information.
5. Choose Sample DB - Database JDBC Connection. With a JDBC connection, the Data
Source dialog shows the database schema on the left and your query on the right.
6. Enter the query SELECT * FROM ORDERS on the right. Note that you can view your
query in three different ways: as text, as an outline, or as a diagram.
7. Click Next. The Fields window is displayed. The Dataset list shows all the discovered
fields.
8. Select the following fields and click the right arrow to add them to your report.
• ORDERID
• SHIPNAME
• SHIPADDRESS
• SHIPCITY
• SHIPREGION
9. Click Next. The Grouping window is displayed. You do not want any grouping for this
report.
10. Click Next and Finish.
Jaspersoft Studio now builds the report layout with the selected fields included as
shown.
You cannot have more than one Ad Hoc component in an Ad Hoc report template
JRXML.
3. Add more fields by clicking the Read Fields button. All the fields discovered are
added as new fields in the report.
You can also change your query in the same dialog. If a new query discovers fewer fields
than used in the existing report, the fields not included the new query are removed
from your report.
6. To add a field to your report, click the field and drag it into the Design.
When the field object is dragged inside the detail band, Jaspersoft Studio creates a
text field element and sets the text field expression for that element.
Deleting Fields
To delete a field from a report, right-click the field in the Design and select Delete.
Previewing a Report
Click the Preview tab at the bottom of the report. The preview compiles the report in the
background with data retrieved by the query through your JDBC connection. The Detail
band repeats for every row in the query results, creating a simple table report.
Each subreport is saved in a separate report file. Reflecting the standard Eclipse design,
saving or previewing a report that contains subreports does not update the subreports.
When you edit a subreport, you must first build the subreport, and then save the file for
the subreport changes to be visible when you preview the report that contains it.
• To build a subreport explicitly, use the Build All button on the toolbar, or type
Ctrl-B. Alternatively, select Project > Build Automatically to have Jaspersoft
Studio do it for you.
• To save a subreport, use File > Save or File > Save As.
1. Choose File > New > Project. The Select a wizard dialog is displayed.
2. Enter Jasper in the Wizards bar to filter actions to those related to Jaspersoft Studio.
3. Select JasperReports Project. Click Next. The New JasperReports Project wizard
appears.
4. Enter a name for your project and click Finish. The Project Explorer displays your
project.
Eclipse Interface
In Eclipse terminology, the initial layout of the Jaspersoft Studio interface is called a
perspective. The default Jaspersoft Studio perspective contains an editor area and views.
Some views appear by themselves, while others are stacked together in tabbed notebooks.
You can open and close views and drag them to different positions in the Eclipse
workbench.
• To open a window you have closed, select Window > Open View from the menu.
Select the window that you want to open from the dropdown list.
• To reset the interface to the default perspective, select Window > Reset Perspective.
• To save a perspective, select Window > Save Perspective As and enter a name for
your perspective.
Understanding Bands
The Design tab is divided into nine predefined bands to which new groups are added. In
addition, Jaspersoft Studio manages a heading band (group header) and a recapitulation
band (group footer) for every group.
A band is as wide as the page width (right and left margins excluded). However, its height,
even if it is established during the design phase, can vary during print creation according to
the contained elements; it can “lengthen” toward the bottom of a page in an arbitrary way.
This typically occurs when bands contain subreports or text fields that have to adapt to the
content vertically. Generally, the height specified by the user should be considered “the
minimal height” of the band. Not all bands can be stretched dynamically according to
content. In particular the column footer, page footer, and last page footer bands are
statically sized.
The sum of all band heights (except for the background) must be less than or equal to the
page height minus the top and bottom margins.
Band Types
The following table contains brief descriptions of the available bands:
Title The title band is the first visible band. It is created only once and can be
printed on a separate page. It is not possible during design to exceed the
report page height (top and bottom margins are included). If the title is
printed on a separate page, this band height is not included in the
calculation of the total sum of all band heights.
Page Header The page header band allows you to define a page header. The height
specified during the design phase usually does not change during the
creation process, except for the insertion of vertically resizable components
such as text fields. The page header appears on all printed pages in the
position defined during the design phase. Title and summary bands do not
include the page header when printed on a separate page.
Column The column header band is printed at the beginning of each detail column.
Header Usually labels containing the column names of a tabular report are inserted
in this band.
Group Header A report can contains zero or more group bands that permit the collection of
detailed records in real groups. A group header is always accompanied by a
group footer (both can be independently visible or not). Different properties
are associated with a group. They determine its behavior from the graphic
point of view. It is possible to force a group header on a new page or in a
new column and to print this band on all pages if the bands below it
overflow the single page (as a page header, but at group level). It is possible
to fix a minimum height required to print a group header: if it exceeds this
height, the group header band is printed on a new page (please note that a
value too large for this property can create an infinite loop during printing).
Group Footer The group footer band completes a group. Usually it contains fields to view
subtotals or separation graphic elements, such as lines.
Column The column footer band appears on at the end of every column. Its
Footer dimensions are not resizable at run time (not even if it contains resizable
elements such as subreports or text fields with a variable number of text
lines).
Page Footer The page footer band appears on every page where there is a page header.
Like the column footer, it is not resizable at run time.
Last Page If you want to make the last page footer different from the other footers, it is
Footer possible to use the special last page footer band. If the band height is 0, it is
completely ignored, and the layout established for the common page is used
for the last page.
Summary The summary band allows you to insert fields containing total calculations,
means, or any other information you want to include at the end of the
report.
Background The background enables you to create watermarks and similar effects, such
as a frame around the whole page. It can have a maximum height equal to
the page height.
Letter 612x792
Note 540x720
Legal 612x1008
A0 2380x3368
A1 1684x3368
A2 1190x1684
A3 842x1190
A4 595x842
A5 421x595
A6 297x421
A7 210x297
A8 148x210
A9 105X148
A10 74X105
B0 2836x4008
B1 2004x2836
B2 1418x2004
B3 1002x1418
B4 709x1002
B5 501x709
ARCH_E 2592x3456
ARCH_D 1728x2593
ARCH_C 1296x1728
ARCH_B 864x1296
ARCH_A 648x864
FLSA 612x936
FLSE 612x936
HALFLETTER 396x612
11X17 792x1224
LEDGER 1224x792
By modifying width and height, it is possible to create a report of whatever size you like.
Although Jaspersoft enables you to create pixel-perfect reports, the page orientation
options, Landscape or Portrait, are there because they are used by certain report exporters.
The page margin dimensions are set by means of the four options on the Page Margin tab.
Columns
Pages, one or more of which make up a report, present bands that are independent from
the data (such as the title or the page footers) and other bands that are printed only if
there are one or more data records to print (such as the group headers and the detail
band). These last sections can be divided into vertical columns to take advantage of the
available space on the page. A column does not concern the record field, but it does
concern the detail band. This means that if you have a record with 10 fields and you desire
a table view, 10 columns are not needed. However, the element must be placed correctly
to have a table effect. Ten columns are returned when long record lists (that are
horizontally very narrow) are printed.
Next, let us set up columns in a report as an example. Create a report from File > New >
Jasper Report. Choose the BlankA4 template and name it ColumnExample. Use Sample DB
- Database JDBC Connection for the data adapter, with the following SQL query: select *
from orders. Fields from the database are discovered. Double-click SHIPNAME to add it to
the report field and click Next twice. Finally, click Finish.
From the outline view, drag the SHIPNAME field in the report in the detail band, resize the
detail band, and remove the unused bands. Go to the Preview tab to see the compiled
report.
By default the number of columns is 1, and its width is equal to the entire page, except the
margins. The space between columns is zero by default. Most of the page is unused. If
multiple columns are used, this report would look better. On the Page Format dialog set
the number of columns to two and compile the report to see the changes.
Jaspersoft Studio automatically calculates the maximum column width according to the
margins and the page width. If you want to increase the space between the columns,
increase the value of the Space field.
The restricted area is used to mark every column after the first, to show that all the
elements should be placed in the first column. The other columns are replicated
automatically during compilation. If you want you can also put elements in the other
columns, but in most cases you need only the first. It is not recommended that you use
parts of the report as margins and columns after the first, if they have to be considered as
though they were a continuation of the first.
Multiple columns are commonly used for print-outs of very long lists (for example, a phone
directory). It is important to remember that when you have more than one column, the
width of the detail band and of linked bands is reduced to the width of the columns.
The sum of the margins, column widths, and space between columns has to be less than or
equal to the page width. If this condition is not met, the compilation results in an error.
Advanced Options
From the Properties view of the report, there are many other options for the report
configuration. Select the report root node from the outline view, and in the Properties view
you see:
• Report Name: It is a logical name, independent from the source file's name, and is
used only by the JasperReports library (for example, to name the produced Java file
when a report is compiled).
• Title on a new page: This option specifies that the title band is to be printed on a
new page, which forces a page break at the end of the title band. In the first page
only, the title band is printed. However, this page is still included in the total page
count.
• Summary on a new page: This option is similar to Title on a new page except that
the summary band is printed as the last page. If you need to print this band on a
new page, the new page only contains the summary band.
• Summary with page header and footer: This option specifies if the summary band is
to be accompanied by the page header and the page footer.
• Float Column Footer: This option forces the printing of the column footer band
immediately after the last detail band (or group footer) rather than the end of the
column. This option is used, for example, when you want to create tables using the
report elements.
• When no data type: When an empty data is supplied as the print number (or the SQL
associated with the report returns no records), an empty file is created (or a stream
of zero bytes is returned). This default behavior can be modified by specifying what
to do in the case of absence of data. The possible values for this field are:
• No Pages: This is the default value. The final result is an empty buffer.
• – Displays a dropdown menu with options for data snapshots and for
restricting the list of data adapters:
• Cache Data in Memory: Creates a data snapshot in RAM.
• Save Data to File…: Saves the data snapshot to a file.
• Load Data from File…: Runs the report using the data in the specified data
snapshot.
• Filter Data Adapters by Report Language: Enables you to restrict the list of data
adapters to only those adapters that are compatible with a specified language,
for example, only those adapters that use SQL.
• Data adapter dropdown – Lists all available data adapters. Use Filter Data
Adapters by Report Language on the menu to restrict the list to adapters that
are compatible with a specified language.
• Run the report – Runs the report. Use the menu immediately to the right to
choose between a normal report and an interactive report. Interactive reports
only support the HTML format.
• Output format menu – Let you select the output format for the report.
• Pagination tools – Use the arrows to go to page through the report or to go to
the first or last page. You can also edit the page text to specify the number you
want (for example, Page 7 of 12) and press Enter.
• Display tools: Zoom in or out, specify a percent, or click the icon to zoom to fit
page width, zoom to fit page, or zoom to actual size.
• Export a sample image – Saves a PNG file of the current page of the report in
a location you specify.
• Export report – Saves the report to a file in the format that you specify from
the dropdown list.
• Show parameters – Expands the parameters panel.
• Parameters panel. Automatically displayed for a report that has parameters that
have been specified for prompting. Otherwise it is hidden. You can display or hide
the parameters pane using the expand/collapse arrows to the right of the panel or
show it by clicking on the Preview menu. Use the following icons to choose what
is displayed in this panel:
• Input parameters – Shows any input parameters that are set for prompting
and lets you manually enter values.
In some cases, bugs in the export format may result in issues in the final output. For
example, some versions of Microsoft Word incorrectly render borders on a table element
exported to DOCX (the left top and bottom borders are missing). You may be able to
find a workaround based on the output format. For example, for the Microsoft Word
bug, you might try the following:
1. In Jaspersoft Studio, create a style named Table_Padding, with 1-pixel left and
right padding.
2. Apply this style to each table element in the report.
Report Elements
The basic building block of a report is the element. An element is a graphical object, such
as a text string or a rectangle. In Jaspersoft Studio, the concept of line or paragraph does
not exist, as it does in word-processing programs. Everything is created by means of
elements, which can contain text, create tables, display images, and so on. This approach
follows the model used by the majority of report authoring tools.
Jaspersoft Studio relies on all the basic elements provided in the JasperReports library:
• Line
• Rectangle
• Ellipse
• Static text
• Text field (or simply field)
• Image
• Frame
• Subreport
• Crosstab
• Chart
• Break
Combining these elements, you can produce every kind of report. JasperReports also
allows developers to implement their own generic elements and custom components for
which they can add support in Jaspersoft Studio to create a proper plug-in.
This chapter contains the following sections:
• Common Element Properties
• Inserting, Selecting, and Positioning Elements
• Formatting Elements
• Working with Advanced Properties
• Graphic Elements
• Text Elements
• Frames
• Working with Spreadsheet Layout
• Inserting Page and Column Breaks
• Working with Composite Elements
• Anchors, Bookmarks, and Hyperlinks
• Advanced Elements and Custom Components
• Custom Visualization Component
The Palette
Elements appear in the palette, located by default in the top right of the UI.
Element Properties
Element properties are divided into categories, visible via tabs in the Properties view. The
attributes available depend on the element type.
• The Appearance tab allows you to set the location, size, color, and text style of the
element.
• The Borders tab allows you to set the padding and border style, color, and width of
the element.
• An element tab allows you to set evaluation time along with properties specific to
the element type. For example:
• The Static Text tab allows you to define unchangeable text for a field, and
control its appearance.
• The Text Field tab allows you to format and position a text field element.
• The Image tab allows you to set image alignment, fill, and scale properties.
Some elements have more than one element-specific tab. For example, the Chart
component has the Chart and Chart Plot tabs, and the Map component has the Map,
Authentication, Markers, and Paths tabs.
• The Inheritance tab allows you to view any attributes inherited from another level,
and override those attributes when possible.
• The Hyperlink tab, available for image, text field, and chart elements, allows you to
define a hyperlink in an element.
• The Advanced tab displays detailed information about the element.
Frequently, the value of an attribute is undefined, and it has a common default value. This
means that the element does not have a specific behavior defined, but gets a behavior
from somewhere else. For example, the default value of the attribute "background color" is
undefined in most of the cases, but when a non-transparent element is added to a report
in the design tab, you can see that it has a white background. The value of the background
color attribute is inherited from a lower level.
Inserting Elements
When you insert an element, you can let Jaspersoft Studio autosize it, or you can size it as
you insert it. Setting the size of an element when you insert it is useful for tabular elements
such as tables and crosstabs.
• Click the element in the palette. The cursor changes to show that an element is
selected. Click and drag in the report editing area to size and place the element. If
you insert a crosstab or table using click and drag, the columns fill the whole
crosstab or table.
Selecting Elements
• Click to select an element in the report editing area.
• Drag to adjust the element's position or change its size by selecting it and dragging
a corner of the selection frame.
• To select several elements at the same time, drag the cursor in a rectangle around
them. When two or more elements are selected, only their common properties are
displayed in the Properties view. If the values of the properties are different, the
value fields are blank (usually the field is shown empty). To edit properties unique to
one element, select only that element.
• Shift-click to select the parent of the current object. For example, shift-click an
element contained directly in a band to select the band.
Positioning Elements
Jaspersoft Studio offers a number of ways to place the elements in your report with
precision.
Using Bands
The top and left values that define the element’s position are always relative to the parent
container (a band or frame).
If you want to move an element from one band to another or to a frame, drag the element
node from the Outline view to the new band (or frame) node.
In the report editing area, you can drag an element from one band to another band, but
the element’s parent band does not change. In general, an element must stay in its band,
but there are exceptions to this rule. For example, you can move an element anywhere in
the report without changing or updating the parent band.
Guides
When dragging or resizing an element, Jaspersoft Studio suggests places to align it based
on the elements currently in the Design tab, the band bounds, and any guides. When the
element you are moving or resizing is in line with another element in the report, a
guideline appears, allowing you to align the elements. To force elements to align with
guidelines, select View > Snap to Guides from the main menu.
You can drag and change the position of a guideline at any time with no effect on the
element’s position.
To remove a guideline, drag it to the upper-left corner of the report editing area.
Container Layouts
A container layout is a design-time tool that adjusts the size and the position of elements
when they are added to or removed from a container. The concept of layout is specific to
Jaspersoft Studio and works only at design time. Layouts do not make a report stretchable
or resizable. At run-time, depending on the design, JasperReports Library may still let
elements overlap or change their position relative to other elements.
Row Relative (default) or The number of the row from which this element starts.
Number an integer between 0 is the first row. When set to Relative, increments the
0 and 1000 last evaluated row by 1.
com.jaspersoft.layout.grid.y
Column Relative (default) or The number of the column from which this element
Number an integer between starts. 0 is the first column. When set to Relative,
0 and 250 increments the last evaluated column by 1.
com.jaspersoft.layout.grid.x
Row Span Integer between 0 Number of rows that the element spans.
and 1000; default =
com.jaspersoft.layout.grid.rowspan
1
Fixed Size Boolean; default = Set to true to size the element manually. Set to false to
false. have the element size automatically using the element's
settings
com.jaspersoft.layout.grid.fixed
Row Weight Number; default = 1 Number that specifies how much space the element's
row takes relative to other rows. Not available when
Fixed Size is True.
com.jaspersoft.layout.grid.weight.x
Column Number; default = 1 Number that specifies how much space the element's
Weight column takes relative to other rows. Not available when
Fixed Size is True.
com.jaspersoft.layout.grid.weight.y
a graphics editor to rotate the image 90°. Note that this rotates the image in any
report where it is used.
2. Create a report using the BlankA4 template and the Empty data source. Do not reuse
the report created in the previous step.
3. Add your vertical image to the title band of your report.
4. Add a chart to the title band of your report, to the right of your image.
5. Resize the title band to fit a chart.
6. Right-click in a blank space in the Title band and select Arrange in Container > Grid
Layout, or select the Title band and select Grid Layout in the Properties view.
The two elements are arranged to fill the band equally.
7. Resize the elements so that the chart takes up most of the space. To do this, select
the chart. In the Properties view, in the Layout section of the Appearance tab, set
Column Weight to 5.
The elements adjust so that the chart width is five times the image width.
8. Now add a static text element to the far right of the title band.
The static text is added at the end of the first row.
9. Position the static text. To do this, select the static text. In the Properties view, in
the Layout section of the Appearance tab, set the following:
• Set Row Number to 1 to move the element to the second row. You could also
have added the static text directly below the first row, but setting the row
explicitly gives you more control.
• Set Column Span to 2 to have the element span both columns. You could instead
set the Column Number to 2 to move the static text under the chart.
10. Set the relative heights of the rows. To do this, select the chart and set Row Weight
to 10 in the Layout section of the Appearance tab of the Properties view. You could
actually do this by changing the settings on any of the three elements, but in this
case, the chart is the main element and you want other elements to adjust to it.
Formatting Elements
Formatting tools help organize the elements in the report. Right-click the element that you
want to work on and select a tool from the context menu.
The tools in the context menu are specific to the selected items. The following tables
explain the tools.
Formatting Tools
Order Tools
Align to Left Aligns the left side to that of the primary Yes
element.
Align to Top Aligns the top side (or the upper part) to Yes
that of the primary element.
Align to Aligns the bottom side (or the lower part) Yes
Bottom to that of the primary element.
element.
Miscellaneous Tools
By default, the Properties dialog displays a form with available properties grouped by
category. The available categories depend on the element type. For example, reports allow
you to set a number of JDBC and timezone properties. Each property has a widget that
allows you to set the property. Deprecated properties are displayed with strikethrough.
The Properties dialog supports the following actions:
• Hover to view the description of a property.
• Right-click on an entry box to set the property to Null or reset it to the default value
(when available).
• Click to switch to a summary table view. Using this view, you can manage
multiple properties at the same time. For example, you can select and copy multiple
properties, and then paste them into another element. To return to form view, click
.
• Click to show only properties that have already been set at element level.
• Enter a string in the Search property entry bar to search for a property by name.
• Some properties include variables in the property names, shown with curly brackets
{}. To use these properties, replace the entire value, including the brackets, with the
name you want to use.
You can also use styles to format some types of elements. Styles can be applied to
multiple elements, but are more restrictive. Properties must be individually applied to
each element.
Create a report
To create the report for the chart
1. Create a new, blank report using the Sample DB data adapter and the query: select *
from PRODUCT.
2. Click Next.
3. Click to select all fields, then click Finish.
4. Delete all bands except for Column Header and Details.
5. In the Outline view, expand the Fields node, select all fields, and drag them to the
detail band.
The fields are added to the detail band and headers are automatically added to the
Column Header band.
6. Drag to select the fields in the detail band, right-click, and select Align in Container >
Align to Top Margin. Then double-click the detail band to resize it to fit the fields.
<property name="net.sf.jasperreports.export.csv.column.names.1"
value="id,name,department"/>
<property name="net.sf.jasperreports.export.csv.column.names.2"
value="address"/>
For this example, the result is the following columns, in this order: id, name, department,
address.
The {arbitrary_name} suffix can be any name you choose. The following code gives the
same result at runtime:
<property name="net.sf.jasperreports.export.csv.column.names.first.column.set"
value="id,name,department"/>
You can use multiple properties with the same prefix for dynamic properties. For example,
you could generate column names from two different parameters:
<propertyExpression
name="net.sf.jasperreports.export.csv.column.names.db.columns">
<![CDATA[$P{columns1}]]>
</propertyExpression>
and
<propertyExpression
name="net.sf.jasperreports.export.csv.column.names.additional.columns">
<![CDATA[$P{other_columns}]]>
</propertyExpression>
Graphic Elements
Graphic elements like lines and shapes are used to make reports more attractive and
readable. You can also add these by dragging them from the palette to the report editing
area.
Line
In Jaspersoft Studio, a line is defined by a rectangle for which the line represents the
diagonal. By default, the foreground color is used as the default color and a 1-pixel-width
line is used as the line style.
You can customize the look, style, and direction of the line in the element’s Properties
view.
Images
An image is the most complex of the graphic elements. You can insert raster images (such
as GIF, PNG and JPEG images) in the report, but you can also use an image element as a
canvas object to render, for example, a Swing component, or to use some custom
rendering code.
Dragging an image element from the Palette into the report editing area opens the Create
new image element dialog. This is the most convenient way to specify an image to use in
the report. Jaspersoft Studio does not save or store the selected image anywhere, it just
uses the file location, translating the absolute path of the selected image into an
expression to locate the file when the report is run. The expression is then set as the value
for the Image Expression property.
You can add an image by explicitly defining the full absolute path of the image file in your
expression. This is an easy way to add an image to the report, but, overall, it has a
significant impact on the report’s portability, since the file may not be found on another
machine (for instance, after deploying the report on a web server or running the report on
a different computer).
Text Elements
Two elements are specifically designed to display text in a report: static text and text field.
Static text is used for creating labels or printing static text set at design time that is not
meant to change when the report is generated. That said, in some cases you still use a text
field to print labels too, since the nature of the static text elements prevents the ability to
display text dynamically translated in different languages when the report is run with a
specific locale and it is configured to use a resource bundle using the JasperReports
internationalization capabilities.
A text field is similar to a static text string, but the content (the text in the field) is provided
using an expression (which can be a simple static text string itself). That expression can
return several kinds of value types, allowing the user to specify a pattern to format that
value. Since the text specified dynamically can have an arbitrary length, a text field
provides several options about how the text must be treated regarding alignment, position,
line breaks and so on. Optionally, the text field is able to grow vertically to fit the content
when required.
By default both text elements are transparent with no border, with a black text color. The
most used text properties can be modified using the text tool bar displayed when a text
element is selected. Text element properties can also be modified using the Properties
view.
Text fields support hyperlinks as well. See Creating a Hyperlink for more information.
Static Text
The static text element is used to show non-dynamic text in reports. The only parameter
that distinguishes this element from a generic text element is the Text property, where the
text to view is specified: it is a normal text, not an expression, and so it is not necessary to
enclose it in double quotes to respect the conventions of Java, Groovy, or JavaScript
syntax.
Text Fields
A text field allows you to print an arbitrary section of text (or a number or a date) created
using an expression. The simplest case of use of a text field is to print a constant string
(java.lang.String) created using an expression like this:
"This is a text"
A text field that prints a constant value like the one returned by this expression can be
easily replaced by a static field. Actually, the use of an expression to define the content of a
text field provides a high level of control on the generated text (even if it is just constant
text). A common case is when labels have to be internationalized and loaded from a
resource bundle. In general, an expression can contain fields, variables, and parameters, so
you can print in a text field the value of a field and set the format of the value to present.
For this purpose, a text field expression does not have to necessarily return a string (that is
a text value): the text field expression class name property specifies what type of value is
returned by the expression. It can be one of the following:
java.sql.Timestamp java.io.InputStream
An incorrect expression class is frequently the cause of compilation errors. If you use
Groovy or JavaScript, you can choose String as the expression type without causing an
error when the report is compiled. The side effect is that without specifying the right
expression class, the pattern (if set) is not applied to the value.
Let us see what properties can be set for a text field:
Blank when null If set to true, this option avoids printing the text field content if the
expression result is a null object that produces the text “null” when
converted in a string.
Evaluation time Determines in which phase of the report creation the Text field
Expression has to be elaborated.
Evaluation group The group to which the evaluation time is referred if it is set to Group.
Text Adjust This option allows the text field to adapt vertically to the content, if the
element is not sufficient to contain all the text lines. Select the required
option from the following:
• CutText: The text is cut if it does not fit the text field element
size.
• StretchHeight: The text field element is stretched in height to
accommodate the entire content.
• ScaleFont: The font size of the text is scaled down so that the
entire content fits the text field element size.
Pattern The pattern property allows you to set a mask to format a value. It is
used only when the expression class is congruent with the pattern to
apply, meaning you need a numeric value to apply a mask to format a
number, or a date to use a date pattern.
Frames
A frame is an element that can contain other elements and optionally draw a border
around them. Since a frame is a container of other elements, in Outline view the frame is
represented as a node containing other elements.
A frame can contain other frames, and so on, recursively. To add an element to a frame,
drag the new element from the palette inside the frame. Alternatively you can use Outline
view and drag elements from a band into the frame. The position of an element is always
relative to the container position. If the container is a band, the element position is relative
to the top of the band and to the left margin. If the container (or element parent) is a
frame, the element coordinates are relative to the top-left corner of the frame. Since an
element dragged from a container to another does not change its top/left properties, when
moving an element from a container to another its position is recalculated based on the
new container location.
The advantages of using a frame to draw a border around a set of elements, with respect
to using a simple rectangle element, are:
• When you move a frame, all the elements contained in the frame move.
• While using a rectangle to overlap some elements, the elements inside the rectangle
are not treated as if they overlap (with respect to the frame), so you do not have
problems when exporting in HTML (which does not support overlapped elements).
• Finally, the frame automatically stretches according to its content, and the element
position type property of its elements refer to the frame itself, not to the band,
making the design a bit easier to manage.
Now suppose that your map is configured with an expression that only displays the map
some of the time. If you size the frame to be bigger than the map, the report inserts white
space when the map is not displayed. Instead, you can size the frame to be smaller than
the map:
Now, the frame expands as necessary to include any non-null content, but no additional
white space is added if the map is not present.
Be careful when creating and modifying reports that use frames that are smaller than
their contents. The user interface does not always make it clear which elements are
contained in a frame. For example, it is possible to add a field to a frame and then
resize the frame so that the frame no longer overlaps the element. To see which
elements are in a frame, select the frame and expand its node in outline view. If you
have trouble moving an element inside or outside a frame, move it in outline view.
2. Right-click on any field and select Arrange in Container > Spreadsheet Layout from
the context menu again.
Again, all elements in the band display the COL annotation. Spreadsheet layout is
now enabled.
Remove a Column
1. Select the EMPLOYEEID heading and press the Delete key.
2. Click Delete Entire Column when prompted.
All elements in the same column are deleted. In this case, the header and the field
are deleted. The other elements move to the left as necessary to close the gap.
There is no option to cancel a delete. However, you can undo the action immediately.
Resize Columns
The real advantage to spreadsheet layout is that it lets you quickly resize columns and
keep the elements aligned across bands.
1. Select the ORDERID header or text field.
2. Click the right side and move the handles to the left to reduce the size of the
OrderID column. All elements in the column are resized together.
3. Select the SHIPADDRESS header or text field. Use the handles on the right to expand
the column. Again, the columns are resized together.
Remove a Header
1. Select the Region header and press Delete.
2. When prompted, select Delete Selected. The item is removed, but the column layout
is preserved.
When you delete an element from the detail band, the associated elements in other
bands are no longer part of the column layout. When you delete an element from a
band other than the detail band, the column layout is not removed.
If you preview the report, it should look something like the following image.
• You can add at most one element in a band to each column. However, you can add
a frame to a column and then add elements inside the frame.
• The element in the detail band is the element that drives the column. Select this
element to specify the column you want to add another element to.
• You can only add a variable to a column that contains its related field.
• If you resize the band, the column elements resize vertically to fit.
a. Go to File > New > Jasper Report or click on the main toolbar.
b. In the New Report Wizard, select Blank A4 in the Report Templates window and
click Next.
c. Select a name and location for your file (for example, Composite Element
Sample Report in MyReports) and click Next.
d. Choose One Empty Record in the Data Source window and click Finish.
2. Place the elements that you want in the Title band and format and position them.
For example, to create a footer that includes your company name and the page
number:
a. Drag the Static Text element to the Title band in your report and type My
Company. Then align the company name to the left by right-clicking the Static
Text element and selecting Align in Container > Align to Left Margin.
b. Drag the Page Number element to the Title band in your report. Align the Page
Number to the right by right-clicking the Page Number element and selecting
Align in Container > Align to Right Margin. Then, with the Page Number element
selected, go to the Text Field tab in the Properties view and click to align the
text right.
c. Select both elements, right-click, and choose Align Components > Align Top.
3. Select all the elements that you want in your composite.
4. (Optional) To have your elements move together, right-click, and select Enclose into
Frame from the context menu.
5. Make sure that all elements are still selected.
You cannot delete the composite elements that are included Jaspersoft Studio.
3. Select the elements that you want to export in the Export Composite Elements
dialog.
4. Click Finish.
5. When prompted, navigate to the location where you want to save the export file,
and click OK.
The selected composite elements are saved as a .zip file in the location that you
chose.
5. If there are additional elements in the file, click Next and configure the next element
as in the previous step.
6. When you have configured all your imported elements, click Finish.
The composite elements are placed in the palette with the settings you configured.
This section describes hyperlinks for images, text fields, and charts. Hyperlinks for
HTML5 charts are defined differently, as described in Creating Hyperlinks in HTML5
Charts.
To set anchor, bookmark, or hyperlink properties, select an image, text field, or chart
element and go to the Hyperlink tab in the Properties view.
• Anchor Name Expression – Expression for the name of the anchor. This name can be
referenced by other hyperlinks. Click the button to open the Expression Editor,
where you can write or build the expression.
• Bookmark Level – Bookmark level when the report is exported to PDF. If you plan to
export your report as a PDF, set a bookmark level to populate the bookmark tree,
making the final document navigation much easier. To make an anchor available as
a bookmark, simply choose a bookmark level higher than one. Defining different
levels creates nested bookmarks.
Bookmarks can also be displayed in JasperReports Server when the report is
displayed in the interactive viewer. To display bookmarks in the server, set the
following property:
<property name="net.sf.jasperreports.print.create.bookmarks" value="true"/>
This property can be set on the report level or globally in the JasperReports Server
WEB-INF\classes\jasperreports.properties file.
The same table of contents is also available in the JasperPrint object, and can be
explored by calling the method:
List<PrintBookmark> getBookmarks()
Hyperlinks
Hyperlinks let you link a location in a report to another destination. The most important
property of a hyperlink is its type, which determines the format of the target. Jaspersoft
Studio supports the following types of hyperlink: The exact properties of a hyperlink
depend on the hyperlink type. The following properties may appear for a hyperlink:
• Link Target – Specifies where to open the link target. The Link Target is similar to
the target attribute of an HTML link. The dropdown box shows the following options:
Self, Blank, Top, Parent. You can also specify a target name, which actually makes
sense only when the hyperlink is used in a web environment.
• Link Type – The following link types are supported in Jaspersoft Studio: Reference,
LocalAnchor, LocalPage, RemoteAnchor, RemotePage, ReportExecution, and dashlet.
You can also define your own custom hyperlink types.
• Target Expressions – Expressions that determine the location of the link target. May
include:
Linking to a URL
To link to a URL, http://www.jaspersoft.com/, select Reference from the Link Type
dropdown in the Properties view. Hyperlinks of type Reference are rendered in all output
formats that support web links, including Microsoft Excel and Word.
When working with a hyperlink of type Reference, you can add parameters via the
Hyperlink Reference Expression. For example, the following expression uses the values of
the city and country fields to dynamically build a URL:
"http://www.someurl.com/search?city=" + $F{city} + "&country= " + $F{country}
Linking to a Report
Several hyperlink types link to an existing report. These types are primarily supported in
PDF and HTML formats:
• LocalAnchor – Links between two locations into the same document. It can be used,
for example, to link the titles of a summary to the chapters to which they refer. To
define the local anchor, it is necessary to specify a hyperlink anchor expression,
which produces a valid anchor name, for example, "title".
• LocalPage – Point to a specific page in the current report. In this case, it is necessary
to specify the page number you are pointing to by means of a hyperlink page
expression, for example Integer.valueOf(2). The expression must return an Integer
object.
• RemoteAnchor – Points to an anchor that resides in an external document. In this
case, the location of the external file must be specified in the Hyperlink Reference
Expression field, and the name of the anchor must be specified in the Hyperlink
Anchor Expression field.
• RemotePage – Points to a particular page of an external document. In this case, the
location of the external file must be specified in the Hyperlink Reference Expression
field, and the page number must specified in the Hyperlink Reference Expression.
Similar to links of type Reference, you can specify additional parameters for these
hyperlink types by appending them to the expression string.
Figure 41: Dragging a report from the server into the Report Design
Hyperlink Types
Jaspersoft Studio provides several types of built-in hypertext links: Reference, LocalAnchor,
LocalPage, RemoteAnchor, RemotePage, and dashlets.
The following table describes the hyperlink types.
LocalAnchor To point to a local anchor means to create a link between two locations
into the same document. It can be used, for example, to link the titles of
a summary to the chapters to which they refer.
To get hierarchical data in the crosstab report hyperlink, you must configure it in
Jaspersoft Studio.
Creating a Hyperlink
Some types of datasets let you assign a hyperlink to the value represented in the chart. In
the report output, clicking the chart opens a web page or navigates to a different location
in the report.
The click-enabled area depends on the chart type. For example, in pie charts, the hyperlink
is linked to each slice of the pie; in bar charts, the click-enabled areas are the bars
themselves.
Image, text field, and chart elements can be used both as anchors into a document and as
hypertext links to external sources or local anchors.
To create a hyperlink
1. Click the Hyperlink tab in the Properties view.
2. In the Link Target dropdown, choose one of the following target types:
• Self: This is the default setting. It opens the link in the current window.
• Blank: Opens the target in a new window. Used for output formats such as HTML
and PDF.
• Top: Opens the target in the current window but outside the frames. Used for
output formats such as HTML and PDF.
• Parent: Opens the target in the parent window (if available). Used for output
formats such as HTML and PDF.
3. In the Link Type dropdown, choose whether the link type is None, Reference,
LocalAnchor, LocalPage, RemoteAnchor, RemotePage, or ReportExecution.
See Hyperlink Types for an explanation of the different choices.
4. Click the button next to Hyperlink Tool Expression to create a tooltip for your
hyperlink.
5. Save your report.
Please note that this component is only supported by the Jaspersoft Community
(community.jaspersoft.com). Jaspersoft Technical Support and Engineering do not
support it.
D3-enabled report
The custom visualization component is a powerful and flexible feature, suitable for
advanced users of JasperReports Library. Using the component requires advanced coding
skills in the following technologies:
• JavaScript
• CSS
• HTML/DHTML
• Optionally, any third-party library you want to expose in Jaspersoft Studio and
JasperReports Server.
Before creating reports that use your third-party library, you must configure various
applications to work together; you must:
1. Install Chrome or Chromium, which renders your JavaScript module's visual
component.
2. Configure Jaspersoft Studio and JasperReports Server to use Chrome/Chromium.
3. Create a JavaScript module that renders an SVG. This main module, as well as any
JavaScript it relies on, are optimized and combined into a single JavaScript file
(using a RequireJS build file (build.js). Jaspersoft Studio simplifies the optimization
process to generate the JavaScript implementation of the component. Place your
JavaScript files somewhere that you Jaspersoft Studio can find it, such as attaching
it to the report unit or placing it on the classpath.
Next, create and deploy reports that rely on your custom visualization component to
render SVG images. Drag the Custom Visualization component from the Elements palette
into the Design tab, and create a report-level property of type
com.jaspersoft.jasperreports.components.customvisualization.require.js; it must specify the
main JavaScript file for your custom visualization. The custom visualization component
appears as a rectangular area of your report. A single custom visualization component can
be used by any number of reports that require the same JavaScript functionality. When
exported to HTML format, these reports can be interactive (assuming that your module
attaches events to the DOM).
You can also create a custom component descriptor in JSON, which lets you add the
following to your component:
• A component UI – You can specify the property names and types and the data items
used by the component.
• A thumbnail image – Used when the component is presented in the component
choose, which appears when a component is dragged into the design view.
• Location of implementation files – You can specify the location of the JavaScript file
and CSS file that implement the component.
This component can help you use any number of JavaScript libraries, such as:
• D3.js
• Raphäel
• Highcharts
• JQuery
For more in-depth information, please see the articles on our Community wiki that
describe the custom visualization component.
Fields
In a report, there are three groups of objects that can store values:
• Fields
• Parameters
• Variables
Jaspersoft Studio uses these objects in data source queries. To use these objects in a
report, they must be declared with a discrete type that corresponds to a Java class, such
as String or Double. After they have been declared in a report design, the objects can be
modified or updated during the report generation process.
This chapter contains the following sections:
• Understanding Fields
• Registration of Fields from an SQL Query
• Registration of JavaBean Fields
• Fields and Text Fields
• Data Centric Exporters
Understanding Fields
A print is commonly created starting from a data source that provides a set of records
composed of a series of fields. This behavior is exactly like obtaining the results of an SQL
query.
Jaspersoft Studio displays the available fields as children of the Fields node in the
document outline view. To create a field, right-click the Fields node and select Create Field.
The new field is included as an undefined entry on the Properties tab. You can configure
the field properties by selecting it.
Select the Object tab to name your field, enter a description, and choose a class.
Select the Advanced tab to enter advanced properties for the field.
declare and configure large numbers of fields using the tools provided by Jaspersoft
Studio. Because the number of fields in a report can be quite large (possibly reaching the
hundreds), Jaspersoft Studio provides different tools for handling declaration fields
retrieved from particular types of data sources.
Inside each report expression (like the one used to set the content of a text field)
Jaspersoft Studio specifies a field object, using the following syntax:
$F{<field name>}
where <field name> must be replaced with the name of the field. When using a field
expression (for example, calling a method on it), keep in mind that it can have a value of
null, so you should check for that condition. An example of a Java expression that checks
for a null value is:
($F{myField} != null) ? $F{myField}.doSomething() : null
This method is generally valid for all the objects, not just fields. Using Groovy or JavaScript
this is rarely a problem, since those languages handle a null value exception in a more
transparent way, usually returning an empty string.
In some cases a field can be a complex object, like a JavaBean, not just a simple value like
a String or an Integer. A trick to convert a generic object to a String is to concatenate it to
an empty string this way:
$F{myfield}+ “”
All Java objects can be converted to a string. The result of this expression depends on the
individual object implementation (specifically, by the implementation of the toString()
method). If the object is null, the result returns the literal text string “null” as a value.
Jaspersoft Studio does not require a query to generate a report. It can obtain data from a
data source that is not defined by a query execution. JasperReports supports multiple
query languages including:
• JSON
• MongoDBQuery
• PLSQL
• SQL
• XLS
• XPath
If the selected data source is a JDBC connection, Jaspersoft Studio tests the access
connection to the data source as you define the query. This allows Jaspersoft Studio to
identify the fields using the query metadata in the result set. The design tool lists the
discovered fields in the bottom portion of the window. For each field, Jaspersoft Studio
determines the name and Java type specified by the JDBC driver.
If your query accesses tables containing large amounts of data, scanning the data source
for field names could take a while. In this case, you might consider disabling the
Automatically Retrieve Fields option to finish your query definition quickly. When you have
completed the query, click the Read Fields button to start the fields discovery scan.
All fields used in a query must have a unique name. Use alias field names in the query
for fields having the same name.
The field name scan may return a large number of field names if you are working with
complex tables. To reduce unnecessary complexity, we suggest that you review the list of
discovered names and remove fields you are not using in your report. When you click OK
all the fields in the list are included in the report design. Although you can remove them
later in the outline view, it is a good idea at this point in the design process to remove any
field names that you are not going to use.
attribute. Paths may be arbitrary and long, and Jaspersoft Studio can recursively parse
attribute trees within complex JavaBeans and to register very specific fields.
We have just discussed the two tools used most frequently to register fields, but we are not
done yet. There are many other tools that you can use to discover and register fields, for
instance, the HQL and XML node-mapping tools.
Tagging Headings
You can tag text fields or static text elements as headings. You can include a range of static
text elements and/or text fields in the same heading.
Setting the property globally inserts tags when you export a report to PDF directly from
Jaspersoft Studio. If you are publishing your reports to another environment, such as
JasperReports Server, you must enable this property in the jasperreports.properties file
in your environment. See the JasperReports Server Administrator Guide for more
information about enabling this property for JasperReports Server.
1. For a table, right-click in the table. For a report, right-click on the root node in the
outline view.
2. Select PDF 508 Tags > Autotag Table from the context menu.
3. Select one of the following options:
• Default – Inherits the property settings from a higher level. If the property has
been set explicitly at a higher level, the current setting is shown on the menu, for
example Default (Enabled).
• Enabled – Enables the property for this table or report. This setting overrides any
value set at a higher level.
• Disabled – Disables the property for this table or report. This setting overrides
any value set at a higher level.
When the net.sf.jasperreports.components.table.generate.pdf.tags is set at the table level,
the setting is displayed in the upper left-hand corner of the table in design view.
1. Tag the first element in your table: PDF 508 Tags > Table > Start.
2. Tag the start and end of each row:
a. Tag the first element in your row: PDF 508 Tags > Table Row > Start.
b. Tag the last element in your row: PDF 508 Tags > Table Row > End.
3. To make a row a header row, add header tags to the start and end:
a. Tag the first element in each header row: PDF 508 Tags > Table Header > Start.
b. Tag the last element in each header row: PDF 508 Tags > Table Header > End.
4. Tag each detail element in each row: PDF 508 Tags > Table Details > Full.
5. Tag the final element in your table: PDF 508 Tags > Table > End.
6. Select Is Tagged.
7. Enter a language code in the Tag Language field.
$F{salesamount} store.sale.amount
$F{salesyear} store.sale.year
$F{cust.name} store.cust.name
When exported to JSON, the data is structured with three distinct paths:
store
sale
amount
year
cust
name
[
{store:
[
{
sale:[{amount:"19000", year:2014}],
cust:[{name:"Acme"}],
}
]
}
]
Note that when you preview your report as JSON, the data is not formatted to be human
readable, as above. You may want to use one of the many JSON formatting tools to review
the output of your JSON tagged report, you can copy the JSON output from the Preview
tab.
It is important to define paths that create a structure that the application receiving the
data can interpret.
12. Review the structure of the data to ensure your application can interpret it.
13. If the data is not structured correctly, click Design and edit each field's JSON export
properties.
14. When you are satisfied with the data returned by Jaspersoft Studio, you can publish
your report to JasperReports Server and begin testing your own application's ability
to use the data passed by the server.
Parameters
Parameters are values usually passed to the report from the application that originally
requested it. They can be used for configuring report features at generation time (like the
value to use in an SQL query), or to supply additional data that is not provided by the data
source (like a custom report title, an application-specific path for images).
Report parameters have many functions in a report. They can be used in the "where"
condition of an SQL query, or to provide additional data to the report (like the value of a
title or a name of the user that runs the report).
A parameter is defined by a name and a Class, which is a Java class type. For example, a
parameter of type java.sql.Connection may be used to populate a subreport, while a simple
java.lang.Boolean parameter may be used to show or hide a section of the report.
This chapter contains the following sections:
• Working With Parameters
• Default Parameters
• Using Parameters in Queries
• Parameters Prompt
• Parameter Sets
Managing Parameters
You can manage parameters using the outline view or on the Parameters tab of the Dataset
and Query dialog.
• To add a parameter set, right-click the Parameters node and choose Create
Parameter Set.
• To change the order of parameters on the menu, select the parameter you want to
move and drag it up and down.
• Default Value Expression – Pre-defined value for the parameter. This value is used if
no value is provided for the parameter from the application that runs the report. The
type of value must match the type declared in the Class field.
You may legally define another parameter as the value of Default Value Expression,
but this method requires careful report design. Jaspersoft Studio parses parameters
in the same order in which they are declared, so a default value parameter must be
declared before the current parameter.
• Evaluation Time – Use this to specify the evaluation time for the parameter:
• Early – Evaluate the parameter default value expression before the data adapter.
• Late – Evaluate the parameter default value expression after the data adapter.
Selecting Properties, and clicking … brings up the Properties dialog. For example, if you
have a web services type data adapter, you see the following properties.
Default Parameters
JasperReports provides some built-in parameters (internal to the reporting engine). You
can read the built-in parameters, but you cannot modify or delete them. Some important
built-in parameters are:
• REPORT_CONNECTION - For a report using JDBC, this parameter holds the JDBC
connection used to run the SQL query.
• REPORT_DATA_SOURCE - This parameter contains the data source used to fill the
report (if available).
• REPORT_LOCALE - This parameter contains the locale used to fill the report.
Some built-in parameters are specific to a query language. For example, if you are using
the Hibernate query language, the reports automatically include the HIBERNATE_SESSION
parameter that holds the Hibernate session for the HQL query.
The built-in parameters are:
Parameter Description
REPORT_CONTEXT
REPORT_CONNECTION This is the JDBC connection passed to the report when the
report is created through an SQL query.
REPORT_DATA_SOURCE This is the data source used by the report when it is not using
a JDBC connection.
Parameter Description
REPORT_LOCALE This specifies the locale used to fill the report. If no locale is
provided, the system default is used.
REPORT_TIME_ZONE This is used to set the time zone used to fill the report. If no
value is provided, the system default is used.
REPORT_CLASS_LOADER This parameter can be used to set the class loader to use when
filling the report.
Parameter Description
REPORT_VIRTUALIZER This defines the class for the report filler that implements the
JRVirtualizer interface for filling the report.
IS_IGNORE_PAGINATION You can switch the pagination system on and off with this
parameter (it must be a Boolean object). By default, pagination
is used except when exporting to HTML and Excel formats.
and the value of the parameter my_order_id is then passed to the statement.
In this query:
SELECT * FROM ORDERS ORDER BY $P!{my_order_field}
my_order_field cannot be treated as an SQL parameter. JasperReports considers this
parameter a placeholder (note the special syntax $P!{}) is replaced with the text value of
the parameter.
Using the same logic, a query can be fully passed using a parameter. The query string
would look like:
$P!{my_query}
A query can contain any number of parameters. When passing a value using the $P!{}
syntax, the value of the parameter is taken as is, the user is responsible of the correctness
of the passed value (SQL escaping is not performed by JasperReports in this case). When
using a parameter in a query, a default value must be set for the parameter to allow
Jaspersoft Studio to run the query to retrieve the available fields.
Relative Dates
You can create a report that filters information based on a date range relative to the
current system date using a parameter of type DateRange. A date range parameter can
take either a date or a text expression that specifies a date range relative to the current
system date.
A relative date expression is always calculated in the time zone of the logged-in user.
However, the
Relative dates do not currently support keywords like "Week-To-Date" (from the start of
the current week to the end of the current day). However, you can set a relative date
period in a query in JRXML using BETWEEN, which has the syntax:
$X{BETWEEN, column, startParam, endParam}
For example, to create a week-to-date query, set startParam to WEEK and endParam to
DAY. You can do this for other time ranges, such as Year-To-Day, Year-To-Week.
<parameter name="myParameter"
class="net.sf.jasperreports.types.date.DateRange">
<defaultValueExpression>
<![CDATA[new DateRangeBuilder("DAY-1").toDateRange()]]>
</defaultValueExpression>
</parameter>
<queryString>
<![CDATA[Select * from account where $X{EQUAL, OpportunityCloseDate,
myParameter}]]>
</queryString>
This JRXML example shows results prior to the end of last month:
<parameter class="net.sf.jasperreports.types.date.DateRange"
name="EndDate">
<defaultValueExpression>
<![CDATA[new net.sf.jasperreports.types.date.DateRangeBuilder("MONTH-
1").toDateRange().getEnd()]]>
</defaultValueExpression>
</parameter>
<queryString>
<![CDATA[SELECT * FROM orders WHERE $X{LESS, order_date, EndDate}]]>
</queryString>
Problem Solution
Set up a relative date parameter called StartDate that takes the value: QUARTER. QUARTER
evaluates to the first day (the first instant, really) of this quarter.
Find all purchases made SQL: select * from orders where $X{LESS, order_date, StartDate}
previous to this quarter
Find all purchases made select * from orders where $X{EQUAL, order_date, StartDate}
in this quarter
• Create a date type input control for each parameter, for example, StartDate and
EndDate.
The following JRXML example uses the BETWEEN keyword in the $X() function to find all
data from the previous 20 years:
<parameter name="StartDate"
class="net.sf.jasperreports.types.date.DateRange">
<defaultValueExpression>
<![CDATA[(new net.sf.jasperreports.types.date.DateRangeBuilder("YEAR-
20")).toDateRange()]]>
</defaultValueExpression>
</parameter>
<parameter name="EndDate"
class="net.sf.jasperreports.types.date.DateRange">
<defaultValueExpression>
<![CDATA[(new net.sf.jasperreports.types.date.DateRangeBuilder
("DAY")).toDateRange()]]>
</defaultValueExpression>
</parameter>
<queryString language="SQL">
<![CDATA[select HIRE_DATE, MANAGEMENT_ROLE, GENDER, SUPERVISOR_ID,SALARY
from employee where
$X{BETWEEN, HIRE_DATE, StartDate, EndDate} limit 200]]>
</queryString>
You can use the getStart() and getEnd() methods to get the precise beginning and end of a
relative date. Both of these methods return a date instead of a date range. The following
example shows how to get the precise start date as a default value expression.
...
HashMap hm = new HashMap();
...
JasperPrint print = JasperFillManager.fillReport(
fileName,
hm,
new JREmptyDataSource());
...
fillReport is a key method that allows you to create a report instance by specifying the file
name as a parameter, a parameter map, and a data source. (This example uses a dummy
data source created with the class JREmptyDataSource and an empty parameter map
created using a java.util.HashMap object.)
Let us see how to pass a simple parameter to a reporting order to specify the title of a
report.
The first step is to create a parameter in the report to host the title (that is a String). We
can name this parameter REPORT_TITLE and the class is java.lang.String (Definition of
REPORT_TITLE).
All the other properties can be left as they are. Drag the parameter into the Title band to
create a text field to display the REPORT_TITLE parameter.
To set the value of the REPORT_TITLE parameter in our application, modify the code of the
previous source code example by adding:
...
HashMap hm = new HashMap();
hm.put(“REPORT_TITLE”,”This is the title of the report”);
...
JasperPrint print = JasperFillManager.fillReport(
fileName,
hm,
new JREmptyDataSource());
...
We have included a value for the REPORT_TITLE parameter in the parameter map. You do
not need to pass values for all the parameters. If you do not provide a value for a certain
parameter, JasperReports assigns the value of Default Value Expression to the parameter
with the empty expression evaluated as null.
When printing the report, Jaspersoft Studio includes the String This is the title of the report
in the Title band. In this case, we just used a simple String. But you can pass much more
complex objects as parameters, such as an image (java.awt.Image) or a data source
instance configured to provide a specified subreport with data. The most important thing
to remember is that the object passed in the map as the value for a certain parameter
must have the same type (or at least be a super class) of the type of the parameter in the
report. Otherwise, Jaspersoft Studio fails to generate the report and returns a
ClassCastException error.
Parameters Prompt
If you set a parameter to be used as a prompt, when running the report, Jaspersoft Studio
asks for the value of the parameter.
Jaspersoft Studio provides input dialogs for parameters of type String, Date, Time,
Number, and Collection.
Parameter Sets
A parameter set is a set of pre-defined parameters that you can add to your report. For
example, you could create a set that contains parameters for your database address fields
(Country, State, City, Zip Code, Street). Then whenever you want to use address
parameters, you can add the set to the report and use the parameters, instead of adding
individual parameters.
Jaspersoft Studio includes the following parameter sets:
• Http Data Adapters Built In Parameters – Parameters that can be used with a data
adapter that connects to a web service.
• Jaspersoft Server Built In Parameters – Parameters used to retrieve user metadata
from JasperReports Server. For example, these parameters let you filter the data in
your report depending on user roles or organization. You must have a valid
connection to a JasperReports Server instance to use these parameters. See
Accessing JasperReports Server from Jaspersoft Studio for more information.
2. Select the parameter set you want to add to your report and click Finish.
The parameters in the set are added to your report.
4. To create an individual parameter inside your set, click Add in the Parameter Set
dialog.
The Parameter dialog is displayed.
5. Add and configure the parameter. The following settings are available:
• Name – Name of the parameter.
• Class – Class type of the parameter.
• Description – A string describing the parameter. This is shown as the parameter
tooltip in the Input Parameters pane in preview.
• Nested Type Name
• Is for Prompting – Enable this to have the Jaspersoft Studio prompt for the
parameter when you preview the report. If you have this selected and are
publishing the report to the server, you need to create input controls on the
server. May also be passed to an external application.
• Value – Default value for the parameter. This value is used if no value is provided
for the parameter from the application that runs the report. The type of value
must match the type declared in the Class field. For example, if you are creating
a Country parameter, you might use the value $F{SHIPCOUNTRY} for your
parameter.
6. Click OK to create the parameter and return to the Parameter Set dialog.
7. When you have created all the parameters you want, click OK to return to the
Preferences dialog.
8. Click OK to return to the design view and create your parameter set.
To use your parameter set in a report, select Create Parameter Set from the Parameters
context menu in outline view.
Variables
You can use variables to store partial results and do complex calculations with the data
extracted from a data source. You can then use these values in other parts of the report,
including other variables.
This chapter contains the following sections:
• Defining or Editing a Variable
• Base Properties of a Variable
• Other Properties of a Variable
• Built-In Variables
• Tips & Tricks
Evaluation Time
Evaluation time is not an attribute of the variable but of elements that can use the variable
in their expressions (like a Text Field). Evaluation time determines when the value of the
variable should be read. A variable can potentially change value at every iteration, so a
value read at one time may be different from the value read another time.
For every element using a variable in its expression, it is possible to say when to evaluate
the variable. And because an expression can contain multiple variables, this parameter also
influences when these variables are read.
The possible evaluation times are:
• Report: The expression is evaluated at the end of the report.
• Page: The expression is evaluated at the end of every page of the report.
• Column: The expression is evaluated at the end of each column (for a single column
report, this is the same as Page).
• Group: The expression is evaluated after the break of the specified group (available
only if at least one group is defined).
• Band: The expression is evaluated after the end of the band where the element with
this evaluation time is placed.
• This is a very specific case, introduced to wait until the other elements in the band
are completely created. Typically the values of the variables are read at the start of
the band. But suppose, for example, you have a subreport with an output parameter
to print in the main report. To print this parameter, it must be read after the
subreport is computed, so the value can be printed when the band is completely
created. In this case, the Band evaluation time is necessary.
• Auto: This is used when the expression contains variables and fields that need to be
evaluated at different times. The variables are evaluated at a time corresponding to
their Reset Type (see below for more information), instead the fields are always
evaluated at time -now. This type is useful when report elements have expressions
that combine values evaluated at different times (for example, percentage out of a
total).
• Now: The value of the expression is evaluated after the read of every record, so at
every iteration, this is the default behavior.
Calculation Function
A calculation function is an attribute that specifies when a variable can be used in
association with the expression to determine the value of the variable. When using a
calculation function, the value of the variable is not determined directly by its expression.
Instead, it is passed to the calculation function that uses it to determine its value.
There are many calculation functions built-in to Jaspersoft Studio:
• Sum: At every iteration, the variable value is summed. This is one of the cases where
the initial value is really important.
• Count: At every iteration, the variable value is incremented by one unit (this is only if
the expression is not null).
• Distinct Count: At every iteration, the variable value is incremented by one unit, but
only if the value of the expression was never returned before.
• Average: The value of the variable is the arithmetic average of all values received in
input from the expression.
• Lowest: The variable takes the value of the lowest element received from the
expression.
• Highest: The variable takes the value of the highest element received from the
expression.
• Standard Deviation: The standard deviation of all the values received from the
expression.
• First: The variable takes the value from the first value returned by the expression.
• System: No calculation is done and the expression is not evaluated. The value of the
variable is the last value set on it. This is useful to store partial results or the final
results of a computation.
• Variance: The variance of all values returned by evaluation of a report variable’s
expression.
Increment Type
As stated above, when a calculation function is defined, the value of the expression is
passed to the function that calculates the variable. By default this occurs for every record
read, but sometimes a different behavior is desired. The increment type parameter enables
you to change the "time" at which the calculation function is used.
The possible values for this attribute are:
• Report: The Calculation Function is called only at the end of the report, passing it to
the expression's value at that moment.
• Page: The Calculation Function is called at the end of each page, passing to it
expression's value at each of those moments.
• Column: The Calculation Function is called at the end of each column (for a one-
column report, this is the same as Page).
• Group: The Calculation Function is called at the start of every occurrence of the
specified group. This option is visible only if at least one group is defined.
• None: The Calculation Function is called after the read of every record, this is the
default behavior.
Remember that the expression is evaluated at every record read, independent of the
increment type selected, but the calculation function is used only when the times match
those defined in the increment type.
Reset Type
The reset type specifies when a variable should be reset to its initial value (or to null if no
initial value is defined). This is useful when the variable is used to compute a partial value,
like a sum or an average of only some of the records read.
The possible values for this attribute are:
• Report: The variable is initialized only one time at the beginning of the report
creation.
• Page: The variable is initialized on each page.
• Column: The variable is initialized again in each new column (for a one-column
report, this is the same as Page).
• Group: The variable is initialized at the start of every occurrence of the specified
group. This option is available only if at least one group is defined.
• None: The variable is never initialized, so the initial value expression is ignored.
Built-In Variables
Jaspersoft Studio makes some built-in variables available to you. See the table below.
These variables cannot be edited. You notice that their names are light gray. Other
variables are black.
PAGE_NUMBER Contains the current number of pages in the report at the report
time.
Expressions
Many settings in a report are defined by formulas, such as conditions that can hide an
element, special calculations, or text processing that requires knowledge of a scripting
language.
Formulas can be written in at least three languages, two of which (JavaScript and Groovy)
can be used without knowledge of programming methods.
All formulas in JasperReports are defined through expressions. The default expression
language is Java, but if you are not a programmer, we recommend JavaScript or Groovy,
because those languages remove Java complexity. The language is a property of the
document. To set it, select the document root node in the Outline view and choose your
language in the Language property in the Properties view.
An expression is a formula that operates on some values and returns a result, like a
formula in a spreadsheet cell. A cell can have a simple value or a complex formula that
refers to other values. In a spreadsheet, you refer to values contained in other cells; in
JasperReports you use the report fields, parameters, and variables. Whatever is in your
expression, when it is computed, it returns a value (which can be null).
Expression Types
An expression's type is determined by the context in which the expression is used. For
example, if your expression is used to evaluate a condition, the expression should be
Boolean (true or false); if you are creating an expression to display in a text field, it is
probably a String or a number (Integer or Double). Using the right type is crucial;
JasperReports requires precision when choosing an expression type.
Some of the most important Java types are:
If an expression is used to determine the value of a condition that determines, for instance,
whether an element should be printed, the return type is java.lang.Boolean. To create it,
you need an expression that returns an instance of a Boolean object. Similarly, if an
expression shows a number in a text field, the return type is java.lang.Integer or
java.lang.Double.
JavaScript and Groovy are not formal about types because they are not typed languages.
The language itself treats a value in the best way by trying to guess the value type or by
performing implicit casts (conversion of the type).
Expression operators
+ Sum (it can be used to sum two numbers or to concatenate two A+B
strings)
- Subtraction A-B
/ Division A/B
|| Boolean operator OR A || B
== Equals A == B
!= Not equals A != B
Regarding the Equals operator: in Java, the == operator can only be used to compare
two primitive values. With objects, you need to use the special method “equals”; for
example, you cannot write an expression like "test" == "test", you need to write
"test".equals("test").
Regarding the Equals operator: in Java, the != operator can only be used to compare
two primitive values.
Within an expression, you can use the syntax summarized in Syntax for referring to report
objects to refer to the parameters, variables, and fields defined in the report.
Syntax Description
$P!{name_ Special syntax is used in the report SQL query to indicate that the
parameter} parameter does not have to be dealt as a value to transfer to a
prepared statement, but that it represents a little piece of the query.
In summary, fields, variables, and parameters represent objects; specify their type when
you declare them within a report.
Expression Result
“test”.length() 4
“test”.substring(0, 3) “tes”
“test”.startsWith(“A”) false
The methods of each object are usually explained in the JasperReports Library Javadocs,
that is available at http://jasperreports.sourceforge.net/api/.
You can use parentheses to isolate expressions and make the overall expression more
readable.
If you use this character in a static text element, “\u20ac” will appear. The value of a
static field is not interpreted as a Java expression.
The first thing to note is that each of these expressions represents a Java Object, meaning
that the result of each expression is a non-primitive value. The difference between an
object and a primitive value makes sense only in Java, but it is very important: a primitive
value is a pure value like the number 5 or the Boolean value true.
Operations between primitive values have as a result a new primitive value, so the
expression:
5+5
results in the primitive value 10. Objects are complex types that can have methods, can be
null, and must be “instanced” with the keyword “new” most of the time. In the second
example above, for instance (new Boolean(true)), we must wrap the primitive value true in
an object that represents it.
By contrast, in a scripting language such as Groovy and JavaScript, primitive values are
automatically wrapped into objects, so the distinction between primitive values and
objects wanes. When using Java, the result of our expression must be an object, which is
why the expression 5+3 is not legal as-is but must be fixed with something like this:
new Integer( 5 + 3 )
The fix creates a new object of type Integer representing the primitive value 8.
So, if you use Java as the default language for your expressions, remember that
expressions like the following are not valid:
• 3 + 2 * 5
• true
• (($P{MyParam} == 1) ? "Yes" : "No")
These expressions don’t make the correct use of objects. In particular, the first and the
second expressions are not valid because they are of primitive types (integer in the first
case and boolean in the second case) which do not produce an object as a result. The third
expression is not valid because it assumes that the MyParam parameter is a primitive type
and that it can be compared through the == operator with an int, but it cannot. In fact, we
said that parameters, variables, and fields are always objects and primitive values cannot
be compared or used directly in a mathematical expression with an object.
5+5
The language automatically encapsulates the primitive value 10 (the result of that
expression) in a proper object. Actually, you can do more: you can treat this value as an
object of type String and create an expression such as:
5 + 5+ ”my value”
Whether or not such an expression resolves to a rational value, it is still a legal expression
and the result is an object of type String with the value:
10 my value
Hiding the difference between objects and primitive values, Groovy allows the comparison
of different types of objects and primitive values, such as the legal expression:
$F{Name} == “John”
This expression returns true or false, or, again:
“340”.substring(0,2) < 100 Always returns true (since the substring method call
produces the string “34”, which is less than 100).
Groovy provides a way to greatly simplify expressions and never complains about null
objects that can crash a Java expression throwing a NullPointerException. It really does
open the doors of JasperReports to people who don’t know Java.
JavaScript is the best choice for users who have no knowledge of other languages. The
other significant advantage of JavaScript is that it is not interpreted at run time, but
instead generates pure Java byte-code. As a result, it offers almost the same performance
as Java itself.
Note: Rhino JavaScript engine has been removed from JasperReports Server. With the
removal of Rhino JS, reports created using JavaScript will not function unless you add
Rhino JS back to your deployment. This can be done by stopping the web server,
downloading version 1.7.14 which at the time of writing is not known to have any CVEs.
This file can be replaced into the WEB-INF/lib folder, and reports that rely on JavaScript
will again be functional.
Fonts
The best way to define and use a font in JasperReports Library is to create and use a font
extension. Font extensions force JasperReports to work with external TTF, SVG, WOFF, or
EOT fonts instead of using built-in or system fonts. This ensures that a specific font
behaves in the same way wherever the report is run.
Using system fonts usually results in unacceptable changes in report format when the
report is deployed on another system. Subtle differences in font size and spacing can affect
not only the appearance of the text but the layout of the report itself. You may lose part of
the text in a text element or the font might not be available at all. Font extensions help
avoid these problems:
• A font can be available in one operating system but not in another. In this case, the
default font is used for the element, but it may not support the expected character
set.
• The Java virtual machine can map logical font family names to different physical
fonts.
• A font that is available in different operating systems can be slightly different from
one operating system to another.
You can incorporate additional information in a font extension, such as: bold and italic
fonts, the text encoding for the font, and a list of locales where the font should be used.
You can also use font extensions to embed your fonts in PDF files.
In addition, you can combine several font extensions into a font set. For example, if you
have data in English and Japanese, you can create a single font set that combines fonts for
those languages.
This chapter contains the following sections:
• Font Extensions Reference
• Example of Using Font Extensions
• Deploying Font Extensions to JasperReports Server
• Add from Path – Specify a folder containing the fonts you want to add as extensions.
• Duplicate – Create a copy of the selected font extensions and/or font sets. Each copy
has a unique name, which can be edited.
• Delete – Delete the selected font extensions and/or font sets. This does not remove
the original font files from your system.
• Up – Move the selected font extension and/or font set up in the list of fonts.
• Down – Move the selected font extension and/or font set down in the list of fonts.
• Create Set – Combine the selected font extensions into a font set.
• Add to Set – Add the selected font extensions to an existing font set. Clicking this
displays a dialog where you can select the font set you want to add the extensions
to.
• Edit – Edit the selected font extension or set. For a font extension, displays The Font
Family Dialog. For a font set, displays the Font Set dialog.
• Export – Export the selected font extension or set.
• [Font Format] – File location for the specific font and attribute. To change or add
a file, use the Browse button to navigate to the file location for the specific font
and attribute. You can only select one file for each tab.
• PDF Font Name (deprecated) – The name of the font when exported to PDF. This
can be a pre-defined PDF font or the name of the font file. Not necessary when
using font extensions.
• PDF Details – Settings used for the font when exported to PDF. Deprecated for static
text and textfields.
• PDF Encoding (deprecated) – The font encoding to use for the font. Defaults to
Identity-H. To avoid Identity-H printing issues, set this to the correct encoding for
your font.
• Embed this font in PDF document (deprecated) – Flag that specifies whether to
embed the font in a generated PDF or not. Embedding fonts is recommended to
ensure consistency across platforms.
If a mapping is present, then web fonts are not used. Do not define a font mapping
unless you want to override the web font functionality.
Font Sets
Font sets let you group font extensions in supersets that can include several languages
and/or scripts. When you use a font set, the font family resolution occurs during text
processing on a per-character basis, allowing you to include characters from different
languages or character sets in the same text element. For example, if you have data that
includes Japanese and English entries, you can create a single font set that contains
Western European and Japanese fonts and use that font set for your data.
1. Make sure that the font files for the fonts have been downloaded and
decompressed. You can also use fonts from a URL.
2. Click Add from Path to open the Fonts path dialog.
3. Click ... and browse to the folder that contains the fonts you want, then click Finish.
Jaspersoft Studio loads all the fonts at that location, extracts the font family name
embedded in the font files, and displays all the extracted fonts in the Preferences
dialog.
Once you have create a font extension, you can edit it by double-clicking its name in the
font list or by selecting it and clicking Edit. See The Font Family Dialog for more
information.
3. Enter a name for your font set and click OK. This example uses SampleFontSet.
The new font set is displayed in the font list.
Next, configure the fonts in the font set so that Lobster is only used for Cyrillic characters,
even though it supports Latin characters.
3. To prevent Lobster from being used by Latin characters, click Add next to the
Exclude Scripts list.
The Scripts name dialog is displayed.
4. Select Latin in the Scripts Name dialog and click OK.
Latin is added to the list of excluded scripts.
5. Click OK to close the Scripts Name dialog; click OK again to close the Font Set
Family dialog and click OK a third time to close the Preference dialog.
2. Go to File > New > Jasper Report or click on the main toolbar.
3. In the New Report Wizard window, select a blank template, such as the Blank A4
template, then click Next.
4. Select the project folder with the data adapter file you just created, give the report a
name, and click Next.
5. On the Data Source page, select the One Empty Record - [OneEmptyRecord.jrdax]
adapter. Make sure to select this adapter, which is local, and not the One Empty
Record adapter that is selected by default.
6. Click Finish.
7. Set the default data adapter for the report:
a. Select the report node in the Outline view.
b. In the Properties view for the report, on the Report tab, scroll down to Dataset >
Default Data Adapter and click ...
c. In the Open Data Adapter dialog, select Custom Value.
d. Enter OneEmptyRecord.jrdax in the Path entry box.
e. Click Finish.
The default font used for a new static text element is SansSerif. This font does
support for extended characters, but because it is a Java logical font that is
translated to a physical font by the JVM, you will not know what font is selected
when the report is run.
6. Select SampleFontSet from the Font menu and 24 from the size menu next to it.
Then resize the static text element so it is large enough to display the text.
7. Save and preview the report. The license for these fonts lets you preview the report
as a PDF.
When working with fonts, look carefully at your uploaded reports. For some fonts or
character sets, you do not see misformatted text; instead, the text is not displayed at
all.
1. Open a web browser, log in to the server, navigate to the report you just created,
and run the report. You should see the correct fonts. If you do not see your fonts,
there has been a problem with uploading the jar to the file system.
2. Export the report as PDF. You should see the updated fonts. If not, there has been
some problem uploading and linking the resource.
When verifying font extensions and sets, it is best to run the report in JasperReports
Server from a web browser. Running the report from Repository Explorer in Jaspersoft
Studio may not show the fonts correctly.
Data Adapters
A data adapter is a resource that specifies how and where to obtain data. Specifically, it is
an object that contains information about how to connect to or retrieve the data, and the
logic to do that. Data adapters are stored in XML files and simplify porting of the report
configuration and data source creation between JasperReports environments. Whether you
use a report with a data adapter XML file in Jaspersoft Studio, publish it to JasperReports
Server or deploy it to a custom JasperReports environment. JasperReports Library can use
it to obtain the data you specify.
This chapter starts by telling you how to create and use data adapters based on the data
adapter types available in Jaspersoft Studio. Data adapters are designed to simplify the
complexities of working with data in the JasperReports Library. However, data adapters are
only one of the ways that JasperReports Library can get data from a data source. As you
get more familiar with Jaspersoft Studio, you may want to go a little deeper and learn
about data in JasperReports Library and the JRDataSource interface.
Usually data adapters are stored as XML files in the same project as the report to simplify
deployment to JasperReports Server or another environment. In Jaspersoft Studio, data
adapters can also be stored in the Repository Explorer, in which case they are visible from
all the projects. If you plan to deploy the report outside Jaspersoft Studio, it is better to
store it in the project from the beginning.
This chapter has the following sections:
• Creating and Editing Data Adapters
• Using Data Adapters in Reports and Datasets
• Working with Database JDBC Connections
• Working with a Collection of JavaBeans Data Adapter
• Working with XML Data Adapters
• Working with XML/A Data Adapters
• Working with CSV Data Adapters
• Using the Empty Record Data Adapter
• Using the Random Data Adapter
1. Click on the main toolbar OR right-click a project in the Project Explorer and
select New > Data Adapter.
2. In the DataAdapter File window, choose the project where you want to save the data
adapter file. This should be the project that contains the reports you want to use
with your data adapter.
3. Enter a name for your adapter and click Next.
The Data Adapters Wizard opens.
4. Select the data adapter type that you want and click Next.
5. Enter a name for your adapter. This name is used when you select an adapter for a
report.
6. Enter the properties needed by the adapter type that you selected. For example, for
a database JDBC connection you need to select a JDBC driver and set the URL and
database username and password. For a CSV file, you need to enter a filename,
column names, and the column separator.
7. (Optional) If you want to test the connection, click the Test button if available.
8. Click Finish to create the adapter.
The adapter is saved as an XML file in the project location that you selected.
report. You also cannot directly export a global driver to a JasperReports Server or
JasperReports IO deployment; export it to an XML file in the project instead. See Project
Folder Types and Report Execution Contexts for more information about project types.
2. Select a location in the same project as the report that is using this adapter, enter a
name for the file, and click OK.
A simple XML file is created in the location that you chose. The data adapter must be
in the same project as your report. To use the same adapter in more than one
project, see Copying a Data Adapter.
Data adapters are hierarchical. That is, if no adapter is directly defined for a subdataset, it
looks for the adapter of its parent dataset, then its parent's parent, and so forth.
• When you publish a report to JasperReports Server, you can select a JasperReports
Server data source to use. See Publishing a Report to JasperReports Server for more
information. If you choose this method to select a data source, any subdatasets in
the report must use the same data source.
• You can choose to set the default data adapter explicitly for the report and/or any
subdatasets. You can set this property separately for any dataset in the report. If this
property is present, you cannot choose a different adapter to preview the report.
4. Choose the format to use for specifying the data adapter location:
• Workspace resource – A file in your workspace, for example, value="test/sample-
adapter.jrdax"/>. This should be a file in the same project as your report. If you
want to use a global adapter, you need to export it to a file first. See Importing
and Exporting Data Adapters for more information.
• Absolute Path in the file system – A file path, for example,
value="file:///C:/Adapters/sample-adapter.jrdax"
• URL – A remote URL that hosts the data adapter file, for example,
value="http://myserver:8080/sample-adapter.jrdax"
• Custom value – A free-form string that identifies the location of the data adapter
to use. You could use this if you wanted to enter a string in the repo: syntax, for
example, value="repo:/reports/interactive/CustomersDataAdapter" See
Understanding the repo: Syntax for more information.
5. If you selected Workspace resource or Absolute Path, click Browse to locate the file
in the workspace or in your file system. Otherwise, enter the URL or free-form string.
6. Click Finish.
The default data adapter is set for the dataset. It is represented in the JRXML file
using the net.sf.jasperreports.data.adapter property.
• To create the connection local to a project, click , enter a name and location
for the data adapter in the DataAdapter File dialog, and then click Next.
The Data Adapter wizard appears (see Data Adapter Wizard).
2. From the list, select Database JDBC connection to open the Data Adapter dialog.
3. Name the connection (use a significant name like Mysql – Test). This is the name
that appears on the list of available connections when you create a report.
4. In the JDBC Driver field, specify the JDBC driver to use for your database connection.
The dropdown displays the names of the most common JDBC drivers.
If a driver is displayed in red, the JDBC driver class for that driver is not present in
the class path and you must obtain and install the driver before using it. See Using a
Database JDBC Connection.
JasperReports Server includes the JDBC drivers for the following commercial
databases: Oracle, MS SQLServer and DB2. In some cases, these drivers provide
functionality not provided by the vendors' driver. However, there may be some
differences in queries between the two drivers. You can use the drivers, or you can
choose to install and use the driver supplied by the database vendor.
If you upload your reports to JasperReports Server, make sure to use the same driver in
both JasperReports Server and Jaspersoft Studio.
• Eclipse secure storage – This is the correct option for security, but can be
difficult to work with when testing and saving adapters. In addition, it can make
it difficult to share adapters with other developers or deploy data adapters to
JasperReports Server.
7. After you have inserted all the data, click the Test button to verify the connection. If
everything's okay, you see a message that the test was successful.
8. Click OK to exit the message.
9. Click Finish to create the connection.
ClassNotFoundError
The ClassNotFoundError exception occurs whenever a data adapter fails to load a class it
requires. In the context of JDBC connections, the most likely cause is that the required
JDBC driver is not present in the classpath. In general, a data adapter has two classpaths
that it uses to find libraries. First, the adapter looks at any paths that were specified inside
the data adapter when it was created. If it cannot load the libraries or classes it needs
using its internal paths, the data adapter uses the Jaspersoft Studio classpath to look for
them.
The Jaspersoft Studio classpath is defined in your Eclipse project. As Jaspersoft Studio
uses its own class loader, it is enough to add resources such as jar files and directories
containing classes to the Jaspersoft Studio classpath.
For example, suppose you want to create a connection to an Oracle database. Jaspersoft
Studio does not ship the vendor's driver for this database. If you choose the
oracle.jdbc.driver.OracleDriver driver, when you test the connection, you see the
ClassNotFoundException, as shown in ClassNotFoundError exception. You need to add the
JDBC driver for Oracle, ojdbc14.jar, to the classpath.
Fields Registration
To use SQL query fields in a report, you need to register them. You do not need to register
all the selected fields—only those actually used in the report. For each field, specify a name
and type. Conversion of SQL and JAVA types shows SQL types and the Java objects that
they map to.
BIGINT Long
The table does not include special types like BLOB, CLOB, ARRAY, STRUCT, and REF,
because these types cannot be managed automatically by JasperReports. However, you
can use them by declaring them generically as Object and managing them by writing
supporting static methods. The BINARY, VARBINARY, and LONGBINARY types should be
dealt with in a similar way. With many databases, BLOB and CLOB can be declared as
java.io.InputStream.
Whether an SQL type is converted to a Java object depends on the JDBC driver used.
For the automatic registration of SQL query fields, Jaspersoft Studio relies on the type
proposed for each field by the driver itself.
Filtering Records
The records in a report can be ordered and filtered. Set sort and filter options in the Report
query dialog by clicking the Dataset and Query button .
Clicking the Data Preview tab shows a subset of your filtered data. The filter expression
must return a Boolean object: true if a particular record can be kept, false otherwise.
If no fields can be selected with the Add field button, check to see if the report contains
fields. If not, close the query dialog, register the fields, and resume the sorting.
PersonBean example
}
public int getAge()
{
return age;
}
To use this collection of beans, you need to create an instance of the Factory class. Your
class, named TestFactory, must contain the actual data that is used by the report. In this
case, it is something similar to this:
return collection;
}
}
A data adapter based on this class would represent five JavaBeans of PersonBean type.
• To create the connection local to a project, click , enter a name and location
for the data adapter in the DataAdapter File dialog, and then click Next.
The Data Adapter wizard appears (see Data Adapter Wizard).
2. To create a connection to handle JavaBeans, select Collection of JavaBeans in the
list of data adapter types.
The fields necessary to create a collection of JavaBeans appear.
If you selected Use field description when you specified the properties of your data
adapter, the mapping between JavaBean attribute and field value uses the field description
instead of the field name.
Jaspersoft Studio provides a visual tool to map JavaBean attributes to report fields. To use
it, open the query window, go to the tab JavaBean Data Source, insert the full class name
of the bean you want to explore, and click Read attributes. The tab displays the attributes
of the specified bean class.
• If an attribute is also a Java object, you can double-click the object to display its
other attributes.
• To map a field, select an attribute name and click the Add Selected Field(s) button.
<addressbook>
<category name="home">
<person id="1">
<lastname>Davolio</lastname>
<firstname>Nancy</firstname>
</person>
<person id="2">
<lastname>Fuller</lastname>
<firstname>Andrew</firstname>
</person>
<person id="3">
<lastname>Leverling</lastname>
</person>
</category>
<category name="work">
<person id="4">
<lastname>Peacock</lastname>
<firstname>Margaret</firstname>
</person>
</category>
<favorites>
<person id="1"/>
<person id="3"/>
</favorites>
</addressbook>
To select only the people contained in the categories (that is, all the people in the address
book), use the following expression:
/addressbook/category/person
Four nodes are returned as shown in the following table.
<person id="1">
<lastname>Davolio</lastname>
<firstname>Nancy</firstname>
</person>
<person id="2">
<lastname>Fuller</lastname>
<firstname>Andrew</firstname>
</person>
<person id="3">
<lastname>Leverling</lastname>
</person>
<person id="4">
<lastname>Peacock</lastname>
<firstname>Margaret</firstname>
</person>
If you want to select the people appearing in the favorites node, use the following
expression:
/addressbook/favorites/person
Two nodes are returned.
<person id="1"/>
<person id="3"/>
Here is another expression. It is a bit more complex, but it shows all the power of the
XPath language. The idea is to select the person nodes belonging to the work category. The
expression to use is the following:
/addressbook/category[@name = "work"]/person
The expression returns only one node, the one with an ID equal to 4, as shown here:
<person id="4">
<lastname>Peacock</lastname>
<firstname>Margaret</firstname>
</person>
• To create the connection local to a project, click , enter a name and location
for the data adapter in the DataAdapter File dialog, and then click Next.
The Data Adapter wizard appears (see Data Adapter Wizard).
2. From the list, select an XML document to open the Data Adapter dialog.
You can configure an XML data adapter to connect to a REST web service. For an
example of connecting to a web service using the JSON adapter, see Connecting to a
Web Service Using a JSON Data Adapter.
id @id Integer
Jaspersoft Studio provides a visual tool to map XML nodes to report fields; to use it, open
the query window and select XPath as the query language. If the active connection is a
valid XML data adapter, the associated XML document is shown in a tree view. To register
the fields, set the record node by right-clicking a Person node and selecting the menu item
Set record node. The record nodes are displayed in bold.
Then one by one, select the nodes or attributes and select the pop-up menu item Add
node as field to map them to report fields. Jaspersoft Studio determines the correct XPath
expression to use and creates the fields for you. You can modify the generated field name
and set a more suitable field type after the registration of the field in the report (which
happens when you close the query dialog).
Insert the different fields in the Detail band. The XML file used to fill the report is that
shown:
The XPath expression for the node set selection specified in the query dialog is:
/addressbook/category/person
<addressbook>
<category name="home">
<person id="1">
<lastname>Davolio</lastname>
<firstname>Nancy</firstname>
<email>davolio1@sf.net</email>
<email>davolio2@sf.net</email>
<hobbies>
<hobby>Music</hobby>
<hobby>Sport</hobby>
</hobbies>
</person>
<person id="2">
<lastname>Fuller</lastname>
<firstname>Andrew</firstname>
<email>af@test.net</email>
<email>afullera@fuller.org</email>
<hobbies>
<hobby>Cinema</hobby>
<hobby>Sport</hobby>
</hobbies>
</person>
</category>
<category name="work">
<person id="3">
<lastname>Leverling</lastname>
<email>leverling@xyz.it</email>
</person>
<person id="4">
<lastname>Peacock</lastname>
<firstname>Margaret</firstname>
<email>margaret@foo.org</email>
<hobbies>
<hobby>Food</hobby>
<hobby>Books</hobby>
</hobbies>
</person>
</category>
<favorites>
<person id="1"/>
<person id="3"/>
</favorites>
</addressbook>
What we want to produce is a document that is more elaborate than those you have seen
so far. For each person, we want to present their e-mail addresses, hobbies, and favorite
people.
You can create this document using subreports. You need a subreport for the e-mail
address list, one for hobbies, and one for favorite people (that is a set of nodes out of the
scope of the XPath query we used). To generate these subreports, you need to understand
how to produce new data sources to feed them. In this case, you use the
JRXmlDataSource, which exposes two extremely useful methods:
public JRXmlDataSource dataSource(String selectExpression)
public JRXmlDataSource subDataSource(String selectExpression)
The first method processes the expression by applying it to the whole document, starting
from the actual root. The second assumes that the current node is the root.
Both methods can be used in the data source expression of a subreport element to
produce the data source to pass to the element dynamically. The most important thing to
note is that this mechanism allows you to make both the data source production and the
expression of node selection dynamic.
The expression to create the data source that feeds the subreport of the e-mail addresses
is:
((net.sf.jasperreports.engine.data.JRXmlDataSource)
$P{REPORT_DATA_SOURCE}).subDataSource("/person/email")
This code returns all the e-mail nodes that descend directly from the present node
(person).
The expression for the hobbies subreport is similar, except for the node selection:
((net.sf.jasperreports.engine.data.JRXmlDataSource)
$P{REPORT_DATA_SOURCE}).subDataSource("/person/hobbies/hobby")
Next, declare the master report’s fields. In the subreport, you have to refer to the current
node value, so the field expression is simply a dot (.),
4. (URL only.) If you entered a URL in the CSV file field, click the Options button to
open the Http Connection Options dialog.
labels). In any case, the column names read from the file are used instead of the
declared ones, so avoid modifying the names found with the Get column names
button.
• If the first line of your CSV file does not contain the column names, set a name
for each column using the syntax COLUMN_0, COLUMN_1, and so on.
If you define more columns than the ones available, you get an exception at report
filling time.
JasperReports assumes that for each row all the columns have a value (even if they
are empty).
6. If your CSV file uses nonstandard characters to separate fields and rows, you can
adjust the default setting for separators using the Separators tab.
7. Click Finish.
This tab lets you configure the following information for the data adapter:
• Data URL – Base URI for the request.
• Username and Password – Credentials for web services that require authentication.
• Request method – The method to use for the data adapter. Supported methods are
GET, POST, and PUT.
• URL Parameters tab – Parameters to append to the URI.
• POST/PUT Parameters tab – Parameters to send in the request body.
• POST/PUT Body tab – Data to send in the request body.
• Headers tab – Parameters to send in the HTTP header.
• The following additional information is shown:
• – The URL parameter in the data adapter has been associated with an HTTP
parameter in the report. The name of the report parameter is shown to the right.
This example uses a public API from a third party to generate a report. This API is not
controlled by Jaspersoft and is subject to change without notice.
3. Enter a name for your adapter, for example NOAA adapter, and click Next.
The Data Adapters Wizard is displayed.
4. Select the data adapter type that corresponds to the type of information the web
service provides. This example uses JSON.
5. Click Next.
6. Enter a name for your adapter. This name is used when you select an adapter for a
report.
7. In the File/URL field, enter the base web services request for your data. You want
this request to be general enough that you can use it for multiple datasets and
reports, but you also want it to contain as much reusable information as possible.
For example, for NOAA, you might enter this request:
https://www.ncdc.noaa.gov/cdo-web/api/v2/data?datasetid=GHCND
8. Select Use the report JSON expression when filling report.
9. Click Options to open the Http Connection Options dialog to configure additional
request parameters. You can later configure these parameters in your report.
• startdate: Set Name to startdate and Value to the current date. (Note: The
NOAA parameter startdate is optional and defaults to the current date.)
• enddate: Set Name to enddate and Value to the current date. (Note: The NOAA
parameter enddate is optional and defaults to the current date.)
• Click the Http Headers tab to add headers to the HTTP request. To do this, click
Add, enter the name and value of your parameter in the Parameter dialog and
click OK. For this example, add the NOAA token you requested:
• token: Set Name to the NOAA parameter token and Value to the NOAA key you
requested previously.
10. Click OK.
11. Click Test Connection to verify the data can be received.
3. Enter the objects that you want to use in your dataset. For this example, enter
results. If you only wanted to get the datatype values for each record, you could
enter results.datatype.
4. Click Read Fields to load the list of fields in the dataset.
5. To optionally preview a subset of the data, select the Data preview tab, then click
Refresh Preview Data.
6. Click OK.
2. Set the number of empty records that you need. Remember, whatever field you add
to the report, its value is set to null. Since this data adapter does not care about
field names or types, this is a perfect way to test any report (keeping in mind that
the fields are always set to null).
3. Click Finish.
4. Name the adapter and set the number of records that you need.
5. Click Finish
To create a global random data adapter that you can use in different projects, go to the
Project Explorer and select New > Data Adapter from the context menu. Global data
adapters cannot be accessed from JasperReports Server or JasperReports IO project
types.
this directly. This section is useful if you want to understand more about the direct data
adapters, or if you are interested in creating a custom data adapter.
package net.sf.jasperreports.engine;
public interface JRDataSource
{
public boolean next() throws JRException;
public Object getFieldValue(JRField jrField) throws JRException;
}
The next method is used to set the current record into the data source. It has to return true
if a new record to elaborate exists. Otherwise it returns false.
If the next method has been called positively, the getFieldValue method has to return the
value of the requested field or null. Specifically, the requested field name is contained in
the JRField object passed as a parameter. Also, JRField is an interface through which you
can get information associated with a field—the name, description, and Java type that
represents it.
Now try writing your personalized data source. You have to write a data source that
explores the directory of a file system and returns the found objects (files or directories).
The fields you create to manage your data source are the same as the file name, which
should be named FILENAME; a flag that indicates whether the object is a file or a directory,
which should be named IS_DIRECTORY; and the file size, if available, which should be
named SIZE.
Your data source should have two constructors: the first receives the directory to scan as a
parameter. The second has no parameters and uses the current directory to scan.
Once instantiated, the data source looks for the files and the directories present in the way
you indicate and fills the array files.
The next method increases the index variable that you use to track the position reached in
the array files, and returns true until you reach the end of the array.
import net.sf.jasperreports.engine.*;
import java.io.*;
public class JRFileSystemDataSource implements JRDataSource
{
File[] files = null;
int index = -1;
public JRFileSystemDataSource(String path)
{
File dir = new File(path);
if (dir.exists() && dir.isDirectory())
{
files = dir.listFiles();
}
}
public JRFileSystemDataSource()
{
this(".");
}
public boolean next() throws JRException
{
index++;
if (files != null && index < files.length)
{
return true;
}
return false;
}
public Object getFieldValue(JRField jrField) throws JRException
{
File f = files[index];
if (f == null) return null;
if (jrField.getName().equals("FILENAME"))
{
return f.getName();
}
else if (jrField.getName().equals("IS_DIRECTORY"))
{
return new Boolean(f.isDirectory());
}
else if (jrField.getName().equals("SIZE"))
{
return new Long(f.length());
}
// Field not found...
return null;
}
}
The getFieldValue method returns the requested file information. Your implementation
does not use the information regarding the return type expected by the caller of the
method. It assumes the name has to be returned as a string. The flag IS_DIRECTORY as a
Boolean object, and the file size as a Long object.
The next section shows how to use your personalized data source in Jaspersoft Studio and
test it.
import net.sf.jasperreports.engine.*;
public class FileSystemDataSourceFactory {
public static JRDataSource createDatasource()
{
return new JRFileSystemDataSource("/");
}
}
This class, and in particular the static method that is called, runs all the necessary code for
instancing the data source correctly. In this case, you create a JRFileSystemDataSource
object by specifying a way to scan the directory root ("/").
Now that you have defined the way to obtain the JRDataSource you prepared and the data
source is ready to be used, you can create the connection through which it can be used.
Create a connection as you normally would (see Working with Database JDBC
Connections), then select Custom implementation of JRDataSource from the list and
specify a data source name like TestFileSystemDataSource (or whatever name you want),
as shown below.
Next, specify the class and method to obtain an instance of your JRFileSystemDataSource,
that is, TestFileSystemDataSource and test.
There is no automatic method to find the fields managed by a custom data source.
In this case, you know that the JRFileSystemDataSource provides three fields: FILENAME
(String), IS_DIRECTORY (Boolean), and SIZE (Long). After you have created these fields,
insert them in the report’s Detail band.
Divide the report into two columns and in the Column Header band, insert Filename and
Size tags. Then add two images, one representing a document and the other an open
folder. In the Print when expression setting of the Image element placed in the foreground,
insert the expression $F{IS_DIRECTORY}, or use as your image expression a condition like
the following:
($F{IS_DIRECTORY}) ? “folder.png” : “file.png”
In this example, the class that instantiated the JRFileSystemDataSource was very simple.
But you can use more complex classes, such as one that obtains the data source by calling
an Enterprise JavaBean or by calling a web service.
This version of Jaspersoft Studio was verified with Spotfire version 7.7. Other versions
may also work but have not been tested extensively.
You can also create reports against SBDFs ; to do so, select one from your Spotfire
library.
6. If you have prompts in your information link and want to set their values using
parameters in Jaspersoft Studio, make sure Use a query (required to use
parameters) is selected.
7. Click OK.
8. Click Test to test your connection.
9. If the test fails, check your URL, credentials, and resource ID.
10. When the test succeeds, click Finish.
It is not uncommon for an Information Link to return millions of rows of data, which
may take some time for Jaspersoft Studio to process when data is loaded, such as when
previewing the report; the same may hold true in JasperReports Server.
7. Click OK.
You are ready to publish your report.
Range
Class Type – java.lang.String
Default Value Expression – The default value expression must be two Strings with a caret
(^) between them. Most often, you want to create three parameters in Jaspersoft Studio:
two parameters that define the endpoints of the range and the third parameter of type
String that is used to pass the range to Spotfire. The endpoint parameters should
correspond to the type of the prompt.
For example, for a Range prompt of type DateTime, you might create two parameters of
type java.sql.Timestamp that are used to take input for the start and end time:
Then you would create a dependent parameter that uses these two parameters to
construct a string to pass to Spotfire:
Multiple selection
Class Type – java.util.Collection; the objects in the collection should correspond to the type
of the prompt. The data adapter mechanism formats the Collection contents appropriately.
Sample Default Value Expression – Arrays.asList(1,2,3,4,5,6,7)
Single selection
Class Type – Corresponds to the type for the prompt. Numbers (and Currency) are passed
with a “9.9999” format; no $ or , are used.
Creating Queries
Jaspersoft Studio provides tools to help you define report fields and create a proper query
(if a query is needed to fetch the report data). You find these tools in the Dataset and
Query dialog.
It also provides a drag-and-drop query builder for easily creating SQL queries. This allows
users who are not familiar with SQL to join tables and produce complex data filters and
where conditions quickly. SQL Builder also provides a way for skilled users to explore the
database and list the metadata such as schemas and available tables.
This chapter contains the following sections:
• Using the Dataset and Query Dialog
• Working with the Query Builder
Use the Dataset and Query dialog to configure your dataset as follows:
• Select a data adapter from the menu next to the icon. Usually a data adapter is
selected, but you can change it.
• Select a query language for the current dataset from the Language menu. (This can
be the main dataset or a subdataset that populates a chart or a table.)
• Enter a query. A query editor is available for several languages including SQL, XPath,
JSON, and the Ad Hoc Query API query language.
• Click Read Fields to enable Jaspersoft Studio discover fields for you. These can be
provided directly by the data adapter or by running the query and reading the
response metadata.
For certain types of data adapters, below the data adapter menu let you view additional
information about the data adapter.
• For Java Bean data sources, view the configuration on the Java Bean tab.
• For data adapters that get their information via a web service, use the Data Adapter
tab.
The tabs at the top provide the user interface for working with your data adapter:
• Query tab – Displays a language and query editor that helps you construct the query
for your dataset.
• Java Bean tab – Displays a tool that helps you introspect a Java class and build
dataset fields from the fields in the class. This is useful for Java data sources.
• Data Adapter tab – Displays any additional user interface specific to the chosen data
adapter type.
Use the tabs at the bottom to perform the following additional tasks:
• Add, edit, or remove fields on the Fields tab.
• Add, edit, or remove parameters on the Parameters tab. See Managing Parameters
Using the Parameters tab in the Dataset and Query Dialog for more information.
• Edit sort options for dataset records on the Sorting tab.
• Provide an expression to filter dataset records on the Filter Expression tab.
• Preview your data on the Preview tab, if supported by the selected data adapter.
• To show all available data adapters and query languages, click and choose Show
All Data Adapters (default).
• To choose a data adapter and restrict the query languages to ones compatible with
the chosen data adapter, click and choose Show Languages For Data Adapter.
• To choose a query language and restrict the view to compatible data adapters, click
and choose Show Data Adapters For Language.
• To configure this setting globally, click and choose Global Preferences, then make
your selection in the Preferences dialog.
This tab lets you configure the following information for the data adapter:
• Data URL – Base URI for the request.
• Username and Password – Credentials for web services that require authentication.
• Request method – The method to use for the data adapter. Supported methods are
GET, POST, and PUT.
• URL Parameters tab – Parameters to append to the URI.
• POST/PUT Parameters tab – Parameters to send in the request body.
• POST/PUT Body tab – Data to send in the request body.
• Headers tab – Parameters to send in the HTTP header.
• The following additional information is shown:
• – The URL parameter in the data adapter has been associated with an HTTP
parameter in the report. The name of the report parameter is shown to the right.
• – The URL parameter in the data adapter has a default value.
Discovering Fields
Defining all the fields of a report by hand can be tedious. JasperReports requires all report
fields to be named and configured with a proper class type. The Dataset and Query dialog
simplifies the process by automatically discovering the available fields provided by a data
adapter, without using a query. To run a query, you need to use the proper data adapter:
for example, to run an SQL query you must use a JDBC data adapter. The Read Fields
button starts the discovery process: the fields found are listed in the Fields tab and added
to the report. Click OK to close this window.
Some query languages, like XPath, do not produce a result that resembles a table, but
more complex structures that require extra steps to correctly map result data to report
fields. An example of this is the multidimensional result coming from MDX results (MDX is
the query language used with OLAP and XML/A connections): in this case, each field is
mapped using one or more properties depending on the requirements of the data. For
some languages, such as instance XPath and JSON query, the Query dialog displays a tool
that simplifies the creation of both the query and the mapping.
The builder has two parts. On the left a tree-view shows all the available schemas and
relative objects like tables, views found by using the JDBC connection provided by the data
adapter. On the right, there are three tabs that present the query in different ways.
The first Text tab contains a text area for writing a query. You can drag tables and other
objects from the metadata view into the text area, so you do not have to write the entire
qualified names of those objects. Although the SQL builder does not support arbitrary
complex queries (which may use database-specific syntax), this text area can be used for
any supported query, including stored procedures if supported by the report query
executer.
If a query has already been set for the report, this text area shows it when the query dialog
is open.
Use the Outline and Diagram tabs to build the query visually. The current version of
Jaspersoft Studio does not support back-parsing of SQL. For this reason, you should use
Outline and Diagram editing mode only to create queries, otherwise the new query
replaces any existing query. If you do attempt to overwrite an existing query, Jaspersoft
Studio alerts you.
The Outline view is a good tool for people with a basic understanding of SQL. It works with
the Diagram view, which represents the simplest way to design a query. In the outline view,
the query is split in its main parts introduced by the relative keyword. Those parts include:
SELECT introduces the portion of the query where is listed all the columns that form a
record of the final result set (which is basically a list of records).
FROM contains the list of tables involved in our queries and if specified the rules to join
that tables.
WHERE is the portion of the query that describes the filters and conditions that the data
must satisfy to be part of the final result, conditions can be combined by using the OR and
AND logical operators and can be aggregated by using parentheses.
GROUP BY indicates a set of fields used to aggregate data and is used when an aggregation
function is present in the SELECT. For example, the following query counts the number of
orders placed in each country.
SELECT
count(*) as number_of_orders,
Orders.country
FROM
Orders
GROUP BY
Orders.country
HAVING works a bit like a WHERE, but it is used with aggregate functions. For example, the
following query filters the records by showing only the countries that have at least 40
orders:
ORDER BY specifies a set of columns for sorting the result set.
SELECT
count(*) as number_of_orders,
Orders.country
FROM
Orders
GROUP BY
Orders.country
HAVING
count(*) > 40
The Diagram view shows the tables in the query with the relative join connections and the
selected fields. This view is very useful, especially to select the relevant fields and easily
edit the table joins by double-clicking the connection arrows.
Selecting Columns
You can drag columns from the database explorer into the SELECT node or other nodes in
the outline view. Make sure the columns that you select are from tables present in the
FROM part of your query.
You can also select fields by their checkboxes in the diagram view.
Finally you can add a column by right-clicking the SELECT node in the outline view and
selecting Add Column. A new dialog prompts you to pick the column from those in the
tables mentioned in the FROM clause. If a column you want to add is not a table column,
but a more complex expression, for instance an aggregation function like COUNT(*), add it
by right-clicking the SELECT node in the outline view and selecting Add Expression.
When a column is added to the query as part of the SELECT section, you can set an alias
for it by double-clicking it.
Aliases are useful when you have several fields with the same name coming from two
different tables.
Joining Tables
You can join tables you have added by selecting shared fields. You can create the
relationship in the Diagram view by dragging a column of the first table onto the column of
the table you are joining to. You can edit this type of join by double-clicking the join
arrows. Currently a single join condition is supported.
You can also edit joins in the outline view by right-clicking a table name and selecting Add
or Edit Table Join.
You can organize conditions by creating condition groups, and then combining them with
or and operators. At least one condition must be true for an OR group. All conditions must
be true for the AND operator. You can double-click to change the value of either of these
group operators.
If the value of a condition is not fixed, you can express it by using a parameter with the
expression: $P{parameter_name}.
When using collection type parameters, the $X{}expressions allow you to use operators like
IN and NOT IN, which determine whether a value is present in the provided list. The $X{}
syntax also allows you to use other operators like BETWEEN for numbers, Date Range, and
Time Range type of parameters. See Expression Operators and Object Methods for more
information about the $X{} syntax.
Acquiring Fields
When your query is ready, it is time to map the columns of the result set to the fields of the
report. When using SQL, this is a pretty straight forward operation.
Press the Read button to run the query. If the query is valid and no errors occur Jaspersoft
Studio adds a field for each column with the proper class type to the fields list.
Data Preview
Use the Data Preview tab to generate a ghost report that maps the fields to the fields tab
using your query and selected Data Adapter. This tool is independent of the query
language and a good way to debug a query or check, which records the dataset returns.
You can connect Jaspersoft Studio to JasperReports Server and move reports between the
two. Jaspersoft Studio uses web services to interact with the server.
Connecting with JasperReports Server enables you to:
• Browse the repository on the server from Jaspersoft Studio.
• Add reports and subreports to the repository from Jaspersoft Studio.
• Drag and drop images and other resources from the repository to Jaspersoft Studio.
• Add and delete folders and resources on the server from Jaspersoft Studio.
• Modify resource properties on the server from Jaspersoft Studio.
• Link input controls to reports on the server.
• Import and export data sources (JDBC, JNDI, and JavaBean).
• Download, edit, and upload JRXML files.
• Connect to multiple servers for access to both test and production environments.
• Create a report in Jaspersoft Studio based on a Domain in JasperReports Server
(commercial edition only).
This chapter contains the following sections:
• Connecting to JasperReports Server
• Configuring a Project for JasperReports Server
• Publishing a Report to JasperReports Server
• Working with JasperReports Server Templates
Connection icon .
The Server profile wizard appears.
3. Enter the URL, usernames, and password for your server. If the server hosts multiple
organizations, enter the name of your organization as well.
The defaults are:
• URL:
• Commercial editions: http://localhost:8080/jasperserver-pro/
• Community edition: http://localhost:8080/jasperserver/
The Server profile wizard automatically detects a server connection beginning with
https and displays a icon. See Connecting to JasperReports Server Over SSL for more
information.
• Organization: There is no default value for this field. If the server hosts multiple
organizations, enter the ID of the organization to which you belong.
You can also open the Trust Store dialog when you are creating a secure connection by
clicking Show Trust Store in the Security Certificate dialog.
The Trust Store dialog lets you do the following:
4. Enter the URL of your CAS server along with the username and password that you
want to use for access.
5. Click OK.
The CAS server is added to the list of available single sign-on servers.
6. Click OK.
4. If the server hosts multiple organizations, enter the ID of the organization to which
you belong. This can be the root organization (in which case you can leave this entry
bar blank) or another organization.
5. Select the CAS server that you want to use for this connection from the SSO Server
menu.
6. Click Test Connection to test the connection. This may take some time, especially
the first time you connect.
7. Click OK in the confirmation dialog.
8. Click OK to create the connection.
The JasperReports Server context is only a simulation. It does not include all the classes
and structure of JasperReports Server.
4. In the Workspace Folder section, browse to the project you want to associate with
this server instance.
5. Click Finish.
4. Open the Main.jrxml file in the editor. You can do this by double-clicking the file, or
by right-clicking the file and selecting Open in Editor.
5. When you open the Main.jrxml file in the editor, the report and all its resources are
copied to the associated project in Jaspersoft Studio. The path for the report in the
repository is duplicated in the Jaspersoft Studio project. To see this, open the
Project Explorer and navigate to the associated folder.
When you upload a report from Jaspersoft Studio to JasperReports Server, you can choose
one of the following options:
• Data Source from Repository – Use an existing JasperReports Server data source for
your report.
• Local Data Source – Create a JasperReports Server data source or upload a
Jaspersoft Studio data adapter file to use in your report.
• No Data Source – Change the data adapter information in your report.
If you are using a JDBC or JNDI data source, make sure that your connection uses the
same driver as your Jaspersoft Studio data adapter. For example, if you connect to an
Oracle database from a commercial edition, you can download and use the native
Oracle driver or you can use the Oracle JDBC driver that is included with Jaspersoft
Studio. If your driver in JasperReports Server does not match the driver used in
Jaspersoft Studio, you could see different data in your uploaded report.
• Click to publish your report and select a JasperReports Server instance and
repository location where you want to save the report. Then click OK. If you are
prompted to upload resources, select your settings.
• Select Data Source from Repository when prompted.
• Click ... and select the correct JasperReports Server data source from the repository.
• If you want to use a JNDI data source, first set up the JNDI connection for your
database in your application server. Make sure to use the same JDBC driver for your
Jaspersoft Studio adapter and the JNDI connection in JasperReports Server.
• Click to publish your report and select a JasperReports Server instance and
repository location where you want to save the report. Then click OK. If you are
prompted to upload resources, select your settings.
• Select Local Data Source when prompted.
• Click ... to open the Add Resource wizard.
• Select the type of data source that you want to create, for example, Datasource
JDBC, and click Next.
• On the Resource Editor page, enter a name and unique ID for the data source. You
can also enter an optional description. Then click Next.
• On the next page, manually fill in the required information for the data source you
want to create.
• Click Finish to create the data source and use it in your uploaded report.
For some types of data sources, such as JDBC, JNDI, and bean data sources, you can
publish a data adapter from Jaspersoft Studio and set it as the data source for the report:
• Make sure that the data adapter you want to upload is saved locally as an XML file in
the same project as your report. See Importing and Exporting Data Adapters for
information about exporting a global data adapter to your project; see Copying a
Data Adapter for information about copying a data adapter from one project to
another.
• The Import dialog shows a list of local and global adapters. Make sure to select a
local adapter, which includes the name of a file. Click OK then Finish to select the
adapter.
• Click Finish to publish the report and the selected data adapter to the repository.
If you are using a custom data adapter or any other adapter that uses one or more jars
that are not included in JasperReports Server, add the jars to a location on your server
classpath.
No Data Source
Use No Data Source when you have configured net.sf.jasperreports.data.adapter in your
JRXML, as described in Default Data Adapter. Setting net.sf.jasperreports.data.adapter lets
you use multiple data adapters in the same report, for example, using a different data
adapter for a subreport.
To use this option:
• Set the default data adapters for the datasets and subdatasets used in your report,
as described in Default Data Adapter.
• Follow these guidelines when setting default data adapters in a report that you want
to publish:
• Do not use global data adapters. The default data adapter must reference a local
file in the same project as your report, or a data adapter already in your
repository.
• Where possible, use inheritance to reduce the number of times you actually set
the default data adapter. If your report uses a specific adapter multiple times, try
to structure the report so that the data adapter is set for a single dataset and
other datasets inherit it. For example, if you have a crosstab and a table that use
the same data adapter, you could create a subreport that contains the table and
crosstab. Then if you set your data adapter as the default for the subreport, the
table and crosstab inherit this adapter. Reusing the data adapter improves
performance when you run the report.
• Publish your report and select No Data Source when prompted.
• When you publish the report, the default data adapters are uploaded to the
repository.
2. Click the Publish Report button in the upper-right corner of the Designer. The
Report Publishing Wizard opens.
6. Select any resources that you want to upload with your report and check the box if
you want to overwrite previous versions of those resources. Click Next. The
Configure the data source window opens.
7. Select a data source configuration. See Choosing a Data Source for a Published
Report for more information.
8. Click Finish. The report is uploaded to the server. If there are no errors, an
appropriate message is shown.
JasperReports Server includes several templates that affect the layout of your reports. You
can add custom templates to your JasperReports Server instance by uploading a JRXML file
to a Templates directory. In addition to font and color choice, templates can contain
images such as logos. In a JasperReports Server template, the absolute path of an image is
in the repository and cannot be overwritten. Other users can apply your template by
selecting Custom Report Template when they create a report from an Ad Hoc View.
To create a template
1. Connect to JasperReports Server as superuser.
The document will look empty, but if you click the Source tab, you see that
attributes are set at the JRXML level. Note the attributes for ChartTitle:
<style name="ChartTitle" forecolor="#000000" fontName="DejaVu Sans" fontSize="12"
isBold="true"/>
You can edit styles directly on the Source tab if you choose.
4. Click the Design tab and in the Outline view, click the arrow next to Styles.
5. Click ChartTitle. The styles open in the Properties view.
You can link to an image in your template by uploading the image to the repository and
then dragging it into the appropriate band in the template. The template uses the
absolute path to the image in the repository and the image cannot be changed or
overwritten.
1. In the Repository Explorer, expand the Servers node and select the JasperReports
Server instance where you want to put the Topic.
If you have not created any server connections, create one before proceeding. For
more information, see Connecting to JasperReports Server.
2. Navigate to the Topic folder. For example, if you are logged in as jasperadmin,
navigate to Ad Hoc Components > Topics.
3. Right-click the Topics folder and select New. The Add Resource wizard appears.
4. Click Report Unit and click Next.
5. Enter a name and optional description it and click Next.
6. Select the Local Resource radio button and click to locate and select the JRXML
you created above. For example, click Upload/Download Resource, click Upload
from Workspace, select the my-topic.jrxml file.
7. Click OK to close the upload window and click Next.
8. Click the Data Source from Repository radio button and click to its right.
9. Navigate to Analysis Components > Analysis connections, select the SugarCRM data
source, and click OK.
10. Click Finish to upload the report unit to the Topics folder so it can be used in the
JasperReports Server Ad Hoc Editor.
If the Topic includes fields with unusual datatypes, those fields do not appear in the Ad
Hoc Editor because JasperReports Server is not equipped to manage them properly. For
example, if the Topic is defined against a MongoDB instance that returns data of type
array, this field is not available in the Ad Hoc Editor. For more information on datatype
support in the Ad Hoc editor, see the JasperReports Server Administrator Guide.
When you create a JRXML file for use as a Topic, you can specify the name to display for
each field the Topic returns. To do so, define a field property named adhoc.display for each
field declared in the JRXML. The adhoc.display field property must have the following
syntax:
<property name=”adhoc.display” value=”Any Name”/>
For example, this JRXML code declares a StoreState field displayed in reports as Store
State:
Topics also support the $R expressions for field names; for more information, see
Expressions.
For fields in a non-domain topic the following properties may be of interest:
• dimensionOrMeasure, which marks a field as a field or a measure
• defaultAgg, the aggregation to use for this measure (for example, avg)
• semantic.item.desc, a description of the field
• DefaultMask, which sets a measure as a $ or date
• Running a Report
• Editing a Report
• Creating and Uploading Chart Themes
If you choose to add an item other than a JasperReport, a dialog allows you to enter
information about the object. If you choose to add a JasperReport, a wizard guides you
through the process. For the best results when adding a JasperReport, open the JRXML
in Jaspersoft Studio and click . Follow the steps in the wizard to publish your report.
See Publishing a Report to JasperReports Server
• To add an Azure certificate, right-click a folder, select New, then select Azure
Certificate. Similarly, you can add a secure file.
If you are logged in as a user with sufficient access rights (such as jasperadmin or
superuser), you can modify property values and save them back to the repository.
Running a Report
Connect to JasperReports Server to test the report changes that you make in Jaspersoft
Studio. For more information, see Connecting to JasperReports Server.
Navigate to your report's JRXML, and click Run Report Unit. If prompted to save the report
unit, specify a location on your local computer and click OK. If the report has input
controls that require values, you are prompted to specify them. The report appears in a
browser window.
Editing a Report
In the Repository Explorer, the icon means a report unit, and means a JRXML file.
When you work with a JRXML file in the Repository, Jaspersoft Studio operates on a copy
of the file. You need to upload the JRXML file to put it back into the repository when
finished.
• Top of Page: the controls are shown at the top of the report viewer.
• In Page: the controls are shown next to the report viewer.
Input controls can be created in the JasperReports Server repository and referenced in
reports. If you want to use an input control from JasperReports Server in a report, the
input control must meet two conditions:
• The parameter name in the input control must correspond to the name of the
parameter in the report. No error occurs for a mismatch, but at run time NULL is
passed instead of the actual value of the parameter.
• The input control and its corresponding parameter must be of compatible
datatypes (for example, both must be text types or date types). If there is a
mismatch, the report fails and an exception is returned.
6. You can also use the JSP field to modify the appearance of the controls. Specify a
name of a JSP file in WEB-INF of the server's host to define the page that displays
input controls.
7. Click Finish.
Jaspersoft Studio supports only the most common options provided by JFreeCharts.
4. In the Outline view, select each category and review the available options in the
Properties view.
5. Select a property to change its value.
Depending on the nature of the property, you might type text, select a color, check
or clear a checkbox, or select a value from a dropdown. As you update the chart
theme, the Preview tab shows your changes. For example, select Title in the Outline
view and choose Bottom from the Position dropdown to move the title beneath the
chart.
6. Click a chart type in the Preview tab to zoom in to examine the effects of your
changes more closely. Click again to zoom out.
7. To view the XML that defines the chart theme’s appearance, click the Source tab.
8. When you are satisfied with the chart theme, click File > Save to save the chart
theme. This saves the chart theme to your local hard drive.
2. Choose the location where you want to save your JAR. To upload to a JasperReports
Server instance, select your server instance and then select the Templates directory.
To create a jar on your current system, select a location on your hard drive.
3. Enter a file name and theme name for your theme.
4. If you want to use the theme to design reports on your current system, save to a
location on your hard drive and select Add the jar to the CLASSPATH to use the
theme in the report designer.
5. Click OK. The chart theme is exported as a JAR.
Once you have uploaded a theme to JasperReports Server, you can use the repo: syntax
in your reports to specify this JAR as your chart theme. The theme can be used at the
report or server level in JasperReports Server. For more information, refer to the
JasperReports Server Administrator Guide.
Domains are structures for managing data in JasperReports Server. They connect to a
normal data source and select tables and columns, join them to others, arrange the results
into business-related sets, give them meaningful labels, and provide access security based
on users and roles. Through the server UI, users can then create reports interactively with
the Ad Hoc editor, and the Domain acts as the data source, providing a curated view of
your database.
Jaspersoft Studio can also create reports based on the domains defined in JasperReports
Server. Such reports use a data adapter to load data accessed through a domain. Then
there are two different query languages that you can use with a domain: the "jasperQL"
query language and the earlier "domain" query language.
The jasperQL language was introduced in version 7.8 and has better support for input
controls and lets you order records by a field and limit the number of records shown. You
can also group by one or more fields in the Dataset and Query dialog. Jaspersoft
recommends using the more advanced jasperQL language.
Before your report can access a domain with either query language, consider the following
requirements:
• Make sure that your domain is fully defined and saved on the server. For information
about creating domains, see JasperReports Server Data Management Using
Domains. The examples in this section use the supermart sample domain.
• Make sure that JasperReports Server is online.
• Optional: Define the server profile or connection object, as described Connecting to
JasperReports Server. You do not need the server profile to create and run a domain
report, but you need it to publish the report back to the server.
• Create a data adapter for the server connection, as described in the next section.
The data adapter may also identify the domain on the server, or the report may
specify the domain.
1. In the Repository Explorer, click or select File > New > Data Adapter from the
menu. In the Data Adapter Wizard that appears, double-click Jaspersoft Server.
Alternatively, you can edit the empty Jaspersoft Server Data Adapter that is created
by default as a template. Double-click it in the Repository Explorer panel to open it
for editing in the Data Adapter Wizard.
2. Enter a name for the data adapter, usually the name of the domain.
3. Enter the URL to access your server, ending in jasperserver-pro/, or click to select
from the list of saved servers.
4. Enter the username and password to access your server. If you access a domain in
an organization, specify the credentials of a user or administrator in the
organization, including the organization name or alias. It is good practice to use the
credentials of the least permitted user who still has access to the domain or
domains you want to access. If you have reports with different Domains using the
same data adapter for this server, make sure that the user has access to all Domains
and all the data that you need in the Domains.
A domain may restrict access to its data based on the user who accesses the data.
Restrictions can be based on usernames, roles, attributes, or any combination of these.
Depending on how your domain is defined, the credentials you choose here may affect
the data that appears in reports that use this adapter. If you access multiple domains,
the data from each of them may be affected by the user given here.
5. Click Test to make sure your server is accessible and the credentials are valid.
6. Optional: enter the repository URL of your domain or click to browse for it. If you
only access one domain on the server, specify it here. If you have several domains,
each report can specify the domain that it uses.
When browsing, you can enter a name and select it from the results, or navigate the
repository tree that is accessible to the user you specified. Mouse over a resource to
see its description and details.
2. Click or select File > New > JasperReport from the menu. The New Report Wizard
is displayed.
3. Select a template and click Next.
4. Select a location to save your report, enter its name, and click Next.
5. Select the data adapter for your domain or server, in this example we use
"Supermart Domain."
The wizard refreshes to show the query language, the pathname of the Domain and
the fields of the Domain that are available.
The default query language is jasperQL. You can select a different domain on the
server if needed, and the dialog updates the available fields. The domain being used
is stored in the report itself, therefore it may be different from the one in the data
adapter.
6. Select fields or folders in the Domain on the left of the dialog, and drag them to the
Fields item on the right to create fields. For example, drag Sales > Stores.
The items are added as a flat list, using the labels from the Domain. At this point,
you can refine the query by adding fields to filters, group by, and order by headings.
These actions are covered in detail in the next section Using the jasperQL Query
Designer.
7. When done, click Next to select the dataset fields. These are the fields that appear in
the report outline for use in creating the report. In this simple example, click to
add all fields.
Figure 155: Fields of the Query Result Selected for the Report
8. Click Finish and the report appears in a new tab with a blank canvas. The elements
and fields of the report appear in the report outline. When you mouse over the
fields, you see the field's label from the domain.
9. Define your report as usual, using the Palette and Outline to add and organize
components.
10. Click Preview to test your report. Jaspersoft Studio compiles your report. If it is
successful, your report is filled and displayed.
11. You are prompted to publish your report on save, or click to publish your report.
For more information, see Publishing a Report to JasperReports Server.
Figure 157: Editing a jasperQL Query in the Dataset and Query Dialog
The panel at the bottom of the Dataset and Query dialog displays the fields that are
selected from the query results (the dataset) for use in the report. If you configure the
jasperQL query fully, you reduce the results so they contain exactly the fields you need. In
that case, click the Read Fields button to "read" all the query result fields into the report,
and they replace any in the Fields tab at the bottom.
The panel at the bottom also has a Data Preview tab for testing the query. Use its controls
to run the query and see the values returned for the fields you have chosen or created. For
example, this lets you check your aggregation, grouping, and expected calculated field
values. This is particularly useful to test any DomEL expressions in your query elements.
The query designer has a Text tab that displays the text of the current query for
information purposes. The jasperQL query is a JSON text that is sent to the server through
a private API. The syntax of the JSON is also private, and editing the query on the text tab
is not recommended.
On the Designer tab, you can create a query of your domain by dragging and dropping
fields, entering expressions, and clicking for certain actions. The elements of the query are
structured like an SQL query. The result is a query that is easy to create and easy to
interpret:
Use the following interactive features of the jasperQL query designer to create your query:
Selecting Fields
Select fields or folders in the Domain on the left of the dialog, and drag them to the Fields
heading on the right to create fields. These are the fields that are returned by the query.
You can have many fields, and later use only the ones you need in the report, or you can
select exactly the fields that you need for the report. The items are added as a flat list,
using the labels from the Domain.
You can mouse over a field name to see its name, ID, and type:
To remove a field from the list under the Fields heading, or any other heading on the right
side, right-click the field and select Delete from the context menu. You can also select the
field and use the Delete key.
To specify distinct values for all fields returned by the query, right-click the Fields heading
and select Set/Reset DISTINCT. You can also double-click the Fields heading to toggle the
setting.
The alias is also useful for giving fields a simple name wherever they appear in Jaspersoft
Studio. Otherwise, the fields are known by their ID, for example: sales_fact_ALL.sales.store_
features.store_sqft.
Filtering Results
Defining a filter in the query reduces the size of the results and means that your report
processes only the rows of data you are interested in. To define a filter, drag a single item
from either side to the Filters heading on the right, or right-click on the item and select
Add to Filters. Choose the comparison operator from the dropdown menu; the available
operators depend on the field type.
Type the comparison value for the filter or click ... to select from a list of available values.
Jaspersoft Studio queries the data through the Domain to display the list. The results
include rows of data for other fields chosen so far. Double-click any row to insert the
bolded value as the comparison value in the filter.
Alternatively, you can right-click the comparison value field and select Parameter or
Function to use JasperReports parameters or functions that you have already defined. Each
of those options brings up a dialog where you can specify the parameter or function. For
example, parameters can be used to compare values against input controls that you have
defined in the report. When using parameters in filters, be sure to define default values for
the parameters to avoid unexpected errors.
For more information on parameters, see Parameters.
Repeat these steps for each filter that you want. For the second filter and each one
thereafter, a menu in the filter expression dialog lets you choose to AND or OR your filter
with the previous one.
To change the operator or value of a filter, double-click it on the right-hand panel. You can
also drag filters to change the order of composition. Finally, you can double-click the
Filters heading and select Replace DomEL Filter. This special filter allows you to write
DomEL expressions on both sides of the operator and compare them.
Grouping Rows
To group by a field, drag the field from the left to the Group By heading on the right, or
right-click on the item and select Add to Group By. Unlike SQL queries, the field being
grouped by must not be selected in the list of fields on the right. In the Group By dialog
you can enter an alias for the field in the AS text box, but it is not required:
Ordering Rows
To order the results by the value of a field, drag the field to the Order By heading on the
right, or right-click on the item and select Add to Order By. The default ordering is
ascending, but you can double-click the item and change the direction of ordering.
Limiting Rows
To limit the number of items shown in your report, double-click the Limit heading in the
right-hand panel and enter the maximum number of rows to return from the query. For
example, if you are working with a large dataset, you might want to limit the time it takes
to run while you are designing your report.
<imageExpression class="java.lang.String">
<![CDATA["repo:AllAccounts_Res2"]]>
</imageExpression>
When you publish a report to JasperReports Server and upload your resources,
Jaspersoft Studio updates the JRXML in the published report to use the repo: syntax
to refer to the uploaded resources in the repository.
• repo: used with a path – A resource saved somewhere in the repository. For
example, to refer to an image in the repository, you might see JRXML like this:
<imageExpression class="java.lang.String">
<![CDATA["repo:/Images/myimage.jpg"]]>
</imageExpression>
5. Drag the _ScheduledTime element from the Outline View to a valid location, such as
the Title Band, in the Designer:
6. Now you can set other properties, such as the text color of the date/time stamp. In
Properties, check Blank when Null to prevent the word null from appearing on the
report when it runs unscheduled.
7. Compile the report, and upload it to JasperReports Server. For more information
about uploading reports to JasperReports Server, see Accessing JasperReports
Server from Jaspersoft Studio.
8. In the server, schedule the report to run immediately.
9. Open the output file.
Figure 173: Output Showing the Scheduled Time the Report Actually Ran
The date and time the report actually ran appears in the output, as well as the scheduled
time. In the screenshot above, there was a 13-second delay between the scheduled start
time and the actual run time.
The built-in JasperReports IO preview engine only works for files located in your
workspace. It is not available for previewing linked files outside your workspace.
JasperReports IO comes with sample reports and resources in its repository for you to use.
Repository Directories
Directory Description
data Contains the data source adapters and data source files for your reports.
JasperReports IO supports the following types of data adapters:
• JDBC connection
• CSV connection
• Excel connection
• Empty connection
• JNDI connection
• Remote XML connection
You can create your own data adapters for JasperReports IO either by using
the DataAdapter Wizard or by creating a custom data adapter using an XML
file. See Creating and Editing Data Adapters for more information.
JR-INF Contains the configuration files for report execution. See JasperReports IO
Report Execution Contexts for information on creating the files.
The report execution context is defined using a context.xml file in the folder named JR-INF,
which has the same parent folder as the report's main template file.
For example, a report that stores its JRXML template file at
/samples/reports/chartcustomizers/ChartCustomizersReport.jrxml within the JasperReports
IO repository must use /samples/reports/chartcustomizers/JR_INF/context.xml for its report
execution context file.
If multiple report templates are stored in the same folder, they share the samereport
execution context file found in the JR-INF subfolder. If you do not want a report template
to share its report execution context with any other reports, it needs to be in its own
subfolder along with the JR-INF folder containing the context.xml file.
Parent Context
Report execution contexts inherit the classpaths and properties from other context files
and you can control which files it inherits from.
• Folder Inheritance (Default)
By default, any report execution context stored in a JR-INF folder inherits from the
contexts stored in the JR-INF folders that are found in all parent folders up to the
root folder of the repository.
• Direct Inheritance
You can specify a path to a parent context by using the <parentContext> tag in the
context file as follows:
<context>
<parentContext>
<path>/parent</path>
</parentContext>
...
</context>
The path needs to specify the absolute repository path to the parent folder
containing the target JR-INF context that you want to use as the parent context.
Notice that the path specifies only the parent folder of the target report execution
context and does not specify the JR-INF folder.
For example, if you want the report execution context at
/samples/reports/chartcustomizers/JR-INF/context.xml to inherit from the context
located at /samples/reports/unicode/JR-INF/context.xml, you need to add the
following to the context.xml file:
<context>
<parentContext>
<path>/samples/reports/unicode</path>
</parentContext>
...
</context>
The report execution context is also inherited from the parents of the specified
context, up to the root folder of the repository.
Classpath
As a Java reporting library, JasperReports has various extension points that allow the
customization of its functionality using custom code in the form of compiled Java classes.
These classes are among the various types of resources that a report might need at
execution time and they can also be stored in the repository, along with the subreports,
style templates, images, fonts, and other report resources.
The custom Java classes needed during a certain report execution need to be packaged as
JAR files and placed in the repository, preferably under the JR-INF/lib subfolder of the
report execution context that uses it.
The JAR then needs to be referenced from within the target context.xml file using a pair of
<entry><path> tags within the <classpath> tag so that it is loaded by the JasperReports IO
reporting service when it runs the report.
For example, a report can use the custom Java code packaged in
/samples/reports/chartcustomizers/JR_INF/lib/repo-sample.jar JAR file when it is
referenced in the context.xml file as follows:
<context>
<classpath>
<entry><path>/samples/reports/chartcustomizers/JR-INF/lib/repo-
sample.jar</path></entry>
</classpath>
...
</context>
Properties
JasperReports IO can use JasperReports Library configuration settings to define specific
behavior in reports.
Some of these configuration settings can be set at the report context execution level by
using the <property> tags in the context.xml file.
The following is an example of setting the chart render type configuration property:
<context>
...
<properties>
<property>
<name>net.sf.jasperreports.chart.render.type</name>
<value>svg</value>
</property>
...
</properties>
</context>
b. Create top-level folder - Select this option if you want the selected top-level
directory of the repository to be recreated as part of the project. If you do not
select this option, Jaspersoft Studio imports the contents of the selected
directory directly into the project folder.
The options under Advanced allow you to create links to files located outside of your
workspace. However, the built-in JasperReports IO preview engine only works for files in
your workspace. It is not available for previewing linked files located outside your
workspace.
You can change the repository type of any folder in your workspace to one of the
JasperReports IO instance, the web application server will attempt to use port 8081 and
will continue to try the next port until it finds one that is not in use. You can specify a
different port for JasperReports IO to use when it starts by setting a new starting port.
Jaspersoft Studio keeps the web application server running until you delete the project or
close Jaspersoft Studio.
If you have multiple JasperReports IO projects in Jaspersoft Studio, each one uses its
own web application server. You can have multiple JasperReports IO instances running
on different ports at the same time until you delete a project or close Jaspersoft Studio.
Jaspersoft Studio starts a web application server for the first time when you preview a
report with JasperReports IO. One server per project uses a free default port 58080. In
case you want to change the port range, you can do it from the preference page and
restart the studio.
Jaspersoft Studio saves the report template with a new parameter that specifies the data
source type and path.
If you change the data source or enter any new input parameters, click the button to run
the report.
Exporting the HighCharts-based report with the JasperReports IO plug-in can be done
by using Chrome/Chromium. The application auto-detects the Chrome/Chromium in the
eight predefined locations.
If the application does not find Chrome/Chromium in these predefined locations, then
point the application to the location of the Chrome/Chromium by specifying the path to
the Chrome executable in net.sf.jasperreports.chrome.executable.path property in the
following file:
[JSS_INSTALL]/jrio/jrio/WEB-INF/classes/jasperreports.properties
l Install Jaspersoft Studio using the .zip package that can be easily extracted to the
desired location.
Consider the 'maximum path length limitation' when choosing the install or extract
location. For more information, refer Maximum Path Length Limitation.
This is a problem, especially with Eclipse-based products, that usually have a deep
nested directory hierarchy.
Understanding Datasets
Datasets allow the engine to iterate through virtual records, just as data sources do, but
they also enable calculations and data grouping using variables and groups. However, they
have no visual or layout information and do not specify how to find the data that is used to
fill the element at run time.
A report can include two types of datasets:
• Main Dataset – The main dataset is responsible for iterating through the data source
records, calculating variables, filtering out records, and estimating group breaks
during the report-filling process. The report data source, along with the parameters,
fields, variables, and groups declared at the report level, represent the building
blocks of the main dataset for the report. All report templates implicitly declare and
use this main dataset.
• Subdataset – You can use a subdataset to provide a secondary record nested within
a report. A subdataset iterates through its data source records similar to a dataset.
However, a dataset can use the same connection that is used to fill the master
report or it can use a different connection or data source. Subdatasets can be used
to iterate through data that is not the main report data source itself, for example, to
gather data for a chart or perform data bucketing for a crosstab.
Because dataset declarations can contain parameters, fields, variables, and groups, they
closely resemble subreports, but they completely lack any visual content (that is, they
have no sections or layout information at the dataset level).
Datasets, when instantiated, expect to receive parameter values and a data source to
iterate through. As a convenience, you can associate an SQL query with a dataset that uses
a JDBC connection.
A dataset gives an abstract description of your record metadata but does not say where
the data is coming from. For example, you can create a dataset that stores the information
that you have three fields – Last Name, First Name, City – and that those fields are text
fields.
When you create a subdataset, you can optionally choose a connection or data source to
use as a resource to specify your fields. For example, if you are retrieving the records above
from a JDBC database, you can use the JDBC connection to retrieve the field information
from your data, rather than entering it manually. However, when you save the dataset it
does not specify the data source, so, for example, you could later retrieve the field values
from the JDBC connection or you could retrieve them from a CSV file. The final binding of
the subdataset to its data retrieval method does not occur until you add an element to
your report and define a dataset run.
Dataset Runs
To use a subdataset, you must define a dataset run. A dataset run is always defined at the
element level and tells where to get the data for the element.
Datasets are filled similar to reports. This means that they require a data source or
connection from which to get the data when they are filled. They can also rely on
parameters for additional information to use when being filled. The dataset run binds the
dataset used by the element with a data source and supplies the values for the dataset
parameters. You can use the same dataset in different elements, and you can configure the
dataset to run at the element level.
A dataset run can only be declared elements that contain datasets, including: charts,
crosstabs, tables, lists, and maps.
Unlike other elements, a table and list always require a subdataset; they cannot use the
main dataset.
When you create a dataset run, you can set the value of the subdataset parameters using
expressions containing main report objects (like fields, variables, and parameters), define a
parameters map to set values for the subdataset parameters at run time, and define the
connection or data source to be used by the subdataset.
Subdatasets
The Dataset page of the Dataset wizard shows the following options:
• Dataset name – A name for the subdataset. Must be unique in the report.
• Dataset radio buttons:
• Create new dataset from a connection or Data Source – Select this to use a
connection or data source to define the metadata for the dataset. The
connection or data source introspects its associated data and suggest fields and
field types for the dataset. Later, when you add an element and create a dataset
run, you make the final choice on where to retrieve the data for the element. At
that point, you can use the same data source/connection, or select a different
one.
• Create an empty dataset – Select this to create a dataset without metadata. In
this case, you need to define the metadata later, when you create a dataset run
that uses this dataset.
A dataset that is configured to use the empty data source is not an empty dataset,
because it still defines fields and other metadata. The empty data source just creates a
number of records where each field value is set to null.
• Next – Displays the Data Source page (only available when Create new dataset from
a connection or Data Source is selected).
The Group By page lets you group fields. In the context of a dataset, groups are only used
to group records and there is no discrete portion of the report tied to them (for example,
like the header and footer bands associated with groups). Primarily, dataset groups are
used with variable calculations.
Dataset Objects
When you create a subdataset, it appears as a node in the outline view for your report.
Expand the node to see the dataset's fields, variables, parameters, and other objects.
You cannot use objects coming from the master report dataset directly in an element that
uses a subdataset. Only subdataset objects can be used in these cases. To use objects from
your main report, you must declare them as parameters in your subdataset. You configure
the binding between the main dataset object with the subdataset parameter inside the
dataset definition, and then set the values for the parameters inside the dataset run.
For example, suppose you have a parameter named MyParam of type String in the main
report and you want to use it with a subdataset. Add it as a parameter to the subdataset
by right-clicking the Parameters node in the subdataset and selecting Create Parameter.
Then in the Properties view for your new parameter, set the name as MyParam, and the
class as java.lang.String. To set the value that this parameter has at runtime, define an
expression in the dataset run of the element that uses the parameter. Setting the
expression for a parameter inside the dataset run means that the parameter is evaluated
when the element is evaluated. This means that when you use a parameter in two different
elements, one inside the title band and one inside the summary band, the parameter's
value can be different in the two different elements.
Dataset Properties
The Properties view for a dataset shows a number of advanced options, most of which can
only be understood and applied in a useful way after you become familiar with
JasperReports. To see the properties for a dataset:
• For a report, select the root node of the report in the outline view. The dataset
properties are shown in the Dataset section on the Report tab in the Properties view.
• For a subdataset, select the subdataset node in the outline view. The dataset
properties are shown in the Properties view.
Option Description
• Filter Expression – Boolean expression that determines whether records that are
read from the data source should be used. Can use all the objects of the dataset
(parameters, variables, and fields). Here are some examples of filter expressions:
• Filter only records where the field FIRSTNAME starts with the letter “L”:
• JavaScript: $F{FIRSTNAME}.substr(0,1) == "L"
• Groovy: $F{FIRSTNAME}.startsWith("L")
• Filter only records where the length of the field FIRSTNAME is less than 5:
• JavaScript: $F{FIRSTNAME}.length < 5
• Filter only records where the field FIRSTNAME is the one provided by the
parameter NAME:
• JavaScript: $F{FIRSTNAME} == $P{NAME}
• Scriptlet Class – A scriptlet is a Java class whose methods are run according to
specific events during report creation, such as the beginning of a new page or the
end of a group. For those who are familiar with visual tools such as Microsoft Access
or Microsoft Excel, a scriptlet can be compared with a module in which procedures
associated with other events or functions (for example, the expression of a textfield)
are inserted. The scriptlet property identifies only the main scriptlet, but other
scriptlets can be added to the report by using the outline view.
• Resource Bundle – Used to internationalize a report. A resource bundle is the set of
files that contain the text of the labels, sentences, and expressions used within a
report in one defined language. What you set in the resource bundle property is the
resource bundle base name, which is the prefix through which you can find the file
with the correct translation. To reconstruct the file name required for a particular
language, some language/country initials (for example, “_it_IT” for Italian-Italy) are
added to this prefix, as well as the .properties extension.
• Default Data Adapter – Sets the name and location of the XML data adapter resource
that JasperReports should use.
• Edit query, filter and sort options button – Opens the Dataset and Query dialog,
where you can edit the query, sorting, and filter options for the subdataset. See
Using the Dataset and Query Dialog for more information.
Dataset Runs
You create a dataset run when you insert an element that contains a dataset into your
report. For example, the fields for defining a dataset run for a basic chart are in the lower
right of the Chart Data Configuration dialog.
If the main report dataset uses a connection, such as a JDBC connection, you see the
following options:
• Don't use any connection or Data Source – Select this if you do not want to specify
any data for the dataset run. You can set this if you have set a data adapter via the
properties view, and want JasperReports Library to use that adapter. This setting
can be used when you want to publish a report with multiple connections to
JasperReports Server.
• Use another connection – Select this and enter a connection expression to use a
connection that is different from the connection in the main dataset. You can use
this for any connection, such as a JDBC connection or big data connection.
• Use a JRDatasource expression – Select this and enter a data source expression if
you want to use a data source. Note that, even when the main report uses a data
source, such as a CSV file or JSON data source, you cannot simply reuse the data
source from the main report. Instead, you must define a subdataset and create a
dataset run that accesses the data source. This is because, unlike a connection, a
data source is consumed when JasperReports iterates through it to fill the element.
This means that when you use the same data source in two different elements, you
must access the data source twice.
• Use same JDBC connection used to fill the master report – If the report uses a
connection, such as a JDBC connection or a Hibernate connection, select this to
have the dataset run use the same connection as the main report. You can
optionally enter a different query from the query in the main report.
When Use same JDBC connection used to fill the master report is selected, the
connection expression uses the built-in parameter for the report's JDBC connection,
$P{REPORT_CONNECTION}.
• Use an empty Data Source – Select this to fill the dataset using an instance of
JREmptyDataSource, that is, a data source that contains a specified number of
records, where the field values are all NULL. See Using the Empty Record Data
Adapter for more information.
If the main report uses a data source, the menu and options are slightly different.
• Don't use connection or data source – Select this if you do not want to specify any
data for the dataset run.
• Use a Connection expression – Select this to use any connection, such as a
connection to a JDBC database or a big data store.
• Use a DataSource expression – Select this to connect to a non-JDBC data source, for
example, a JSON or XML data source.
Parameters Tab
This tab allows you to set values for the subdataset parameters using calculated
expressions. Expressions can reference main report objects such as fields, variables, and
parameters. However, objects from your main report are not directly available in a
subdataset. To use parameters from your main report, you must declare them in your
subdataset and then assign their values in a dataset run.
Parameters map values can be provided as expressions, making the map potentially
dynamic. For example, you can use a parameters map to pass the username of the user
running the report, or define the connection or data source used by the subdataset.
Your application can create a map designed for the subdataset, pass it to the master report
using a parameter, then use that parameter as an expression (for example, $P{myMap}) to
pass the map to the subdataset. If you want, you can pass the same parameters map to
the main report and to the subdataset, using the built-in parameter REPORT_
PARAMETERS_MAP. In this case, the parameters map expressions $P{REPORT_
PARAMETERS_MAP}.
Create a report
1. Create a basic report using a blank template, for example, Blank A4, and click Next.
2. Give your report a name, for example, DataSetReport, and click Next.
3. Choose Sample DB - Database JDBC Connection and click Next.
You can create a data adapter separately or click New... to create a data adapter
directly from this dialog. Adapters can be created globally (embedded in the workspace)
or local to a specific project. Using a local adapter makes it easier to deploy the report
to JasperReports Server. See Creating and Editing Data Adapters for more information.
4. Enter the SQL query select count(*) as tot_orders from orders and click Next.
5. Add TOT_ORDERS as a field and click Finish. The report is displayed.
6. Drag the TOT_ORDERS field to the Detail band. If you want, you can remove all
bands except the Title, Detail, and Summary bands, and add a static text field to the
title band to identify the report.
7. Preview the report.
The resulting main report has a single record containing the total number of orders.
Create a subdataset
1. Right-click your report's root node in the outline view.
2. Select Create Dataset from the context menu.
The Dataset wizard is displayed.
3. Enter a name for your dataset. For this tutorial, name it ExampleDataset.
4. For this tutorial, select Create new dataset from a connection or Data Source. This
includes a data adapter as part of your dataset definition.
If you select Create an empty dataset, your dataset does not include any data adapter
or field information. You need to configure this information separately for each dataset
run.
5. Click Next.
6. Select the data source that you want for your dataset and click Next. For this
example, select Sample DB.
3. In the dataset run section of the Chart Wizard, select the dataset you created,
ExampleDataset.
4. Select Use same JDBC connection used to fill the master report from the dropdown
menu. This causes the expression to be set automatically to the connection used by
the main report ($P{REPORT_CONNECTION}).
5. To force the expression context to update the fields, parameters, and values after
the dataset run configuration, close the dialog, then reopen it by double-clicking the
chart. If you do not force an update, you do not see the correct fields in the
expression editor.
6. Set the chart dataset expressions (the expressions used to fill the chart):
• Click … next to Series to open the Series dialog. Then select SERIES1 and click
… to open the expression editor and enter the following expression:
$F{SHIPCOUNTRY}
Click Finish, then click OK to return to the Chart Wizard. Note that the Key field
below the chart updates to show the same value as the series.
• Click … next to Value to open the expression editor. Enter the following
expression:
$$F{COUNTRY_ORDERS}}
Click Finish to return to the Chart Wizard.
You cannot use objects from the master report dataset in an element that uses a
subdataset. Only subdataset objects can be used. To use an object from the master
report dataset, you must pass it as a variable or a parameter.
Report Bursting
Jaspersoft Studio provides a built-in report bursting feature that allows you to burst a
report based on some parameters and generate multiple reports, with each report having
specific data. You can send these reports to different recipients with data relevant to them.
For example, a single report containing shipping data of countries, such as Mexico, Canada,
and the US, can be burst into different reports based on each country.
Report bursting is done by a report that triggers the bursting operation. Because reports
have the built-in capability to retrieve records from a database, they can iterate through
the records in the database. A bursting report needs a JasperReports Server connection to
work with JasperReports Server. This connection is provided by the Jaspersoft Server data
adapter and helps to retrieve information from JasperReports Server to trigger the
bursting.
Bursting Scriptlet
A bursting report has a special scriptlet that is a bursting component. This scriptlet is
attached to the data set of the bursting report. You can define a scriptlet by using scriptlet
properties including, Name, Description, and Class. However, for class, there is a default
Bursting a Report
The following example shows how to burst a report and send data of a country related to
each recipient.
To burst a report
1. Create a CSV file with two columns Country and Email, and create a data adapter
that points to this CSV file.
2. Create a report containing two fields country $F(Country) and Email address of
recipient $F(Email). This report is a bursting report used for bursting operation.
3. A bursting scriptlet is required for the bursting report. To create a scriptlet, in the
Outline view, right-click the Scriptlets, and select Create Bursting Scriptlet. It creates
a bursting scriptlet.
4. To edit the properties of the bursting scriptlet, right-click the bursting scriptlet and
select Edit Bursting Properties. Bursting scriptlet edit dialog appears.
5. On the Parameters tab, click Add to add the parameter. Report Bursting Parameter
dialog appears. Enter the Parameter name and Parameter value that you want to
pass to the burst reports. For example:
Parameter name: ShipCountry_1
Parameter value: $F{Country}
6. On the Options Configuration tab, select the Essential Options from the left panel
and set the following fields:
Server profile: select the server connection from the dropdown for the bursting
report. For example, JasperReports Server Pro.
Enabled: true
Job Label: Sales By Country
Report URI: browse the repository and select the report you want to burst.
The path to the burst report in a bursting report is interpreted as relative to the user
that runs the report. So if the burst report is part of an organization, you cannot have a
bursting report that works for both superuser and users from that organization
(jasperadmin and joeuser). superuser needs the absolute path and users from the
organization needs a relative path. It is recommended to run bursting reports that
belong to the same organization as the user.
b. In the Subject field, enter the subject for the mail to be sent to recipients.
c. In the Message field, type the message you want to send to recipients.
d. Click OK.
9. Run a bursting report.
Burst reports are created in the output folder for different countries in both formats PDF
and Excel.
Report Splitting
With report splitting, you can run a report in a JasperReports Server scheduler and get the
output into the individual parts. Each part of the report is saved separately in the
repository and sent to different recipients. Report splitting is based on the report parts. You
can create report parts using a band-based report or a report book. The following example
shows a report splitting procedure using a band-based report.
15. Run the report in the scheduler. To do this, right-click the report and select Run in
Background from the context menu.
16. On the Output Options tab, set the output options and click Submit.
17. On the Notifications tab, enter the email address and subject of the email to be sent
to each recipient. Provide dynamic values in the following text fields To, CC, and
Subject.
18. Select the Include report files as attachments option and click Submit.
A single report is split into three separate reports and sent to the email addresses of
different recipients.
To create a tabular layout for a simple report with columns that resize together, you
can use the spreadsheet layout. While not as complex as the Table component, you can
use it directly in a report without defining a dataset. See Working with Spreadsheet
Layout for more information.
Creating a Table
To create a table
• To autosize your table, drag the Table element from the Elements palette into
any band of the report.
• To set the size of the table manually when you insert it, click the Table element ,
but do not drag. The cursor changes to show that an element is selected. Click
and drag in the report editing area to size and place the element. When you size the
table when you first insert it, the columns fill the whole table.
Once you have placed your table in your report, use the Table Wizard to choose a new or
existing dataset for your table.
2. Name your dataset and select your option: Create new dataset from a connection or
data source or Create an empty dataset. For this example, choose the first option
and click Next. You are prompted to select a data source and design query.
3. Select a data source and enter an SQL query such as: select * from orders and click
Next. You are prompted to select dataset fields.
4. Select the fields that you want in your table and add them to the Fields list on the
right. Then click Next. You are prompted to select the fields to group by from among
your chosen fields.
5. Select one or more fields to group by and move them to the Fields list on the right.
Click Next. You are prompted to select a connection.
8. Select one or more fields to for table columns and move them to the Fields list on
the right. Click Next. You are prompted to select a layout.
9. Select the layout for your table, and click Finish. The table appears where you
dragged the table element in your report.
Editing a Table
To edit a style in the palette, double-click the style and edit it in the Layout window. You
can save it either as a new style or with the same name. To edit the table layout in the
Design tab, right-click the table and choose Change Table Style.
You can also decide which table sections to create. If the dataset for the table contains
groups, it can be convenient to select the Add Group Headers and Add Group Footers
checkboxes.
To delete a style, right-click it in the Table Styles tab and choose Delete Style.
• To edit the content and style of a cell, click the cell. Switch to the Properties view
where you can edit location, size, color, style, and print details for the cell.
• To edit the size and position of a cell, or copy or delete it, right-click on the cell and
select an action from the context menu.
Here you can set the dataset parameters to filter the data used in the table dynamically.
Suppose, for instance, you have a report that displays order details in a table, you can use
a parameter in your SQL query to specify the order ID to filter the order details.
Unlike charts and crosstabs, a table always requires a subdataset. Tables cannot use the
main dataset.
Table Structure
Tables consist of cells and columns. This section provides more information about working
with each of these elements.
Table Elements
A table must have at least one column, but it can have any number. A set of columns can
be collected into a column group with a heading that spans several or all the columns.
Each table is divided into sections similar to the main document bands:
• Table header and footer - each printed only once.
• Column header and footer - repeated on each page the table spans. For column
groups, the table can display a group header and footer section for each group and
for each column.
• Detail - repeated for each record of the table. Each column contains only one detail
section, and the section cannot span multiple columns.
In the Outline view, table sections are shown as child nodes of the table element node.
In the Design tab, each column has a cell for each section (for example, one cell for the
table header section, another for the table footer). A cell can be undefined. If all the cells of
a section are undefined, the section is not printed. If the height of all the cells of a section
is zero, the section is printed but is not visible in the Design tab.
Table Cells
A cell can contain any JasperReports element. When an element is dropped on a cell,
Jaspersoft Studio automatically arranges the element to fit the cell size. To change the
arrangement of the elements, right-click the cell (or element) and select an option from the
context menu. Alternatively, you can insert a frame element in the cell and add all the
required elements in that frame.
You can delete a cell by right-clicking and choosing Delete cell. If the cell is the only
defined cell in the column, the entire column is removed. Similarly, if a cell is undefined,
right-click it and select Add cell to create the cell. An undefined cell is automatically
created when the user drags an element into it (see Working with Columns).
• To add and delete columns, click in the column header or footer. The selected row
and column are outlined. Select an option from the action menu. By default, when
Jaspersoft Studio adds a column to a table, the new column inherits the properties
of the other columns.
• Table cells are containers that can include other elements. To set a layout for the
cell contents, click in the column header or footer and select Arrange in Container
from the action menu, then select a layout option. See Positioning Elements in
Containers
• You can drag a column to any position, inside or outside a group. Move a column
within the same section by dragging the nodes that represent the columns in the
outline view.
Column Groups
A column is composed of a set of cells. If you create a column group, a column heading
can span all columns in the group. A column group can include other column groups.
A column group acts as a single unit when you drag it. If you drag the last column out of a
column group, the column becomes a simple column and the remaining group cells are
deleted.
When you create a column group, every column section gets a group heading, as shown in
Group headings, but you can remove unnecessary headings. On the left of the figure, there
are two columns (most of the sections in the columns have only one record; one section
has two records). When the columns are grouped, each column section gets a group
heading, as shown in the center. However, most of the group headings are unnecessary, so
their heights have been set to zero to hide them, as shown on the right.
5. Drag the Chart tool from the Palette into the Summary band. The Chart Wizard
opens.
In the Design tab, the chart is a placeholder and does not display your data.
To configure a chart
1. Double-click the chart. The Chart Data Configuration window opens.
The Chart Data tab shows the fields within the specified dataset. You find
detailed descriptions of field types and their functionality in JasperReports
Library Ultimate Guide.
3. Set 10 for Max slices to show. For a chart of many slices, this field specifies the
number to show. A chart slice labeled Other contains the slices not shown.
4. On the Dataset tab, you can define the dataset within the context of the report.
You can use the Reset on controls to reset the dataset periodically. This is useful, for
example, when summarizing data relative to a special grouping. Use the Increment
on control to specify the events that trigger the addition of new values to the
dataset. By default, each record of the chart's dataset corresponds to a value
printed in the chart. You can change this behavior and force the engine to collect
data at a specific time (for instance, every time the end of a group is reached).
Set Reset on to Report since you do not want the data to be reset, and leave
Increment Type set to None so that each record is appended to your dataset.
5. Also in the Chart Data Configuration dialog, enter an expression to associate with
each value in the data source. For a Pie 3D chart, three expressions can be entered:
key, value, and label.
• Key expression identifies a slice of the chart. Each key expression must be a
unique. Any repeated key simply overwrites the duplicate key. A key can never
be null.
• Value expression specifies the numeric value of the key.
• Label expression specifies the label of a pie chart slice. This is the key expression
by default.
Next to each field, click the button. Enter the following:
Value: $F{orders}
Label: $F{shipcountry}
Key: $F{shipcountry}
6. Click Finish.
7. Save your report, and preview it to see the result.
In this chart, each slice represents a country and the shipping total for that country.
For more information about setting hyperlinks, see Anchors, Bookmarks, and
Hyperlinks.
JasperReports Server takes advantage of only a small portion of the capabilities of the
JFreeChart library. To customize a graph, you must write a class that implements the
following interface:
net.sf.jasperreports.engine.JRChartCustomizer
The only method available from this interface is the following:
public void customize(JFreeChart chart, JRChart jasperChart);
It takes JFreeChart and JRChart objects as its arguments. The first object is used to
produce the image, while the second contains all the features that you specify during the
design phase that are relevant to customize the graph.
Spider Charts
Spider charts (or radar charts) are two-dimensional charts designed to plot a series of
values over multiple common quantitative variables by providing an axis for each variable,
arranged as spokes around a central point. The values for adjacent variables in a single
series are connected by lines. Frequently the shape created by these lines is filled in with
color.
In Jaspersoft Studio, the spider charts are separate from the rest of the charts available in
the Community Project, because they are a separate component in the JasperReports
Library. But you use them just as other JFree Charts.
4. Drag a Static Text element into the title bar, and name your report something like
“Employee Orders by Month and Country”.
5. Enlarge the Summary band to 350 pixels by changing the Height entry in the Band
Properties view.
2. Select the report in the Outline view, and in the Properties view, click the Edit query,
filter, and sort options button. The Dataset and Query dialog opens.
To filter your data in a Spider Chart, you must filter it in the Dataset and Query dialog.
3. To filter data for a more readable chart, click the Increment Expression tab and
enter the expression below with no manual line breaks, then click OK.
( $F{shipcountry}.startsWith("N") || $F{shipcountry}.startsWith("M") || $F
{shipcountry}.startsWith ("U") || $F{shipcountry}.startsWith ("I") ) || $F
{shipcountry}.startsWith("A") && ( $F{shipname}.startsWith( "M" ) || $F
{shipname}.startsWith( "A" ) || $F{shipname}.startsWith( "G" ) )
4. Double-click the chart to display the Chart Data Configuration dialog.
5. Click the Series button and create the series $F{employeeid}.
6. Click the Value button and create the value MONTH($F{orderdate}).
7. Click the Category button and create the category $F{shipcountry}.
8. Click Finish.
Chart Themes
Chart themes give you full control over the style of your JFree charts. You can create a
chart theme and use it in multiple reports for a uniform look. And you can update that look
for all those reports simply by updating the chart theme. Jaspersoft Studio is the
supported tool for creating JFree chart themes.
2. Enter or select the parent folder, name the file, and name your theme. Click OK.
A dialog indicates that the Chart Theme was generated.
Chart Customizers
Chart customizers are Java classes that change the appearance of charts. Chart
customizers let you implement JFreeChart functionality that has not been directly included
in JasperReports. For example, you can use chart customizer classes to change the shape
of the legend icons in a chart or change the colors or pattern of the bars in a bar chart.
Jaspersoft Studio provides a simple UI for applying chart customizers. This includes a
number of out-of-the-box customizers for common configurations as well as a mechanism
to let you add your own customizers to the UI. In addition, if you create a configurable
customizer, that is, a customizer that lets the user set values in the report rather than
hard-coding them, you can create a user interface for it using a JSON file.
5. Fill in the properties as prompted by the user interface. For example, the following
values for Legend Shape change the legend to a circle:
• Apply to – All Items
• Shape Type – Ellipse
• Width – 10
• Height – 10
6. Click Finish.
The customizer selection dialog is closed and the customizer is applied to your
chart. Click Preview to view your chart.
A chart customizer defines a customize method that takes a JFreeChart object and a
JRChart object. The customize method can access chart settings and change them. During
report execution, JasperReports calls the customize method for the chart and applies the
settings, along with the settings from the JSON file. RangeAxisCustomizerSample is as
shown below.
RangeAxisCustomizerSample
package com.jaspersoft.studio.sample.customizer;
import org.jfree.chart.JFreeChart;
import org.jfree.chart.axis.NumberAxis;
import org.jfree.chart.axis.ValueAxis;
import org.jfree.chart.plot.CategoryPlot;
import org.jfree.chart.plot.XYPlot;
import net.sf.jasperreports.customizers.axis.AbstractAxisCustomizer;
import net.sf.jasperreports.engine.JRChart;
/**
* Customizer to define the minimum and maximum value of the domain axis,
works for
* XY plot
*/
public class RangeAxisCustomizerSample extends AbstractAxisCustomizer
{
@Override
public void customize(JFreeChart jfc, JRChart jrc)
{
ValueAxis valueAxis = null;
if (valueAxis != null)
{
configValueAxis(valueAxis, PROPERTY_MIN_VALUE, PROPERTY_MAX_VALUE);
{
"label": "Range Axis Range and Tick - Sample",
"description": "Customizer to set the range for the axes and the tick
spacing for an axis chart.",
"customizerClass":
"com.jaspersoft.studio.sample.customizer.RangeAxisCustomizerSample",
"supportedPlot": ["13","14","15"],
"sections": [
{
"name": "Customizer configuration",
"expandable": false,
"properties": [
{
"name": "minValue",
"label": "Range Min",
"description": "The minimum value on the axis",
"mandatory": false,
"readOnly": false,
"type": "double"
},
{
"name": "maxValue",
"label": "Range Max",
"description": "The maximum value on the axis",
"mandatory": false,
"readOnly": false,
"type": "double"
},
{
"name": "tickUnit",
"label": "Distance",
"description": "The space between ticks.",
"mandatory": false,
"defaultValue": "1",
"readOnly": false,
"type": "double"
}
]
}
]
}
CHART_TYPE_AREA 1
CHART_TYPE_BAR3D 2
CHART_TYPE_BAR 3
CHART_TYPE_BUBBLE 4
CHART_TYPE_CANDLESTICK 5
CHART_TYPE_HIGHLOW 6
CHART_TYPE_LINE 7
CHART_TYPE_PIE3D 8
CHART_TYPE_PIE 9
CHART_TYPE_SCATTER 10
CHART_TYPE_STACKEDBAR3D 11
CHART_TYPE_STACKEDBAR 12
CHART_TYPE_XYAREA 13
CHART_TYPE_XYBAR 14
CHART_TYPE_XYLINE 15
CHART_TYPE_TIMESERIES 16
CHART_TYPE_METER 17
CHART_TYPE_THERMOMETER 18
CHART_TYPE_MULTI_AXIS 19
CHART_TYPE_STACKEDAREA 20
CHART_TYPE_GANTT 21
• sections – Property that controls the display of the user interface. Has the following
attributes:
• name – Name for the user interface dialog.
• expandable – Boolean; for chart customizers, always set to false.
• properties – Attribute that contains sections to define each entry box in the user
interface. Each entry box has the following attributes:
• name – Name of the argument to pass to the customizer class.
• label – Name that appears in the user interface.
• description – Tooltip that appears on hover.
• mandatory – Boolean. When true, the property is required. When false, the
property is optional.
• readOnly – Sets attribute as read-only. Not used for chart customizers.
• type – Type of the attribute, as expected by the customizer class.
• defaultValue (optional) – Default value for an optional property.
To add a non-configurable customizer, use an empty list for the properties. For
example:
"sections": [
{
"name": "Customizer configuration",
"expandable": false,
"properties": []
}
]
This section describes functionality that can be restricted by the software license for
Jaspersoft Studio. If you do not see some of the options described in this section, your
license may prohibit you from using them. To find out what you are licensed to use, or
to upgrade your license, contact Jaspersoft.
The HTML5 Chart Edit dialog has two configuration views: simple and advanced.
• A simple view lets you quickly configure your categories, measures, and series
contributor.
• Advanced view gives you more control and access to advanced features.
You can also preview a chart from the chart dialog by clicking in the HTML5 Chart Edit
dialog.
This chapter has the following sections:
• Overview of HTML5 Charts
• Example of a Bar Chart Using Simple Configuration
• Example of a Pie Chart
• Example of a Tile Map Chart
• Example of a Time-Series Spline Chart
• Example of a Tree Map Using Multiple Levels and Advanced Formatting
• Example of a Scatter Chart Using Advanced Configuration
• Example of a Column-Spline Chart
• Creating Hyperlinks in HTML5 Charts
In HTML5 Charts, Jaspersoft Studio are similar to Ad Hoc charts in JasperReports Server.
Before you add a chart to your report, consider the best way to display your data. The
following table describes the available chart types.
Icon Description
Icon Description
Line. Displays data points connected with straight lines, typically to show
trends.
Spline. Displays data points connected with a fitted curve. Allow you to
take a limited set of known data points and approximate intervening
values.
Area charts - Compare values displayed as shaded areas. Compared to line charts, area charts
emphasize quantities rather than trends.
Area. Displays data points connected with a straight line and a color
below the line. Groups are displayed as transparent overlays.
Icon Description
Stacked Area. Displays data points connected with a straight line and a
solid color below the line. Groups are displayed as solid areas arranged
vertically, one on top of another.
Stacked Percent Area. Displays data points connected with a straight line
and a solid color below the line. Groups are displayed as portions of an
area of fixed size, and arranged vertically one on top of each other.
Area Spline. Displays data points connected with a fitted curve and a
color below the line. Groups are displayed as transparent overlays.
Stacked Percent Area Spline. A variation of area spline charts that present
values as trends for percentages, totaling 100% for each category.
Dual-Level Pie. A variation of pie charts that present the grouped values
in two concentric circles. The inner circle represents the coarsest
grouping level in the data. In Jaspersoft Studio, note these rules about
data configuration for dual-level pie charts:
• Only one measure is displayed (the first)
• The last row level is rendered as the outer pie
Icon Description
• The next to the last row level is rendered as the inner pie. If only
one row level is defined, the inner pie consists of a single section
representing the total
Scatter and Bubble Charts - Show the extent of correlation, if any, between the values of
observed quantities.
Scatter. Displays a single point for each point in a data series without
connecting the points.
Multi-Axis Charts - Compare trends in two or more data sets whose numeric range differs
greatly.
Multi-Axis Column. A column chart with two series and two axis ranges.
Multi-Axis Line. A line chart with two series and two axis ranges.
Multi-Axis Spline. A spline chart with two series and two axis ranges.
Icon Description
Combination Charts - Display multiple data series in a single chart, combining the features of
an area, bar, column, or line charts.
Column Line. Combines the features of a column chart with a line chart.
Time Series Charts - Illustrate data points at successive time intervals. Also called Fever Chart.
Time Series Area. Displays data points over time connected with a
straight line and a color below the line.
Time Series Area Spline. Displays data points over time connected with a
fitted curve and a color below the line.
Time Series Line. Displays data points over time connected with straight
lines.
Icon Description
Time Series Spline. Displays data points over time connected with a fitted
curve.
Spider Charts - Display data in line or data bars arranged on a circular spider web chart. It is
also called a Radar Chart.
Spider Line. Plots one or more series over multiple common quantitative
variables by providing axes for each variable arranged as spokes around a
central point. The line variation of spider charts displays values as points
arranged around the circular web. The data points are joined by a line.
Each point's distance from the central point indicates the relative value.
Spider Area. Plots one or more series over multiple common quantitative
variables by providing axes for each variable arranged as spokes around a
central point. The area variation of spider charts is similar to the line
variation, but the shape defined by the line that connects each series'
points is filled with color.
Range Charts
Heat Map. Represents data in a matrix format, using color coding to show
values.
Time Series Heat Map. Represents data across time in a heat map, using
color coding to show values.
Icon Description
Dual Measure Tree Map. Displays data as color-coded rectangles. The size
of each rectangle is proportional to the first measure and the color
represents the second measure.
One Parent Tree Map. Displays data as nested rectangles. The size of each
rectangle is proportional to the measure of the data it represents. The
nested rectangles represent the current level of aggregation while the
larger rectangle represents the parent level in the hierarchy. Click a
parent rectangle to drill down to the nest rectangles.
Tile Map. Displays data in the form of tiles aligned on a grid to create a
pattern. The related data measure is displayed on each tile.
Gauge Charts
Icon Description
measures.
• Two or more Measures required in the Columns location.
• One or more Fields required in the Columns location.
• Define the minimum and maximum sizes, color stops, and layout
on the Appearance tab.
A panel similar to the one in this section is used for the following chart types: Bar,
Column, Line, Area, Spline, AreaSpline, StackedBar, StackedColumn, StackedLine,
StackedArea, StackedSpline, StackedAreaSpline, StackedPercentBar,
StackedPercentColumn, StackedPercentLine, StackedPercentArea,
StackedPercentSpline, StackedPercentAreaSpline, SpiderColumn, SpiderLine,
SpiderArea.
2. Select a chart type based on the information that you want to display. See HTML5
Chart Types for help. You can use the menu at the left to restrict the selection to a
particular type of chart. For this example, choose Bar.
3. Click the Data Configuration tab. This tab includes options for configuring chart
dataset, chart properties, and hyperlinks. The options on this tab reflect the type of
chart that you selected.
Figure 236: HTML5 Charts Properties > Chart Data > Configuration
4. Enter the expression that you want to use for the categories. You can enter the
expression directly, or click to open the Expression Editor. For this example, enter
the following:
• Category Expression – $F{SHIPCOUNTRY}.
5. Enter the information that you want for the series:
• Series – This menu displays the default name of the series, for example, Series 1.
If you want to change the name, use advanced configuration.
• Value Expression – Enter the expression that you want to use as a base for the
measure calculation. For this example, use $F{Freight}.
• Aggregation Function – Select the function to apply to the value expression. For
this example, use Average.
• Tooltip Expression – Enter an expression to display as a label for the measure.
For this example, enter "Average Freight".
6. To preview the chart from inside the dialog, click Show Chart Preview.
A preview is displayed in the right of the dialog. This preview can take some time to
load the first time it is run.
8. You can optionally filter the dataset by entering an expression in the Increment
expression text box. You can enter text directly or click to open the Expression
Editor. For this example, filter your dataset using the following increment
expression:
$F{SHIPCOUNTRY}.startsWith("I") ||
$F{SHIPCOUNTRY}.startsWith ("S") ||
$F{SHIPCOUNTRY}.startsWith ("U")
9. Click to refresh the preview.
10. Click OK to close the HTML5 Chart Edit dialog.
A placeholder for the chart is inserted in the design view of your report. The design
view of a report does not display live data for a chart.
11. Save, then click the Preview tab to see your chart. To see an interactive preview,
select HTML from the Preview dropdown. Hover over a bar to see the average
freight.
The preview works best when you are using the same dataset as the main report.
Parameters may not be applied and multiple levels or series may not be displayed.
Formatting a Chart
You can set the HTML formatting of the chart using the Chart Formatting tab in the HTML5
Edit Charts dialog. Most of these properties can be set using an expression.
You can set additional options using the Show Advanced Properties button. See
Advanced Formatting of HTML5 Charts for more information.
You can set JasperReport element properties for an HTML5 chart, such as position or
evaluation time, in the Properties view. See Setting Advanced Options for HTML5 Charts
in Properties View for more information.
5. Expand Legend, select Legend > Sizes and Position, and set the location of the
legend on the graph:
• Horizontal Alignment – right.
• Vertical Alignment – middle.
• X offset – -6. This moves the legend inside the plot background color.
6. Select Legend > Items and set the following:
• Items Layout – vertical.
7. Click OK.
Creating a Hyperlink
1. Double-click your bar chart or right-click and select Edit Chart properties.
2. Click the Data Configuration tab.
3. Click Edit Hyperlink.
A panel similar to the one in this section is used for the following chart types: Pie,
SemiPie.
3. Choose HTML5 Charts from the Components Pro section of the Palette, and drag
it into the Summary band of your report.
The HTML5 Chart Edit Dialog is displayed.
4. Select a chart type based on the information that you want to display. You can use
the menu at the left to restrict the selection to a particular type of chart. For this
example, choose Pie.
5. Click the Data Configuration tab. This tab includes options for configuring chart
dataset, chart properties, and hyperlinks. The options on this tab reflect the type of
chart that you selected. The dialog shown in this example is used for pie and semi-
pie charts.
Figure 243: HTML5 Charts Properties > Chart Data > Configuration
6. Enter the required information on the Data subtab. For this example:
• Slice Expression – Enter the expression that you want to use for the slices. You
can enter the expression directly, or click to open the Expression Editor. For
this example, use $F{SHIPCOUNTRY}.
• Value Expression – Enter the expression that you want to use as a base for the
measure calculation. For this example, use $F{ORDERID}.
• Aggregation Function – Select the function to apply to the value expression. For
this example, use DistinctCount.
• Tooltip Expression – Enter an expression to display when a user hovers over a
slice of the pie. For this example, enter "Orders".
• Ordering – Select an order for the slices. For this example, choose Ascending.
This displays the slices in alphabetical order.
7. To preview the chart from inside the dialog, click Show Chart Preview.
A preview is displayed to the right of the dialog. This preview can take some time to
load the first time it is run.
8. Click the Dataset subtab. This subtab lets you choose a dataset and dataset
properties. For this example, use the default [Report main dataset].
9. You can optionally filter the dataset by entering an expression in the Increment
expression text box. You can enter text directly or click to open the Expression
Editor. For this example, filter your dataset using the following increment
expression:
$F{SHIPCOUNTRY}.startsWith("I") ||
$F{SHIPCOUNTRY}.startsWith ("S") ||
$F{SHIPCOUNTRY}.startsWith ("U")
10. Click to refresh the preview.
Figure 244: HTML5 Charts Properties > Chart Data > Configuration
Figure 246: HTML5 Charts Properties > Chart Data > Configuration
4. Under Categories Levels, select Level1 and click Modify. Then enter the following:
• Expression: $F{y}
• Value Class Name: java.lang.Integer
Click OK.
5. Under Series Level, select Series1 and click Modify. Then enter the following:
• Expression: $F{x}
• Value Class Name: java.lang.Integer
Click OK.
6. Under Measures, select Measure1 and click Modify. Then enter the following:
• Value Expression: $F{population}
• Value Class Name: java.lang.Integer
Click OK.
7. Click the Chart Formatting tab, select Chart > Title on the left and enter your title in
the Title text box. For this example, enter US states by population in 2016.
8. Select Subtitle and enter Subtitle in the Subtitle text box. For this example, enter
Source: Wikipedia.
9. On the Chart Formatting tab, select Tilemap on the left. You can set two additional
properties of the tilemap chart: Tile Shape and Color By Point.
10. Select the tile shape from the dropdown. For this example, Tile Shape is Hexagon
and Color By Point is set to false.
The default tile shape is Hexagon, but you can also select Circle, Diamond, or Square. If
Color By Point is set to true, any tile in the chart is colored with consecutive colors in the
'Colors' chart property. The Color By Point property can be neglected when colors are
defined in the colorAxis property.
13. On the Item list tab, click to add an item. A new item is created with the name
Item 1. Enter the following information.
• colorAxis.dataClasses.color: #F9EDB3
• colorAxis.dataClasses.name: <1M
• colorAxis.dataClasses.to: 1000000
14. To add a second item, click and enter the following information.
• colorAxis.dataClasses.color: #FFC428
• colorAxis.dataClasses.from: 1000000
• colorAxis.dataClasses.name: 1M-5M
• colorAxis.dataClasses.to: 5000000
Click OK.
15. To enable the labels to appear in each tile map, select plotOptions > tilemap >
dataLables and set enabled to true.
16. To preview the chart from inside the dialog, click Show Chart Preview.
4. Enter an expression for the date in the Date Expression field. You can click to use
the expression editor or enter the expression manually. For this example, enter:
$F{ORDERDATE}.
5. To use multiple series, select Define your series manually.
6. Define your first series. For this example, use the following data:
• Series – Series 1. The name of the series is automatically generated. You cannot
change it in a simple configuration.
• Value Expression – $F{FREIGHT}.
• Aggregation Function – Highest
This example shows a tree map for three levels of data: country, region, and city. The
dialog shown in this example is used for TreeMap and OneParentTreeMap.
Figure 254: Tree Map After Drill Through, Showing Formatting Issues
• When a country, such as the USA, is selected, the adjacent country is shown on the
chart.
• The label to return to a higher level reads undefined.
You can use advanced formatting to set these properties. For more information about
advanced formatting, see Advanced Formatting of HTML5 Charts
3. Click Add.
4. The Chart Property dialog is displayed.
5. To prevent the names of other countries from showing on the border of the charts,
enter the following, then click OK:
• Property name – plotOptions.treemap.dataLabels.overflow
• Property value – none
6. To change the text of the button, click Add, enter the following, then click OK:
• Property name – plotOptions.treemap.drillUpButton.text
• Property value – Back
7. Click OK to apply your properties and return to Design view.
Preview the chart in HTML to drill through and see your changes.
Figure 257: Tree map after formatting issues have been corrected
Static Highcharts properties are always recognized as String. If you have problems
setting a static Boolean or numeric property, set it as an expression. For example, to set
plotOptions.series.dataLabels.enabled to false, use the following JRXML:
<hc:chartPropertyname="plotOptions.series.dataLabels.enabled">
<hc:propertyExpression><![CDATA[false]]></hc:propertyExpression>
</hc:chartProperty>
6. Under Categories Levels, select Level1 and click Modify. Then enter the following:
• Name: ShipCountry
• Expression: $F{SHIPCOUNTRY}
• Value Class Name: java.lang.String
• Order: Ascending
Click OK.
7. Under Categories Levels, click Add and create a second Category with the following
information:
• Name: ShipCity
• Expression: $F{SHIPCITY}
• Value Class Name: java.lang.String
• Order: Ascending
Click OK.
8. Under Series Level, select Series1 and click Modify. Then enter the following:
• Name: Order Year
• Expression: YEAR($F{ORDERDATE})
• Value Class Name: java.lang.Integer
• Order: Ascending
Click OK.
9. Under Measures, select Measure1 and click Modify. Then enter the following for
maximum freight:
• Name: Max Freight
• Label Expression: "Max Freight"
• Calculation: Highest
• Value Expression: $F{FREIGHT}
• Value Class Name: java.math.BigDecimal
Click OK.
10. Under Measures, select Measure0 and click Modify. Then enter the following for
average freight:
• Name: Average Freight
• Label Expression: "Average Freight"
• Calculation: Average
• Value Expression: $F{FREIGHT}
• Value Class Name: java.math.BigDecimal
Click OK.
The chart is now configured. Click OK to close the dialog, then preview the chart.
6. Select Series 2 from the dropdown and configure the second measure for total
orders. This measure is used for spline:
• Value Expression: $F{ORDERID}
• Aggregation Function: DistinctCount
• Tooltip Expression: "Total Orders"
7. Click OK to return to design view.
8. Save and preview your report. It should look like the following figure.
have different names. If you want, you can use this dialog to change the name to
Average Freight.
The supported constant values for series property type are column, line, and spline.
Before creating a hyperlink, you can view the hyperlink you just created to see how it is
configured in the advanced view.
5. Click OK twice.
Once again, you can preview the chart. Now, for each country, the chart shows the
number of orders split by year.
Figure 273: Defining the URL to Open when the Measure is Clicked
ProductFamily hyperlink property, and by setting it to a value like Drink, can pre-filter its
results.
clicking Show Advanced Properties. Properties that differ from the defaults are highlighted
in yellow.
You can set a subset of properties for an Ad Hoc chart in Jaspersoft Studio, using the
Chart Properties > AdHoc Overrides section. However, this is not recommended. If you
are working with Ad Hoc charts in JasperReports Server, set your chart properties on
the server, using the Advanced Properties tab in the Chart Formatting dialog. For more
information about setting properties for Ad Hoc charts in JasperReports Server, see
Advanced Chart Formatting on the community website.
For a list of available properties, see the Highcharts website. Note that in some cases,
user-defined properties may not be compatible with Jaspersoft Studio.
1. Click Add in the advanced view of the Chart Formatting tab in the HTML Chart Edit
dialog.
Gradient property
• Name – chart.backgroundColor.linearGradient
This setting is nested below the chart and background color settings.
• Use an expression – true
Stops property
• Name – chart.backgroundColor.stops
This setting requires an array of arrays and is expressed through the nested use of
java.util.Arrays.
• Use an expression – true
• Property value:
java.util.Arrays.asList
(
java.util.Arrays.asList(0, "#b5bdc8"),
java.util.Arrays.asList(0.36, "#828c95"),
java.util.Arrays.asList(1, "#28343b")
)
Figure 278: Chart with a gradient background, set via user-defined properties
3. Expand the Misc section and click ... next to Edit Properties.
The Properties dialog opens.
4. Click Add to add a property.
5. Enter the following information:
• Name: com.jaspersoft.jasperreports.highcharts.interactive
• Value: false
6. Click OK and then click Finish.
Like many advanced charting options, this option can be set at a higher level. If you set an
option at multiple levels, the lowest level is the one that is applied.
• To disable this option for a report, click the report's root node in Outline view and
make sure that the Properties view is displayed. In the Properties view, on the tab,
select Advanced > Misc > Properties and click ... to open the Properties Dialog. Enter
the values shown above and click OK twice to apply the setting.
• To disable this option Jaspersoft Studio, select Window > Preferences from the
menu (Eclipse > Preferences on Mac). In the Preferences dialog, select Properties and
click Add to open the Properties Dialog. Enter the values shown above and click OK
twice to apply the setting.
You can also set this particular option in JasperReports Server. See the JasperReports
Server Administrator Guide for more information.
Master-detail Chart
A Master-detail chart is used to illustrate a large amount of data in the simplest way. It has
two interactive charts, a master chart and a detail chart. You can select a horizontal region
on the master chart and the detail chart boundaries on the X-axis change to the selected
area boundaries. This lets you see a detailed view of the data on the chart by selecting a
region on the master chart.
This feature is supported by all HTML5 charts except the following:
• Pie Charts
• Gauge Charts
• Spider Charts
7. To define an additional measure, click Add. For this example, define a second
measure using the following data.
• Name – "Measure2"
• Label Expression – "Series 2"
• Value Expression – $F{FREIGHT}
• Value Class Name – java.lang.Number
Click OK.
8. Add a third measure with the following data:
• Name – "Measure3"
Unlike HTML output, other output formats like PDF, PPTX, Excel, display the master
chart only because there is no interactivity in these formats.
You can increase the complexity of a crosstab by adding more row or column groups, or by
using another summary function, such as sum, average, or percent. For example, the
following crosstab shows the sum of the monthly cost of food for each pet (measure) by
gender (column) and group and species (rows). Note that when there are multiple row or
column groups in a crosstab, they are displayed hierarchically.
Figure 284: Example of a crosstab with multiple row groups and a sum
Crosstabs in JasperReports support row and column groups, totals and subtotals, and
individual cell formatting. Data to fill the crosstab can come from the main report dataset
or from a subdataset.
This chapter has the following sections:
• Example of Creating a Crosstab
• Working with Crosstab Properties
• Using the Crosstab Editor
• Working with Crosstab Parameters
3. Drag the Crosstab tool into the Summary band. The Dataset page of the Crosstab
wizard is displayed.
4. For this example, make sure that Create a Crosstab using an existing dataset is
selected, and select [Main Dataset] from the dropdown menu.
5. Click Next. The Columns screen is displayed.
6. Enter one or more fields that you want as column groups. For this example, choose
the ORDERDATE field.
7. Select the ORDERDATE field. Then click the Unique value in the Calculation column
and select Year from the dropdown menu. This aggregates the orders by year.
When you have a time field in your crosstab, you can use the Unique aggregation
function to group records having the same value, or you can aggregate it any of the
following ways:
• Using a time-based aggregation function (such as Year, Month, Week, or Day)
when you define the group
In this example, this is shown in the previous step.
• Using a dataset query when you create the crosstab.
In this example, in the first step of the wizard, you could create a dataset
that uses a query that returns the year, such as select ORDERDATE, SHIPVIA,
SHIPPOSTALCODE, SHIPCOUNTRY, SHIPPEDDATE, YEAR(SHIPPEDDATE) as
SHIPPEDYEAR from orders.
• Manually editing the element expression in the crosstab editor after the crosstab
has been created, as described in Editing the expression of a group.
In this example, you could change the column element expression from $F
{SHIPPEDDATE} to YEAR($F{SHIPPEDDATE}).
10. Make sure that the fields appear in the order you want them in the crosstab. For this
example, ensure that SHIPCOUNTRY appears first in the list by selecting it and
clicking Up.
Grouping by SHIPCOUNTRY and then SHIPPOSTALCODE results in each row in the
crosstab referring to a specific country, with subgroups by postal code within the
country. Unlike in the main report, JasperReports sorts the data for you, although
you can disable this function to speed up the fill process if your data is already
sorted.
11. Click Next. The Measures screen is displayed.
12. Enter one or more fields that you want as measures. For this example, choose
ORDERID.
Measures define the detailed data in the crosstab. Normally, this is the result of an
aggregation function like the count of orders by country by year, or the sum of
freight for the same combination (country/year). By default, the aggregate function
is Count, which is what we want for this example. To change the aggregate function,
you would select ORDERID, click Count, and select a different value from the
dropdown menu.
16. Select the crosstab to display a border with handles. Drag the right-hand handle of
the crosstab to the right margin of the report.
17. Preview your report. You see a crosstab. The row and column headers are the values
of the fields that you selected for the rows and columns. For each row and column,
the value is the number of orders for that year and postal code.
You can set the dynamic page width for the crosstab reports by adding the following
property to the JRXML file.
<property name="net.sf.jasperreports.export.pdf.size.page.to.content" value="true"/> -
When set to true, it enlarges the PDF page when a crosstab report is exported to PDF
format.
• Repeat Column Headers – When selected, the column headers are printed on every
page when the crosstab spans additional pages.
• Repeat Row Headers – When selected, the row headers are printed on every page
when the crosstab spans additional pages.
• Column Break Offset – Specifies the vertical space between sections of a crosstab
when the crosstab exceeds the page width and two sections appear on the same
page.
You can export a report with crosstab in the Microsoft Excel - Metadata(.xlsx) format from
the JasperReports Server. To do so, in Jaspersoft Studio, select the Ignore Pagination on
the Report tab in the properties view. As a result, you can get tabular data on a single
page.
3. Drag an outline to resize the row or column. Make sure that the cells are large
enough to contain their content completely when you run the report.
Figure 294: Outline tree view – crosstab details in the crosstab editor
When you preview the crosstab, the second row group is now bucketed by the first
character of the postal code.
The new group is added to the crosstab as the innermost row group.
5. To set the value class of the group, select the top-level node of the new SHIPREGION
group in the outline view of the crosstab editor. Then, in the Cell tab of the
properties view, enter the following value:
• Value Class Name – java.lang.String
6. Change the order of the groups by selecting the top-level node of SHIPREGION in the
outline view and dragging it above SHIPPOSTALCODE.
7. Preview the report.
A crosstab can have multiple measures. If you add multiple measures when you first create
a crosstab, each measure shows up under the Measure node in the outline view of the
crosstab editor. You can also add measures after the crosstab has been created by
dragging a text field into a measure cell in your crosstab and setting an expression. In this
case, the measure is only visible in the detail node of the outline view. For an example of
adding a measure and setting its expression, see Adding a Measure as a Text Field.
Expressions for elements in a crosstab, such as print-when expressions and text field
expressions, can only contain measures. In this context, you cannot use fields, variables,
or parameters directly. You always have to use a measure.
Measure Properties
The following properties are available for measures that you added when you first created
the crosstab:
• Name – Name of the measure.
• Calculation – Calculation to use for the measure. See Calculation Function for more
information.
• Percentage of Type – Set this to Grand Total to display your measure as a
percentage of the grand total.
• Value Expression – Expression to use for calculating the measure. To edit this
expression, click .
• Value Class – Java class to use for the expression.
• Incrementer Factory Class Name – Optional custom Incrementer class. Use this to
implement your own calculation if the available calculation types are not sufficient.
Class must be instantiated via a factory that implements the
net.sf.jasperreports.engine.fil.JRIncrementerFactory interface.
• Percentage Calculation Class Name – Optional custom calculator class to perform
the percentage calculation. Must use the
net.sf.jasperreports.crosstabs.fill.JRPercentageCalculator interface.
Adding a measure
1. Create a report:
a. Choose a blank template.
b. Select the Sample DB data adapter and click Next.
6. Drag a text field into the intersection of the first row and column.
The text field is added to the column.
9. Click to the right of the Expression field to open the expression editor.
10. Add a formula to calculate the following percentage:
(Number of orders placed in this country and in this year) / (All orders placed in
this country)
For Java, use the following expression:
new Double(
$V{ORDERID_MEASURE1}.doubleValue()
/
$V{ORDERID_MEASURE1_ORDERDATE1_ALL}.doubleValue()
)
(double)$V{ORDERID_MEASURE1} / (double)$V{ORDERID_MEASURE1_ORDERDATE1_ALL}
A percentage must be treated as a floating-point number. For this reason, extract the
double-scalar values from ORDERID_MEASURE1 and ORDERID_MEASURE1_
ORDERDATE1_ALL objects even if they are the objects of the class-type Integer.
Use crosstab parameters in the crosstab elements. They are not the same as the dataset
parameters that are used in expressions, in the crosstab context, to filter a query and
calculate values.
2. In the outline view, right-click the Parameters node in the Crosstab element and
select Create Parameter.
3. To set the value of the crosstab parameter, double-click the parameter to open the
expression editor. Create an expression for your parameter and click OK.
You can use a map to set the value of the declared crosstab parameters at run time. In this
case, you need to provide a valid parameters map expression in the crosstab properties.
You can set the following map properties using the Map tab:
• Map Preview – Opens a Google Maps window. This window supports standard
Google Maps functionality, such as dragging, zooming, and switching between Map
and Satellite views.
Changes to this window are reflected in the map in your report. In addition, you can
change the map's center in any of the following ways. When you close the preview,
the map is automatically centered at the selected location:
• Address – Enter an address in the entry bar to center the map at that location.
• Latitude and Longitude – Enter a latitude and longitude to center your map at
that location.
• Double-click – Double-click anywhere on the map to center it at that location.
• Map Type – The Google Maps view. Options are: roadmap, satellite, terrain, and
hybrid.
• Latitude – The latitude of the map center. You can type directly in the entry bar, or
click to enter an expression.
• Longitude – The longitude of the map center. You can type directly in the entry bar,
or click to enter an expression.
• Address – A String representing the address of the center. You can type directly in
the entry bar, or click to enter an expression. The value must be enclosed in
quotes, for example, "350 Rhode Island Ave., San Francisco, CA".
• Zoom – Integer representing the Google Maps zoom level. You can type directly in
the entry bar, or click to enter an expression.
• Language – String that sets the in-map language. You can type directly in the entry
bar, or click to enter an expression. The value must be enclosed in quotes, for
example, "ru-RU". See the Google Maps documentation for more information.
• Map Scale – Sets the size of the scale bar at the bottom of the map.
• Evaluation Time – dropdown that lets you set the evaluation time of the map. See
Evaluation Time for more information.
• Image Type – dropdown that lets you set the image type to use when the map is
embedded in your report.
• On Error Type – dropdown that lets you set the type of message to display when
there is an error with the map.
Figure 306: Authentication tab in the Properties view for a map component
1. Select Window > Preferences to open the Preferences dialog (Eclipse > Preferences
on Mac).
2. Navigate to Jaspersoft Studio > Properties.
3. To configure a property, click Add to open the Properties dialog, enter the name of
the property and the property's value, then click OK. You can configure the following
Google Maps APIs properties. See the JasperReports Library configuration reference
for more information on each property:
• net.sf.jasperreports.components.map.client.id – Specifies the client ID for Google
Maps API for Business. If set, it takes precedence over the API key property. It
usually works along with the signature property for signed URLs.
• net.sf.jasperreports.components.map.key – Specifies the Google Maps API key.
• net.sf.jasperreports.components.map.signature – Specifies the encrypted client
signature for signed request URLs.
• net.sf.jasperreports.components.map.version – Indicates which version of the
Google Maps API should be loaded.
4. When you have specified all your properties, click OK to exit the Preferences dialog.
Setting the property globally sets the properties when the report is run inside Jaspersoft
Studio. If you are publishing your reports to another environment, you must enable
these properties in the jasperreports.properties file in your environment.
Marker Properties
You can set properties for each marker. The marker properties available are a subset of
Google Maps' properties. See Marker and Path Properties for more information.
5. Specify a location for your marker. You can do this by entering latitude and
longitude, entering an address, or defining markers on the map preview:
• Latitude and Longitude – Enter the latitude and longitude coordinates for your
marker. You can type directly in the entry bar, or click to enter an expression.
For this example, enter the following values:
• Latitude – 37.833
• Longitude – -122.4167
• Address – The address is used only if Latitude and Longitude are blank. You can
type directly in the entry bar, or click to enter an expression.
6. (Optional) Set the title for your marker, if any.
7. (Optional) To have a new browser window or tab open with related information
when a user clicks the marker, enter the URL and select the Target type.
8. (Optional) Set your icon type (default or custom) and icon properties:
• If you are using the default marker, you can set additional properties, such as
color, label. These properties are not available for a custom icon. This example
uses the color 00CCFF and the label J.
• To use a marker icon other than the default, click Custom Icon to specify a URL
that points to the image to use. Currently, we do not support loading an image
directly from the repository or as a resource local to the report. Instead, the
JavaScript API loads the icon from the URL. Then set additional optional
properties for your marker, such as icon height, width, origin, and anchor.
9. Click OK to return to the Markers dialog.
10. To create additional markers, click Add, enter the marker properties, then click OK
to return to the Markers dialog.
11. Click OK to create your markers.
12. Once you have defined your markers, preview your report in HTML. For this example,
select the Empty Data Set for your preview.
• To edit a marker's location, double-click the marker to open the Marker dialog.
Sample Data
In this example, we use a CSV file containing the following data for San Francisco
landmarks. This file includes data used by markers and paths.
2. Click on the main toolbar. When prompted, navigate to the same folder as your
report.
3. Name the file SFDataAdapter.jrdax and click Next.
4. Select CSV File as the data adapter type and click Next. The CSV File dialog opens.
Figure 310: Creating a sample data adapter for markers and paths
8. For a dataset, you typically want to use expressions for your values. For each
property you want to read from the dataset, click on the entry bar, select Use
Expression and enter the expression to use. For this example, use the following
expressions:
• Latitude – $F{latitude}
• Longitude – $F{longitude}
• Address – $F{landmark}
9. Click OK. The Markers dialog displays the markers you just created.
10. Click OK. Your markers are displayed on the Marker tab of the Properties view, along
with any other markers you have created.
Figure 314: Properties view showing markers added manually and markers defined from a
dataset
11. Preview your report in HTML. The example below shows the markers from the
sample dataset along with a static marker.
Modifying Markers
To edit a marker
1. Select the map and click the Markers tab in the Properties view.
2. Select the marker that you want to change and click Edit.
3. To change the dataset, make sure you have set up another dataset in your report
before editing the marker. Then you can select the Dataset tab here and select the
new dataset from the Dataset Run menu.
4. To change marker properties, select the Markers tab, and edit your properties.
To delete a marker
1. Select the map and click the Markers tab in the Properties view.
2. Select the marker that you want to delete and click Delete.
• A name that serves as a path identifier; the name must be unique in your report.
• A collection of places (points) on the map defined by latitude/longitude coordinates
or addresses. These are connected to form the path.
• (Optional) A style that specifies various style configuration properties, such as line
and fill color, line weight, and opacity.
1. Create a data file with the path data that you want. For this example, create a CSV
file with the data provided above. Make sure to include a blank line at the end of the
file.
5. Click the Dataset tab in the Path dialog and select Use Dataset.
6. In the Dataset Run section, select your styles dataset (PathStyles) and accept the
default settings. You have already set the default data adapter for this dataset.
7. Select the Items tab and click Add to open the Style dialog.
8. For each property you want to read from the dataset, click on the entry bar,
select Use Expression and enter the expression to use. For this example, use the
following expressions:
• Name – $F{name}
• Stroke Color – $F{strokecolor}
• Stroke Opacity – $F{strokeopacity}
• Stroke Weight – $F{strokeweight}
• Fill Color – $F{fillcolor}
• Fill Opacity – $F{fillopacity}
• Is Polygon– $F{ispolygon}
9. Click OK to return to the Items dialog.
10. Click OK to create the style set.
Figure 316: Styles on the Path tab of the Properties view for a map
4. Select your path from the Paths menu. The Paths menu has the following
characteristics:
• If you already have static paths defined for your map, you can select a path
name from the Paths menu. Points you create are added to the currently
selected path. You can switch between paths at any time.
• If you have not created any static paths, then you can enter a name on this
menu. If a static path exists, you cannot create a one.
5. To add a point to the current path, right-click on the location you want and select
Add marker.
6. To delete one or more markers, select the markers in the panel at the right and
press Delete, or right-click on the marker and select Delete.
9. For each property you want to read from the dataset, click on the entry bar,
select Use Expression, and enter the expression to use. For this example, use the
following expressions:
• Path Name – $F{path}
• Latitude – $F{latitude}
• Longitude – $F{longitude}
• Address – $F{landmark}
• Style – $F{style}
10. Click OK. The path information is added to the Path section in the Properties view.
11. Preview your report in HTML. The following image shows the example without
markers. If you added the markers earlier, they are also visible.
3. To change the dataset, make sure you have set up another dataset in your report
before editing the path or path style. Then you can select the Dataset tab here and
select the new dataset from the Dataset Run menu.
4. To change path or style properties, select the Items tab, and edit your properties.
Property Description
Name String. Name used to identify the marker or path; must be unique for markers
or paths in the report.
Latitude Number between -90 and 90. The latitude of a location is in degrees.
Longitude Number between -180 and 180. The longitude of a location is in degrees.
Address String. The address or placeID of a location. Only used if Latitude and
Longitude are not available.
Color String. The color of the path or marker. For best results, use hexadecimal
representation, as not all Google API implementations support color strings.
Clickable Boolean. When true, the marker or path can handle mouse events. Default is
true.
Draggable Boolean. When true, a user can drag the marker or path contour. Default is
false.
Property Description
Visible Boolean. When true, the marker or path is visible. Default is true.
Z Index Number. The index determining the order in which objects are displayed on
the map. Elements with higher values are displayed in front of similar
elements with lower values. Markers are always displayed in front of paths.
Target String. Target attribute specifying where to open the linked document.
Custom Icon Use Custom Icon settings to use a marker icon other than the default. You
must specify a URL that points to the image to use. Currently, we do not
support loading an image directly from the repository or as a resource local to
the report. Instead, the JavaScript API loads the icon from the URL.
You can set additional optional properties for your marker, such as icon
height, width, origin, and anchor.
Custom Use Custom Shadow Icon settings to use a shadow icon other than the
Shadow Icon default. You must specify a URL that points to the image to use. Currently, we
do not support loading an image directly from the repository or as a resource
local to the report. Instead, the JavaScript API loads the icon from the URL.
You can set additional optional properties for your shadow, such as height,
width, origin, and anchor.
Info Window Use the Info Window settings to add an info window. You can define the
window content, pixel offset, and maximum width.
Label String. Single character that appears on the marker. Not available for custom
Property Description
markers.
Cursor String. Mouse cursor to show on hover. Not available for custom markers.
Parent Style String. Name of path style to use as a parent style. The current style inherits
the parent's properties if the parent style is present in the report. Elements
set locally in the current style override elements set in the parent.
Stroke Color String. Color of the stroke; for most consistent results, use hexadecimal
format. The default is #000000.
Stroke Number. The path's opacity. Number between 0 (transparent) and 1 (opaque).
Opacity The default is 1.
Fill Color String. Color of the fill for the polygon when Is Polygon is true. Takes values in
hexadecimal format. The default is null.
Fill Opacity Number. The opacity for the polygon's fill when Is Polygon is true. Number
between 0 (transparent) and 1 (opaque). The default is 1.
Is Polygon Boolean. When true, creates a polygon (closed path) by connecting the last
point on the path to the first point. The default is false (open polyline).
Property Description
Editable Boolean. When true, a user can edit the path by dragging the control points
on the path line. Default is false.
Geodesic Boolean. When true, dragged paths follow the great circles on the earth's
surface. In this case, since the map is a projection, the lines may not appear
straight. When false, paths are straight lines on the map. Defaults to false.
This section describes functionality that can be restricted by the software license for JasperReports
Server. If you don’t see some of the options described in this section, your license may prohibit you
from using them. To find out what you're licensed to use, or to upgrade your license, contact
Jaspersoft.
In addition to the other types of map component that Jaspersoft Studio supports, TIBCO
GeoAnalytics Maps are also supported. These multi-layer maps are designed for use in
interactive web environments, and support both markers and paths. They also support the
ability to provide a street address and resolve it to the correct latitude and longitude
(sometimes called geolocation).
Because these components download content from either TIBCO's service or from Google
Maps, they require a connection to the Internet. While the maps themselves are freely
available, using the GeoAnalytics geolocation serve to resolve street addresses requires an
additional license.
These maps are well suited to web-based environments, such as HTML export or
when viewed through an interactive viewer such as JasperReports Server; however,
limitations in the underlying technology prevent some TIBCO GeoAnalytics Map
features from working in static formats, such as PDF. In this case, the map is
converted to an image, which is always downloaded from Google Maps instead of
TIBCO's server. In addition, if the map's location is resolved from a street address, the
canvas may be blank (or blue); this happens when the address's latitude and
longitude are not available.
If your target output format is something other than HTML, consider using the
standard map component.
The map component consists of three layers: a map, a set of paths, and a set of markers.
The lowest layer contains the map itself, rendered by your choice of providers: TIBCO Maps
or Google Maps. In both cases, the image is formed of tiles retrieved from a remote server.
The next two layers (first paths then markers) can contain paths and markers or shapes.
defining them in the jasperreports.properties file so that they can share across
multiple reports. These properties are:
• com.jaspersoft.jasperreports.tibco.maps.customer - the customer name used
with TIBCO GeoAnalytics Maps
• com.jaspersoft.jasperreports.tibco.maps.key - the corresponding license key for
the specified user
2. To define a location, edit the TIBCO Maps component's Location properties. Entering
a latitude/longitude pair or address defines a static location. You can also use
parameters to define the components location and all other TIBCO Map properties
dynamically.
Map attributes determine how the map layer of the component is rendered. The attributes
are all optional:
Use Canvas true false This property refers to the way that the map is rendered (by using a
canvas or SVG layers)
Repeat X true | Specifies whether tiles are repeated when the world's bounds are exceeded
false horizontally
To specify a different dataset to resolve the map attributes based on expressions, click the
Use Dataset checkbox to select it, and select the dataset to use in the Dataset Run.
Figure 321: Defining the Dataset to use to resolve map attribute expressions
Data Runs are used throughout Jaspersoft Studio and its related products when a report
includes a subdataset. Use a Data Run to define values for the subdataset's parameters.
Understanding Layers
Each layer in the map component controls different aspects of the final map rendered in
your report:
• The maps layer defines the map tiles that are displayed by the component's image,
which are determined by its location and zoom, the maximum and minimum zoom
allowed in the component, and the image's opacity.
• The marker layer defines locations on the map that display an image you select.
• The path layer defines lines between locations on the map.
Each layer can be named uniquely. These names can be displayed in the JasperReports
Server interactive report viewer in the Layers dropdown; this allows your user to select
which layers to drawn.
Figure 322: Layer names defined in the component can control the layers drawn in the final
report
Static Markers
1. Edit the map component's properties.
2. On the Markers tab, click Add.
3. Define your marker by specifying a location and icon. The list of properties for a
marker includes:
• target
• string
• optional
• _blank
• The hyperlink target for the marker
4. Specify the icon as a URL that points to the image to use. It's loaded by the
JavaScript API.
Jaspersoft does not currently support loading an image directly from the repository,
or as a resource local to the report.
The location can be set by latitude/longitude coordinates or an address to be
geolocated, as described above.
5. For the addresses, set each property to form the address: country, state, zip, city,
street.
This is a simplified example. The more common scenario is to read location data from the
database.
Dynamic Markers
The steps above define the marker as a static address known when the report was created.
But it is far more useful to define the markers based on locations in your report's data
dynamically. A single map can use both static and dynamic markers, and locations can be
based on data from more than one data source.
In this example, we use data from the City College of San Francisco's public facilities data
set that we have saved as an Excel file.
Building B
Since the data set includes both street addresses and latitude/longitude pairs, we can
explore both functions.
6. Click OK.
7. Use the data adapter to populate the dataset. With the CollegeFacilities dataset
selected in the outline view, click the Advanced tab in the Properties view, then
select the property Properties and click the button ellipsis to open the properties
dialog.
8. Add a property: net.sf.jasperreports.data.adapter, and specify the name of the data
adapter file saved earlier (CollegeFacilities.jrdax).
We can use this new dataset to set markers on the map.
9. Select the map in the Design tab, click the Markers tab, and click Add.
10. Click Dataset, check the Use Dataset checkbox, and click Add.
11. Select the CollegeFacilities dataset and accept the defaults. Studio uses the data
adapter referenced by the net.sf.jasperreports.data.adapter property set previously
for this dataset.
12. Click OK.
The dataset is added to the list of datasets that we use for markers.
13. Click Values and create an expression for each marker property: for example, provide
the title, street, city, state, country.
This example uses an icon from the web: Pink Push Pin.
14. Click OK.
You can color each state or region with a different color. To do so, select the Plot Options
section and set Color by Point to true. Color for each region is picked from the Color
Palette. The process flows in a circular way. When the last color is picked up from the
palette, the next color is the first color in the same palette.
Figure 332: Simple Map with Inner Borders and Color by Point Property Enabled
The two sets of data, map data and chart data are generated independently of each other.
You can use both of them in the same map element. The data can be joined by using a
field or column with common values in both Map and Chart data sets.
This section describes:
• Retrieving Chart Data
• Joining Data Using the Default hc-key Field
• Configuring Chart Data of the Map
• Joining Data Using a Pair of Related Fields
• Rendering a Subregion of the Map
• Creating a Hyperlink
• Zooming in the Map
• Adding Map Navigation Control
4. If there is no hc-key under Measures, click Add and follow step 4 to step 11 to add
the hc-key value for each chart data point. Enter the following values:
• Name: hc-key
• Select the Hidden checkbox
• Label Expression: $F{hc-key}
• Calculation: Nothing
• Value Expression: $F{hc-key}
• Value Class Name: java.lang.String
5. Click OK.
6. Under Measures, select Measure1 and click Modify.
7. Click the Advanced Properties tab and click Add. The Edit Property dialog is
displayed.
8. Set the following values:
• Contributor: SeriesItemProperty
• Property Name: hc-key
9. Select the Use Measure Value and then select the hc-key from the dropdown list.
You can see that the color of the map has been changed. This is because when you link the
chart data to the map, the Color Axis property takes precedence over the Color by Point
property.
• Min: 0
• Max: 40000000
• Tick Interval: 10000000
• Min Color: #88FCEF
• Max Color: #2E0EE6
3. To configure a map legend for adding quantitative information, select the Legend
section and set the following. For example:
• Show Legend: true
• Background Color: #FFFFFF
4. Select the Tooltip section and set Show Tooltip to true.
5. To add hc_a2 value for each chart data point, on the Data Configuration tab, click
Switch to advanced configuration.
6. In the Measures section, click Add. The Measure dialog is displayed.
a. Enter the following values:
• Name: hc_a2
• Select the Hidden checkbox
• Label Expression: $F{hc_a2}
• Calculation: Nothing
• Value Expression: $F{hc_a2}
• Value Class Name: java.lang.String
b. Click OK.
c. Under Measures, select Measure1 and click Modify.
d. Click the Advanced Properties tab and click Add. The Edit Property dialog is
displayed.
e. Set the following values:
• Contributor: SeriesItemProperty
• Property Name: hc_a2
• Select the Use Measure Value and then select hc_a2 from the dropdown list.
7. In the Plot Options section, select Data Labels and set the following:
• Enabled: true
• Format: {point.hc_a2}
8. Click to refresh the preview.
In the join expression, always start with the name of the field in the GeoJSON map data
(that is "hc-a2").
2. Click to refresh the preview. You can see that the data is correctly mapped and
the map remains the same.
Figure 341: Displaying Data for the West Region of the United States
In case you provide null for the Value Expression and set the inner borders visible and the
Render All Areas to false, the map looks like this:
Creating a Hyperlink
The HTML5 map component also supports hyperlinks. You need to create a hidden
measure to associate a hyperlink with every state on the map.
To create a hyperlink
1. Change the expression of Value Expression back to $F{value}.
2. Under Measures, click Add to add a new hidden measure and enter the following
information:
• Name: linkName
• Select the Hidden checkbox.
• Label Expression: $F{name}
• Calculation: Nothing
• Value Expression: "https://en.wikipedia.org/wiki/" +$F{name}
1. On the Map Formatting tab, select the Map section and enter the following
information:
Zoom Type: xy
Because the HTML5 maps are two-dimensional, setting the Zoom Type to ‘x’ or ‘y’
generates only proportional responses. For instance, if Zoom Type is set to ‘x’ only, the
‘y’ dimension cannot grow beyond the y-axis bounds, it enlarges with a small fraction.
As a consequence, the ‘x’ dimension enlarges proportionally with the same fraction.
The zoomed region is magnified. You can also reset the map dimensions to their initial
values by clicking the Reset zoom button in the upper-right corner of the Preview window.
The map navigation control button is added on the upper-left corner in the Preview
window; you can click the "+" or "-" button to zoom in or zoom out the map.
Subreports also let you combine two or more child lists of data relating to a single parent
element, for example, a report with multiple detail bands of different types. You map
parameters between the master report and its subreports to create a blended report where
each subreport displays details for each record from the master report. As the master
report runs, each time a subreport element is reached, it is run and its content is
embedded into the output of the master report.
Uses for subreports include:
• Modularizing reports–You can create a subreport with your preferred data fields and
layout, then use the subreport in multiple master reports.
• Combining multiple queries or data sources in a single report.
2. Select Create a new report and click Next. The New Report Wizard > Report
Templates window is displayed.
3. Select a template for your subreport. For this example, select one of the blank
templates. Click Next. The New Report Wizard > Report file window opens.
4. Select a location for your subreport, and name it. Click Next. The Data Source
window opens.
5. Choose to use the same data adapter as the main report, or a different data adapter.
For this example, choose the same adapter (Sample DB). Enter the following SQL
query:
select count (*), shipcity from orders group by shipcity
6. Click Next.
7. Add all the fields to the list on the right. Click Next.
8. Click Next to skip the Group By step. The Subreport > Connection window opens.
9. Choose to connect either to the same database as the main report or to a different
database. For this example, click Use same connection used to fill the master report.
10. Click Next. The Subreport Parameters window opens.
11. For this example, skip this window and click Finish. A new report opens containing
all bands.
12. Delete all bands but the Title or Summary band to eliminate extra white space in
your report.
You now have a location into which to place your table, chart, or other element
attached to the new subreport.
Understanding Subreports
There are three steps to creating and adding a subreport:
1. Create a report–Create a parent or master report that contains the subreport.
2. Create a subreport–Create and compile a subreport. Optionally create a dynamic
connection to filter the records of the subreport based on the parent’s data.
3. Add the subreport to the parent report–Insert a subreport element and specify the
following:
• The data adapter or data source for the subreport.
• The location of the subreport's compiled Jasper file.
• An optional parameters map (it can be empty) to set the report parameters used
in the dynamic connection.
Subreports
A subreport is simply a report composed of its own JRXML source and compiled in a Jasper
file. Generally speaking, creating a subreport is very similar to creating any other report.
The margins of a subreport are usually set to zero for subreports because a subreport is
meant to be a portion of a page, not an entire document. The horizontal dimension of the
subreport should be as large as the element into which it is placed in the parent report.
Subreport Elements
You add a subreport to a report by dragging the Subreport element from the palette. At
design time, the element is rendered as a rectangle with the dimensions specified in the
subreport.
The Subreport element does not need to be the same size as the subreport. You can
think of the Subreport element as a place holder defining the position of the top-left
corner to which the subreport is aligned. However, we recommend that you set the
dimensions of the Subreport element to the dimensions of the subreport to visualize
the layout of the final report.
Property Description
Run To Bottom When true, the subreport element consumes the entire vertical space
available on the report page.
Overflow Type When not specified, the subreport stretches to accommodate the
content.
Expression (Required) Expression that can be used to load the Jasper object to
use when filling the subreport portion of the document. Evaluated at
run time to retrieve the Jasper object for the subreport.
Using Cache Specifies whether the subreport's report object is kept in memory or
reloaded each time it is used. It is common for a subreport element
to be printed more than once (or once for each record in the main
dataset).
Property Description
Datasource to the subreport. This option is useful at times. In this case, the
Expression subreport should have the document property When No Data Type
set to something like All Sections, No Detail, or No Data Section.
Edit Return Values Allows you to define how to store values in local variables calculated
or processed in the subreport (such as totals and record count).
Edit Parameters Allows you to define name/expression pairs used to set a value for
the subreport parameters dynamically.
The following properties must be set to link the subreport to the parent report:
• Expression – Retrieves the Jasper object that implements the subreport.
• Connection Expression or Datasource Expression – Defines how to feed the object
with data.
• Parameters – Sets the values of the subreport parameters.
This means that using an expression of type String means you are in some way trying to
specify a file path. Optionally, you can put your Jasper file in the classpath and refer to it
as a resource, using an expression something like "subreport.jasper".
You cannot use a relative path to locate the subreport file; that is, if you have a report
in c:\myreport\main_report.jasper, you cannot refer to a subreport using an expression
like ..\\mysubreports\\mysubreport.jasper.
This is because JasperReports does not keep in memory the original location of the
Jasper file that it is working with. This makes perfect sense, considering that a Jasper
object is not necessarily loaded from a physical file.
To simplify report design when loading a subreport from the file system, do one of the
following:
• Place the subreport file in a directory that is in the classpath. This permits you to
use very simple subreport expressions, such as a string containing just the name of
the subreport file (that is, “subreport.jasper”). Jaspersoft Studio always includes the
classpath of the directory of the report that is running, so all the subreport Jasper
files can be found easily if they are in the same directory.
• Parametrize the Jasper file location and create on-the-fly the real absolute path of
the file to load. This can be achieved with a parameter containing the parent
directory of the subreport (let us call it SUBREPORT_DIRECTORY) and an expression
like this:
$P{SUBREPORT_DIRECTORY} + "subreport.jasper"
One advantage of this approach is that you can use the Jasper files’ local directory
as the default value for the SUBREPORT_DIRECTORY parameter. The developer who
integrates JasperReports in his applications can set a different value for that
location just by passing a different value for the SUBREPORT_DIRECTORY parameter.
• Use another connection–Select this to specify a different JDBC data adapter for the
subreport.
• Use a JRDataSource expression–Select this to use a JRDataSource object to fill the
subreport.
• Use an empty datasource–Select this to set the data source expression to new
JREmptyDataSource(). That creates a special data source that provides a single
record with all the field values set to null. This is useful when the subreport is used
to display static content such as headers, footers, and backgrounds. In this case, in
the subreport, set the report property When no data type to All Data No Details or
No Data Section to ensure that at least a portion of the document is actually
printed.
JDBC connections make using subreports simple enough. A connection expression must
identify a java.sql.Connection object (ready to be used, so a connection to the database is
already opened). Typically, we run the SQL query using the same database connection as
the parent report; the connection can be referenced with the REPORT_CONNECTION built-
in parameter. It must be clear that if we pass a JDBC connection to the subreport, it is
because we defined an SQL query in the subreport, a query that is used to fill it.
Using a different data source is sometimes necessary when a connection like JDBC is not
being used. It is more complicated but extremely powerful. It requires writing a data source
expression that returns a JRDataSource instance that you then use to fill the subreport.
Depending on what you want to achieve, you can pass the data source that feeds the
subreport through a parameter, or you can define the data source dynamically every time
it is required. If the parent report is run using a data source, this data source is stored in
the REPORT_DATASOURCE built-in parameter. On the other hand, the REPORT_
DATASOURCE should never be used to feed a subreport. A data source is a consumable
object that is usable for feeding a report only once. Therefore, the parameter technique is
not suitable when every record of the master report has its own subreport (unless there is
only one record in the master report). When we discuss data sources this is clearer and you
see how this problem is easily solved with custom data sources. You also see how to create
subreports using different types of connections and data sources.
Subreport Parameters
One of the most common uses of subreport parameters is to pass the key of a record
printed in the parent report to run a query in the subreport through which you can extract
the records referred to (report headers and lines). For example, let us say you have in the
master report a set of customers, and you want to show additional information about
them, such as their contact info. The subreports use the customer ID to get the contact
info. The customer ID should be passed to the subreport as a parameter, and its value
changes for each record in the master report.
To pass parameters from the master report to a subreport, you create a set of parameter
name/object pairs that feed the parameters map of the subreport. To do this, click the Edit
Parameters button on the Subreport tab of the Properties view to open the Subreport
Parameters dialog.
When a report is invoked from a program (using one of the fillReport methods, for
instance), a parameters map is passed to set a value for its parameters. A similar
approach is used to set a value for subreport parameters. With subreports you do not
have to define a map (even, if possible, specifying a Parameters Map Expression). The
report engine takes care of that for you.
To configure a parameter you want to pass to the subreport, click Add in the Subreport
Parameters dialog to open the Parameter Configuration dialog, which lets you set the
following:
• Name–Name of the parameter. A parameter must have the same name in the master
report and the subreport. Parameter names are case-sensitive.
If you make an error in typing the name or the inserted parameter has not been
defined, no error is generated. In most cases, the report fails silently.
map to the subreport. It is also possible to pass to the subreport the same parameters map
that was provided to the parent by using the built-in parameter REPORT_PARAMETERS_
MAP. In this case the expression looks like this:
$P{REPORT_PARAMETERS_MAP}
Since the subreport parameters can be used with this map, you could even use it to pass
common parameters, such as the username of the user running the report.
Report Templates
Templates are one of the most useful tools in Jaspersoft Studio. You can use the provided
templates as the basis for new reports. You can also use a template as a model and add
fields, text fields, and groups in the Report Wizard.
This chapter explains how to build custom templates that appear in the Template Chooser.
It has the following sections:
• Template Structure
• Creating and Customizing Templates
• Saving Templates
• Adding Templates to Jaspersoft Studio
You can also create JasperReports Server templates and upload them to the server. See
Working with JasperReports Server Templates.
Template Structure
A template is a JRXML file. When you create a report, Jaspersoft Studio loads the selected
template's JRXML file with any modifications you have specified in the wizard. If you do not
use the wizard, your template is just copied along with all the referenced images in the
location you have specified.
When you open the Report Template dialog (File > New > Jasper Report) scans all paths
specified as template directories. Any valid JRXML files found are included in the Report
Template dialog. If a template provides a preview image, the image is displayed.
Otherwise, a white box appears.
A template contains all or some of the same parts as a report. Remember the following
when creating a template or editing an existing template:
• A report's page formatting is the page formatting of its template.
• Each band in a report is, by default, the same size as that band in its template.
• Every element placed in the Summary, Title, Page Header and Page Footer bands of
a template appears in every report that uses that template.
• The Column Header band should contain only a Static Text element, and its text
content must be Label. The appearance, font, and the other attributes of this label
create every label inserted in this band.
• The Group Header band should contain only a Text Field with the string
“GroupField” (including the double quotes). As with the Column Header this
assumes an example to generate every field that goes in this band.
• The Detail band should contain only a Text Filed with the string “Field” (including
the double quotes). Again, this is used to generate every field that goes in this band.
When you group data using the wizard, the wizard creates all the necessary report
structures to produce your groups. The Report Wizard supports up to four groups, with a
group header and group footer associated with each. If the template defines one or more
groups and you group the data, the wizard tries to use any existing groups before creating
a group. By default, groups in the template are deleted if they are not used. For each
group, the wizard sets the group expression and adds a label for the name and a text field
showing the value of the group expression (which is always a field name, because the
grouping criteria set using the wizard is one of the selected fields).
To create a template
1. Go to File > New > Jasper Report to open the New Report Wizard.
2. Select a template to start. Click Blank Letter and Next.
3. Choose where you want to store the file, name the new template, and click Next.
For creating a template, there is no need to connect to a data source.
4. Select One Empty Record - Empty rows and click Finish.
6. Name your group and click Next. The Group Layout dialog is displayed.
7. Leave both Add the Group Header and Add the Group Footer checked, and click
Finish.
Your report is similar to the one in Report Containing Group Header and Footer.
Customizing a Template
Now that you have a blank template, you can customize it to suit your preference. For
example, you can add your company name and logo, page numbering, add a background
for your report, and set band and column sizes. You can also use this procedure to change
an existing template.
To customize a template
1. Add a graphic: Drag an Image element where you want the image to appear. This is
usually the Title band.
For more information about the Image element, see Graphic Elements.
2. Add a title: Drag a Static Text element to the Title band. Style the text in the
Properties view. For more information about Static Text elements, see Text
Elements.
3. Want the background to cover the entire page? Right-click the element in the
Outline and choose Maximize Band Height. Otherwise, set the Background band to
the size you want. Drag an Image element into the Background band to create your
background.
4. Add page numbering to the Page Footer band: Drag a Page Number element into the
band, and place it where you want it. You can also add a Page X of Y element if you
prefer.
5. Want a label in the Column Header band? Add a Static Text element with the text
“Label”.
6. Set styles for your report’s text: Add a Text field to the Group Header and a Text
field to the Detail band. Set the text of the first Text field to “GroupField” and the
text of the second Text field to “Field”. Format the text as you like.
7. Save your template file.
8. Click the Preview tab. Your template should like something like the one in Template
Preview.
Saving Templates
Jaspersoft Studio templates require a flat folder structure (resources and reports in the
same folder). This way, when you export a template, the paths and resources in the
exported report point to the same directory.
2. Click the New... button and navigate to the directory in which you want to store your
template.
Exporting a Template
Save your template for future use.
1. Go to File > Export as Report Template. The Template Export dialog opens.
2. Click the Browse button and navigate to the directory where you want to save your
template. Click Next.
The Define Type and Categories dialog opens.
3. In the dropdown, choose whether the template type is a Standard Report or a Table-
Based report.
This selection is used to validate the report. For example, by selecting Standard
Report, the validation process searches for the group field with the text group or for
the column header label with the text label. If any of the required fields are not
found, an error message is displayed.
4. Select the categories for the template available and use the arrow button to add
them to the Selected Categories.
5. Click Finish.
4. Click Apply.
5. Click OK.
When you go to File > New > Jasper Report, your new template appears, along with the
default templates.
Report Splitting
With report splitting, you can run a report in a JasperReports Server scheduler and get the
output into the individual parts. Each part of the report is saved separately in the
repository and sent to different recipients. Report splitting is based on the report parts. You
can create report parts using a band-based report or a report book. The following example
shows a report splitting procedure using a band-based report.
15. Run the report in the scheduler. To do this, right-click the report and select Run in
Background from the context menu.
16. On the Output Options tab, set the output options and click Submit.
17. On the Notifications tab, enter the email address and subject of the email to be sent
to each recipient. Provide dynamic values in the following text fields To, CC, and
Subject.
18. Select the Include report files as attachments option and click Submit.
A single report is split into three separate reports and sent to the email addresses of
different recipients.
Report Books
A report book is a single .jrxml that bundles multiple reports into a single object. Like a
single report, a report book is driven by a data set that allows you to define the flow of the
book’s sections, and the parts within those sections.
This section provides a walkthrough of the report book creation process, using the
sample.db included with your JasperReports Server installation. You create a cover page,
table of contents, and subreports to build into your report book.
Creating a report book has a number of separate tasks, including:
• Creating the Report Book Framework
• Creating and Adding Reports to the Report Book
• Refining the Report Book
• Configuring the Table of Contents
• Report Book Pagination
• Publishing the Report Book
5. In the Project Explorer, select the My Reports folder, change the file name to
Sample_Book.jrxml, and click Next.
6. In the Data Source window, select a data adapter. For our walkthrough, use Sample
DB – Database JDBC Connection.
7. In the text panel, enter the following query then click Next:
select distinct shipcountry from orders order by shipcountry
8. In the Fields window, move SHIPCOUNTRY from the Dataset Fields panel to the
Fields panel and click Next.
9. In the Book Sections window, make sure that all three options are selected:
• Create Cover Section
• Create Table of Contents
• Create Back Cover Section
10. Click Finish.
Your Report Book project opens in Jaspersoft Studio.
In Jaspersoft Studio, open the Project Explorer and expand the My Reports folder. There,
you can see the jrxml files you just created:
• Sample_Book_backcover.jrxml
• Sample_Book_cover.jrxml
• Sample_Book_toc.jrxml
• Sample_Book.jrxml
Sample_Book.jrxml is open in the main Design tab. This is the file in which you organize
the report parts. You notice three groups for the book part types:
• Cover and Table of Contents contains Sample_Book_cover.jrxml and Sample_Book_
toc.jrxml.
• Content is empty.
• Backcover contains Sample_Book_backcover.jrxml
When you select each these book parts in the design window, you can view and edit their
properties in the Properties View, as you can with standard reports and subreports.
Next, you create a subreport and add it to your report book.
• CUSTOMERID
• FREIGHT
• SHIPCITY
• SHIPCOUNTRY
8. Click Next.
9. In the Group By window, move the SHIPCITY dataset field into the Fields pane.
10. Click Finish. The Content_Page_One.jrxml appears in the Design tab.
11. In the Project Explorer, right-click Content_Page_One.jrxml and select Compile
Report. The resulting file, Content_Page_One.jasper, appears in the Project Explorer.
10. Click OK and confirm that the parameter has been added to the Part Parameters list,
then click Finish.
12. Click to open the Expression Editor, and click Fields in the left panel.
13. Double-click SHIPCOUNTRY Field String to add it to the expression, then click Finish.
14. Click OK in the Parameter Configuration Dialog, then Finish in the Report Part
Parameters window.
4. In the Designer view, click to open the Dataset and Query Dialog.
5. Modify the query to say:
select count(*) c, shipcity from orders where shipcountry = $P{Country} group by
shipcity
6. Click OK.
7. Save Country_Intro.jrxml.
8. In the Outline view, drag Country from the Parameters list into the Title band.
9. Click the Country parameter ($P{Country}).
10. In the Properties view, click Text Field. Increase the font size to 26.
11. Click outside the parameter element.
Next, you can add a chart to the intro pages that provides a graphical representation of the
data in the section.
8. Select Fields from the first column, and double-click SHIPCITY Field String to add it
to the expression.
9. Click Finish.
10. Update the Name field to "City" and click OK.
11. Back in the Chart Properties dialog, update the following information:
• Name: Number of orders.
• Label Expression: "Number of orders"
• Calculation: Nothing
• Value Expression: Delete new Integer1, click , and double-click C Field Long,
then click Finish.
12. Click OK, then save the report.
13. Compile Country_Intro.jrxml to create a .jasper file.
Now, you can add the Country_Intro page to your book, and configure it to display the
correct data.
To add bookmarks
1. Open Country_Intro.jrxml in the Design tab.
2. Click the Country parameter in the Title band.
3. In the Properties view, click Hyperlink.
4. Expand the Anchor and Bookmark section.
5. Click to open the Expression Editor, and click Parameters.
6. Double-click Country Parameter String to add it to the expression, then click Finish.
7. In the Properties view, change the Bookmark Level to 1.
8. Click outside the design space in the Design tab, then click Report in the Properties
view.
9. Click to enable Create bookmarks.
" "+$V{MASTER_TOTAL_PAGES}
11. Click Finish.
12. As you did in steps 6-7, use the Evaluation Time dropdown menu to select Master.
13. Save your project.
Properties
You can set JasperReports properties in the Jaspersoft Studio > Properties page of the
Preferences window. Setting a property here sets it as the default for all reports. You can
also set many properties at the report or element level. A property set at the element level
overrides a property set at the report level. A property set at the report level overrides a
property set at the Jaspersoft Studio level.
JasperReports Samples
JasperReports Library provides a number of sample reports that show how to use many of
the available features. You can download and install the samples as a project in Jaspersoft
Studio as follows:
1. Select File > New > Other from the main menu.
2. In the New dialog, expand Jaspersoft Studio.
3. Select JasperReports Samples and click Next.
4. Enter a name for the project folder and click Finish.
The sample reports are downloaded to the location that you chose. You can now view and
work with these reports in Jaspersoft Studio.
Configuration
You can set two preferred (default) units of measure, one at the field level, the other at the
report level. The report level unit is used wherever there is not a preferred field unit of
measure. The report's default unit of measure is the pixel.
• Pixels
• Inches
• Millimeters
• Centimeters
Enter a value and begin typing a unit of measure. Auto-complete lists the matching-
supported values for you to choose from.
Approximations
Even though Jaspersoft Studio handles many units of measure, JasperReports works only
with pixels. So pixels are the only unit allowed in the project file. Jaspersoft Studio
approximates measurements and converts them to pixels. For example, 5 cm is converted
to the nearest whole-number value in pixels. In this case the 5 centimeters is converted to
139 pixels (approximately 4.97 cm).
Mac OS X
To set the clean flag at startup on Mac OS X, run the following commands:
cd <jss-install>/Contents/MacOS
./Jaspersoft\ Studio\ Professional -clean
Linux
To set the clean flag at startup on Linux, run the following commands:
cd <jss-install>
./Jaspersoft\ Studio\ Professional -clean
Windows
To set the clean flag at startup on Windows, edit the desktop shortcut as follows:
1. Right-click on the desktop shortcut and select Properties.
2. On the Shortcut tab, append -clean to the Target field. For example:
"<jss-install>\Jaspersoft Studio Professional" -clean
3. Click OK.
4. Double-click the shortcut to run the application.
5. Once you have cleaned the application, edit the shortcut again to remove the -clean
flag to avoid slowing down application startup.
The Jaspersoft Studio application logger preferences cannot be exported, since they are
determined in part by your application INI configuration.
You can choose to export all of these categories or only a subset of them; however, you
cannot choose individual items inside a category. The result of the export is a single zip file
(compressed archive), which can be imported into another Jaspersoft Studio instance.
Again, you can choose which of the available categories inside the zip you want to import.
3. Select the categories that you want to export and click Next.
4. Enter the location and name that you want for the exported file and click Finish.
A zip file is created in the location that you chose.
If the file is a valid configuration file, the wizard shows the resource categories that
can be imported, with the number of resources in each category. If the file is not a
valid configuration file, you receive an error message.
4. Select the resource categories that you want to import and click Finish.
5. If there is a naming conflict between an imported resource and an existing resource
in your Jaspersoft Studio configuration, choose the action in you want in the
displayed dialog. For resource categories other than Jaspersoft Studio properties
and JasperReports Library properties, you have three choices:
• Overwrite–Overwrites the existing resources with the imported resources of the
same name.
• Keep both–Automatically renames the conflicting imported resources with a
unique name.
• Skip–Keeps the existing resources and discards the imported resources.
For Jaspersoft Studio properties and JasperReports Library properties, which do not
support multiple instances, you are prompted to choose to overwrite or not.
As before, you must choose the same action for all conflicting resources in a
category. For example, if you have multiple conflicting global data adapters, you
must overwrite, keep both, or skip all global data adapters. A separate dialog is
shown for each category where you have conflicting resources. You can choose
different actions for different categories.
If you are exporting your reports to JasperReports Server, you should configure the
version in the JasperReports Server connection settings, as described in Advanced
Connection Settings. Use the compatibility setting only if you are using your reports on
your own application built from JasperReports Library.
3. To save your reports in an earlier version of JRXML, select the version you want from
the Version menu in the Source .jrxml Version section of the dialog.
4. To remove Jaspersoft Studio properties from your compiled reports, select Do not
save Jaspersoft Studio properties. Properties specific to Jaspersoft Studio include
some layout information, dimensions in pixels or millimeters, and the data adapter
that was most recently used in Jaspersoft Studio.
5. To use an earlier version of JasperReports Library to compile reports, select the
version you from the Version menu in the Compiler Settings section of the dialog. If
the version you want is not available, set it up as described in the next step.
6. To add a version of JasperReports Library to the Version menu in the Compiler
Settings section of the dialog click Manage JasperReports Versions and select the
version you want:
a. To use a version you already have installed, click Add From Path, then select the
directory where the JasperReports Library is located.
Jaspersoft Studio verifies that the path contains JasperReports Library and adds
the version to the Version menu in the Compiler Settings section of the
Compatibility dialog.
b. To download and install JasperReports Library from a URL, click Add From URL
and select the URL from SourceForge
(https://sourceforge.net/projects/jasperreports/) or from another location.
Jaspersoft Studio downloads and verifies the jar files, copies the files to a
Jaspersoft Studio internal directory, and adds the version to the Version menu in
the Compiler Settings section of the Compatibility dialog.
The Eclipse UI changes to the Java perspective. A Java icon is added to the top right of
the Eclipse window. In future, you can switch to this perspective by clicking . To switch
back to the Jaspersoft Studio perspective, click the Report Design icon .
1. Right-click your project name in the Package Explorer and select Build Path > Add
Libraries.
2. In the Add Library dialog, select JasperReports Libraries, then click Finish.
The selected library is added to SimpleChartCustomizer.
3. Right-click your project name in the Package Explorer and select Build Path > Add
Libraries.
4. In the Add Library dialog, select JasperReports Library Dependencies, then click
Finish.
For example, if you are creating a chart customizer, the library dependencies you have
added include the JFreeCharts libraries.
2. Click the icon and select Data Snapshot Options. The Data Snapshot Options
dialog appears.
3. Select the Enable data snapshot checkbox and click OK.
4. Run the report to capture the report data.
The data in the snapshot is used to fill the report. Information about the snapshot is
displayed in the Report State window, including when the snapshot was created
(Data Queried At) and the name and location of the snapshot file.
Concepts of JasperReports
This chapter illustrates JasperReports' base concepts for a better understanding of how
Jaspersoft Studio works.
The JasperReports API, the XML syntax for report definition, and details for using the
library in your own programs are documented in the JasperReports Library Ultimate Guide.
This guide, along with other information and examples, is directly available on the
Jaspersoft community site at http://community.jaspersoft.com.
JasperReports is published under the LGPL license, which is a less restrictive GPL license.
JasperReports can be freely used on commercial programs without buying expensive
software licenses and without remaining trapped in the complicated net of open source
licenses. This is important when reports created with Jaspersoft Studio are used in a
commercial product; in fact, programs only need the JasperReports library to produce
prints, which work something like runtime executables.
This chapter contains the following sections:
• JRXML Sources and Jasper Files
• Data Sources and Print Formats
• Project Folder Types and Report Execution Contexts
• Using JasperReports Extensions in Jaspersoft Studio
• A Simple Program
xsi:schemaLocation="http://jasperreports.sourceforge.net/jasperreports
http://jasperreports.sourceforge.net/xsd/jasperreport.xsd"
name="My first report" pageWidth="595" pageHeight="842"
columnWidth="535"
leftMargin="20" rightMargin="20" topMargin="20" bottomMargin="20">
<queryString language="SQL">
<![CDATA[select * from address order by city]]>
</queryString>
<field name="ID" class="java.lang.Integer">
<fieldDescription><![CDATA[]]></fieldDescription>
</field>
<field name="FIRSTNAME" class="java.lang.String">
<fieldDescription><![CDATA[]]></fieldDescription>
</field>
<field name="LASTNAME" class="java.lang.String">
<fieldDescription><![CDATA[]]></fieldDescription>
</field>
<field name="STREET" class="java.lang.String">
<fieldDescription><![CDATA[]]></fieldDescription>
</field>
<field name="CITY" class="java.lang.String">
<fieldDescription><![CDATA[]]></fieldDescription>
</field>
<group name="CITY">
<groupExpression><![CDATA[$F{CITY}]]></groupExpression>
<groupHeader>
<band height="27">
<staticText>
<reportElement mode="Opaque" x="0" y="0" width="139" height="27"
forecolor="#FFFFFF" backcolor="#000000"/>
<textElement>
<font size="18"/>
</textElement>
<text><![CDATA[CITY]]></text>
</staticText>
<textField hyperlinkType="None">
<reportElement mode="Opaque" x="139" y="0" width="416" height="27"
forecolor="#FFFFFF" backcolor="#000000"/>
<textElement>
<font size="18" isBold="true"/>
</textElement>
<textFieldExpression class="java.lang.String"><![CDATA[$F{CITY}]]>
</textFieldExpression>
</textField>
</band>
</groupHeader>
<groupFooter>
<band height="8">
<line direction="BottomUp">
<reportElement key="line" x="1" y="4" width="554" height="1"/>
</line>
</band>
</groupFooter>
</group>
<background>
<band/>
</background>
<title>
<band height="58">
<line>
<reportElement x="0" y="8" width="555" height="1"/>
</line>
<line>
<reportElement positionType="FixRelativeToBottom" x="0" y="51"
width="555"
height="1"/>
</line>
<staticText>
<reportElement x=”65” y=”13” width ”424” height=”35”/>
<textElement textAlignment=”Center”>
<font size=”26” isBold=”true”/>
</textElement>
<text><![CDATA[Classic template]]> </text>
</staticText>
</band>
</title>
<pageHeader>
<band/>
</pageHeader>
<columnHeader>
<band height="18">
<staticText>
<reportElement mode="Opaque" x="0" y="0" width="138" height="18"
forecolor="#FFFFFF" backcolor="#999999"/>
<textElement>
<font size="12"/>
</textElement>
<text><![CDATA[ID]]></text>
</staticText>
<staticText>
<reportElement mode="Opaque" x="138" y="0" width="138" height="18"
forecolor="#FFFFFF" backcolor="#999999"/>
<textElement>
<font size="12"/>
</textElement>
<text><![CDATA[FIRSTNAME]]></text>
</staticText>
<staticText>
<reportElement mode="Opaque" x="276" y="0" width="138" height="18"
forecolor="#FFFFFF" backcolor="#999999"/>
<textElement>
<font size="12"/>
</textElement>
<text><![CDATA[LASTNAME]]></text>
</staticText>
<staticText>
<reportElement mode="Opaque" x="414" y="0" width="138" height="18"
forecolor="#FFFFFF" backcolor="#999999"/>
<textElement>
<font size="12"/>
</textElement>
<text><![CDATA[STREET]]></text>
</staticText>
</band>
</columnHeader>
<detail>
<band height="20">
<textField hyperlinkType="None">
<reportElement x="0" y="0" width="138" height="20"/>
<textElement>
<font size="12"/>
</textElement>
<textFieldExpression class="java.lang.Integer"><![CDATA[$F{ID}]]>
</textFieldExpression>
</textField>
<textField hyperlinkType="None">
<reportElement x="138" y="0" width="138" height="20"/>
</textField>
<textElement>
<font size="12"/>
</textElement>
<textFieldExpression class="java.lang.String"><![CDATA[$F
{FIRSTNAME}]]>
</textFieldExpression>
<textField hyperlinkType="None">
<reportElement x="276" y="0" width="138" height="20"/>
<textElement>
<font size="12"/>
</textElement>
<textFieldExpression class="java.lang.String"><![CDATA[$F
{LASTNAME}]]>
</textFieldExpression>
</textField>
<textField hyperlinkType="None">
<reportElement x="414" y="0" width="138" height="20"/>
<textElement>
<font size="12"/>
</textElement>
<textFieldExpression class="java.lang.String"><![CDATA[$F
{STREET}]]>
</textFieldExpression>
</textField>
</band>
</detail>
<columnFooter>
<band/>
</columnFooter>
<pageFooter>
<band height="26">
<textField evaluationTime="Report" pattern="" isBlankWhenNull="false"
hyperlinkType="None">
<reportElement key="textField" x="516" y="6" width="36" height="19"
forecolor="#000000" backcolor="#FFFFFF"/>
<textElement>
<font size="10"/>
</textElement>
<textFieldExpression class="java.lang.String"><![CDATA["" +
$V{PAGE_NUMBER}]]></textFieldExpression>
</textField>
<textField pattern="" isBlankWhenNull="false" hyperlinkType="None">
<reportElement key="textField" x="342" y="6" width="170"
height="19"
forecolor="#000000" backcolor="#FFFFFF"/>
<box>
<topPen lineWidth="0.0" lineStyle="Solid" lineColor="#000000"/>
<leftPen lineWidth="0.0" lineStyle="Solid" lineColor="#000000"/>
<bottomPen lineWidth="0.0" lineStyle="Solid"
lineColor="#000000"/>
<rightPen lineWidth="0.0" lineStyle="Solid" lineColor="#000000"/>
</box>
<textElement textAlignment="Right">
<font size="10"/>
</textElement>
<textFieldExpression class="java.lang.String"><![CDATA["Page " +
$V{PAGE_NUMBER} + " of "]]></textFieldExpression>
</textField>
During compilation of the JRXML file (using some JasperReports classes) the XML is parsed
and loaded in a JasperDesign object, which is a rich data structure that allows you to
represent the exact XML contents in memory. Regardless of the language used for
expressions inside the JRXML, JasperReports creates a special Java class that represents the
whole report. The report is then compiled, instanced, and serialized in a JASPER file, ready
for loading at any time.
JasperReports' speedy operation is due to all of a report’s formulas being compiled into
Java-native bytecode and the report structure being verified during compilation instead of
at run time. The JASPER file contains no extraneous resources, such as images used in the
report, resource bundles to run the report in different languages, or extra scriptlets and
external style definitions. All these resources must be provided by the host application and
at run time.
specify fill data for the output report: parameters and data sources. Both kinds of data are
presented by means of a generic interface named JRDataSource.
Figure 368: Data Source and Parameter Flows for Report Creation
JRDataSource allows a set of records organized in tables (rows and columns) to be read. It
enables JasperReports to fill a report with data from an explicit data source, using a JDBC
connection (already instanced and opened) to whichever relational database you want to
run an SQL query on (which is specified in the report).
If the data do not meet your requirements, you may need to specify values to condition the
report’s execution; you can create name/value pairs to pass to the print engine. These pairs
are named parameters, and they have to be preventatively declared in the report. Through
fillManager, you can join a JASPER file and a data source in a JasperPrint object. This object
is a meta-print that can create a real print after you export it in the format of your choice
through appropriate classes that implement the JRExporter interface.
JasperReports give you pre-defined exporters, such as those for creating files formatted as
PDF, XLSX, CVS, XML, RTF, ODF, text, HTML, and SWF. Through the JRViewer class, you can
view the print directly on the screen and print a hard copy.
• The report can access global (repository explorer) data adapters. See Creating a
Global Data Adapter for more information.
• Report preview defaults to Java.
JasperReports IO Context
JasperReports IO is a REST-based reporting service for JasperReports Library. The
JasperReports IO context is defined using a context.xml file in a folder named JR-INF. See
JasperReports IO Report Execution Contexts for more information.
If you have a folder with a JasperReports IO context, the environment is configured as
follows:
• The repository root is taken from the project preferences. If it is not set, the
repository root defaults to the project root.
• The report classpath is read from the JR-INF/context.xml files.
• The project takes the JasperReports Library properties from the JR-INF/context.xml
files.
A Simple Program
In conclusion, the following is an example of a simple program that shows how to produce
a PDF file from a Jasper file using a data source named JREmptyDataSource, a utility data
source that provides zero or more records without fields. The file test.jasper, referenced in
the example, is the compiled version of the code in .
JasperTest.java
import net.sf.jasperreports.engine.*;
import net.sf.jasperreports.engine.export.*;
import java.util.*;
public class JasperTest
{
public static void main(String[] args)
{
String fileName = "/devel/examples/test.jasper";
String outFileName = "/devel/examples/test.pdf";
HashMap hm = new HashMap();
try
{
JasperPrint print = JasperFillManager.fillReport(
fileName,
hm,
new JREmptyDataSource());
JRExporter exporter =
new net.sf.jasperreports.engine.export.JRPdfExporter();
exporter.setParameter(
JRExporterParameter.OUTPUT_FILE_NAME,
outFileName);
exporter.setParameter(
JRExporterParameter.JASPER_PRINT,print);
exporter.exportReport();
System.out.println("Created file: " + outFileName);
}
catch (JRException e)
{
e.printStackTrace();
System.exit(1);
}
catch (Exception e)
{
e.printStackTrace();
System.exit(1);
}
}
}
Glossary
Ad Hoc Editor
The interactive data explorer in JasperReports Server Professional and Enterprise editions.
Starting from a predefined collection of fields, the Ad Hoc Editor lets you drag and drop
fields, dimensions, and measures to explore data and create tables, charts, and crosstabs.
These Ad Hoc views can be saved as reports.
Ad Hoc Report
In previous versions of JasperReports Server, a report created through the Ad Hoc Editor.
Such reports could be added to dashboards and be scheduled, but when edited in
Jaspersoft Studio, lost their grouping and sorting. In the current version, the Ad Hoc Editor
is used to explore views which in turn can be saved as reports. Such reports can be edited
in Jaspersoft Studio without loss, and can be scheduled and added to dashboards.
Ad Hoc View
A view of data that is based on a Domain, Topic, or OLAP client connection. An Ad Hoc
view can be a table, chart, or crosstab and is the entry point to analysis operations such as
slice and dice, drill down, and drill through. OLAP View You can save an Ad Hoc view as a
report in order to edit it in the interactive viewer, schedule it, or add it to a dashboard.
Aggregate Function
An aggregate function is one that is computed using a group of values; for example, Sum or
Average. Aggregate functions can be used to create calculated fields in Ad Hoc views.
Calculated fields containing aggregate functions cannot be used as fields or added to
groups in an Ad Hoc view and should not be used as filters. Aggregate functions allow you
to set a level, which specifies the scope of the calculation; level values include Current (not
available for PercentOf), ColumnGroup, ColumnTotal, RowGroup, RowTotal, Total.
Amazon Web Services (AWS)
Cloud platform, used to provide and host a family of services, such as RDS, S3, and EC2.
Analysis View
OLAP View
Audit Archiving
To prevent audit logs from growing too large to be easily accessed, the installer configures
JasperReports Server to move current audit logs to an archive after a certain number of
days, and to delete logs in the archive after a certain age. The archive is another table in
the JasperReports Server's repository database.
Audit Domains
A Domain that accesses audit data in the repository and lets administrators create Ad Hoc
reports of server activity. There is one Domain for current audit logs and one for archived
logs.
Audit Logging
When auditing is enabled, audit logging is the active recording of who used JasperReports
Server to do what when. The system installer can configure what activities to log, the
amount of detail gathered, and when to archive the data. Audit logs are stored in the same
private database that JasperReports Server uses to store the repository, but the data is
only accessible through the audit Domains.
Auditing
A feature of JasperReports Server Enterprise edition that records all server activity and
allows administrators to view the data.
Calculated Field
In an Ad Hoc view or a Domain, a field whose value is calculated from a user-defined
formula that may include any number of fields, operators, and constants. For Domains, a
calculated field becomes one of the items to which the Domain's security file and locale
bundles can apply. There are more functions available for Ad Hoc view calculations than
for Domains.
CloudFormation (CF)
Amazon Web Services CloudFormation gives developers and systems administrators an
easy way to create and manage a collection of related AWS resources, provisioning, and
updating them in an orderly and predictable fashion.
CRM
Customer Relationship Management. The practice of managing every facet of a company's
interactions with its clientele. CRM applications help businesses track and support their
customers.
CrossJoin
An MDX function that combines two or more dimensions into a single axis (column or row).
Cube
The basis of most OLAP applications, a cube is a data structure that contains three or more
dimensions that categorize the cube's quantitative data. When you navigate the data
displayed in an OLAP view, you are exploring a cube.
Custom Field
In the Ad Hoc Editor, a field that is created through menu items as a simple function of one
or two available fields, including other custom fields. When a custom field becomes too
complex or needs to be used in many reports, it is best to define it as a calculated field in a
Domain.
Dashboard
A collection of reports, input controls, graphics, labels, and web content displayed in a
single, integrated view. Dashboards often present a high level view of your data, but input
controls can parametrize the data to display. For example, you can narrow down the data
to a specific date range. Embedded web content, such as other web-based applications or
maps, make dashboards more interactive and functional.
Dashlet
An element in a dashboard. Dashlets are defined by editable properties that vary
depending on the dashlet type. Types of dashlet include reports, text elements, filters, and
external web content.
Data Island
A single join tree or a table without joins in a Domain. A Domain may contain several data
islands, but when creating an Ad Hoc view from a Domain, you can only select one of them
to be available in the view.
Data Policy
In JasperReports Server, a setting that determines how the server processes and caches
data used by Ad Hoc reports. Select your data policies by clicking Manage > Server >
Settings Ad Hoc Settings. By default, this setting is only available to the superuser account.
Data Source
Defines the connection properties that JasperReports Server needs to access data. The
server transmits queries to data sources and obtains datasets in return for use in filling
reports and previewing Ad Hoc reports. JasperReports Server supports JDBC, JNDI, and
Bean data sources; custom data sources can be defined as well.
Dataset
A collection of data arranged in columns and rows. Datasets are equivalent to relational
results sets and the JRDataSource type in the JasperReports Library.
Datatype
In JasperReports Server, a datatype is used to characterize a value entered through an
input control. A datatype must be of type text, number, date, or date-time. It can include
constraints on the value of the input, for example maximum and minimum values. As such,
a datatype in JasperReports Server is more structured than a datatype in most
programming languages.
Denormalize
A process for creating table joins that speeds up data retrieval at the cost of having
duplicate row values between some columns.
Derived Table
In a Domain, a derived table is defined by an additional query whose result becomes
another set of items available in the Domain. For example, with a JDBC data source, you
can write an SQL query that includes complex functions for selecting data. You can use the
items in a derived table for other operations on the Domain, such as joining tables,
defining a calculated field, or filtering. The items in a derived table can also be referenced
in the Domain's security file and locale bundles.
Dice
An OLAP operation to select columns.
Dimension
A categorization of the data in a cube. For example, a cube that stores data about sales
figures might include dimensions such as time, product, region, and customer's industry.
Domain
A virtual view of a data source that presents the data in business terms, allows for
localization, and provides data-level security. A Domain is not a view of the database in
relational terms, but it implements the same functionality within JasperReports Server. The
design of a Domain specifies tables in the database, join clauses, calculated fields, display
names, and default properties, all of which define items and sets of items for creating Ad
Hoc reports.
Domain Topic
A Topic that is created from a Domain by the Data Chooser. A Domain Topic is based on
the data source and items in a Domain, but it allows further filtering, user input, and
Group
In a report, a group is a set of data rows that have an identical value in a designated field.
• In a table, the value appears in a header and footer around the rows of the group,
while the other fields appear as columns.
• In a chart, the field chosen to define the group becomes the independent variable
on the X axis, while the other fields of each group are used to compute the
dependent value on the Y axis.
Hierarchy Level
In an OLAP cube, a member of a dimension containing a group of members.
Input Control
A button, check box, drop-down list, text field, or calendar icon that allows users to enter a
value when running a report or viewing a dashboard that accepts input parameters. For
JRXML reports, input controls and their associated datatypes must be defined as repository
objects and explicitly associated with the report. For Domain-based reports that prompt for
filter values, the input controls are defined internally. When either type of report is used in
a dashboard, its input controls are available to be added as special content.
Item
When designing a Domain or creating a Topic based on a Domain, an item is the
representation of a database field or a calculated field along with its display name and
formatting properties defined in the Domain. Items can be grouped in sets and are
available for use in the creation of Ad Hoc reports.
JasperReport
A combination of a report template and data that produces a complex document for
viewing, printing, or archiving information. In the server, a JasperReport references other
resources in the repository:
• The report template (in the form of a JRXML file)
• Information about the data source that supplies data for the report
• Any additional resources, such as images, fonts, and resource bundles referenced by
the report template.
The collection of all the resources that are referenced in a JasperReport is sometimes
called a report unit. End users usually see and interact with a JasperReport as a single
resource in the repository, but report creators must define all of the components in the
report unit.
JasperReports IO
An HTTP-based reporting service for JasperReports Library that provides a REST API for
running, exporting, and interacting with reports and a JavaScript API for embedding
reports and their input controls into your web pages and web applications.
JasperReports Library
An embeddable, open source, Java API for generating a report, filling it with current data,
drawing charts and tables, and exporting to any standard format (HTML, PDF, Excel, CSV,
and others). JasperReports processes reports defined in JRXML, an open XML format that
allows the report to contain expressions and logic to control report output based on run-
time data.
JasperReports Server
A commercial open source, server-based application that calls the JasperReports Library to
generate and share reports securely. JasperReports Server authenticates users and lets
them upload, run, view, schedule, and send reports from a web browser. Commercial
versions provide metadata layers, interactive report and dashboard creation, and
enterprise features such as organizations and auditing.
Jaspersoft Studio
A commercial open source tool for graphically designing reports that leverage all features
of the JasperReports Library. Jaspersoft Studio lets you drag and drop fields, charts, and
sub-reports onto a canvas, and also define parameters or expressions for each object to
create pixel-perfect reports. You can generate the JRXML of the report directly in Jaspersoft
Studio, or upload it to JasperReports Server. Jaspersoft Studio is implemented in Eclipse.
Jaspersoft ETL
A graphical tool for designing and implementing your data extraction, transforming, and
loading (ETL) tasks. It provides hundreds of data source connectors to extract data from
many relational and non-relational systems. Then, it schedules and performs data
aggregation and integration into data marts or data warehouses that you use for reporting.
Jaspersoft OLAP
A relational OLAP server integrated into JasperReports Server that performs data analysis
with MDX queries. The product includes query builders and visualization clients that help
users explore and make sense of multidimensional data. Jaspersoft OLAP also supports
XML/A connections to remote servers.
JavaBean
A reusable Java component that can be dropped into an application container to provide
standard functionality.
JDBC
Java Database Connectivity. A standard interface that Java applications use to access
databases.
JNDI
Java Naming and Directory Interface. A standard interface that Java applications use to
access naming and directory services.
Join Tree
In Domains, a collection of joined tables from the actual data source. A join is the relational
operation that associates the rows of one table with the rows of another table based on a
common value in given field of each table. Only the fields in a same join tree or calculated
from the fields in a same join tree may appear together in a report.
JPivot
An open source graphical user interface for OLAP operations. For more information, visit
http://jpivot.sourceforge.net/.
JRXML
An XML file format for saving and sharing reports created for the JasperReports Library and
the applications that use it, such as Jaspersoft Studio and JasperReports Server. JRXML is
an open format that uses the XML standard to define precisely all the structure and
configuration of a report.
Level
Specifies the scope of an aggregate function in an Ad Hoc view. Level values include
Current (not available for PercentOf), ColumnGroup, ColumnTotal, RowGroup, RowTotal,
Total.
MDX
Multidimensional Expression Language. A language for querying multidimensional objects,
such as OLAP (On Line Analytical Processing) cubes, and returning cube data for analytical
processing. An MDX query is the query that determines the data displayed in an OLAP view.
Measure
Depending on the context:
• In a report, a formula that calculates the values displayed in a table's columns, a
crosstab's data values, or a chart's dependent variable (such as the slices in a pie).
• In an OLAP view, a formula that calculates the facts that constitute the quantitative
data in a cube.
Mondrian
A Java-based, open source multidimensional database application.
Mondrian Connection
An OLAP client connection that consists of an OLAP schema and a data source. OLAP client
connections populate OLAP views.
Mondrian Schema Editor
An open source Eclipse plug-in for creating Mondrian OLAP schemas.
Mondrian XML/A Source
A server-side XML/A source definition of a remote client-side XML/A connection used to
populate an OLAP view using the XML/A standard.
MySQL
An open source relational database management system. For information, visit
http://www.mysql.com/.
Navigation Table
The main table in an OLAP view that displays measures and dimensions as columns and
rows.
ODBO Connect
Jaspersoft ODBO Connect enables Microsoft Excel 2003 and 2007 Pivot Tables to work with
Jaspersoft OLAP and other OLAP servers that support the XML/A protocol. After setting up
the Jaspersoft ODBO data source, business analysts can use Excel Pivot Tables as a front-
end for OLAP analysis.
OLAP
On Line Analytical Processing. Provides multidimensional views of data that help users
analyze current and past performance and model future scenarios.
OLAP Client Connection
A definition for retrieving data to populate an OLAP view. An OLAP client connection is
either a direct Java connection (Mondrian connection) or an XML-based API connection
(XML/A connection).
OLAP Schema
A metadata definition of a multidimensional database. In Jaspersoft OLAP, schemas are
stored in the repository as XML file resources.
OLAP View
Also called an analysis view. A view of multidimensional data that is based on an OLAP
client connection and an MDX query. Unlike Ad Hoc views, you can directly edit an OLAP
view's MDX query to change the data and the way they are displayed. An OLAP view is the
entry point for advanced analysis users who want to write their own queries. Ad Hoc View
Organization
A set of users that share folders and resources in the repository. An organization has its
own user accounts, roles, and root folder in the repository to securely isolate it from other
organizations that may be hosted on the same instance of JasperReports Server.
Organization Admin
Also called the organization administrator. A user in an organization with the privileges to
manage the organization's user accounts and roles, repository permissions, and repository
content. An organization admin can also create suborganizations and mange all of their
accounts, roles, and repository objects. The default organization admin in each
organization is the jasperadmin account.
Outlier
A fact that seems incongruous when compared to other member's facts. For example, a
very low sales figure or a very high number of help desk tickets. Such outliers may indicate
a problem (or an important achievement) in your business. The analysis features of
Jaspersoft OLAP excel at revealing outliers.
Parameter
Named values that are passed to the engine at report-filling time to control the data
returned or the appearance and formatting of the report. A report parameter is defined by
its name and type. In JasperReports Server, parameters can be mapped to input controls
that users can interact with.
Pivot
To rotate a crosstab such that its row groups become column groups and its column
groups become rows. In the Ad Hoc Editor, pivot a crosstab by clicking .
Pivot Table
A table with two physical dimensions (for example, X and Y axis) for organizing information
containing more than two logical dimensions (for example, PRODUCT, CUSTOMER, TIME,
and LOCATION), such that each physical dimension is capable of representing one or more
logical dimensions, where the values described by the dimensions are aggregated using a
function such as SUM. Pivot tables are used in Jaspersoft OLAP.
Properties
Settings associated with an object. The settings determine certain features of the object,
such as its color and label. Properties are normally editable. In Java, properties can be set
in files listing objects and their settings.
Report
In casual usage, report may refer to:
• A JasperReport. JasperReport
• The main JRXML in a JasperReport.
• The file generated when a JasperReport is scheduled. Such files are also called
content resources or output files.
• The file generated when a JasperReport is run and then exported.
• In previous JasperReports Server versions, a report created in the Ad Hoc Editor. Ad
Hoc Report
Report Run
An execution of a report, Ad Hoc view, or dashboard, or a view or dashboard designer
session, it measures and limits usage of Freemium instances of JasperReports Server. The
executions apply to resources no matter how they are run (either in the web interface or
through the various APIs, such as REST web services). Users of our Community Project and
our full-use commercial licenses are not affected by the limit. For more information, please
contact sales@jaspersoft.com.
Repository
Depending on the context:
• In JasperReports Server, the repository is the tree structure of folders that contain
all saved reports, dashboards, OLAP views, and resources. Users access the
repository through the JasperReports Server web interface or through Jaspersoft
Studio. Applications can access the repository through the web service API.
Administrators use the import and export utilities to back up the repository
contents.
• In JasperReports IO, the repository is where all the resources needed to create and
run reports are stored. The repository can be stored in a directory on the host
computer or in an S3 bucket hosted by Amazon Web Services. Users access the
repository through a file browser on the host machine or through the AWS console.
Resource
In JasperReports Server, anything residing in the repository, such as an image, file, font,
data source, Topic, Domain, report element, saved report, report output, dashboard, or
OLAP view. Resources also include the folders in the repository. Administrators set user
and role-based access permissions on repository resources to establish a security policy.
Role
A security feature of JasperReports Server. Administrators create named roles, assign them
to user accounts, and then set access permissions to repository objects based on those
roles. Certain roles also determine what functionality and menu options are displayed to
users in the JasperReports Server interface.
S3 Bucket
Cloud storage system for Amazon Web Services. JasperReports IO can use an S3 bucket to
store files for its repository.
Schema
A logical model that determines how data is stored. For example, the schema in a
relational database is a description of the relationships between tables, views, and indexes.
In Jaspersoft OLAP, an OLAP schema is the logical model of the data that appears in an
OLAP view; they are uploaded to the repository as resources. For Domains, schemas are
represented in XML design files.
Schema Workbench
A graphical tool for easily designing OLAP schemas, data security schemas, and MDX
queries. The resulting cube and query definitions can then be used in Jaspersoft OLAP to
perform simple but powerful analysis of large quantities of multi-dimensional data stored
in standard RDBMS systems.
Set
In Domains and Domain Topics, a named collection of items grouped together for ease of
use in the Ad Hoc Editor. A set can be based on the fields in a table or entirely defined by
the Domain creator, but all items in a set must originate in the same join tree. The order of
items in a set is preserved.
Slice
An OLAP operation for filtering data rows.
SQL
Structured Query Language. A standard language used to access and manipulate data and
schemas in a relational database.
Stack
A collection of Amazon Web Services resources you create and delete as a single unit.
System Admin
Also called the system administrator. A user who has unlimited access to manage all
organizations, users, roles, repository permissions, and repository objects across the entire
JasperReports Server instance. The system admin can create root-level organizations and
manage all server settings. The default system admin is the superuser account.
Topic
A JRXML file created externally and uploaded to JasperReports Server as a basis for Ad Hoc
reports. Topics are created by business analysts to specify a data source and a list of fields
with which business users can create reports in the Ad Hoc Editor. Topics are stored in the
Ad Hoc Components folder of the repository and displayed when a user launches the Ad
Hoc Editor.
Transactional Data
Data that describe measurable aspects of an event, such as a retail transaction, relevant to
your business. Transactional data are often stored in relational databases, with one row for
each event and a table column or field for each measure.
User
Depending on the context:
• A person who interacts with JasperReports Server through the web interface. There
are generally three categories of users: administrators who install and configure
JasperReports Server, database experts or business analysts who create data
sources and Domains, and business users who create and view reports and
dashboards.
• A user account that has an ID and password to enforce authentication. Both people
and API calls accessing the server must provide the ID and password of a valid user
account. Roles are assigned to user accounts to determine access to objects in the
repository.
View
Several meanings pertain to JasperReports Server:
• An Ad Hoc view. Ad Hoc View
• An OLAP view. OLAP View
• A database view. See http://en.wikipedia.org/wiki/View_%28database%29.
Product-Specific Documentation
The documentation for this product is available on the Jaspersoft® Studio Product
Documentation page.
USE OF CLOUD SG SOFTWARE AND CLOUD SERVICES IS SUBJECT TO THE TERMS AND CONDITIONS
OF AN AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED AGREEMENT, OR, IF THERE IS NO
SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER AGREEMENT WHICH IS DISPLAYED WHEN
ACCESSING, DOWNLOADING, OR INSTALLING THE SOFTWARE OR CLOUD SERVICES (AND WHICH IS
DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH LICENSE AGREEMENT OR CLICKWRAP
END USER AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE
OF THIS DOCUMENT IS SUBJECT TO THOSE SAME TERMS AND CONDITIONS, AND YOUR USE HEREOF
SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.
This document is subject to U.S. and international copyright laws and treaties. No part of this
document may be reproduced in any form without the written authorization of Cloud Software
Group, Inc.
Jaspersoft, JasperReports, Visualize.js, and TIBCO are either registered trademarks or trademarks of
Cloud Software Group, Inc. in the United States and/or other countries.
All other product and company names and marks mentioned in this document are the property of
their respective owners and are mentioned for identification purposes only. You acknowledge that all
rights to these third party marks are the exclusive property of their respective owners. Please refer to
Cloud SG’s Third Party Trademark Notices (https://www.cloud.com/legal) for more information.
This document includes fonts that are licensed under the SIL Open Font License, Version 1.1, which is
available at: https://scripts.sil.org/OFL
Copyright (c) Paul D. Hunt, with Reserved Font Name Source Sans Pro and Source Code Pro.
Cloud SG software may be available on multiple operating systems. However, not all operating
system platforms for a specific software version are released at the same time. See the “readme” file
for the availability of a specific version of Cloud SG software on a specific operating system platform.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
This and other products of Cloud SG may be covered by registered patents. For details, please refer
to the Virtual Patent Marking document located at https://www.tibco.com/patents.