How to Identify Secure Cookies:

Browser Developer Tools: Open your browser's Developer Tools (F12), navigate to the Application (Chrome/Edge) or Storage (Firefox) tab, select Cookies, and check the "Secure" column for a checkmark.

Set-Cookie Header: Inspect network traffic to view the HTTP response header. A secure cookie will contain the ; Secure flag at the end of the Set-Cookie line.

JasperReports IO: 4 steps

Get Started
install, docs & samples

Develop
reports & visualization

Generate
the content you develop

Embed
into your apps

Getting started tutorials: Develop

Develop your first report in Jaspersoft Studio

Already familiar with Jaspersoft Studio? Skip to the next section

This tutorial provides a tour of Jaspersoft Studio – a powerful desktop designer used to develop reports and data visualizations – and demonstrates the process of creating your first report using the tool.

...Or create an interactive data visualization in Jaspersoft Studio

Learn more Jaspersoft Studio fundamentals in the following videos:

• Jaspersoft Studio Overview [Data sheet]
• Quickstart guide to Jaspersoft Studio

• How to create and use expressions in Jaspersoft Studio

• Using report templates in Jaspersoft Studio

• How to create and use styles in Jaspersoft Studio

• More guides and tutorials for Jaspersoft Studio

Learn the basics of how JasperReports IO and Jaspersoft Studio work together

This video introduces the fundamental concepts of setting up a Jaspersoft Studio project to leverage the JasperReports IO service.

Get step-by-step instructions on how to set up your first JasperReports IO project in JSS

This tutorial takes concepts from the video above and demonstrates how to actually implement them in Jaspersoft Studio, including creating and configuring a JasperReports project in Jaspersoft Studio.

Creating and organizing a repository in Jaspersoft Studio

This tutorial demonstrates how to create and organize a repository in Jaspersoft Studio for a JasperReports IO project. Repositories in Jaspersoft Studio are used to store all the files and assets used in your reports and visualizations. Examples of repository assets include fonts, images, style templates, resource bundles, and more.

Creating connections to data with data adapters in Jaspersoft Studio

This tutorial demonstrates how to create and configure data adapters in Jaspersoft Studio for a JasperReports IO project. Data adapters are links that connect your report or visualization to your data source(s). When a report or visualization is run, data adapters fetch data from your data source(s) to fill it.

Ready for Step 3?

Click here to learn how to generate the reports and visualizations you've developed.

This page explains the best practices to connect to your Amazon data using Jaspersoft for AWS.
For Amazon Elastic MapReduce (EMR) see the Amazon EMR connection page.
For non-Amazon data sources see the JDBC/JNDI connections section below.

Prerequisites

• JasperReports Server is running.

• You can login as superuser.

• Get help with these requirements here:  Launching Jaspersoft for AWS.

Connect to Amazon RDS or Redshift

JasperReports Server can automatically discover and connect to Amazon Relational Database Server (RDS) and Amazon Redshift using the auto-connect feature.

1. Menu: Create -> Data Source

2. Use EC2 instance credentials

The data source type should be set to "AWS Data Source". You should use "EC2 instance credentials". If EC2 instance credentials are not available, then see the Additional Connection Possibilities section below.

3. Enter Database connection info

JasperReports Server is able to detect your RDS and Redshift data sources. This is possible because the IAM Role associated with the EC2 instance is allowed to execute the actions "rds:Describe*" and "redshift:Describe*". It pre-populates the Database Name, Driver, and URL.

You must enter the database username and password. For security reasons Amazon does not store these credentials, so Jaspersoft cannot retrieve them.

The default database is automatically populated, but you may manually enter another if your RDS or Redshift instance has multiple databases.

4. Test

You should always test your connection. Testing does more than just testing.

• It creates a DB Security Group.

• It adds the internal IP of the EC2 instance to the security group to authorize ingress to RDS.

• This is possible because the IAM Role provides the instance with credentials like "rds:CreateDBSecurityGroup" and "redshift:AuthorizeClusterSecurityGroupIngress".

• If you want to control details of the security group name or specify the IP address manually because you have a complex VPC Topology, then navigate to the menu Manage -> Server Settings -> AWS Settings

5. Create a Domain

Jaspersoft's metadata layer is called "Data Domains". Choose the menu Create -> Domain.

Follow the domain creation wizard to build a domain.

6. Analyze your data

Choose the menu Create -> Ad Hoc View. Find your newly created domain and use the ad hoc environment to begin analyzing your data.

7. Next steps

Refer to the Online Learning Portal for lots of details on creating domains, performing ad hoc analysis, and creating reports.

Additional Connection Possibilities

1. AWS Credentials

Under normal circumstances it's best to launch Jaspersoft BI on an EC2 instance with an associated IAM Role. This role provides the instance with EC2 credentials.

If this option is not available for some reason, then it's possible to use AWS credentials instead. If you already have AWS Credentials, you may enter the Access Key and Secret Key.

If you do not have AWS Credentials, you may run the CloudFormation Template "jrs-create-user" to generate credentials.

2. JDBC / JNDI Connections

NOTE: When using JDBC for data source connections, the user will be responsible for managing the security groups to allow access from the Jaspersoft server to the data source. Please refer to the comparison of benefits of JDBC connections vs. AWS Data Sources, detailed below.

