Knowledge Base: FAQs

Connecting to Amazon RDS/Redshift from a remote TIBCO JasperReports® Server fails

Sun, 19 Nov 2017 03:26:56 +0000

Issue

When trying to create an AWS Data Source on TIBCO JasperReports^® Server you are seeing the following error message:

Possible cause and solution

A probable cause for this type of error message is that the automatic access rules setup for this JasperReports Server instance is disabled in Cloud Settings. Log in as superuser, then go to Manage -> Server Settings -> Cloud Settings, and make sure the the following property is checked:

Connecting to Amazon RDS/Redshift from JasperReports® Server deployed on premises

Sun, 19 Nov 2017 03:17:26 +0000

Use case

In this scenario, the database (either Redshift or one of database types available as Amazon RDS) is deployed in cloud, and TIBCO JasperReports^® Server is deployed locally or somewhere outside AWS.

The steps

In this scenario you will have to use AWS credentials to connect to Amazon RDS/Redshift. One way to do this is to click on the Generate Credentials link in AWS Data Source dialog:

And then follow the steps to generate a user with credentials from CloudFormation Template. It should be done within a minute.

Another way to create the credentials is to log into your AWS console, go to Services -> IAM -> Users, select your user, go to the Security Credentials tab, and generate a new pair by clicking on the 'Create Access Key' button.

WARNING: keep any active keys safe; if a malicious user gets a hold of the Access Key and the Secret Key, they will have access to the resources deployed on your AWS account and will be able to use them at your expense.

Once created, copy the Access Key and the Secret Key to the data source fields. After this you can select the required region, find available databases with 'Find My AWS Data Sources' button and connect using your database credentials.

Other notes

You may also have to specify your JasperReports Server's public IP address so that AWS data source can create a security rule on AWS for your server to be able to connect to Amazon RDS/Redshift. The IP is specified in the web interface of JasperReports Server under Manage->Server Settings->Cloud Settings:

NoSuchMethodError after applying 6.4.0 hotfix

Fri, 17 Nov 2017 00:37:18 +0000

Issue description

After applying a cumulative hotfix for TIBCO JasperReports^® Server v6.4.0 some reports fail with the following error:

java.lang.NoSuchMethodError: net.sf.jasperreports.engine.fill.BaseReportFiller.getUsedPageWidth()I

Cause and solution

The latest hotfix for JasperReports Server 6.4.0 contains an additional step which is not usually present in most hotfix packages:

Delete the files listed in the section "Deleted files" from the web application files structure.

The mentioned section lists the ../WEB-INF/lib/jasperreports-6.4.1.jar file, which you have to delete prior to applying the hotfix. Since this step is unique to the latest version of 6.4.0 hotfix, it is fairly easy to overlook

How to pass an XML Datasource to a Table Component

Sat, 13 May 2017 19:08:27 +0000

Issue Description

It is possible pass an XML Datasource to a jrxml's Table Component.

Resolution

The JasperReport Samples can be combined to provide information and examples of passing an XmlDatasource to a Table Component. So we'll reference these:

Subreport example:

http://jasperreports.sourceforge.net/sample.reference/subreport/index.html#subreports

XmlDatasource example:

http://jasperreports.sourceforge.net/sample.reference/xmldatasource/index.html

The files can be used within Studio via File -> New -> Project , browsing to the JasperReports Samples project, then running the report against the "Sample DB" datasource where possible.

Table Components, like charts and crosstabs get their data from "datasets". A dataset is similar to a subreport in many ways, so a table and subreport are very similar. The XmlDataSource sample's CustomersReport calls a subreport, so we can use it as the basis for our table.

In typical subReport element you define either or to specify the source used to populate the sub. (see Subreport example )

In typical table component you specify the dataset via a datasetRun element, like:

(for more info on datasets and datasetruns see the JR Ultimate Guide Datasets chapter)

But as you've seen in XmlDatasource sample, instead of , the Xpath query executor (queryString language="xPath") can expect $P{XML_DATA_DOCUMENT} . You can do the same thing with table compoments, skip the datasetRun, and just set subreportParameterExpression>$P{XML_DATA_DOCUMENT}

