Issue Description

A customer tries to access their JasperReports Server from behind a proxy or loadbalancer and find this error in their logs:

2016-09-15 11:41:11,534 ERROR CsrfGuard,http-nio-8080-exec-6:44 - potential cross-site request forgery (CSRF) attack thwarted (user:, ip:192.168.150.15, method:POST, uri:/jasperserver-pro/rest_v2/reports/organizations/8001/Reports/uic_s_month_adm/inputControls/, error:required token is missing from the request)

Resolution

The CsrfGuard is protecting from Cross Site Request Forgery - https://www.owasp.org/index.php/Cross-Site_Request_Forgery (CSRF)

The message "required token is missing from the request" indicates that our application is expecting a token which isn't present in the http headers forwarded from the proxy or loadbalancer.

The token we expect is defined in jasperserver-proWEB-INFcsrfjrs.csrfguard.properties, org.owasp.csrfguard.TokenName=OWASP_CSRFTOKEN

In 5.6.x the value was JASPER_CSRF_TOKEN, but in 6.3.x it is OWASP_CSRFTOKEN .

Your network engineers should evaluate the headers and ensure the correct token is being passed

Ref. Case 00071217

The customer would like some hardware recommendation for the following configuration:

Parameters for estimating exact hardware requirements are:

• Report concurrency (number of reports run at the same time), intensity of user activity (e.g. think-time).

  It will be max 300 concurrent reports execution in a worst case scenario. 

• Report complexity and result sizes. 

  Max 4,50,000 transactions per day and 22 days in a month. 

• Existing RAM, Allocated Heap memory size, CPU Cores and other hardware specifications. 

  1. Usage Physical/Virtual OS Software Hostname CPU (Core) Mem (GB) Disk – IBM SAN SVC 

  2. Jboss1 Virtual RHEL 6.6 JBOSS EAP 6.2.4 ldctvljboa01 4 8 20G (OS) +80G (Data) 

  3. jboss2 Virtual RHEL 6.6 JBOSS EAP 6.2.4 ldctvljboa02 4 8 20G (OS) +80G (Data) 

  4. Marklogic1 Virtual RHEL 6.6 ML 8.0-4 ldctvlmara01 8 128 20G (OS) +200G (Data) 

  5. Marklogic2 Virtual RHEL 6.6 ML 8.0-4 ldctvlmara02 8 128 20G (OS) +200G (Data) 

  6. marklogic3 Virtual RHEL 6.6 ML 8.0-4 ldctvlmara03 8 128 20G (OS) +200G (Data) 

  7. Web Virtual RHEL 6.6 Apache ldctvlwebd01 2 4 20G (OS)+ 100G(Data)

  8. Jasper soft Virtual RHEL 6.6 TBD ldctvlappd01 4 32 20G (OS) + 50G(Data) 

• Active users: Active users will be max 300 . 

• Concurrent report executions: the subset of active users that are simultaneously demanding system resources like Jasper reports execution at any given time. 

Suggestion

This would be question for service team (PS/SE) to provide individual guidance on sizing. The customer's answers indicate they do not have a well defined usage plan at this time. let me read between the lines here ....

300 concurrent users running reports all the time (worst case).

• this is unlikely for an interactive system - would only happen for production reporting

No ad hoc (domains) or dashboards

4 core, 32GB RHEL for Jaspersoft 

• - could dedicate up to 30GB for Tomcat + Jaspersoft 
• - reports only do not need a large amount of memory 

IF - and this is really important - only IF: 

• the individual reports perform in a reasonable amount of time - under 5 secs, say 

• the 300 users are submitting 1 report every 30 seconds - which would be typical for interactive reports 

=> You would need 6-8 cores.

There are many variables that come into play when estimating size. Our services team can help you evaluate this.

Whether they can get that performance depend on their environment and use cases (what is being run, what is the speed of the data sources ... ).

They need to test the reports to determine base line performance and then extrapolate what their capacity will be. 

It is no longer possible in TIBCO Jaspersoft^® Studio 6.2.1 to individually control the size and position of an element inside a cross tab (or table) cell. Any element added or edited automatically snaps to the width and height of the cell. If there are multiple elements in a cell, the height is divide equally between the elements to fit the cell.

Resolution

A property called 'layout' controls how the text controls can be resized within a crosstab cell. In Jaspersoft^® Studio 6.2.1, the default behavior is that the layout property is set to 'vertical layout'. This forces the text control within the crosstab cell to conform to the dimensions of the cell. Setting the layout property to 'free layout' will allow users to change the width and length of the text control within the cell.

Ref. Case 00068065

When attempting to create a new user via REST API the error code returned is an http 400 error.

Resolution:

The user being created has several roles associated with it, including ROLE_SUPERUSER. Attempts to replicate in house showed one key difference in our test cases, that being in the in house test case the superuser user was used to login and then submit the request while in the customer's test case, a tenant administrator was used. Tenant administrator users typically do not have the ability to assign that role to users, as this role exists at the root level. Once they used the superuser account, creating the user, succeeded.

When remove 'CA' from filter - there are 5 bars which are for should be without 'orange' color. However, you see the 'orange' color on 'DF' field, the 'dark grey' one is removed (the last in the list).

How to get the legend color to stick to the color assigned?

Solution:

Using property 'SeriesItemProperty' instead of 'SeriesProperty' would apply the colors to the entire series accordingly