Amazon RDS or Redshift

When connecting to Amazon RDS or Redshift, it is best to use the data source type "AWS Data Source" to make configuration easier. If you prefer, JDBC connections may used to connect to Amazon RDS or Redshift, per below. To connect using JDBC, choose the data source type "JDBC Data Source". Enter all connection information and test. Alternatively, you can choose "JNDI Data Source" and refer to a data source defined in Apache Tomcat.

Benefits of defining your own JDBC connections:

• You have complete control

Benefits of using AWS Data Sources:

• Jaspersoft provides the driver and URL

• Data source automatically recovers if the IP address changes

• Data source automatically recovers if DB Security Groups are modified

Connect to Amazon Elastic MapReduce

The JasperReports Server auto-connect feature is not supported for Amazon Elastic MapReduce (EMR). Connections to EMR need to be configured manually.
Please see the Amazon EMR connection page for details.

Jaspersoft offers Hourly, Annual, and BYOL (Bring Your Own License) AMIs. The AMIs should be launched via instructions on this page using Cloud Formation Templates. Cloud Formation Templates ensure that Jaspersoft is configured properly for your selected AMI size, for example Memory configuration. Cloud Formation Templates are particularly important for VPC configuration.

Follow the steps listed below to get your instance running. You can also find more details about launching and managing Jaspersoft for AWS in our Guide.

Prerequisites

• Amazon AWS Account
  Don't have an AWS account? Sign up here.

• Amazon Key Pair for security
  Don't have an Amazon Key Pair defined? Define one here.

• Jaspersoft annual subscription (only needed for BYOL AMI)

Note about AWS EC2 instances

AWS EC2 instances are charged per hour or annually. Please make sure to follow instructions to turn off your EC2 instance server running Jaspersoft after use. If not, you will continue to be charged by the hour for EC2 usage.  Remember that when you stop your EC2 instance server, no one will have access to any reports or dashboards you have created until you restart the EC2 instance server.

When you stop an EC2 instance server, you will still be charged for EBS usage. If you prefer not to be charged for EBS, make sure to terminate your EC2 instance server.  Remember that if you do so, none of your work will be retrievable.

Start an EC2 instance with Jaspersoft inside VPC

Following these steps will give you a secure and easily maintainable instance of Jaspersoft.
Launching a server manually in the EC2 console will work fine, but you will miss out on the auto-connect for Amazon RDS and Redshift that the CloudFormation Templates provide.

Launching Jaspersoft for AWS

Additional Information

Using the EC2 Console

Launching a server manually in the EC2 console will work fine, and you'll have a useful business intelligence server, but you'll miss out on several features to make your life easier. It's recommended to always launch using the provided CloudFormation Templates.

Additional CloudFormation Templates

Jaspersoft's CloudFormation templates allow you to automatically create all of the resources needed for a Business Intelligence server. This includes defining the AMI to be used for a new EC2 instance, defining an IAM Role to set the EC2 credentials, and defining policies to allow this role to connect to AWS data sources. These policies include actions including "rds:CreateDBSecurityGroup", "redshift:AuthorizeClusterSecurityGroupIngress", and "ec2:DescribeSecurityGroups".

Instead of running the template "jrs-launch-instance" which creates all needed resources, it's possible to run templates to create just the IAM Role or IAM User. After running these templates, Jaspersoft BI for AWS can be launched from the EC2 Console. Be sure to associate the correct IAM Role with the EC2 instance so that the BI server will be authorized to connect to Amazon RDS and Amazon Redshift data.

"filter_in_target" is the filter internal reference name in the hyperlinked dashboard. To find out this filter's internal name, users can export the dashboard and inspect exported zip file content. Under dashboard repository structure, users should find a {dashboard_name}.xml file. In this file, look for <inputControl> seåction and filter_in_target name is identified in the <name> property tag.

As for the dashlet_param value in $P{} part of the URL, users can simply type in the field name in the dashlets properties parameters list.

NOTICE feature for Auto-complete parameters is based on previously accessed items in a dashboard in the designer. This feature does not provide items from all dashlets on a newly designed dashboard. Users will need to save the dashboard first, then edit hyperlink to get all available items in Auto-complete parameters list.

TTC-20181101

BUILD FAILED
C:\Jaspersoft630\JRS630\buildomatic\bin\validation.xml:495: The following error occurred while executing this line:
C:\Jaspersoft630\JRS630\buildomatic\bin\validation.xml:376: The following error occurred while executing this line:
C:\Jaspersoft630\JRS630\buildomatic\conf_source\db\sqlserver\db.xml:29: The following error occurred while executing this line:
C:\Jaspersoft630\JRS630\buildomatic\bin\app-server.xml:60: C:\Jaspersoft630\JRS630\buildomatic\bin\app-server.xml:60: Error invoking getDriver() method

Solution:

This is a classic Jaspersoft installation hurdle. The "Error invoking getDriver() method" accompanied by a failure in the db.xml script means that the buildomatic Ant scripts cannot find the JDBC driver required to communicate with your database.

Looking at your stack trace (\conf_source\db\sqlserver\db.xml), you are trying to connect to a Microsoft SQL Server database.

Because of licensing restrictions, TIBCO Jaspersoft does not always bundle proprietary JDBC drivers (like those for SQL Server or Oracle) in the standard installer or ZIP file. You have to add it manually before running the build scripts.

