Knowledge Base: Best Practices

JasperServer tried to contact 104.96.227.25

Tue, 05 Oct 2021 22:28:47 +0000

Please see the current latest Administration Guide for details on configuring the Heartbeat.

Enable/Disable the heartbeat

With a newly installed JasperReports Server, you will be asked whether to opt-in to the JasperReports Server Heartbeat or not.
To opt-in, click OK. To opt-out, click the check box to remove the check and click OK.
You can also manually enable or disable the heartbeat by modifying the jasperserver-pro/WEB-INF/applicationContext-logging.xml file. To disable, set the enabled property to false like below:

For additional information on enabling and disabling the heartbeat component refer to the JasperReports Server Administrator Guide.

For more information on the JasperReports Server Heartbeat Program click here.

Removing 'ticks' from Fusion Angular Gauge Chart when used as ArcGauge

Tue, 08 Mar 2022 12:17:50 +0000

Problem:

In order to remove 'ticks' or 'lines' from the ArcGuage as shown in the below image:

Solution:

Add the following property to the element in the jrxml.

In JasperServer Studio you can find it under Widget Pro Properties/Widget Data/Angular Dials/Modify/Radius. It shows 0 by default, but it's not actually set in the JRXML. You can try to change the value up and down to force JSS to set the property.

Note : This is a specific use case and specific solution that you can try to meet the exact requirement.

option for Stretch with overflow

Thu, 09 Nov 2023 15:53:29 +0000

In our old jasper studio versions there was a option "Stretch with overflow". This option was used to allow the text field to stretch downwards in order to display all its text when it doesn't fit in the defined text field height. This property will work irrespective of cell height that you provide.

This option is now removed in our newer versions and replaced with

Stretch Height (which is the same as the old stretch with overflow)

Stretch with overflow is now part of the text adjust options:

Cut Text (which is the default)
Stretch Height (which is the same as the old stretch with overflow)
Scale Font (which instead of stretching the element, JasperReports will try to decrease the font size until the full text fit the textfield size).

Please find attached screenshot.

How to remove added extra loggers starting with com.jaspersoft.

Wed, 12 Jul 2023 07:58:11 +0000

Issue Description:

Usually customer add additional loggers explicitly under the black space present in Log Settings tab to analyze and debug the issues specific to component which are not already present in Log Settings. But going further when issue get resolves they require to remove this added extra loggers to not compromise on performance and to avoid extra loggers to get captured in log files.

But , for some of the loggers added which has prefix with "com.jaspersoft....". then this loggers are not present with the same name in Restore default while deleting this loggers.

For example , When you added loggers as below .

com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob
com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJobFileSavingImpl
com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJobMailNotificationImpl

Resolution:

To remove this added extra loggers under the log settings tab , You will need to navigate to

Manage >> Server Settings >> Restore default and search for below loggers and delete and click on the save button present on bottom left corner.

log4j.com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob
log4j.com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJobFileSavingImpl
log4j.com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJobMailNotificationImpl

Here, log4j is getting appended as the prefix for some of the extra loggers added. There is no need to restart the Jasperserver server as this changes get applied on fly.

Hope this helps. Have a GREAT day ahead!

Thank you

Resolving SSLHandshakeException in Jaspersoft Studio After Certificate Renewal

Fri, 08 Jan 2021 07:21:56 +0000

Problem Description:

Users may encounter a connection failure when attempting to link Jaspersoft Studio to JasperReports Server following an SSL certificate update. Despite the certificate being renewed, the application returns a javax.net.ssl.SSLHandshakeException.

Error Trace

The typical stack trace observed is:

java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

This error indicates that the Java Runtime Environment (JRE) powering Jaspersoft Studio cannot verify the trust chain of the certificate presented by the server.

Solution:

While this error generally points to a missing certificate in the Java cacerts truststore, it can be particularly nuanced when replacing an existing certificate from the same CA.

If you have confirmed that the primary server certificate is valid and the path in Studio is correct, ensure that the Intermediate Certificate has also been updated within your keystore or truststore. Java requires the complete chain of trust to be present; if the new server certificate was signed by a different intermediate bundle than the expired one, the handshake will fail because the "path" to the Root CA is broken.

Recommended Steps:

Verify the Chain: Use an SSL tool to ensure the server is broadcasting the full certificate chain (Root, Intermediate, and Identity).
Update the JRE Truststore: Ensure the new Intermediate CA is imported into the specific JRE used by Jaspersoft Studio: keytool -import -alias intermediate_alias -keystore ../lib/security/cacerts -file intermediate.crt
Restart Studio: Java caches truststore information at startup; a full restart is required after any keytool modifications.