In the attached CustomersXmlMain.jrxml, I edited the XmlDataSource samples main report to remove the subreport and replace it with a table component. To do this I:

Ran the table wizard to get basic field layout.
Then I grabbed the query from the Xmldatasource example's subreport, OrdersReport.jrxml:
```
    
```
Created a parameter for the table's dataset
Edited the jrxml source, modifying the datasetRun to have three parameters, one for the parameterized query, the others for the Xpath executor:
```
    
        
    


    
        
    


    
        
    
```

References:

http://community.jaspersoft.com/documentation/jasperreports-library-ultimate-guide

Ref. Case 01438960

customersxmlmain_0.jrxml

Manually Update AWS Marketplace Instances to use Tomcat 8/Java 8

Wed, 15 Nov 2017 01:08:49 +0000

Steps to Manually Upgrade the Java and Tomcat versions from 7 to 8 on the Amazon AWS Marketplace CloudFormation Template AMIs

Steve Park, CISSP, Principal Customer Success Engineer, TIBCO Jaspersoft

Written on November 14th, 2017

The AMIs that are included with the hourly and BYOL Cloud Formation Templates (CFT) available on the Amazon Marketplace use Tomcat 7 and Java 7. In addition to being no longer officially supported, both our internal testing and feedback from customers indicate that Tomcat 8 and Java 8 offer superior performance. In order to upgrade the Tomcat and Java versions, please follow the following steps. These steps were tested using JasperReports Server 6.3.0, but I'm unaware of any issues when using either version 6.3.2 or version 6.4.

Manual Upgrade Steps

Launch either an hourly or BYOL instance on the Marketplace and SSH into it using the ec2-user@ account
Become the root user:
```
sudo su -
        
```
Update all of the packages on the instance:
```
yum update
        
```
Remove the Tomcat 7 server:
```
yum erase tomcat7
        
```

Remove OpenJDK7:

yum erase java-1.7.0-openjdk.x86_64

Install OpenJDK8:

yum install java-1.8.0-openjdk.x86_64

Edit the /etc/profile file and add the following line right above the EXPORT command:
```
JAVA_HOME=/usr/lib/jvm/jre-1.8.0
        
```

Add JAVA_HOME to the list of variables set by the EXPORT command:

export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE HISTCONTROL JAVA_HOME

Execute the source command on the command line to set the JAVA_HOME environment variable:
```
source /etc/profile
        
```
Run the echo command on the command line to verify the JAVA_HOME environment variable has been properly set:
```
echo $JAVA_HOME
        
```
Install Tomcat 8:
```
yum install tomcat8
        
```
Change the tomcat user's home folder by executing the following command on the command line:
```
usermod -d /usr/share/tomcat8 tomcat
        
```
Navigate to the /etc/jasperserver folder:
```
cd /etc/jasperserver
        
```
Navigate to the /etc/jasperserver folder:
```
cd /etc/jasperserver
        
```

Rename the tomcat7.config file to tomcat8.config:

mv tomcat7.config tomcat8.config

Open the tomcat8.config file in a text editor like vi, and change the second CATALINA_OPTS= line to:
```
CATALINA_OPTS="$CATALINA_OPTS -XX:+UseG1GC"
        
```
Save and close the file
On the command line, replace all occurrences of tomcat7 with tomcat8 in the files in the current directory:
```
sed -i 's/tomcat7/tomcat8/g'
        
```

Edit the memory_settings.sh file in a text editor like vi and replace its contents with the following:

#!/bin/sh
            rm -f /tmp/instance-type
            wget -q http://169.254.169.254/latest/meta-data/instance-type -O /tmp/instance-type
            itype=`cat /tmp/instance-type`
            case $itype in
            ("m1.medium") echo "-Xms2048m -Xmx2048m -XX:MetaspaceSize=512m -XX:MaxMetaspaceSize=512m -Xss2m";;
            ("m3.medium") echo "-Xms2048m -Xmx2048m -XX:MetaspaceSize=512m -XX:MaxMetaspaceSize=512m -Xss2m";;
            ("m1.large") echo "-Xms5500m -Xmx5500m -XX:MetaspaceSize=1024m -XX:MaxMetaspaceSize=1024m -Xss2m";;
            ("m3.large") echo "-Xms5500m -Xmx5500m -XX:MetaspaceSize=1024m -XX:MaxMetaspaceSize=1024m -Xss2m";;
            ("m1.xlarge") echo "-Xms13300m -Xmx13300m -XX:MetaspaceSize=1024m -XX:MaxMetaspaceSize=1024m -Xss2m";;
            ("m3.xlarge") echo "-Xms13000m -Xmx13000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("m3.2xlarge") echo "-Xms28000m -Xmx28000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("c1.xlarge") echo "-Xms5500m -Xmx5500m -XX:MetaspaceSize=1024m -XX:MaxMetaspaceSize=1024m -Xss2m";;
            ("m2.xlarge") echo "-Xms15000m -Xmx15000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("m2.2xlarge") echo "-Xms30000m -Xmx30000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("m2.4xlarge") echo "-Xms62000m -Xmx62000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("hi1.4xlarge") echo "-Xms560000m -Xmx560000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("hs1.8xlarge") echo "-Xms107000m -Xmx107000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("cc1.4xlarge") echo "-Xms20000m -Xmx20000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("cc2.8xlarge") echo "-Xms56000m -Xmx56000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("cg1.4xlarge") echo "-Xms20000m -Xmx20000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("m4.large") echo "-Xms5500m -Xmx5500m -XX:MetaspaceSize=1024m -XX:MaxMetaspaceSize=1024m -Xss2m";;
            ("m4.xlarge") echo "-Xms13000m -Xmx13000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("m4.2xlarge") echo "-Xms28000m -Xmx28000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("m4.4xlarge") echo "-Xms60000m -Xmx60000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("m4.10xlarge") echo "-Xms150000m -Xmx150000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("r3.xlarge") echo "-Xms280000m -Xmx280000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("r3.2xlarge") echo "-Xms56000m -Xmx56000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("c4.xlarge") echo "-Xms5500m -Xmx5500m -XX:MetaspaceSize=1024m -XX:MaxMetaspaceSize=1024m -Xss2m";;
            ("c4.2xlarge") echo "-Xms13000m -Xmx13000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("c4.4xlarge") echo "-Xms280000m -Xmx280000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            ("c4.8xlarge") echo "-Xms56000m -Xmx56000m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -Xss2m";;
            (*) echo "-Xms2048m -Xmx2048m -XX:MetaspaceSize=512m -XX:MaxMetaspaceSize=512m -Xss2m";;
            esac

Save the file and exit the text editor
On the command line, navigate to the /etc/tomcat8 folder:
```
cd /etc/tomcat8
        
```
Edit the tomcat8.conf file and change the JAVA_HOME variable to:
```
/usr/lib/jvm/jre-1.8.0
        
```
Save the file and exit the text editor
On the command line, use the cat command to append the contents of the /etc/jasperserver/tomcat8.config file to the /etc/tomcat8/tomcat8.conf file:
```
cat /etc/jasperserver/tomcat8.config >> /etc/tomcat8/tomcat8.conf
        
```

Copy the /etc/jasperserver jrs_* files to their respective locations in the /etc/init.d folder:

cp /etc/jasperserver/jrs_boot_settings.sh /etc/init.d/jrs_boot_settings
            cp /etc/jasperserver/jrs_init.sh /etc/init.d/jrs_init