1. Download the SQL Server JDBC Driver

If you don't already have it, download the official Microsoft JDBC Driver for SQL Server. For Jaspersoft 6.3.0, you typically need a driver compatible with Java 7 or 8 (usually sqljdbc4.jar, sqljdbc41.jar, or sqljdbc42.jar).

2. Place the Driver in the Buildomatic Directory

The buildomatic tool looks for database-specific drivers in a very specific folder. Copy your downloaded .jar file and paste it into this exact directory based on your stack trace:

C:\Jaspersoft630\JRS630\buildomatic\conf_source\db\sqlserver\jdbc\

(Note: If the jdbc folder does not exist inside the sqlserver directory, create it).

3. Verify default_master.properties

Open your C:\Jaspersoft630\JRS630\buildomatic\default_master.properties file and double-check your database settings. Ensure the driver class is specified correctly for SQL Server:

In default_master.properties make sure that the native driver configuration matches the jar you have. Due to certain buildomatic restrictions, the jar filename needs also to accommodate the configuration as well. That means that you need to have a JAR in the following naming format: artifactID-version.jar. If you are missing the version then you won't be able to specify the maven.jdbc.versionMake sure the user has full read access to the JAR file.

Upgrade your server to version 10.

org.apache.http.client.HttpResponseException: illegal.parameter.value.error
The value "JRXML.content" for parameter "JRXML.content" is invalid.

If you are currently running MySQL 8.4 or planning to upgrade to it, we recommend updating your JasperReports Server installation to Hotfix 9.0.0 build hotfix_JRSPro9.0.0_cumulative_20260428_0806.zip or later to take advantage of this certified support.

When opening Jaspersoft Studio for the first time, you will be prompted to login with your Jaspersoft community email and password. 

Note: If you do not already have an account, you will need to create one at: https://community.jaspersoft.com/register/

This login process is only required once, upon first launching the software.  When logging in, if a message appears that "The provided credentials are invalid", please try the following steps:

Provided credentials are invalid.  Now what?

1. Double-check the email and password were entered correctly.
   You can confirm your account email and password by logging into the community site at: https://community.jaspersoft.com/login/
    

2. Disable your VPN or proxy server.
   If you have determined the account email and password entered are correct, the issue is often due to either a VPN or proxy server being unable to connect to the Jaspersoft login server.  In such a scenario, disabling these temporarily for the login process will usually resolve the issue, allowing Jaspersoft Studio to connect and confirm your login credentials.  Once logged in, you can re-enable your VPN/proxy server.  Again, you will only need to log in the first time starting up Jaspersoft Studio.
    

3. Use the Alternative Login Method.
   For those who cannot or do not wish to disable their VPN proxy server, we have provided users with an Alternative Login Method.  Clicking this provides you with the options to either:
       a) Scan the QR code and log in to the community site with your phone, or
       b) Click the "Copy URL button" and paste this into a browser window to log in.  
   Once you have successfully logged in via one of these methods, you will be given a code to insert into the box and validate your account.

   

4. Still unable to login?
   On rare instances, a user may experience difficulty due to their unique configuration. In this scenario, rather than an alert stating "Your login credentials are invalid", you might get an exception error with a readout of the error details below.  Please reach out to us via chat for assistance. 

We hope this post has helped get you connected.  Ready to Get started with Jaspersoft Studio?

Welcome to the Jaspersoft® Studio tutorials archive.
Here you will find a list of related tutorials, tips & tricks, and other useful resources.

Getting Started with Jaspersoft® Studio

The following tutorials explain the basics of how Jaspersoft Studio works. They are highly recommended, especially to new users.

What is Jaspersoft Studio?

Getting Started with Jaspersoft Studio

Designing a Report

Report Structure

Drag & Drop

Exporting Reports

Measure Units

Additional Tutorials

The following will help you explore further and get the most out of Jaspersoft Studio.

The Expression Editor: What it is and how it works

The Expression Editor: How to extend it and contribute your own functions

Using Report Variables

Using Report Parameters

Using Report Groups

Element Attributes and Styles

The Styles Template

The Inheritance Tab

Creating Charts and Subreports

Creating Charts and Datasets

Using Subreports

Using XML Datasources

Using the List component

Using Table and Crosstab components

Connect Jaspersoft Studio to JasperReports Server

How to Create and Use a JRDataSource Adapter

How to Create and Use a JRDataSourceProvider Adapter

Creating a Custom Report Template

How to Translate Jaspersoft Studio

How to Install a Jaspersoft Studio Translation

How to Publish a Jaspersoft Studio Translation

Compile with Older JasperReports Version from Jaspersoft Studio

Custom Font with the Font Extension

The Composite Elements

Import Projects and Settings from a Previous Version of Jaspersoft Studio

Report Books in Jaspersoft Studio

Jaspersoft Studio Layouts

See also:

• Introduction to Jaspersoft Studio
• Jaspersoft Studio Features
• Jaspersoft Studio Usage Reporting
• Designing a Report with Jaspersoft Studio
• Exporting reports with Jaspersoft Studio
• Jaspersoft Studio Tutorials Archive

If using a proxy server in the DMZ to communicate with JasperReports® Server running behind the firewall, user will also need to make sure to include proxy server name as part of the catalina connector setting in server.xml file in addition to the port and protocol settings:

scheme="https" proxyName="my.report.proxy.server.com" proxyPort="443" secure="true"

Otherwise, use could get cross-site scripting error and was not able to access JasperReports® Server Manage web UI for administrators.

NOTE: This is a specific use case and a generic solution that you can try to resolve the issue.

TTC-20160731-70119

Overview

This page provides a comprehensive guide to system requirements and installation procedures for JasperReports® Server.

When moving TIBCO Jaspersoft^® Studio from one machine to another, or when simply attempting to replicate a setup on a different machine, it might be helpful to have a quick way to copy/move your existing configuration of TIBCO JasperReports^® Server connections and/or the Data Adapters

Solution

The TIBCO JasperReports Server connection definitions are stored in the workspace, particularily in

\.metadata\.plugins\com.jaspersoft.studio\serverprofiles

Just copy the contents of this folder to the new instanace of TIBCO Jaspersoft Studio and restart it.

Similarly, the data adapter definitions are stored in .metadata.pluginscom.jaspersoft.studiodataAdapters folder and can be migrated too

JasperReports Server extends the core functionality of the JasperReports Library into a full-scale reporting platform. It adds essential management tools like security protocols, resource repositories, and report scheduling. Furthermore, its comprehensive public interfaces make it highly customizable and easy to integrate into your existing software ecosystem.

For details, see the JasperReports Server User Guide > Getting Started Page

At the center of the Jaspersoft BI Suite is JasperReports Server, which enables you to:

• Easily create new reports using an intuitive web-based drag and drop Ad Hoc reporting interface. (Enterprise Edition capability)
• Efficiently and securely manage many reports.
• Interact with reports, including entering parameters and drilling on data.
• Arrange reports and web content to create appealing, data-rich dashboards that quickly convey business trends. (Enterprise Edition capability)
• Host separate organizations securely and transparently through multi-tenancy. (Enterprise Edition capability)

For details, see What is JasperReports Server?

Requirements

See the Supported Platform Datasheet for the up-to-date list of supported software, including databases, JVMs, and web browsers.

Additionally, to ensure the application functions correctly, we recommend adjusting your browser security settings to permit the following:

• Cookies
• Pop-ups (new windows/tabs)
• Javascript
• AJAX
• DHTML

Configuration

Here is a Jaspersoft Product Configuration Reference. Also, for additional information, see the JasperReports Server Ultimate Guide.

Using JasperReports Server

Connecting to your data

Creating a datasource

• Connecting JasperReport Server to your Database for reporting (creating a datasource).
• Comprehensive List of Articles on Data Sources

Creating a domain

• Data Management Using Domains
• Comprehensive List of Articles on Domains 

Domain security

• Defining a Domain Security File

Creating your first Ad Hoc View

For information about Ad Hoc Editor, see the  Working with the Adhoc Editor section in the JasperReports Server User Guide.

Working with dashboards

For information about dashboards, see the Working with Dashboards section in the  JasperReports Server User Guide.

Reports and report viewer

For information about reports and report viewer, see the Running Reports and the Report Viewer section in the  JasperReports Server User Guide.

How can I get help?

If you require assistance, you can find a complete list of Jaspersoft's formal support services here.

See also:

For additional information, see the following resources:

• JasperReports Server product page on the Jaspersoft website
• JasperReports Server overview page on the Jaspersoft community site
• Getting Started with REST Web Service API
• Other JasperReports Server Getting Started Articles

Could you please provide us the detailed Installation steps of Jaspersoft Studio v6.2.1 Software on Linux x86_64?

Answer:  

1. Open the archive "TIBCOJaspersoftStudioPro-6.2.1.final-linux-x86_64.tgz" file to get "TIBCOJaspersoftStudioPro-6.2.1.final-linux-x86_64.tar" file out.

2. Untar this file and extract all its content into a folder on Linux machine, for example

   /opt/tibco
   

3. After extracting all the Studio components, check and make sure you have execution permission to deployment folder

4. You can start the Studio from the installed location, for example:

   $ /opt/tibco/TIBCOJaspersoftStudioPro-6.2.1.final/Jaspersoft Studio Professional
   

Note: This wiki article is for old JSS 6.2.1 version installation.

You're performing an upgrade from version 7.1.0 to 8.0.0 using upgrade-samedb Same Database upgrade script and your historic upgrade path has been the following:

7.1.0 -> 7.2.0 -> 7.5.0 -> 7.8.0 -> 7.9.0 -> 8.0.0

On the last step you're getting a similar error:

[advanced-sql] Executing resource: /opt/jasperreportsserver/buildomatic/install_resources/sql/mysql/upgrade-mysql-7.9.0-8.0.0-pro.sql
[advanced-sql] Failed to execute:   ALTER TABLE JIAccessEvent DROP FOREIGN KEY FK7caj87u72rymu6805gtek03y8
[advanced-sql] java.sql.SQLSyntaxErrorException: (conn=17) Can't DROP 'FK7caj87u72rymu6805gtek03y8'; check that column/key exists
[advanced-sql] Failed to execute:   ALTER TABLE JIAccessEvent DROP FOREIGN KEY FK8lqavxfshc29dnw97io0t6wbf
[advanced-sql] java.sql.SQLSyntaxErrorException: (conn=17) Can't DROP 'FK8lqavxfshc29dnw97io0t6wbf'; check that column/key exists