Issue with AM / PM mask when exporting ad hoc report to XLS/XLSX

Fri, 10 Jun 2016 23:18:59 +0000

Problem:

You have an ad hoc view with date field that uses date format which includes AM/PM component. For example:

MMM dd, yyyy HH:mm:ss a

When you export this to XLS or XLSX you get invalid mask for cell format:

mmm d, yyyy h:mm:ss a

Solution:

Edit the applicationContext.xml file, find the following section:

Add the following entries:

Save the file and restart the server.

Sample Report: Changing Report Grouping at Run Time Based on User's Input

Thu, 02 Jun 2016 22:07:05 +0000

The purpose of this sample report is to show user one of the way to change report grouping structure dynamically using available JR features. The techniques used in this report design are very basic features of JasperReports product. We encourage users to review TIBCO JASPERSOFT® STUDIO USER GUIDE RELEASE 6.2 document and get themselves familiar with the product in order to use it efficiently, effectively, and creatively to meet their report requirement.

Key Design Considerations:

- This report uses jasperserver repository "profile" database to list organizations, its users, and as associated roles.

- To simplify report design and avoid complex structure, this report utilizes simple tabular layout without grouping. Users with report design expertise who have mastered the JR features can utilize group function to create more complex report structures.

- The report data is grouped based on user's input, and report rows are displayed by grouping sequence.

- Report input selection is based on predefined key values and translated into "order by" syntax before being injected as a piece of report SQL query replacement via $P!{}.

It is imperative not to inject user's input directly into report SQL query using $P!{} to avoid hacking and malicious acts through SQL injection. Using a hidden parameter as a buffer zone instead, as demonstrated in this report design, to control and limit what can be used in the actual report SQL query.

Report Design:





    
    
    
        
    
    
        
    
    
        
    
    
        
    
    
    
    
    
        
    
    
        <band height="35" splitType="Stretch">
            <property name="com.jaspersoft.studio.unit.height" value="pixel"/>
            <textField>
                <reportElement x="0" y="0" width="570" height="30" uuid="51f0449a-2105-483e-926b-f3616fdd97d0"/>
                <textElement>
                    <font size="14" isBold="true"/>
                </textElement>
                <textFieldExpression><![CDATA["Demo Report on Dynamic Grouping of "+$P{GroupItem}]]></textFieldExpression>
            </textField>
        </band>

Report Outputs:

======================================

TTC-20160602

How to Group and Display Timestamps in 15 Minute Interval in Ad Hoc Cross Tab

Wed, 01 Jun 2016 06:17:23 +0000

Report Requirement:

JasperReports Server Ad hoc View currently supports grouping date by hour, day, month, quarter and year. User's requirement is to have a date type column added to the cross tab and group the date by 15 minute intervals.

Solution:

In a domain ad hoc view, the simplest way to group user's date in 15 minutes interval in the cross tab is to create a derived table to convert the timestamp field value into 15 minutes increment and join this table with data source table, then use the new timestamp from derive table to display data in the cross tab with "Minutes by Day" group.

User can use integer division to carry out the conversion operation. First convert timestamp into Unix date in second unit then do an integer divide by 900 (15 minute interval). The fraction of 15 minutes will get dropped by this operation. Multiple the result by 900 and we will get the Unix dates in the 15 minutes interval. Construct the timestamp from this Unix date and user can have the timestamp fields only contain minutes in 0, 15, 30 and 45 tick marks.

The following is a test SQL query for the derived table and its CSV output.

select id
, FROM_UNIXTIME((UNIX_TIMESTAMP(previouspasswordchangetime) div 900) * 900) as previouspasswordchangetime
from jasperserver.jiuser

id,previouspasswordchangetime
1,2014-12-16 14:15:00.0
2,2014-12-16 14:15:00.0
3,2014-12-16 14:30:00.0
4,2014-12-16 14:30:00.0
5,2014-12-16 14:30:00.0
6,2014-12-16 14:30:00.0

===========================================
TTC-20160531-67189

Using Derived Hidden Parameter In Report Design To Ensure User Selected Date For The Report Is Not In The Future

Wed, 01 Jun 2016 06:01:03 +0000

Report Requirement:

User is using JR 5.0.1 version of which the Relative Date had not been implemented. User wants to select report data based on user's input date DATE_END as the following:

A. If the date provided <= NOW(), run the report as is based on user's selected date;
B. If the date provided > NOW(), run the report selecting data based on Today's date at midnight.

Solution:

We need to create a secondary "hidden" (non-prompting) parameter in the report design template to derive the date based on user input from DATE_END parameter and use it in the SQL query. This secondary date DATE_END2 parameter is based on user's input date and today's date, whichever is smaller, to select report data. The parameter is constructed in the following exact order in the report design to have it work correctly:

This derived date parameter $P!{DATE_END2 then can be used in the report SQL query in the following fashion:

SELECT
........
WHERE
"datetime" > '$P!{DATE_END2}'::timestamp - interval '1 $P!{INTERVAL}'
AND "datetime" <= '$P!{DATE_END2}'

==================================

TTC-20160531-67712

Running JasperReports Server Bundled Installer in Silent Mode

Wed, 11 May 2016 21:42:04 +0000

Introduction

JasperReports Server bundled installers install bundled Apache Tomcat, PostgreSQL servers, and PhantomJS. Normally, these installers run in either graphical or text-based menu mode. However, it's possible to install JasperReports Server silently using an options file. This install mode can be particularly helpful when used as part of another product installation.

Step-by-Step instructions

Open a text editor and add the following lines:

mode=unattended
installer-language=en
jasperLicenseAccepted=yes
prefix={path to install location e.g. C:\jrs63 or /opt/jrs63}

Save the file as options.txt or whatever file you wish and close the text editor
Open a command line window and browse to where the installer has been saved

Run the following command:

Windows:

jasperreports-server-{version}-windows-x64-installer.exe --optionfile options.txt

Linux:

./jasperreports-server-{version}-linux-x64-installer.run --optionfile options.txt

Result

JasperReports Server will install silently then exit. The server will need to be started separately. To do so, execute the ctlscript.sh or ctlscript.bin file with the start option.

Additional Information

To see a list of available options, run the installer from the command line with the --help option.

An example with additional options may look as follows:

mode=unattended
installer-language=en
jasperLicenseAccepted=yes
prefix={path to install location e.g. C:\jrs63 or /opt/jrs63}
postgres_installation_type=bundled
postgres_locale=en
postgres_port=5432
postgres_password=
tomcat_installation_type=bundled
tomcat_server_port=8080
tomcat_server_shutdown_port=8005
tomcat_server_ajp_port=8009
phantomjs_installation_type=bundled
jasperserver_install_sampledata=1

Localizing Domain Data

Tue, 12 Apr 2016 21:11:41 +0000

How To Access Localized Data Via A Domain

TIBCO JasperReports Server offers users the ability to localize domain labels by leveraging the Java platform's built-in internationalization support using resource bundles. But accessing and analyzing localized data isn't as straightforward a proposition. The usual recommendation for this use case is to create multiple domains, one for each locale, store the localized data in separate database tables, and limit user access to the domains via roles. While this approach is fine in limited situations, some customers have reported performance and scalability issues and others have found this approach to be inflexible and difficult to maintain. There is an alternate approach that allows for localized data to be stored inline in a single table and uses a single domain to access it. The purpose of this wiki article is to present step-by-step guidance to implement this approach.

Prerequisites

JasperReports Server Professional (any version)
One or more database tables with localized inline data

Configuration Steps

Create a new domain or edit an existing one and launch the Domain Designer
Click the Calculated Fields tab
Enter the following values in the text fields to create a new calculated field:
- Field Name: any descriptive name (this example uses "user_locale")
- Type: String
- Expression: groovy('org.springframework.context.i18n.LocaleContextHolder.getLocale()')
Click the Save Field button
Create another calculated field by populating the text fields with the following values:
- Field Name: any descriptive name (this example uses "Locale_Check")
- Type: Boolean
- Expression: == constant_fields_level.user_locale
Click the Save Field button
Click the Pre-filters tab
Find the second calculated field created in the previous step (called "Locale_Check" in this example) and double-click it
In the new filter that appears, leave the default equals in the combo box and enter true in the text field to the right of the combo box
Click OK and Submit to save the domain

Testing

If you have the sample data installed and you're using PostgreSQL as your database, perform the following steps to test the solution:

Download, unzip and execute the following SQL script against the SugarCRM sample database:

simple_domain_test_data_sql.zip
Modify the /organizations/organization_1/domains/simple_domain using the steps described above
Create an Ad Hoc view using the Simple Domain as a data source.
Select the Opportunities set, drag or click it into the Selected Fields list, and click OK
In the Ad Hoc editor, expand the Opportunities node
Drag or click the Opportunity and Sales Stage fields to add them to the report
Save the Ad Hoc view
Log out of JasperReports Server
On the login screen, click the Show locale and timezone link
Change the Locale combo box setting from en_US to es
Provide your credentials and re-login to JasperReports Server
Click Ver -> Repositorio and navigate to the Ad Hoc view created in the previous steps
Upon executing the Ad Hoc view, you should see the constrained data set with the locale filter automatically applied

Known Issues

Due to Ad Hoc caching, you might still see the non-localized data the first couple of times you execute the Ad Hoc view. It may be necessary to log in as Superuser and manually clear the Ad Hoc cache from the Manage -> Server Settings page.

Domain Ad Hoc View Report Listing

Fri, 01 Apr 2016 04:37:07 +0000

When making changes to a domain, users often want to know which ad hoc view report unit will get affected by the change. Users can downloadexport(2).zipand import it into TIBCO JasperReports^®Server repository, then run "50. Domain Reference Listing Ad Hoc View Report" under publicSamplesReports repository folder to get the list of report units using that domain.

TTC-20160331

When Using the Bundled Installation of TIBCO JasperReports® Server an Error "The System cannot find file cmd.exe" is Received

Thu, 28 May 2020 16:46:50 +0000

Issue:

When using the bundled installation of TIBCO JasperReports^® Server, towards the end of installation, an error of "The System cannot find file cmd.exe". You may see the full error as follows:

Problem running post-install step. Installation may not complete correctly

Error running C:Jaspersoftjasperreports-server-X.X.X/servicerun.bat STOP:

The system cannot find the file cmd.exe.

Solution:

This error may be do to not sufficient permission on the server. Cmd.exe is command prompt. You have to have administrator permissions to run command prompt on the server to start and stop JasperReports^® Server.

How to Configure Default Values in Scheduler Notification Tab

Wed, 10 Feb 2016 08:18:21 +0000

Question:

How do I set default values in Notification tab of report scheduler?

Answer:

Please note the solution below verified with TIBCO JasperReports^® Server v.6.1.1

Default values for Notification tab can be setup in a Javascript file:

Quote

jasperserver-proscriptsbower_componentsjrs-uisrcschedulermodeljobModel.js

Add the following code after repositoryDestination: {.....} model definition (line ~1465):

mailNotification: {

    toAddresses:  { address: ['JohnSmith@mail.com', 'BobSmith@mail.com'] },
    ccAddresses:  { address: ['RedGreen@mail.com'] },
    bccAddresses: { address: ['BlueJack@mail.com'] },

    subject:      'Ouptut Job - Year Sales',
    messageText:  'See attached...',

    skipEmptyReports: true,
    includingStackTraceWhenJobFails: false,
    skipNotificationWhenJobFails:    false,
    resultSendType: 'SEND_ATTACHMENT' // SEND, SEND_EMBED, SEND_EMBED_ZIP_ALL_OTHERS,
                                      // SEND_ATTACHMENT, SEND_ATTACHMENT_ZIP_ALL
},
alert: {
    recipient:   'OWNER_AND_ADMIN',   // NONE, OWNER, ADMIN, OWNER_AND_ADMIN
    jobState:    'ALL',               // NONE, ALL, FAIL_ONLY, SUCCESS_ONLY
    subject:     'Year Sales Job Status',
    messageText: 'Successful run.',

    messageTextWhenJobFails: 'Job Output failed.',
    includingStackTrace:     true,
    includingReportJobInfo:  true,

    toAddresses: { address: ['statusForAdmin@mail.com'] }
}

You need to replace dummy values with your custom ones.

Please note that by default JasperReports Server uses so-called optimized scripts.

In order to test the changes you can add _opt=false parameter to URL to make the server uses non-optimized scripts:

Quote

http://localhost:8080/jasperserver-pro/flow.html?_flowId=searchFlow&_opt=false

If the changes meet your requirements, you should regenerate optimized scripts as described in JasperReports Server guide:

Quote

http://community.jaspersoft.com/documentation/jasperreports-server-ultimate-guide/v561/customizing-javascript-files

An Example of Custom AdHoc Report Generator and Report Builders : Export Ad Hoc Table Report Data to JSON

Thu, 04 Feb 2016 11:49:25 +0000

Introduction - Why this Article?

I often get the question, "What can I do if I want the Reports generated from Ad Hoc to be different than the default ones?".

One part of the answer is, "you can use a Report Template".

But this is just one part of the answer. Indeed, what we barely know is that the introduction of this concept of Report Template was linked to a more generic and powerful engine : the Report Generator.

To be more precise, a Template is a part of a Generator.

As a reminder, a Report Template permits you to:

Create a pixel perfect report from an ad hoc view
Adjust the look and feel on the existing structure of an Ad-Hoc Report and will act as a Stamp.

But, if you want to touch in a deeper way on the Report Structure, the Template will not be the answer anymore.

To change the logic with which the report/JRXML is generated, starting from an AdHoc View, you will need to create/adapt a ReportGenerator and its dependencies.

We introduced last year the JSON exporter which requires the user to add some properties on the Text Fields to create the Json Structure (for further in formation please consider Json Metadata Exporter).

To adapt in a generic way the generated Report to be exportable in Json, we will so need to use another object which is part of a Report Generator, the Report Builder.

The Report Builder permits the user to automate the JRXML generation with the Ad-Hoc view as an entry point. It is important to be clear on the wording.

NB

You can use the sample code to build your own library as a JAR file and add it to your server.

http://community.jaspersoft.com/wiki/build-your-customized-jar-jasperreports-server

It is recommended to replace the level sample in the package name hierarchy with something else specific to your project or company name.

This code has been tested on the latest release of the Professional edition of JasperReports Server, which is 6.1.1 at the time of writing. It is likely to work on 6.1,6.0.1 and 6.2.

Please be aware that this sample code is provided AS IS, it is your responsibility to review it and make sure it satisfies your requirements. Feel free to modify it and adapt it to your needs.

Principles and Definitions / the existing part

As documented in TIBCO JasperReports^® Server Administrator Guide, v6.0, Configuring Ad Hoc, Templates_and_Generators, JasperReports Server allows you to customize the way Reports are generated from Ad Hoc View.

A custom report generator can be written in java/groovy and enabled in configuration applicationContext-adhoc.xml. They should be designed as classes and MUST implement com.jaspersoft.ji.adhoc.service.AdhocReportGenerator interface.

To make them available to the user compiled jar should be placed under WEB-INF/lib folder or class file under WEB-INF/classes.

By default JasperReport Server is using the SimpleReportGenerator.

Which contains references to several ReportBuilders.

For our use case the only one we need to modify is the tableReportBuilder.

Let’s have a look to the related bean definition into the /WEB-INF/applicationContext-adhoc.xml, when we generate a report from ad-hoc without choosing any template this is what is used:

The bean which interests us is the following:

Showing that we can add easily a new Report Generator.

By default the list is empty, but once we activate a ReportGenerator reference, the popup menu which appears when you Save an AdHoc view and Create a report will change, a new Option permitting to choose a Report Generator will appear, and the popup window will then look like :

Back to our example : Let’s generate Json Reports !

To do so and following the previous explanations we will just need to:

Create our ReportGenerator, for our use case we will just copy the SimpleReportGenerator and rename it CustomWikiReportGenerator.<

Create a copy of the default TableReportBuilder named TableReportBuilderExtendable, I just switched all the methods from private to protected in order to extend it.

I just modified some methods to accept a Boolean named group which determines the behavior and structure of the json regarding if some groups have been created into the used Table Ad Hoc view.

All the modification are signaled by a comment containing the keyword JSON:

First Example, I Just changed the signature of the method:

/**
* Modified by plambert for group in detail JSON path
*/
protected JRDesignTextField getDetailField(int x, AdhocColumn column, boolean group)
{
    JRDesignTextField textField = new JRDesignTextField();

    textField.setStyleNameReference("TableDetailTextStyle");
    textField.setStretchWithOverflow(true);
    textField.setStretchType(StretchTypeEnum.RELATIVE_TO_TALLEST_OBJECT);
    textField.setBlankWhenNull(true);
    textField.setEvaluationTime(EvaluationTimeEnum.NOW);
    textField.setHyperlinkType(HyperlinkTypeEnum.NONE);
    textField.setHyperlinkTarget(HyperlinkTargetEnum.SELF);
    textField.setX(x);
    textField.setY(0);
    textField.setWidth(column.getWidth());
    textField.setHeight(detailBandHeight);
    textField.setKey("textField");
    textField.setHorizontalAlignment(HorizontalAlignEnum.getByName(column.getAlignment()));
    setMaskPattern(textField, column);
    return textField;
}

Second Example, I added this statement into the getTable() method in order to use this boolean in every required method which have had their signature changed:

//added for JSON
boolean tableHasGroup = state.getGroups().size() > 0;
//end

Again I did not change any other logic there a part Signature and usage of boolean group.

Create TableReportBuilderJSON which extends TableReportBuilderExtendable

This is where we will adapt the logic of the existing TableReportBuilder to add the json properties onto every concerned text fields.

For instance the following snippet permits to get into the JSON export the group and column names as attributes and the content of the Detail Text Field and Group Footer Text Field as values:

//to add the detail values to the JSON
@Override
protected JRDesignTextField getDetailField(int x, AdhocColumn column ,boolean group)
{
    JRDesignTextField textField =  super.getDetailField(x, column ,group);
    if(!(column.getFieldName().equals("_artificial")))
    {
        if(group) {
            textField.getPropertiesMap().setProperty("net.sf.jasperreports.export.json.path", "table.group.detail."+column.getLabel());
        }
        else {
            textField.getPropertiesMap().setProperty("net.sf.jasperreports.export.json.path", "table.detail."+column.getLabel());}
        }
        return textField;
    }
    //to add the group name to the JSON
    @Override
    protected JRDesignTextField getGroupFooterTextField( AdhocGroup adhocGroup, AdhocColumn column, int level)
    throws Exception {
        JRDesignTextField summaryTextField =  super.getGroupFooterTextField(adhocGroup, column, level);
        summaryTextField.getPropertiesMap().setProperty("net.sf.jasperreports.export.json.path", "table.group."+adhocGroup.getLabel()+"."+column.getLabel());
        return summaryTextField;
    }

Etc...

Following this logic for such an AdHoc View you will be able to export this Json Structure:

Another Example :

We need to put the .jar in the /WEB-INF/lib folder (ReportGeneratorTableJSON.jar if we consider the attached material).

Then we will just need to add this CustomWikiReportGenerator bean definition in the /WEB-INF/applicationContext-adhoc.xml

To do so 5 steps :

Add at the end of the Reportgenerator bean list:

Just after add the new ReportBuilder TableReportBuilderJSON bean definition.

Modify the reportGeneratorFactory list of reportGenerators to add our wikiReportGenerator.

Edit /WEB-INF/jsp/modules/common/jrsConfigs.jsp to put "" around commonReportGeneratorsMetadata value as follow:

  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  ~ GNU Affero  General Public License for more details.
  ~
  ~ You should have received a copy of the GNU Affero General Public  License
  ~ along with this program. If not, see .
  --%>

<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
<%@ taglib prefix="fn" uri="http://java.sun.com/jsp/jstl/functions" %>
<%@ taglib uri="/spring" prefix="spring"%>
<%@ taglib uri="http://www.springframework.org/security/tags" prefix="authz"%>
<%@ page import="com.jaspersoft.jasperserver.war.webHelp.WebHelpLookup" %>

<%--Global JRS State/Config object --%>

Knowledge Base: Best Practices

JasperServer tried to contact 104.96.227.25

Enable/Disable the heartbeat

Removing 'ticks' from Fusion Angular Gauge Chart when used as ArcGauge

Problem:

Solution:

option for Stretch with overflow

How to remove added extra loggers starting with com.jaspersoft.

Issue Description:

Resolving SSLHandshakeException in Jaspersoft Studio After Certificate Renewal

Error Trace

Recommended Steps:

Issue with AM / PM mask when exporting ad hoc report to XLS/XLSX

Sample Report: Changing Report Grouping at Run Time Based on User's Input

How to Group and Display Timestamps in 15 Minute Interval in Ad Hoc Cross Tab

Using Derived Hidden Parameter In Report Design To Ensure User Selected Date For The Report Is Not In The Future

Running JasperReports Server Bundled Installer in Silent Mode

Introduction

Step-by-Step instructions

Result

Additional Information

Localizing Domain Data

How To Access Localized Data Via A Domain

Prerequisites

Configuration Steps

Testing

Known Issues

Domain Ad Hoc View Report Listing

When Using the Bundled Installation of TIBCO JasperReports® Server an Error "The System cannot find file cmd.exe" is Received

Issue:

Solution:

How to Configure Default Values in Scheduler Notification Tab

Question:

Answer:

See also:

An Example of Custom AdHoc Report Generator and Report Builders : Export Ad Hoc Table Report Data to JSON

Introduction - Why this Article?

NB

Principles and Definitions / the existing part

Back to our example : Let’s generate Json Reports !