Navigate to the /etc/init.d folder:
```
cd /etc/init.d
        
```
Enable the jrs_init script to run on startup:
```
chkconfig jrs_init on
        
```
Change ownership of the /etc/init.d/jrs* scripts to ec2-user:
```
chown ec2-user:ec2-user /etc/init.d/jrs*
        
```
Edit the /etc/tomcat8/server.xml file and change the port from 8080 to 80:
Edit the /etc/yum/post-actions/allowTomcatToBindPort80.action file and change all occurrences of tomcat7 to tomcat8
Save the file and exit the text editor
On the command line, navigate to the /usr/share/jrs_dist/jasperreports-server-bin folder:
```
cd /usr/share/jrs_dist/jasperreports-server-bin
```
Recursively change the tomcat7 references to tomcat8 in all files:
```
find ./ -type f -exec sed -i -e 's/tomcat7/tomcat8/g' {} \;
```
On the command line, navigate to the buildomatic folder that's under the current folder:
```
cd buildomatic
        
```
Deploy the JasperReports Server web application:
```
./js-ant deploy-webapp-pro
        
```
Copy the password-changer-1.0.jar file from /etc/jasperserver to /usr/share/tomcat8/lib:
```
cp /etc/jasperserver/password-changer-1.0.jar /usr/share/tomcat8/lib
        
```

Copy the ROOT application from tomcat7 to tomcat8:

cp -R /var/lib/tomcat7/webapps/ROOT /var/lib/tomcat8/webapps

Change ownership of /var/lib/tomcat8 to tomcat:

chown -R tomcat:tomcat /var/lib/tomcat8

Change ownership of /usr/share/tomcat8 to tomcat:

chown -R tomcat:tomcat /usr/share/tomcat8

Exit out of the SSH session
In the web browser, assuming you're still logged in to AWS, click Services -> EC2
Click the Running Instances link
Click the checkbox next to the running instance, then click Actions -> Image -> Create Image
Provide an image name and description, then click the Create Image button
Click the Services menu item, then under Management Tools, click the CloudFormation link
Click the name of the running stack
Mouse over the Other Actions button in the upper-right corner and select the View/Edit template in Designer option
In the template code section in the lower half of the page, scroll until you find the section that begins with Mappings and contains AWSRegionAMI
In the desired region, change the name of the AMI id to the one you just saved
Mouse over the File menu button in the upper-left corner (it looks like a page with the upper-right corner folded over) and select Save
If you don't have an S3 bucket to save the template to, you may need to save it as a local file until you can create an S3 bucket later
Close the CloudFormation stack editor and return to the Running Instances page
Click the name of the running stack again
Click the Update Stack button in the upper-right corner
Specify either the S3 template URL or upload the saved template file to S3
Continue through the wizard until the stack restarts

Validation

You can validate the steps taken by SSH'ing into the new instance and running the following commands:

sudo su -
    java -version    # should show Java 8
    ps -eaf | grep tomcat   # should show the server using /var/lib/tomcat8 file locations

Error in buildomatic trying to use JTDS jdbc driver - "Error invoking getDriver() method"

Tue, 14 Nov 2017 22:59:44 +0000

Issue Description

A customer attempted to switch buildomatic installation processes to use the jdbc driver from JTDS. They encountered an error when running buildomatic commands, "Error invoking getDriver() method". The error means the jar file is found, but we're using the wrong class name to try and load the driver "class" from within the jar

The TIBCO JasperReports^® Server Installation Guide reviews steps for using the default TIBCO jdbc driver for Microsoft Sql Server, as well as Microsoft's own jdbc driver which we refer to as native. These are described in the Installation guide in section titled "Working With JDBC Drivers". It does not review steps for using a third-party driver like the JTDS driver

Resolution

If you simply want JasperReports Server (the webapp) to use JTDS you could just update META-INFcontext.xml and stick the jar in Tomcat/lib. If you want the buildomatic process to use JTDS then one solution, in addition to the things you've already done within your default_master.properties file is to do:

Comment-out the jdbcDriverMaker=native in default_master.properties, these steps won't use the native.
Edit 6.3.0binbuildomaticconf_sourcedbsqlserverdb.properties, commenting out the initial driver value and adding a new driver, like:
```
# driver class
# jdbcDriverClass=tibcosoftware.jdbc.sqlserver.SQLServerDriver
jdbcDriverClass=net.sourceforge.jtds.jdbc.Driver
```

Edit 6.3.0binbuildomaticconf_sourcedbsqlserverdb.templates.properties, commenting out the initial url and add a new one, like:

# port or instance are appended to host name in dbHost property during setup 
# admin.jdbcUrl=jdbc:tibcosoftware:sqlserver://${dbHostOrInstance};sendTimestampEscapeAsString=false 
# js.jdbcUrl=jdbc:tibcosoftware:sqlserver://${dbHostOrInstance};databaseName=${js.dbName};sendTimestampEscapeAsString=false admin.jdbcUrl=jdbc:jtds:sqlserver://${dbHostOrInstance};sendTimestampEscapeAsString=false js.jdbcUrl=jdbc:jtds:sqlserver://${dbHostOrInstance};databaseName=${js.dbName};sendTimestampEscapeAsString=false

NOTE, you should double-check whether or not sendTimeStampEscapeAsString is a valid option/param for the jtds driver.

js-ant clean-config, followed by js-ant gen-config (to save and rebuild the associated configuration values and files)
The .jar needs to be in 6.3.0binbuildomaticconf_sourcedbsqlserverjdbc
Save and restart.

Ref. Case 01528977

How to count the number of reports and dashboards that reside within a specific tenant / organization or folder

Sat, 13 May 2017 18:36:26 +0000

Issue Description

How to count the number of reports and dashboards that reside within a specific tenant / organization? This will require a SQL query against the repository tables.

Resolution

To count the number of reports and dashboards that reside within a specific tenant/org you'll have match reports/dashboards to folders since resources are identified by the folder they reside in, rather than some tenantID. Underlying reportunits and dashboard are defined in JIResource table which contains field 'parent_folder' which identifies the folder ID they are within.

So first you'll need to interrogate the URI field of JIResourceFolder which contains ID and URI. So if I new that the org "Greg" created reports and dashboards within organzations/greg/dailyreports, I'd find the ID via:

select id 
  from jiresourcefolder 
 where URI like '%organization/Greg/dailyreports%'

Then you could do the following to fetch all reports and dashboards residing in that folder. If the folder ID was 12345:

select count(*)  
  from jiresource 
 where parent_folder = 12345  
   and (   resourcetype = 'com.jaspersoft.jasperserver.api.metadata.jasperreports.domain.ReportUnit' 
        or resourcetype = 'com.jaspersoft.ji.dashboard.DashboardModelResource')

For Ad Hoc Views, the resourcetype would be:

 'com.jaspersoft.ji.adhoc.AdhocDataView'

Note, Reports Saved from Ad Hoc View are the same as regular jrxml-based reports, which is:

 'com.jaspersoft.jasperserver.api.metadata.jasperreports.domain.ReportUnit'

Ref. Case 01444894

TIBCO JasperReports® Server install with Oracle 12c and "username should starts with c##" message

Wed, 15 Nov 2017 02:46:04 +0000

Issue Description

Oracle 12c with CDB/PDB configured requires particular users for TIBCO JasperReports^® Server installation.

The first symptom is that during js-install.bat (or other buildomatic commands) you encounter an error with message:

"username should starts with c##".

Resolution

Oracle CDB/PDB provides a multi-tenant architecture. If you are seeing the "username should starts with c##" message this is a sign that you are using a local or regular user to connect to the CDB. If you connect directly to the PDB via a specific SID, then the local or regular user should be fine, but you can't connect regular or local user to the CDB per Oracle, see https://docs.oracle.com/database/121/DBSEG/users.htm#DBSEG573

To connect to the CDB follow the instructions in the Installation Guide: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-installation-guide/v630/installing-war-file-using-js . It states that for Oracle 12c with CDB/PDB a common user should be specified in the default_master.properties file using the ## syntax as specified by Oracle:

Use settings for Oracle, except for the following changes:

dbUsername=c##jasperserver sid=cdb1

Ref. Case 01533066

Initial login password for AWS single instance VS cluster

Thu, 09 Nov 2017 19:58:20 +0000

Issue

When installing TIBCO JasperReports^® Server on a local/private machine, the default documented login/password are superuser/superuser. However this combination does not work for JasperReports Server instances deployedo on AWS using one of the CloudFormation templates.

Explanation

For single instances, the default password for a newly created will be the same as your instance name:

When deploying Jaspersoft for AWS Cluster, the default password will be the same as the password of the database created/used for this cluster:

In both cases you will be prompted to change the password upon first login.

This information is also mentioned on the Getting Started for JasperReports Server AWS instances

First deployment of TIBCO JasperReports® Server on AWS fails

Wed, 08 Nov 2017 00:30:39 +0000

Use case description

The first deployment of TIBCO JasperReports^® Server on AWS instance for the account using a cloud formation template failed for no clear reason (for the reference, a full list of pre-configured instances of JasperReports^® Server on AWS can be found on this page). No AWS instance was successfully deployed for this account previously.

Probable cause and solution

The most common reason for a pre-configured cloud formation instance to fail is that the Sofrware Terms were not accepted for the account. The Software Terms are found on a separate page than the actual templates, which is why this step is easy to overlook. To accept the Software Terms, log into your AWS account and follow this link:

https://aws.amazon.com/marketplace/search/results/ref=gtw_navgno_search_box?searchTerms=jaspersoft&search=

Select the type of an instance you need (Hourly or BYOL) and follow the corresponding link. On the next page you should see an option to accept the terms if you have not done so yet.

WARNING: once accepted DO NOT launch directly using 1-Click or the EC2 Console, but use a link to one of the cloud formation templates from this page instead.

The Software Terms tab should look something (except for you it should be active if not accepted yet):

Filter external roles via LDAP

Thu, 09 Nov 2017 05:38:08 +0000

Issue:

We need to restrict certain roles from database from getting synched into TIBCO JasperReports^® Server.

Resolution:

To restrict particular roles one can use below property from LDAP context file.


    
        JRS_.*
        EXT_.*

Above example restrict the roles you create in TIBCO JasperReports Server to roles that begin with JRS_ or EXT_ from your external database.

Dashboard Drill down

Thu, 09 Nov 2017 00:31:08 +0000

How to have a drill down on a Adhoc chart in dashboard that will open the table report in new tab with Parameters.

Click on create Dashboard and add a Adhoc chart .
It will open up the Adhoc view editor and then choose a data source for the chart.
Below screenshot shows sample from Emplyee report with City as filter
Save the Adhoc chart and return to Dashboard. This will add chart as dashlet
Prepare a table report taking parameter as City. In this example I have used Sample report Accounts.
Click on Map Parameters and map the parameters as shown below.
Right click on chart dashlet and click on properties and then to Hyperlink Tab.
Tick mark on "Enable Hyperlinks:" and choose 'Open new page' from Action option.
Click on browse and choose table report saved earlier.
After choosing the report add Parameter at the end like below:
Click Ok and now run the dashboard and click on the bar chart. This should open table report in new tab with specified parameter value from Dashboard.

Running report against JSON data file behavior

Fri, 18 Aug 2017 22:56:23 +0000

Issue Description:

How has the behavior changed when running a report that goes against a JSON file from 6.2 onwards?

Resolution:

- 6.2.1: This is working as expected

- 6.3.2: The following error is thrown

net.sf.jasperreports.engine.JRException: repo.input.stream.not.found

- 6.4.0: No error is generated, but instead 'null' is displayed in the browser

A defect has been filed to address this issue.

Custom bean datasource sample

Fri, 25 Aug 2017 22:41:11 +0000

This article is to introduce an example bean data source based on existing samples available in jasper. If you download the TIBCO JasperReports^® Library available on http://eDelivery.tibco.com, you will find several example reports that connect to a custom data source. You can import this project into jasperpStudio to see the JRXMLs, and in this case, we are interested in DataSourceReport1.jrxml.

This report connects to a custom data source, and we will connect it to a bean data source we will create once we publish this report to jasperServer.

First we will need to start by making a change to the sample found at samplescustomDataSourcesrcexamplecds

In the CustomSimplifiedDataSourceService.java file, add the below method

public static ReportDataSourceService createDataSourceInstance() {
        return new CustomSimplifiedDataSourceService();
    }

This method is used by jasperServer to create the data source service that then accesses the JRDataSource. Once this is added, build the code using the readme.txt instructions in the customDataSource folder. The class files generated under customDataSourceclassesexamplecds should be copied to the WEB-INFclassesexamplecds folder. You will also need to create a bean definition xml file that contains the bean name and class e.g.