What to do in this situation?

Solution:

There is a hotfix available for this issue. Please download either the latest 8.0.2 hotfix and apply it to buildomatic by following the readme.txt instructions under js-install.zip or download the 8.0.2 WAR artifact which has this fixed baseline.


Note : This is a specific use case and generic solution that you can try to resolve the issue.

• Athena
• Cassandra
• Impala
• Neo4j
• Spark

Important Note: No default DataSource properties or configurations are changed, Jaspersoft is removing the JAR files from the WAR file.

How to Get the Simba Drivers

Refer to the following URLs to get these Simba Drivers:

How to Install a Driver

To Install a Driver:

1) Create a custom components folder at the buildomatic level.
    In components folder, add the following folders: 
    a) A META-INF folder which contains components.properties file. In the property file, create these two properties:
        connectors.XXX.enabled = true|false
        connectors.XXX.artifacts = XXX.jar
    b) Create a folder named XXX-connector in which to place the JAR file.
    
    This folder structure can be achieved by executing target:
        <jrs bin>buildomatic> js-ant gen-components-metainf -DcomponentId=XXX(connector name) -DcomponentArtifacts=YYY(Driver along with version).jar 
        
2) After creating the folder structure, execute target js-ant install-components.

For example: <jrs bin>buildomatic> js-ant install-components

This will repackage the jasperserver-pro.WAR and deploy the JAR in the Tomcat WEB-INF/lib folder.

3) To update the JAR version, change the JAR version in components->META-INF->components.properties file at connectors.XXX.artifacts=YYY.jar

then place the specified version JAR in the components>XXX-connector folder and run script js-ant install-components. 
For example: <jrs bin>buildomatic> js-ant install-components

4) To remove a JAR, create or update components>META-INF>components.properties file as connectors.XXX.enabled = false OR you can add connectors.XXX.enabled = false in default_master.properties file and run js-ant install-components. 

For example: <jrs bin>buildomatic> js-ant install-components

Note: Some of the driver download URLs may not be working. Please try downloading the driver from an alternative source or location.

How to Enable or Disable a Driver

To disable a driver, keep the entry connectors.XXX(connector).enabled = false in components>META-INF>components.properties file
To enable a driver, keep the entry connectors.XXX(connector).enabled = true in components>META-INF>components.properties file

After repackaging and Tomcat deployment is done, restart Tomcat.
    
To only repackage jasperserver-pro.WAR, run script:  <jrs bin>buildomatic> js-ant package-components
To only deploy in Tomcat webapp/WEB-INF/lib, run script:  <jrs bin>buildomatic> js-ant deploy-components
To repackage jasperserver-pro.WAR and deploy in Tomcat webapp/WEB-INF/lib, run script: <jrs bin>buildomatic> js-ant install-components

How to Download a Driver using the URL

Enable a driver using URL by following these steps:
If there is any custom component, include in lib WEB-INFlib without having JAR in the system, there is an option to keep the corresponding URL through which you can download the JAR property:
connectors.${project.artifactId}.url={URL from where we can download URL}

For example, for simba-athena, this folder structure can be achieved by using ant command:
    <jrs>/jasperserverbuildomatic> js-ant gen-components-metainf -DcomponentId=simba-athena -DcomponentArtifacts=AthenaJDBC42-2.0.35.1000.jar -DcomponentUrl=https://s3.amazonaws.com/athena-downloads/drivers/JDBC/SimbaAthenaJDBC-2.0.35.1000/AthenaJDBC42-2.0.35.1000.jar

Case 1:
    connectors.simba-athena.enabled=true
    connectors.simba-athena.artifacts=AthenaJDBC42-2.0.35.1000.jar
    connectors.simba-athena.url=https://s3.amazonaws.com/athena-downloads/drivers/JDBC/SimbaAthenaJDBC-2.0.35.1000/AthenaJDBC42-2.0.35.1000.jar
    
    Driver will get downloaded into /tmp/componentsXXX/components/simba-athena-connector 

Case 2:
    connectors.simba-athena.enabled=
    connectors.simba-athena.artifacts=AthenaJDBC42-2.0.35.1000.jar
    connectors.simba-athena.url=https://s3.amazonaws.com/athena-downloads/drivers/JDBC/SimbaAthenaJDBC-2.0.35.1000/AthenaJDBC42-2.0.35.1000.jar
    The simba-athena.enabled property will be considered to true because we are providing the URL property and the driver will get downloaded.

Case 3:
    connectors.simba-athena.enabled=true
    connectors.simba-athena.artifacts=AthenaJDBC42-2.jar
    connectors.simba-athena.url=https://s3.amazonaws.com/athena-downloads/drivers/JDBC/SimbaAthenaJDBC-2.0.35.1000/AthenaJDBC42-2.0.35.1000.jar
    
    If the driver name format differs from the download path, you can mention the required format in connectors.simba-athena.artifacts so that the driver will get renamed to required format .