VO - 20181101, case #01575456

color.jrxml

When running a report in TIBCO Jaspersoft Studio, the report renders and runs fine. When the same report is ran in TIBCO JasperReports Server, the report does not run and you encounter the following error:

ERROR Validator - Invalid SQL:An error has occurred. Please contact your system administrator. (6632)

Solution:

This issue is caused by the SQL validator due to your query. To test this issue is caused by the validator you can disable it using the following instructions:

Navigate to the following directory:

C:\Jaspersoft\jasperreports-server-6.4.2\apache-tomcat\webapps\jasperserver-pro\WEB-INF\classes\esapi\security-config.properties

Change the following property in the security-config.properties file: 

security.validation.sql.on=true

to

security.validation.sql.on=false

A server restart is required to take effect. Once this change was made, and your report now works in JasperReports Server, the validator rejected your query. It is recommended to keep the validator on and only to disable it for tests.

To adjust or change the validation to accept your SQL without disabling the validation, you can make the following changes:

In the same security-config.properties file, you can modify the following property:

security.validation.sql.comments.regexp=(?:/\\*.*?\\*/)|(?:--.*?$)|(?:\\#.*?$)

You will have to add the validation there and also in the validation.properties file. The property to change in the validation.properties file is as follows:

Validator.ValidSQL=(?is)^\\s*(select|call)\\b((?!\\binto\\b)[^;])*;?\\s*$

This is just an example. Your validator may be different for your query not to be rejected by the validator.

ref: 01631182

When a report is exported to XLSX, XLS, CSV, ODS or Excel formats, the resulting files do not have logo. This issue is present for the sample reports with the Jaspersoft logo as well as company logos in reports.

Solution:

By default, JasperReports Server ignores graphics on certain exports such as excel. To get the logo to display, there will be a configuration change that needs to be done and a server restart.

The configuration change is in the applicationContext.xml file located in the WEB-INF folder. My specific location is here:

C:\Jaspersoft\jasperreports-server-7.1.0\apache-tomcat\webapps\jasperserver-pro\WEB-INF 

In the file, there is a property as follows: 

<property name="ignoreGraphics" value="true"/>

with will need to be changed to: 

<property name="ignoreGraphics" value="false"/>

Once this change has been made, a server restart will be required to take effect. Logos will be displayed in excel exports.

ref: 01634483

When creating a report book with a table of contents, the table of contents do not work in Visualize.js. The table of contents work when running the report in JasperReports Server. 

Solution:

To have the table of contents work in Visualize.js, you have to enable hyperlinks in Visualize.js. Here is a sample on how to enable hyperlinks in a report:

function (v) {
    v("#container").report( {
        resource: "/public/case_01459246/Actions_Details",
        linkOptions: {
            beforeRender: function (linkToElemPairs) {
                linkToElemPairs.forEach(showCursor);
            },
            events: {
                "click": function(ev, link) {
                    ev.stopPropagation();
                    if (link.type == "Reference") {
                        window.open(link.href);
                    }
                    console.log(link);
                }
            }
        },
        error: function (err) {
            alert(err.message);
        }
    });
 
    function showCursor(pair) {
        var el = pair.element;
        el.style.cursor = "pointer";
    }
 
});

More information can be found in the JasperReports Server Visualize.js guide on enabling hyperlinks.

ref: 01637643

When configuring and adjust your report, it works and looks just as you wanted in TIBCO Jaspersoft^® Studio, but in TIBCO JasperReports^® Server, your report looks different and the properties you have added to your report do not work.

Solution:

In JasperReports^® Server, there is a configuration file called "jasperreports.properties" located in the following path:

C:Jaspersoftjasperreports-server-7.1.0apache-tomcatwebappsjasperserver-proWEB-INFclasses

This file will overwrite or have priority over your report properties in any of your reports. It is recommended to change or disable the properties in the jasperreports.properties file so that your reports can run those certain properties.

ref: 01554991

Issue:

When trying to delete an organization, you may get the following error:

