Scott Andersen

Jaspersoft offers many ways to integrate reporting with applications. Jaspersoft Reports can be integrated using java code, iFrames, REST, and javascript. Choosing from the various options depends on the functionality desired, the amount of work you are willing to expend to get the desired results, and how much control over the end result you want. Java Code Using JasperReports Library you have access to java code that will allow you to generate reports and connect to data sources. All the data connectivity, report generation, and distribution is controlled directly in the java code. Although this gives you microscopic control of your end result, it is also the most labor intensive, requiring months (if not years) to develop the reporting features you need in your application. If you have time and the java developer resources available, this can be an option. User Interface / iFrames JasperReports Server is a complete reporting portal providing a white label capable user interface to give your users access to an enterprise grade reporting solution. The server can be integrated with your application’s security, so you can give access to the server as a separate reporting portal. Portions of this UI can be embedded inside your application using IFrames. This allows you to take advantage of the advanced interactive report viewer, ad hoc report designer, dashboard designer, and other features provided by JasperReports Server. Thus you take advantage of decades of development provided by Jaspersoft. A possible drawback is that using IFrames you are limited in what control you have over the interface. Web Services JasperReports Server has a comprehensive suite of web services available via REST. By implementing these REST calls in your application, you can let JasperReports Server handle the heavy lifting when it comes to connecting to data and generating reports. You also have access to other aspects of the server, such as dashboards, scheduling, and administrative functions. Thos administrative services allow you to simplify things when it comes to operational tasks around the environment. Javascript If you want to take full advantage of the power of JasperReports Server, while maintaining control over the end user experience, Jaspersoft’s “Visualize.js” javascript API gives you that control in an easy to implement solution. You are not limited to embedding reports and dashboards. Visualize.js gives you the capability to control interactions with those reports and dashboards, both in passing data into the reports to control their results, to capturing actions and events associated with the reports and managing how the application responds. And this can be accomplished within a day or so, if not in hours! Comparison of your options JasperReports Library Embed reports using java code Design reports using Jaspersoft Studio Needs a java developer to embed. All delivery code is done by you, using the JasperReports Library classes. You have complete control of what the application does with regards to report delivery.. For more information check out the javadoc: https://jasperreports.sourceforge.net/api/index.html and samples : https://jasperreports.sourceforge.net/sample.reference.html JasperReports Server UI / iFrame embedding JasperReports Server is a full feature reporting portal Reports created using Jaspersoft Studio, the Ad Hoc Designer, and the Dashboard Designer. White labeled to reflect your styles. Can be delivered as a stand alone reporting portal, or embedded using iFrames. Information on JasperReports Server: https://community.jaspersoft.com/documentation/jasperreports-server/tibco-jasperreports-server-ultimate-guide/vv900/js-ultimate-guide-_-api-_-repository-http-api/ Web services Embed using REST API calls. The web services can be provided either by JasperReports Server (JRS) or JasperReports IO (JR-IO). JR IO reports are designed using Jaspersoft Studio, while JRS adds access to visualizations created by the Ad Hoc Designer, and the Dashboard Designer.. Access via REST calls can be accomplished from a wide variety of platforms; not limited to java You control the presentation layer. REST API documentation for JRS: https://community.jaspersoft.com/documentation/jasperreports-server/tibco-jasperreports-server-rest-api-reference/vv900/jasperreports-server-rest-api-reference-_-overview/ And for JR-IO https://demo.jaspersoft.com/jrio-docs/#rest-api-reference Visualize.js Embed using javascript Visualizations can be provided either by JasperReports Server or JasperReports IO (JR_IO). JR IO reports are designed using Jaspersoft Studio, while JRS adds access to visualizations created by the Ad Hoc Designer, and the Dashboard Designer.. You have detailed control over the interaction between the visualizations and your application using javascript Information on visualize.js for JRS: https://tibcosoftware.github.io/js-visualize/#introduction And for JR-IO: https://demo.jaspersoft.com/jrio-docs/#live-javascript-client-samples The great news is you can combine usage of all these options as needed, providing a robust enterprise reporting solution.

The ad hoc report designer is a great tool to create a report. However, selected filter values are not displayed on the resulting report. This can be resolved by either putting the ad hoc view on a dashboard (which gives you access to the selected parameters); however, this approach limits the formatting of those values. A better approach is to use an ad hoc template to display the input values in a formatted way. Here are the steps to reference the filter values in a template. Create an ad hoc report that has a filter on it. Create a template that displays the selected values from the input control. Instructions on creating an ad hoc template can be found in the Jaspersoft Studio User Guide, section 12.4. https://community.jaspersoft.com/documentation/jaspersoft-studio-user-guide-820/v820/publishing-report-template To reference the parameters from the ad hoc view you need to access the “REPORT_PARAMETERS_MAP” parameter. This java.util.Map object contains all the parameters selected within the ad hoc view. The key within the parameter map will be the identifier in the domain of the field being filtered, appended with a sequential value. The first time a field is used as a filter it will be “_1”, the second “_2” and so forth. To get the identifier, you can either look at the domain: or drop the ad hoc view onto a dashboard and mouse over the filter to get the field identifier. In the image below, it is “product_family_1”. In the “Text” field expression on the template, reference the “REPORT_PARAMETERS_MAP” value as follows: CONCATENATE($P{REPORT_PARAMETERS_MAP}.get( "product_family_1" ).toString())This template can be used when creating a report from the ad hoc view. The example template is attached below.