Case 4:
    connectors.simba-athena.enabled=
    connectors.simba-athena.artifacts=
    connectors.simba-athena.url=https://s3.amazonaws.com/athena-downloads/drivers/JDBC/SimbaAthenaJDBC-2.0.35.1000/AthenaJDBC42-2.0.35.1000.jar
    
    In this case, it will treat enabled flag to true and artifacts will be assigned with AthenaJDBC42-2.0.35.1000.jar from URL 

 

   Note: The location for accessing the driver is provided for convenience only, and this does not constitute an endorsement or representation that this drivers is fit for any  particular purpose. You are solely responsible for the deployment and use of the driver in connection with the JasperReports Server product.

   2. On the New Data Source page, from the Type drop-down, select JDBC.
   3. From the JDBC Driver drop-down, select Other.

    4. In the JDBC Driver field enter, org.elasticsearch.xpack.sql.jdbc.EsDriver.
    5. Click Add Driver.
    6. In the Select Driver dialog, click Choose File to browse to the required file.

  7. Click Upload.
  8. In the URL, enter jdbc:es://dbhost:9200/?ssl=true&ssl.keystore.location=/opt/home/jasperserver/truststore_jdbc.jks&ssl.keystore.pass=elasticsearch&ssl.truststore.location=/opt/home/jasperserver/truststore_jdbc.jks&ssl.truststore.pass=elasticsearch.
  9. Provide relevant information in the User Name, Password and Time Zone fields.
       Note:
      JDBC Driver and URL are mandatory fields.
  10. Click Test Connection to check if all inputs are correct.
  11. Click Save to save the data source.

Connect to Elasticsearch with security enabled JDBC URL

To connect to ElasticSearch with security enabled JDBC URL, ssl must be set to true (ssl=true) and the related certificates, and the key must be provided. For details, see SQL JDBC.  

To get and repackage the files, search for xpack.security.http.ssl: section in the elasticsearch.yml.

To get the truststore_jdbc.jks file on Linux:

1. On terminal, run the `openssl pkcs12 -export -out bundle_jdbc.p12 -in elastic.crt -inkey elastic.key` command.
2. Select a secure password, when prompted.
3. On terminal, run the `keytool -keystore truststore_jdbc.jks -import -file CA.crt -alias cacert` command.
4. Select a secure password, when prompted.
5. Type 'yes'.
6. On terminal, run the `keytool -destkeystore truststore_jdbc.jks -importkeystore -srckeystore bundle_jdbc.p12 -srcstoretype PKCS12` command.
7. Enter the password to get the truststore_jdbc.jks file. 
8. Copy the truststore_jdbc.jks file to /opt/home/jasperserver on JasperReports Server

Fullfillment & Access

Product Update

Cloud

Community

Fulfillment & Access

• Edelivery: Main customer contacts are sent a fulfillment email, with information on how to access the TIBCO Edelivery Site If you have not received access to the edelivery site but need to do so, please reach out to your TIBCO Sales rep, or ask the person at your company who purchased the product(s) -- as they may have been the one to whom this information was sent. Find and download your Jaspersoft product license(s) in the Customer Portal.
• Supported Platforms: The Platform Support Guide provides information that will help you prep to set up your own Jaspersoft environment in your organization, on your own servers.
• Documentation: Jaspersoft's documentation is a great place to learn and understand your analytics products with detailed documentation. After you have obtained your license and reviewed our Installation Guide, be sure to review our knowledge base article on Applying Your Jaspersoft License

Product Update

You can keep up to date with different information about TIBCO products by subscribing to updates for the product in question through your support.tibco.com portal. Hover over Your Name, then click on Product Interest and Knowledgebase subscriptions. Check the boxes to each product you would like to receive notifications for. 

Our Product Release Strategy will help you plan for Jaspersoft product software releases and technical support polices for software versions.

Cloud: Launching Jaspersoft for AWS

Our AWS Quick Start page has detailed information on working with AWS. It points to our AWS Github, Deployment Guide and provides background on the architectural set up of the implementation.

Community Access & Layout

Our Jaspersoft Community helps you ask and answer product questions with responses from other knowledgeable community members and even experts at Jaspersoft. It's fast and easy to signup for Community accounts.

• Forum  — Read, Ask and Answer
• Knowledgebase — Read, Learn & Contribute
• Extensions — Extend & Build

← Back toJaspersoft Customer Orientation

Install and Configure

1. Hardware Requirements: Covers the minimums required to run Jaspersoft.

2. 64 Bit Bundled Installer: Our bundled installer accounts for one of the two ways you can install Jaspersoft.

3. War File Distribution: Our WAR File Distribution allows for more control over your Jaspersoft installation configuration and supports the use of databases beyond PostgreSQL and application servers beyond Apache Tomcat.

4. Docker Installation: If you are looking to set up Jaspersoft within Docker containers we have a github that can help you.

5. Jaspersoft for AWS: Our Quick Start guide should help you and your team get Jaspersoft up and running in AWS.

Documentation

In addition to the Admin, JasperReports^® Server User Guide and Ultimate Guide detailed on our Jaspersoft^® Customer Orientation page admins should review the following documentation.

1. Our Security Guide to ensure their Application, Users, and Domains are properly protected.

2. The Supported Platforms Sheet will detail what has been test and'or certified to work with Jaspersoft.

3. Upgrades will take place at some point, review our Upgrade Guide prior to embarking on this endeavor.

4. When utilizing Ad-Hoc Reporting a firm understanding of working with Domains will go a long way to ensuring you are maximizing your use of Jaspersoft.  