could not delete: [com.jaspersoft.ji.adhoc.hibernate.Repo Adhoc DataView#2816];
 SQL [delete from JIResource where id=? and version=?]; constraint [fk98818b77324cfecb];
 nested exception is org.hibernate.exception.ConstraintViolationException:
 could not delete: [com.jaspersoft.ji.adhoc.hibernate.RepoAdhocDataView#2816] 

Solution:

This issue is caused by a referenced report,ad hoc view, data source, dashboard, or resource pointing to the public folder. After deleting the referenced object in question, you should now be able to delete the organization.

ref: 01551864

When using TIBCO Jaspersoft^® Studio 6.4.x, there is an issue saving an existing report. It will not allow you to save the report to changes that were made. 

Solution:

In some versions of 6.4.x, this defect exists where you cannot save a report. We recommend using the latest version of Jaspersoft^® Studio 6.4.x as this fix has been implemented. A work around is also saving the report with ".jxml" at the end. Manually adding the ".jxml" will allow you to save your report. 

ref: 01540185

When running a dashboard, all looks fine, but editing a dashboard and adjusting the length or width, you get the error "Resource '/public/Reports/Your_Report' is not accessible." 

Solution:

This error can happen if the chart type is changed in the report. The report in the dashboard looks for the old chart type. This issue can also be caused by the "Hyperlinks" tab under dashboard is referencing a report that has moved in the repository. This issue can be resolved by remaking the dashboard or changing the hyperlink.

ref: 01527117

Introduction:

How to performance/stress/load test your JasperReports Server Environment. The best option is to use a tool from Apache called JMeter.

Download and Install:

This tool can be downloaded here:

https://jmeter.apache.org/download_jmeter.cgi

For this How-to, I am using JMeter 4.0.

Configuring and Using JMeter:

Once you have JMeter installed, you will have to set the JAVA_HOME to be used with JMeter. Once that is done, start JMeter. Right-click on "Test Plan" -> "Add" -> "Thread (Users) -> "Thread Group"

Once you have opened the "Thread Group", you can set your configuration. The following properties we are going to configure are:

Number of Threads: The number of users are are simulating.

Ramp-Up Period (in seconds): The time it takes to start the initial execution of your reports.

Loop Count: How many times this will report execution will loop (to simulate how many times the report will be executed).

So once you have your configuration, your "Thread Group" may look something like this:

For this test, our report will run for a total of 50 times. 

Once this is done, you can choose a report to simulate. In this test, we chose a ad hoc report to test this functionality and exporting to PDF. This report is included in the samples for JasperReports Server. This report is

04. Product Results by Store Type Report. To start your configuration, you will have to again right-click your "Thread Group" -> "Add" -> "Config Element" -> "HTTP Request Defaults". 

Once that is added, you will have to configure the path. Server Name or IP is "localhost" by default, which we need to keep, and the port number is 8080 by default, which we also will need to keep. For this specific test, we will be using this path:

http://localhost:8080/jasperserver-pro/rest_v2/reports/public/Samples/Reports/04._Product_Results_by_Store_Type_Report.pdf?j_username=superuser&j_password=superuser

Your configuration should look like this:

Some Additional Configuration:

To get a summary of your results, you can use the "View Results in Table" or use the "Summary Report". To add the table results, right-click your "Thread Group" -> "Add" -> "Listener" -> "View Results in Table". You can do the same, but select "Summary Report" for some additional information. Your results should look similar to this:

Your summary table will also look something like this:

I have also attached my jmx file for testing and reference.

http_request.jmx

User had tried to use onComponentOK to link between subjobs for non error execution and use onComponentError link to diverse the job flow to send out eMail notification when a sub job fails. What happened with this Jaspersoft ETL job design is that if a sub job (say subjobA) failed, onComponentError component sent the job flow to tSendEmail component which sent out the eMail notification as expected. However, after the successful completion of the eMail, the subjobA status became OK thus triggering onComponentOK link to continue job execution on the rest of subjobs.

After some research on the Talend community forum, we have found a tDie component that can be used to stop the subjobs execution. The tDie component will send a message to a tLogCatcher and allow the Job to terminate a Job, with a specified exit code, once the message has been processed. The user needs to make sure the "die on child error" is check marked for the job.

NOTE: This wiki article is for reference only and it may not meet all use case design scenarios as the tangible resolution. We encourage users to please refer to relevant Talend reference material and community forum for questions relating to ETL usage and job design issues.

TTC-20181022

I want only a certain group within my Active Directory to be able to login to JasperReportsServer. How do I achieve that?

Resolution:

What you can do is make sure users get no roles by default when trying to login, and map your LDAP group you want to allow logging in to an internal JasperReportsServer role that allows for login. This is all done within the applicationContext-externalAuth-LDAP-mt.xml file. So for instance you might have something like

<bean>

<property name="defaultInternalRoles">
    <list>

   </list>
</property>
<property name="organizationRoleMap">

   <-->
    <!--Example of mapping customer roles to JRS roles

   <entry>

      <key>

         <value>Admin LDAP!</value>

      </key>
    <!-- JRS role that the <key> external role is mapped to

<value>ROLE_ADMINISTRATOR</value>

</entry>

</map>

</property>

</bean>

"iText was originally released under the MPL/LGPL. On December 1, 2009, with the release of iText 5, the license was switched to the Affero General Public License v3. Projects that did not want to provide their source code (as required by the AGPL) could either purchase a commercial license to iText 5 or continue using previous versions of iText under the MPL/LGPL.

"During the due diligence process to prepare for iText 5, several IP issues with iText 2 were discovered and fixed. The different IP owners agreed to remove as many copies of the old versions from the web, but the old version still lives on in several forks. Despite this, iText 2.1.7 is still being distributed by iText on Github  and on Maven Central. For instance: iText 4 for Java was never officially released. However, iText with the svn tag 4_2_0 was made available with the release description "This is the final version of iText available as an MPL/LGPL library. "  It was a fork created by a third party that hijacked the com.lowagie groupId (which is explicitly forbidden in the Guide to uploading artifacts to the Central Repository) because this fools users into upgrading to this third party version, instead of upgrading to an official version."

TIBCO is aware of the allegations stated in the Wiki article and, after making appropriate inquiries, has determined that TIBCO may continue to distribute iText 2.x in TIBCO products in conformance with TIBCO's obligations to its end users.  

Per the notice in the various TIBCO Jaspersoft product license files as shown below, TIBCO Jaspersoft include the iText 2.1.7 version as licensed/modified under the Mozilla Public License. The licensing issue as addressed in the above Wiki article has no impact on how we've chosen to include iText 2.1.7 (as licensed under the MPL) in TIBCO Jaspersoft products, therefore it should bear no adverse effect on our users using TIBCO Jaspersoft products.

--------------------------------------------------------------------------------------------------------------------------------------------

Ref: Notice excerpt from TIBCO JasperReports Server 7.1.1

* iText, a free Java-PDF library 2.1.7

TIBCO Software Inc. has made modifications to certain files of the Original Code of this component.  The Original Code is “iText, a free JAVA-PDF library”, by Initial Developer, Bruno Lowagie, and Co-Developer, Paulo Soares.

This component and its modified and unmodified source code are licensed under the Mozilla Public License v1.1, a copy of which is included below.  You may obtain a copy of the applicable source code at http://jasperreports.sourceforge.net/maven2/com/lowagie/itext/ or by contacting TIBCO Software Inc.

                          MOZILLA PUBLIC LICENSE
                                Version 1.1

                              ---------------

1. Definitions.

     1.0.1. "Commercial Use" means distribution or otherwise making the
     Covered Code available to a third party.

     1.1. "Contributor" means each entity that creates or contributes to
     the creation of Modifications.

     1.2. "Contributor Version" means the combination of the Original
     Code, prior Modifications used by a Contributor, and the Modifications
     made by that particular Contributor.

     1.3. "Covered Code" means the Original Code or Modifications or the
     combination of the Original Code and Modifications, in each case
     including portions thereof.

     1.4. "Electronic Distribution Mechanism" means a mechanism generally
     accepted in the software development community for the electronic
     transfer of data.

     1.5. "Executable" means Covered Code in any form other than Source
     Code.

     1.6. "Initial Developer" means the individual or entity identified
     as the Initial Developer in the Source Code notice required by Exhibit
     A.

     1.7. "Larger Work" means a work which combines Covered Code or
     portions thereof with code not governed by the terms of this License.

     1.8. "License" means this document.

     1.8.1. "Licensable" means having the right to grant, to the maximum
     extent possible, whether at the time of the initial grant or
     subsequently acquired, any and all of the rights conveyed herein.

     1.9. "Modifications" means any addition to or deletion from the
     substance or structure of either the Original Code or any previous
     Modifications. When Covered Code is released as a series of files, a
     Modification is:
          A. Any addition to or deletion from the contents of a file
          containing Original Code or previous Modifications.

          B. Any new file that contains any part of the Original Code or
          previous Modifications.

     1.10. "Original Code" means Source Code of computer software code
     which is described in the Source Code notice required by Exhibit A as
     Original Code, and which, at the time of its release under this
     License is not already Covered Code governed by this License.

     1.10.1. "Patent Claims" means any patent claim(s), now owned or
     hereafter acquired, including without limitation,  method, process,
     and apparatus claims, in any patent Licensable by grantor.

     1.11. "Source Code" means the preferred form of the Covered Code for
     making modifications to it, including all modules it contains, plus
     any associated interface definition files, scripts used to control
     compilation and installation of an Executable, or source code
     differential comparisons against either the Original Code or another
     well known, available Covered Code of the Contributor's choice. The
     Source Code can be in a compressed or archival form, provided the
     appropriate decompression or de-archiving software is widely available
     for no charge.

     1.12. "You" (or "Your")  means an individual or a legal entity
     exercising rights under, and complying with all of the terms of, this
     License or a future version of this License issued under Section 6.1.
     For legal entities, "You" includes any entity which controls, is
     controlled by, or is under common control with You. For purposes of
     this definition, "control" means (a) the power, direct or indirect,
     to cause the direction or management of such entity, whether by
     contract or otherwise, or (b) ownership of more than fifty percent
     (50%) of the outstanding shares or beneficial ownership of such
     entity.

2. Source Code License.

     2.1. The Initial Developer Grant.
     The Initial Developer hereby grants You a world-wide, royalty-free,
     non-exclusive license, subject to third party intellectual property
     claims:
          (a)  under intellectual property rights (other than patent or
          trademark) Licensable by Initial Developer to use, reproduce,
          modify, display, perform, sublicense and distribute the Original
          Code (or portions thereof) with or without Modifications, and/or
          as part of a Larger Work; and

          (b) under Patents Claims infringed by the making, using or
          selling of Original Code, to make, have made, use, practice,
          sell, and offer for sale, and/or otherwise dispose of the
          Original Code (or portions thereof).

          © the licenses granted in this Section 2.1(a) and (b) are
          effective on the date Initial Developer first distributes
          Original Code under the terms of this License.

          (d) Notwithstanding Section 2.1(b) above, no patent license is
          granted: 1) for code that You delete from the Original Code; 2)
          separate from the Original Code;  or 3) for infringements caused
          by: i) the modification of the Original Code or ii) the
          combination of the Original Code with other software or devices.

     2.2. Contributor Grant.
     Subject to third party intellectual property claims, each Contributor
     hereby grants You a world-wide, royalty-free, non-exclusive license

          (a)  under intellectual property rights (other than patent or
          trademark) Licensable by Contributor, to use, reproduce, modify,
          display, perform, sublicense and distribute the Modifications
          created by such Contributor (or portions thereof) either on an
          unmodified basis, with other Modifications, as Covered Code
          and/or as part of a Larger Work; and

          (b) under Patent Claims infringed by the making, using, or
          selling of  Modifications made by that Contributor either alone
          and/or in combination with its Contributor Version (or portions
          of such combination), to make, use, sell, offer for sale, have
          made, and/or otherwise dispose of: 1) Modifications made by that
          Contributor (or portions thereof); and 2) the combination of
          Modifications made by that Contributor with its Contributor
          Version (or portions of such combination).

          © the licenses granted in Sections 2.2(a) and 2.2(b) are
          effective on the date Contributor first makes Commercial Use of
          the Covered Code.

          (d)    Notwithstanding Section 2.2(b) above, no patent license is
          granted: 1) for any code that Contributor has deleted from the
          Contributor Version; 2)  separate from the Contributor Version;
          3)  for infringements caused by: i) third party modifications of
          Contributor Version or ii)  the combination of Modifications made
          by that Contributor with other software  (except as part of the
          Contributor Version) or other devices; or 4) under Patent Claims
          infringed by Covered Code in the absence of Modifications made by
          that Contributor.

