JReport allows you to embed reports and dashboards in multiple ways. One of the first things you need to decide is whether you want your analytics within your existing application or in a separate application/window.
To achieve different styles of embedding reports and dashboards into your application, JReport offers different options for security and user authentication: JReport Built-in SSO, 3rd-Party SSO – OAuth 2.0, or URL Direct. A brief explanation of each follows. Option 1: JReport Built-in SSO Pros Cons More secure. Full control over customization by the development team.
Visual Analysis is a separately licensed feature of JReport since Version 12. It allows a user to interactively browse the data using a Business View. The user can easily drag and drop groups and aggregations to create crosstabs showing values, bar charts, bench charts, line charts, pie charts and shapes. It does not access any detail items in the Business View.
The possible causes of this problem are: •The key is an evaluation key and it has expired. Solution: Purchase the permanent key from Jinfonet or extend the evaluation key. •The incorrect JREngine.jar has been included into your classpath. Solution: Make sure the correct JREngine.jar file extracted from the right JReport Engine installation is included in the classpath.
When you add your own User Data Source (UDS) into JReport, you may specify a parameter string to control the result set returned by the UDS. The parameter string can be an arbitrary format, because it is parsed by your code in the UDS.
You can call JReport Server APIs or set a default real path for the Public Reports folder before the server starts to accomplish it. 1. The following is a demo to demonstrate the usage of server API methods of deployment: /* * Copyright (c) 1998, Jinfonet Software, Inc. All rights reserved.
There are two types of task exporting a report to PDF directly. One is to publish a report to disk and the generated PDF result file will be saved in the file system; the other way is to export a report to PDF file which will be put in the temp folder of JReport Server.
JReport Server GUI does not support setting dbuser/password before showing parameter page. Once the parameter page appears, the default database user from jdbc connection will be used. To set the dbuser/password before the parameter page appears, you can use Server API to realize it.
They are corresponding to all kinds of publish types, such as Publish to email with reports: TASK_TO_MAIL (jet.server.schedule.jrtasks.SendJRMailTask) Publish to version: TASK_TO_VERSION (jet.server.schedule.jrtasks.UpdateRptTask) Publish to file: TASK_TO_FILE (jet.server.schedule.jrtasks.PublishToDiskTask) Publish to email without reports: TASK_SEND_NORMAL_EMAIL(jet.server.schedule.jrtasks.SendMa
There are three constant values used to define the locale information when you run the report via the Server API: APIConst.TAG_ENABLE_NLS, APIConst.TAG_REPORT_LANGUAGE and APIConst.TAG_REPORT_COUNTRY.