Return to Jaspersoft Customer Orientation page.

This is a guide to connecting TIBCO Jaspersoft^® Studio to Apache Drill via JDBC connector. It was tested with TIBCO Jaspersoft Studio 6.2.0 on Windows 7 using Apache Drill 1.4

http://community.jaspersoft.com/project/jaspersoft-studio/releases

Download Drill JDBC driver

The JAR file should be included with any Drill distribution, the path below is where the MapR Drill JDBC driver is located

/opt/mapr/drill/drill-1.4.0/jars/jdbc-driver/drill-jdbc-all-1.4.0.jar

Copy this jar file to your environment, it was placed in the Download folder for us.

Run Jaspersoft Studio

Create a new Data Adapter

Using the Database JDBC Connection

Add the jar file on the Driver Classpath page

Put the relevant details in the Database Location page.

Note:

• ‘org.apache.drill.jdbc.Driver’ is not available on the drop down box so it should be typed
• drill.url: jdbc:drill:zk=<zkhost:port>,<zkhost:port>,<zkhost:port>/drill/<cluster-id>
• the <cluster-id> can be found in the $DRILL_HOME/conf/drill-override.conf file
• drill.user: <username>
• drill.password: <password>

Press test connection

Create a view in Apache drill on a data source

For this example, a simple csv file was used and placed in the root of the MapR file system

# ls -lrt
-rw-r--r--  1 mapr     mapr   1034773 Mar 16 10:54 customers.all.csv

# head customers.all.csv
16841,"Lisa Wells","tx","FEMALE","26-35",40,"basic"
19905,"Neely Nova","va","MALE","15-20",45,"basic"
17718,"William Bush","il","FEMALE","51-100",29,"basic"
21975,"Gerald Staples","ma","MALE","26-35",28,"basic"
20468,"William Conners","de","MALE","36-50",32,"basic"
16670,"John Rubio","oh","MALE","15-20",42,"basic"
18600,"Jay Holland","fl","FEMALE","21-25",43,"basic"
23438,"James Hogsett","ne","FEMALE","15-20",30,"basic"
20669,"Florence Black","pa","FEMALE","26-35",24,"basic"
22880,"Judith Stuart","ga","MALE","21-25",25,"basic"

Create a view using the following command

# create or replace view `dfs`.`tmp`.`customer` as
SELECT columns[0] as `customer_id`,
       columns[1] as `name`,
       columns[2] as `state`,
       columns[3] as `gender`,
       columns[4] as `age_group`,
       columns[5] as `age`,
       columns[6] as `account_type`
 FROM `dfs`.`default`.`customers.all.csv`

Test the View

SELECT * FROM `dfs`.`tmp`.`customer`

Now Back to TIBCO Jaspersoft® Studio

Create a new report

Select Data and query editor dialogue

Enter your query and press Read Fields and then OK.

The fields are now populated and ready for you to use

Details regarding requirements and installation to get started with Jaspersoft® Studio.

Hardware requirements

Jaspersoft Studio needs a 64-bit processor and at least 500MB of hard-disk space. The RAM required depends on how complex the reports are. We recommend dedicating 2GB of RAM to Jaspersoft Studio, and because your system likely runs other applications that also need RAM, a total of 4GB is suggested.

Software requirements and installation

Like any Java-based application, Jaspersoft Studio needs the Java Runtime Environment (JRE) to run. However, to compile report scriptlets, the full Java Development Kit (JDK) is required. For details on supported Java versions, see the Platform Support Guide.

Jaspersoft Studio supports most common operating systems, including:

• Windows 10 or newer (64-bit)
• Linux 64-bit, with support for Debian and CentOS
• macOS 14.x or 15.x (64-bit)

Jaspersoft Studio can be downloaded from here. There are two versions available for download:

• The free community edition
• The paid commercial edition

The commercial edition come with a 30-day free trial. Once you select an option (community or commercial), a list of available download choices are shown for the different operating systems, and you can choose the one that suits your needs.

For the commercial edition:

• js-jss_x.x.x_linux_x86_64.tgz
• js-jss_x.x.x_macosx_x86_64.dmg
• js-jss_x.x.x_sources.zip
• js-jss_x.x.x_windows_x86_64.exe
• js-jss_x.x.x_windows_x86_64.zip

x.x.x represents the version number of Jaspersoft Studio.

For the community edition, the Eclipse RCP application files available are:

• js-studiocomm_x.x.x_linux_x86_64.tgz
• js-studiocomm_x.x.x_macosx_x86_64.dmg
• js-studiocomm_x.x.x_windows_x86_64.exe
• js-studiocomm_x.x.x_windows_x86_64.zip

Download and install the correct Java and Jaspersoft Studio versions for your operating system.

Launching Jaspersoft Studio

In most cases, installation is as simple as downloading the file and double-clicking it to launch the setup wizard. Then, follow the on-screen instructions from there. 

Jaspersoft Studio requires you to login with your Jaspersoft community user account credentials the first time you open the file. This is a one-time process, and you will not need to login again.  If you do not have a community account, you can sign up here.

On rare occasion, a user may experience an issue logging in.  If you have any trouble, please see this guide to logging in via the alternative method.

Now, ready to get started?