3. Distribution Obligations.

     3.1. Application of License.
     The Modifications which You create or to which You contribute are
     governed by the terms of this License, including without limitation
     Section 2.2. The Source Code version of Covered Code may be
     distributed only under the terms of this License or a future version
     of this License released under Section 6.1, and You must include a
     copy of this License with every copy of the Source Code You
     distribute. You may not offer or impose any terms on any Source Code
     version that alters or restricts the applicable version of this
     License or the recipients' rights hereunder. However, You may include
     an additional document offering the additional rights described in
     Section 3.5.

     3.2. Availability of Source Code.
     Any Modification which You create or to which You contribute must be
     made available in Source Code form under the terms of this License
     either on the same media as an Executable version or via an accepted
     Electronic Distribution Mechanism to anyone to whom you made an
     Executable version available; and if made available via Electronic
     Distribution Mechanism, must remain available for at least twelve (12)
     months after the date it initially became available, or at least six
     (6) months after a subsequent version of that particular Modification
     has been made available to such recipients. You are responsible for
     ensuring that the Source Code version remains available even if the
     Electronic Distribution Mechanism is maintained by a third party.

     3.3. Description of Modifications.
     You must cause all Covered Code to which You contribute to contain a
     file documenting the changes You made to create that Covered Code and
     the date of any change. You must include a prominent statement that
     the Modification is derived, directly or indirectly, from Original
     Code provided by the Initial Developer and including the name of the
     Initial Developer in (a) the Source Code, and (b) in any notice in an
     Executable version or related documentation in which You describe the
     origin or ownership of the Covered Code.

     3.4. Intellectual Property Matters
          (a) Third Party Claims.
          If Contributor has knowledge that a license under a third party's
          intellectual property rights is required to exercise the rights
          granted by such Contributor under Sections 2.1 or 2.2,
          Contributor must include a text file with the Source Code
          distribution titled "LEGAL" which describes the claim and the
          party making the claim in sufficient detail that a recipient will
          know whom to contact. If Contributor obtains such knowledge after
          the Modification is made available as described in Section 3.2,
          Contributor shall promptly modify the LEGAL file in all copies
          Contributor makes available thereafter and shall take other steps
          (such as notifying appropriate mailing lists or newsgroups)
          reasonably calculated to inform those who received the Covered
          Code that new knowledge has been obtained.

          (b) Contributor APIs.
          If Contributor's Modifications include an application programming
          interface and Contributor has knowledge of patent licenses which
          are reasonably necessary to implement that API, Contributor must
          also include this information in the LEGAL file.

               ©    Representations.
          Contributor represents that, except as disclosed pursuant to
          Section 3.4(a) above, Contributor believes that Contributor's
          Modifications are Contributor's original creation(s) and/or
          Contributor has sufficient rights to grant the rights conveyed by
          this License.

     3.5. Required Notices.
     You must duplicate the notice in Exhibit A in each file of the Source
     Code.  If it is not possible to put such notice in a particular Source
     Code file due to its structure, then You must include such notice in a
     location (such as a relevant directory) where a user would be likely
     to look for such a notice.  If You created one or more Modification(s)
     You may add your name as a Contributor to the notice described in
     Exhibit A.  You must also duplicate this License in any documentation
     for the Source Code where You describe recipients' rights or ownership
     rights relating to Covered Code.  You may choose to offer, and to
     charge a fee for, warranty, support, indemnity or liability
     obligations to one or more recipients of Covered Code. However, You
     may do so only on Your own behalf, and not on behalf of the Initial
     Developer or any Contributor. You must make it absolutely clear than
     any such warranty, support, indemnity or liability obligation is
     offered by You alone, and You hereby agree to indemnify the Initial
     Developer and every Contributor for any liability incurred by the
     Initial Developer or such Contributor as a result of warranty,
     support, indemnity or liability terms You offer.

     3.6. Distribution of Executable Versions.
     You may distribute Covered Code in Executable form only if the
     requirements of Section 3.1-3.5 have been met for that Covered Code,
     and if You include a notice stating that the Source Code version of
     the Covered Code is available under the terms of this License,
     including a description of how and where You have fulfilled the
     obligations of Section 3.2. The notice must be conspicuously included
     in any notice in an Executable version, related documentation or
     collateral in which You describe recipients' rights relating to the
     Covered Code. You may distribute the Executable version of Covered
     Code or ownership rights under a license of Your choice, which may
     contain terms different from this License, provided that You are in
     compliance with the terms of this License and that the license for the
     Executable version does not attempt to limit or alter the recipient's
     rights in the Source Code version from the rights set forth in this
     License. If You distribute the Executable version under a different
     license You must make it absolutely clear that any terms which differ
     from this License are offered by You alone, not by the Initial
     Developer or any Contributor. You hereby agree to indemnify the
     Initial Developer and every Contributor for any liability incurred by
     the Initial Developer or such Contributor as a result of any such
     terms You offer.

     3.7. Larger Works.
     You may create a Larger Work by combining Covered Code with other code
     not governed by the terms of this License and distribute the Larger
     Work as a single product. In such a case, You must make sure the
     requirements of this License are fulfilled for the Covered Code.