This xml should be placed in the WEB-INF folder. Once you restart JasperServer, you should be able to create a new bean data source in the repository, with the bean name "myBean" and method as the method as createDataSourceInstance.
You can test this data source by publishing the DataSourceReport1.jrxml to jasperServer and specify the bean data source in the report unit.

beandatasource.zip

jMeter and REST data source performance testing

Thu, 14 Sep 2017 18:05:16 +0000

Issue Description:

Is it possible to do performance testing REST data sources using jMeter

Resolution:

Using jMeter, it is possible to do performance testing on REST data sources. The starting point is the reference link below to create the script:

https://www.3pillarglobal.com/insights/performance-testing-of-a-restful-api-using-jmeter

The key here is the ability to switch the REST calls in the script to any REST call you wish to

specify. Supposing you have a data source that fetches the list of resources in a jasper repository

database and you want to see how it performs. You would want to add the following items to the script:

right click thread group -> add -> config element -> http cookie manager
right click thread group -> add -> sampler -> http request (REST request for login)
right click thread group -> add -> sampler -> http request (REST request to fetch resources)
right click http request created in step 3 -> add -> config element -> http header manager (specify accept header)

Attached is an example jMeter script that contains the above.

rest_api_performance_test_jasper.jmx

Common errors when working with REST based datasources

Fri, 28 Apr 2017 23:47:58 +0000

Issue Description:

What are some common pitfalls when setting up REST based datasources?

Resolution:

[toc]

- net.sf.jasperreports.engine.JRException: java.lang.IllegalStateException: Target host is null

The above error is likely due to the data source being incorrectly configured in TIBCO JasperReports^® Server. Make sure the URI parameter is populated.

- Communication error java.net.UnknownHostException: someRemoteHost

The above error is likely due to some problem with JasperServer connecting to the remote host. Check if there is anything obstructing communication between JasperServer and the remote host.

Unable to see full result set from REST datasource

Tue, 23 May 2017 23:52:39 +0000

Issue Description:

When previewing a report connecting to REST using web service data adapter, only one row of data is returned. How can the rest of the data be retrieved?

Resolution:

Fetching data from a REST endpoint is similar to fetching data in XPath, in that depending on how you specify your root path that is where the search for the data will be conducted. For instance, supposing you are designing a report in jasperStudio that connects to a REST endpoint via data adapter. When you tell jasperStudio how to fetch the data in the dataser and query dialog window -> fields tab, you click 'get server response' button and a list of nodes is generated corresponding to what the endpoint returns. The leaf level is what you would use to specify as the root path (which can be done if you right click on the node and choose 'set as root path'), which should contain the data returned from REST.

Sample report connecting to JSON file

Thu, 28 Sep 2017 22:53:54 +0000

Issue Description:

Is there an example of a report that reads from a JSON file?

Resolution:

In 6.4, if you install the samples you will see in the repository under /public/Samples/Reports an example report - 41._Sample_Report_Using_Json_Data_Source. This report connects to a JSON data file located in the report unit. The key here is a parameter in the JRXML called net.sf.jasperreports.json.source that points to the JSON file:

In case you don't install the sample data, the report is attached here for your convenience. You can import this zip using either js-import utility or via the GUI in the jasperReports Server application.

samplejsonreport.zip

Where to obtain example reports utilizing custom data sources

Fri, 27 Oct 2017 23:52:50 +0000

Issue Description:

Are there example reports that utilize custom data sources, and if so, where are they?

Resolution:

These sample reports are available in the TIBCO JasperReports^® Library download, available on our eDelivery portal (http://eDelivery.tibco.com). These reports can be imported into TIBCO Jaspersoft^® Studio Pro as a project, with the report design files as well as the data adapters needed to connect to the data sources. The following steps can be used to obtain these reports:

Once logged into the eDelivery portal, go to 'All-Products A-Z' -> 'J' hyperlink under 'catalog' -> 'TIBCO JasperReports Server - Enterprise Edition' -> 'TIBCO JasperReports Library Software' and download the zip file
After you've unzipped it, launch TIBCO Jaspersoft^® Studio Pro
Go to File -> Import -> Existing Projects into Workspace -> Select root directory radio button -> browse to the folder where you unzipped the zip file -> finish button
After import, open the project explorer tab -> expand the JasperReports Samples folder -> datasource to locate the sample reports that utilize custom data sources

TIBCO JasperReports® Server and TIBCO Jaspersoft® OLAP License

Tue, 05 Jul 2011 11:58:46 +0000

Our aim at TIBCO Jaspersoft^® is to maintain the free nature of open source to end users, while establishing commercial relationships with vendors who are leveraging our code for their benefit. Jaspersoft offers many open source products which are under the guidance of either the GNU Affero General Public License (AGPLv3) or GNU Lesser General Public License (LGPLv2.1) license. Our goal is to provide guidance on the usage of each product while maintaining compliance with the appropriate license.

TIBCO JasperReports^® Server and TIBCO Jaspersoft^® OLAP Community Editions are governed by the GNU Affero GPL. It is very important to you and your organization to understand the terms of use of ^TIBCOJasperReports Server and TIBCO Jaspersoft OLAP in the context of the GNU Affero GPL.

If you plan on distributing (i.e., allowing the public to download or access over the internet) a software application or web site containing or using TIBCO JasperReports Server and TIBCO Jaspersoft OLAP, please note that your application/web site becomes subject to the GNU Affero GPL conditions. As a result, you are required to make the source code of your application/web site and any customized code freely and publically available to all people and organizations.

If you do not wish to make your source code freely available, TIBCO Jaspersoft offers a commercial subscription that allows you to maintain the proprietary nature of your application and custom code and not be obligated to disclose it to others. Commercial subscriptions also includes support, indemnification, training, documentation, extended features and more. We are open to partnering and have a successful world-wide partner program providing such benefits as mutual lead generation.

If you or your organization has a policy against using software governed by the LGPL or GNU Affero GPL, a commercial subscription may also be of interest to you.

See TIBCO Jaspersoft Product Overview for more details.

Discussion on visualize.js Error Handling

Tue, 31 Oct 2017 22:43:47 +0000

Question:

I'm having an issue catching an error from visualize so that I can deal with it and move on. I have tried the error handler code listed in several examples:

function handleError(err) 
{
    location.reload(); 
    alert(err.message); 

    // location.reload(); 
}

something similar in the report definition, and a page level handler:

window.onerror = function myErrorHandler(errorMsg, url, lineNumber) { 
    // deal with error 
    location.reload(); 
    return false; 
}

However, I can't seem to find anything to deal with this type of error:

xdm.remote.page.js:5 POST http://usswvulxp433.luxgroup.net:8080/jasperserver-pro/rest_v2/reportExecutions 404 (Not Found) 

visualize.js:50 15:05:43.504 [bi/report/Report] [visualize.js:50] [ERROR] - resource.not.found : Resource 

/public/Reports/Utilities/UT_0013_REACTIVE_WORK_ORDERSx not found.

This is forced where I'm looking for a non-existent report, but the same behavior is happening on connection issues or report run failures.

Answer:

We have Visualize.js API Samples that you may take a look and use it to run some tests against your JasperReports Server (JRS) instance to help debug your code. Those samples are available from the community site at:

http://community.jaspersoft.com/sites/default/files/wiki_attachments/main_2.html

You can also try out with this jsfiddle test script:

http://jsfiddle.net/tchen4jsfiddle/guu9e3cy/

It executes our sample AllAccounts report under /public/Samples/Reports/AllAccounts repository folder from a locally installed TIBCO JasperReports^® Server instance. If you change the report name to a non-existing one such as "AllAccounts1", you will see the alert message popup as shown below.

Here is another sample visualize.js to run our sample report from a local TIBCO JasperReports Server instance. This report has input control and you can test it from this jsfiddle script:

http://jsfiddle.net/tchen4jsfiddle/gbh7128b/1/

You can use it as the frame work to test your report by

Changing the server host reference