JasperReports Web Studio is a visual, web-based designer for creating and editing report templates. While Jaspersoft Studio remains the most comprehensive desktop tool, the Web Studio offers a convenient alternative for building dynamic content and data visualizations for the JasperReports Library and other Jaspersoft products.

You can deploy JasperReports Web Studio in a couple of ways. It can be used as a standalone web application or integrated into an existing JasperReports Server to add report-editing capabilities.

Getting started

The standalone version of JasperReports Web Studio is available as a ZIP file. This package includes everything required to run the application on Linux, Windows, or macOS.

To get started, simply download the ZIP file and extract its contents to a folder. From there, open a terminal or command prompt, navigate to that folder, and run either the start.sh (for Linux/macOS) or start.bat (for Windows) script.

By default, the application runs on http://localhost:8088, but you can change the port and other settings in the start script, if required.

When you first open the web application, a login screen appears. From here, you can connect to different repositories, such as JasperReports Server instances, Google Drive accounts, GitHub projects, or Jackrabbit repository, to access your reporting resources.

By default, you can only connect to either an existing JasperReports Server instance or to Jackrabbit repository. The options to log in with Google Drive and GitHub are disabled because they require extra configuration in the start script for their OAuth2 authentication.

Configuration

JasperReports Web Studio can be configured in different ways through properties. These properties may be:

• passed as environment variables
• added in the jrws.properties file
• added in the java system properties.

JasperReports supports a large number of built-in charts created using the popular open source library JFreeChart. Chart types include Pie, Bar, Stacked Bar, Line, Area, Bubble, Gantt, Thermometer and Meter. In this tutorial we will learn how to add a multi-series chart to a report. This tutorial uses the same example explained in Designing a Report with Jaspersoft Studio. We suggest you complete that tutorial before beginning this one.

The goal is to have the same report described in the tutorial Designing a Report with Jaspersoft Studio, with a bar chart showing the number of shipments for every city.

Placing the Graph

The report created in the earlier tutorial is composed of multiple bands, each with different print times. For example, the detail band is printed for every record read from the data source, the page header and footer are printed at the start and at the end of every page and so on. For this tutorial we will use the Summary band that is printed at the end of the report. Note that in this report the Summary band is not visible from the designer because its height is set to 0. It is, however, visible from the outline view, so select it from there and change its height in the property tab to 400 pixels, as shown in the following image:

The Subreport

A subreport is an element that includes a report inside another report. The idea in this tutorial is to have a subreport containing just the graph, and a main report that includes the subreport in the summary section.

For the purposes of this tutorial, we want to use two reports because in the main report we need a list of records without any aggregation so we had used the query "select * from orders" and from all the fields read we had selected the order id, the shipment name, shipment address, shipment city, shipment region. But for the graph in the subreport we don't need a list of records, just a group of them. In other words, we need the records grouped by the shipment city. For this reason we need two queries, one that returns all the records  (for the main report) and one for the group (for the subreport). Because a report can have only one main query, we need to use another report for the additional query. Note that there are other ways to use more than a query on the report, but for now we choose this one to introduce the concept of subreport.

In the first step of the wizard we have three choices:

1. Create a new report as subreport.
2. Use an existing report as subreport.
3. Put an empty report as subreport, as a placeholder.

Since we are doing this from scratch select the first option, Create a new report, and click Next.

Now we will seen a wizard almost identical to the one seen when we created the first report. This time, since we need only a blank paper with a graph select BlankA4 and hit Next.

Now we need to choose the location and the filename of the new report, put it in the standard location MyReports and as name use "GraphReport" and click Next.

Now we have to select the data adapter. Since we need to use the same data source for both reports, select the same data adapter as used in the main report. We must also provide the query to retrive the fields, so enter the query that returns the records grouped by the shipment city. Every record read from the database with this query contains two fields: the number of elements for a city and the name of the city. After that we can click Next.

At this point we can see the fields included by the second query. Click the add all button or double-click on each field until they are in the right list. After that click Next. The following step in the wizard is to create groups into the report, but this is unnecessary for our goal. Click Next again.

Now we have to select the connection to the database. Since we are using the same database as in the main report we can select the first option and click Next. In the following step in the wizard, we could create some parameters that can be passed from the main report to the subreport, but we don't need them so click the button Finish.

Now we have a new report with all his bands, but we need only one of them. In fact, we need only a band for the graph, and the band must be printed only once, so the detail band is excluded. We can choose the Title or Summary band. If we decide to choose Title, we need to remove the other bands because otherwise they will take up space unnecessarily. So for each band except Title right-click on its element in the outline view and choose Delete. The name of a deleted band appears in light gray text in the outline view, so at the end of the process the only band with a black name must be Title.

The Chart

Now we can place the chart. Drag its element from the palette into the Title band to open the wizard, select the bar chart and click Next.

In the next step you can configure the series of the chart, as shown in the following image:

Then click Finish to create the chart. Since we need space, resize the Title band with an height of 350 pixels. Right-click on the chart, select Size to Container and then Fill Both. The chart will take all the space in the band. Now we can switch to the Preview tab and if it is all correct, save this subreport and switch to the main report as shown in the following image:

Now the only thing to do is to resize the subreport element to fill the Summary band, and compile the report. On the last page you will get a result like this:

More on Complex Reporting

Subreports in Jaspersoft Studio