4. Inability to Comply Due to Statute or Regulation.

     If it is impossible for You to comply with any of the terms of this
     License with respect to some or all of the Covered Code due to
     statute, judicial order, or regulation then You must: (a) comply with
     the terms of this License to the maximum extent possible; and (b)
     describe the limitations and the code they affect. Such description
     must be included in the LEGAL file described in Section 3.4 and must
     be included with all distributions of the Source Code. Except to the
     extent prohibited by statute or regulation, such description must be
     sufficiently detailed for a recipient of ordinary skill to be able to
     understand it.

5. Application of this License.

     This License applies to code to which the Initial Developer has
     attached the notice in Exhibit A and to related Covered Code.

6. Versions of the License.

     6.1. New Versions.
     Netscape Communications Corporation ("Netscape") may publish revised
     and/or new versions of the License from time to time. Each version
     will be given a distinguishing version number.

     6.2. Effect of New Versions.
     Once Covered Code has been published under a particular version of the
     License, You may always continue to use it under the terms of that
     version. You may also choose to use such Covered Code under the terms
     of any subsequent version of the License published by Netscape. No one
     other than Netscape has the right to modify the terms applicable to
     Covered Code created under this License.

     6.3. Derivative Works.
     If You create or use a modified version of this License (which you may
     only do in order to apply it to code which is not already Covered Code
     governed by this License), You must (a) rename Your license so that
     the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape",
     "MPL", "NPL" or any confusingly similar phrase do not appear in your
     license (except to note that your license differs from this License)
     and (b) otherwise make it clear that Your version of the license
     contains terms which differ from the Mozilla Public License and
     Netscape Public License. (Filling in the name of the Initial
     Developer, Original Code or Contributor in the notice described in
     Exhibit A shall not of themselves be deemed to be modifications of
     this License.)

7. DISCLAIMER OF WARRANTY.

     COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
     WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
     WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF
     DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING.
     THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE
     IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT,
     YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE
     COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER
     OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF
     ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

8. TERMINATION.

     8.1.  This License and the rights granted hereunder will terminate
     automatically if You fail to comply with terms herein and fail to cure
     such breach within 30 days of becoming aware of the breach. All
     sublicenses to the Covered Code which are properly granted shall
     survive any termination of this License. Provisions which, by their
     nature, must remain in effect beyond the termination of this License
     shall survive.

     8.2.  If You initiate litigation by asserting a patent infringement
     claim (excluding declatory judgment actions) against Initial Developer
     or a Contributor (the Initial Developer or Contributor against whom
     You file such action is referred to as "Participant")  alleging that:

     (a)  such Participant's Contributor Version directly or indirectly
     infringes any patent, then any and all rights granted by such
     Participant to You under Sections 2.1 and/or 2.2 of this License
     shall, upon 60 days notice from Participant terminate prospectively,
     unless if within 60 days after receipt of notice You either: (i)
     agree in writing to pay Participant a mutually agreeable reasonable
     royalty for Your past and future use of Modifications made by such
     Participant, or (ii) withdraw Your litigation claim with respect to
     the Contributor Version against such Participant.  If within 60 days
     of notice, a reasonable royalty and payment arrangement are not
     mutually agreed upon in writing by the parties or the litigation claim
     is not withdrawn, the rights granted by Participant to You under
     Sections 2.1 and/or 2.2 automatically terminate at the expiration of
     the 60 day notice period specified above.

     (b)  any software, hardware, or device, other than such Participant's
     Contributor Version, directly or indirectly infringes any patent, then
     any rights granted to You by such Participant under Sections 2.1(b)
     and 2.2(b) are revoked effective as of the date You first made, used,
     sold, distributed, or had made, Modifications made by that
     Participant.

     8.3.  If You assert a patent infringement claim against Participant
     alleging that such Participant's Contributor Version directly or
     indirectly infringes any patent where such claim is resolved (such as
     by license or settlement) prior to the initiation of patent
     infringement litigation, then the reasonable value of the licenses
     granted by such Participant under Sections 2.1 or 2.2 shall be taken
     into account in determining the amount or value of any payment or
     license.

     8.4.  In the event of termination under Sections 8.1 or 8.2 above,
     all end user license agreements (excluding distributors and resellers)
     which have been validly granted by You or any distributor hereunder
     prior to termination shall survive termination.

9. LIMITATION OF LIABILITY.

     UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
     (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL
     DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE,
     OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR
     ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
     CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL,
     WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER
     COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN
     INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
     LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY
     RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
     PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
     EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO
     THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.

10. U.S. GOVERNMENT END USERS.

     The Covered Code is a "commercial item," as that term is defined in
     48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer
     software" and "commercial computer software documentation," as such
     terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48
     C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995),
     all U.S. Government End Users acquire Covered Code with only those
     rights set forth herein.

11. MISCELLANEOUS.

     This License represents the complete agreement concerning subject
     matter hereof. If any provision of this License is held to be
     unenforceable, such provision shall be reformed only to the extent
     necessary to make it enforceable. This License shall be governed by
     California law provisions (except to the extent applicable law, if
     any, provides otherwise), excluding its conflict-of-law provisions.
     With respect to disputes in which at least one party is a citizen of,
     or an entity chartered or registered to do business in the United
     States of America, any litigation relating to this License shall be
     subject to the jurisdiction of the Federal Courts of the Northern
     District of California, with venue lying in Santa Clara County,
     California, with the losing party responsible for costs, including
     without limitation, court costs and reasonable attorneys' fees and
     expenses. The application of the United Nations Convention on
     Contracts for the International Sale of Goods is expressly excluded.
     Any law or regulation which provides that the language of a contract
     shall be construed against the drafter shall not apply to this
     License.

12. RESPONSIBILITY FOR CLAIMS.

     As between Initial Developer and the Contributors, each party is
     responsible for claims and damages arising, directly or indirectly,
     out of its utilization of rights under this License and You agree to
     work with Initial Developer and Contributors to distribute such
     responsibility on an equitable basis. Nothing herein is intended or
     shall be deemed to constitute any admission of liability.

13. MULTIPLE-LICENSED CODE.

     Initial Developer may designate portions of the Covered Code as
     "Multiple-Licensed".  "Multiple-Licensed" means that the Initial
     Developer permits you to utilize portions of the Covered Code under
     Your choice of the MPL or the alternative licenses, if any, specified
     by the Initial Developer in the file described in Exhibit A.

EXHIBIT A -Mozilla Public License.

     ``The contents of this file are subject to the Mozilla Public License
     Version 1.1 (the "License"); you may not use this file except in
     compliance with the License. You may obtain a copy of the License at
     http://www.mozilla.org/MPL/

     Software distributed under the License is distributed on an "AS IS"
     basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
     License for the specific language governing rights and limitations
     under the License.

     The Original Code is ______________________________________.

     The Initial Developer of the Original Code is ________________________.
     Portions created by ______________________ are Copyright © ______
     _______________________. All Rights Reserved.

     Contributor(s): ______________________________________.

     Alternatively, the contents of this file may be used under the terms
     of the _____ license (the  "[___] License"), in which case the
     provisions of [______] License are applicable instead of those
     above.  If you wish to allow use of your version of this file only
     under the terms of the [____] License and not to allow others to use
     your version of this file under the MPL, indicate your decision by
     deleting  the provisions above and replace  them with the notice and
     other provisions required by the [___] License.  If you do not delete
     the provisions above, a recipient may use your version of this file
     under either the MPL or the [___] License."

     [NOTE: The text of this Exhibit A may differ slightly from the text of
     the notices in the Source Code files of the Original Code. You should
     use the text of this Exhibit A rather than the text found in the
     Original Code Source Code for Your Modifications.]

TTC-20181017

Hi There are lots of items that can be configured as per the following link: http://jasperreports.sourceforge.net/config.reference.html As far as I know, some items listed in above link can be put into the JRXML file, and some can be put into the TIBCO JasperReports^® Server  configuration file(i.e. jasperreports.properties). The question is, how can a customer know where they should put the configuration item into when they decide to use a specific one?

Resolution

All the configuration has the option given as scope that is Global |report|Element|Column etc.. If it is Global that means you could configure in jasperreports.properties file else you can configure in report level or at column level.

Ref. Case 00065876

Here we recreate the report shown in this demo, but do so without using the custom web service extension demonstrated there.

As opposed to the indicated demo, we are going to create a data adapter of type JSON File, which is a built-in type in JRL and JSS, instead of the custom data adapter type made available by that optional extension used in that demo.

The JSON data adapter allows specifying a remote URL instead of a local JSON file, as the source for the data.

When using an URL, the button next to the File/URL field changes from File to Options and thus allows setting request parameters and request headers for the HTTP call that will be made to the specified URL to retrieve the JSON data.

Once saved, the data adapter file would be available in the list of data adapters from which we can pick during the report creation wizard.

The report creation wizard will try connect to the remote URL and retrieve some data. It will show this data in the left panel and allows to select the node in the JSON object which represents the data source records for the report.

Once the data source record node selected, it will propose the selection of available fields that can be picked from the record node to use as report fields.

At the end of the report wizard, we obtain a JRXML file in which the main dataset has a JSONQL query and dataset fields that have special configuration properties which map them to specific nodes or attributes in the current record JSON node.

Adding some fields in the detail band helps complete the creation of a simple tabular report displaying records coming from JSON data loaded from a remote REST location.

Attached to this page are the data adapter file and the report template file used in this article.

noaadataadapter.xml

noaareport.jrxml

Resolution

This is default behavior of GMail.

If an email exceed 102kb size (GMail limit), GMail just clips the message and add

[Message clipped]  View entire message

text and hyperlink and the page bottom, on the left side and causes the shift.

If an email has less then 102kb, the report displays as expected.

This behavior out of  TIBCO JasperReports® Server control.

Please review an article that explains GMail behavior:

https://epicfizz.com/gmail-message-clipped-why-and-fix/

What you could try is to install 'Trimless for Google Mail™' Chrome extension which expands trimmed parts, removes "Show trimmed content" button and as a result, the report displayed centered:

https://chrome.google.com/webstore/detail/trimless-for-google-mail/niepjjjfafhadmfdminbckmciijcaagc

Chrome restart may required to make the extension work.

Ref. Case 01638281

TIBCO JaasperReports^® Server is configured behind load balancer and when attempting to login via the TIBCO JaasperReports Server login page, the authentication fails and navigates from /jasperserver-pro/loginsuccess.html page  back to /jasperserver-pro/login.html.

Resolution:

The proxy definition template requires certain rules to dictate to Jasper what content to request from the application once authentication is successful. Below is an example template containing some rules that should be in a proxy definition:

# ************************************

<VirtualHost *:443>
  ServerName external.example.com

  ## Vhost docroot
  DocumentRoot "/srv/www/external.example.com"

  ## Directories, there should at least be a declaration for /srv/www/external.example.com

  <Location "/">

        Order allow,deny
        Allow from all

  </Location>

  <Proxy "*">

        Order deny,allow
        Allow from all

  </Proxy>

  ## Logging
  ErrorLog "/var/log/httpd/external.example.com_error_ssl.log"
  ServerSignature Off
  CustomLog "/var/log/httpd/external.example.com_access_ssl.log" combined

  ## Request header rules
  ## as per http://httpd.apache.org/docs/2.2/mod/mod_headers.html#requestheader
  RequestHeader set X-Forwarded-Proto "https"
  RequestHeader set X-Forwarded-Port "443"

  ## Proxy rules
  ProxyRequests Off
  ProxyPreserveHost On
  ProxyPass /jasperserver-pro http://internal.example.local:8080/jasperserver-pro
  ProxyPassReverse /jasperserver-pro http://internal.example.local:8080/jasperserver-pro

  ## SSL directives
  SSLEngine on
  SSLCertificateFile      "/etc/pki/tls/certs/ssl.crt"
  SSLCertificateKeyFile   "/etc/pki/tls/private/ssl.key"
  SSLCertificateChainFile "/etc/pki/tls/certs/chain.crt"

  # SSL Proxy directives
  SSLProxyEngine On
</VirtualHost>

Please note the above template should be customized to the particular environment where this will be deployed.

According to the external authentication cookbook, to synchronize a user's roles in external authentication with the TIBCO JasperReports^® Server repository a user must first login. How would synchronizing several users at once be achieved?

Resolution:

The REST login call can be utilized to synch external users in a batch because scripts can be built around the REST call that will perform a login request. Such a script can potentially be built to read the list of external users (in LDAP for example) and then passed to the REST login call. More information about the REST login call can be found in chapter 3.3 of the TIBCO JasperReports Server REST API Reference v7.1.0.

We have created a dashboard and want to use http api to display it.

Here is the URL we use : https://<IP address>/reports/flow.html?_flowId=dashboardRuntimeFlow&dashboardResource=%2Fpublic%2FDashBoard_Test_Hack&decorate=no&viewAsDashboardFrame=true&j_username=superuser&j_password=superuser

But we have got this exception instead of Dashboard that should be rendered:

2016-02-17 08:37:30,799 ERROR AdhocEngineServiceImpl,http-bio-8080-exec-3:1695 - [LoadDashboard]: Unable to cast to DashboardResource

Answer:

As of JasperReports Server 6.0, dashboards don't use the flow.html entry point used by Spring Web Flow. Instead, they use an updated dashboard entry point.

The following example opens a dashboard for viewing:

http://<host>:<port>/<context>/dashboard/viewer.html#/public/Samples/Dashboards/1._Supermart_Dashboard

To open a dashboard for editing, call the Dashboard Designer:

http://<host>:<port>/<context>/dashboard/designer.html#/public/Samples/Dashboards/1._Supermart_Dashboard

More detail on HTTP API can be found in Ultimate guide

(please see Executing Dashboards section):

http://community.jaspersoft.com/documentation/tibco-jasperreports-server-ultimate-guide/v610/repository-http-api

Issue Description

Customer developed a JRXML report with Charts Pro component.

When the report runs in JasperReports Server, output looks good, per requirements.

However, when the report exported to PDF format, it shows some extra axis lines, please refer to printscreen.

How to fix the issue?

Resolution

The lines, displayed in PDF output, are so-called divisional lines:

https://www.fusioncharts.com/dev/chart-guide/chart-configurations/div-lines-and-grids

In order to remove/hide them in PDF, try to specify the following settings in 'Divisional Lines and Grids' menu of the chart settings:

Num = 0

Color = #FFFFFF

Alpha = 0

Please find attached printscreen:

It might be possible that the properties seem to be already set.

In that case try to change them to another value and then back to the provided one, to make sure the values are really saved,

or manually modify report JRXML file and add required properties:

<fc:chartProperty name="divLineColor">
    <fc:propertyExpression><![CDATA[new java.awt.Color(-1)]]></fc:propertyExpression>
</fc:chartProperty>
<fc:chartProperty name="numDivLines">
    <fc:propertyExpression><![CDATA[new Integer(0)]]></fc:propertyExpression>
</fc:chartProperty>
<fc:chartProperty name="divLineAlpha">
    <fc:propertyExpression><![CDATA[new Integer(0)]]></fc:propertyExpression>
</fc:chartProperty>

Ref. Case 01597755