Jaspersoft Reviews

In our organization, the main purpose of Jaspersoft is for reporting purposes, and that's where we usually schedule and send the reports to the user for their business.

The main thing I appreciate about Jaspersoft is the ease of creating reports; it's very straightforward. When we need to create custom reports with a query, we can directly go to Jasper Studio, develop the report, write the query, bring that data, and develop the report in any way we prefer.

The second thing is regarding generating the report from ad-hoc views; it is very straightforward. We just need to drag and drop the columns we need for developing the report, and with that, we can schedule it and generate the report. If we want to develop a custom report using the query, we can develop it easily, and we can format it as we prefer. Generating reports with ad-hoc views is very easy; just drag and drop the columns and apply the necessary filters as defaults whenever the report is executed, which is a very good aspect of Jaspersoft.

I have worked on both generating a report using ad-hoc views and writing a custom query in Jasper Studio to design and publish it in Jaspersoft. Generating the report from ad-hoc views is the most suitable option for me; it's the best path to take.

The main dislike about Jaspersoft is the latency issue; sometimes when the report is generating, it takes more time than expected based on the report. For example, the project management tool I'm currently working on has the OBS, Organizational Breakdown Structure, and whenever Jaspersoft query fetches this OBS data, it takes more time than we usually expect. The user is somewhat hesitant about this issue; when the report takes so much time, the user gets annoyed. If Jaspersoft could fix the latency issues, it would be a good tool for anyone to work with.

Regarding lagging, whenever we generate reports on large data like OBS data—which is the hierarchy of the organization—Jaspersoft sometimes experiences delays. The latency issue is apparent when pulling this data. Additionally, when developing a report from ad-hoc views in Jaspersoft and specifically when scheduling it, the scheduling doesn't always work as expected. Both the latency and scheduling parts can be challenging in Jaspersoft.

I have four years of experience working with Jaspersoft.

The initial deployment of Jaspersoft is very easy; it is not difficult at all. If you go through the deployment steps we need to follow, it's straightforward with nothing much complicated.

From start to finish, it almost takes one hour. Jasper installation will not take more than fifteen minutes. When the build starts, it should not take more than twelve minutes. Before that, we need to set the Java path and home along with the environmental variables, which takes some time, including installing the installers from the appropriate site, unzipping it, and setting the environment variables. I believe it will take around thirty to fifty minutes to complete the installation. After that, we need to make some changes in the application.properties file, where we incorporate our server details, and this process won't take more than one hour.

One person can do the deployment; it's not a big task and is very easy. The only thing required is awareness of how to get it deployed. Once you understand the steps to deploy, one person can handle Jaspersoft installation alone in the system.

Pricing-wise, I haven't had much chance to see how much budget has been allocated for Jaspersoft, but it's not disclosed to anyone; it's completely managed by the client.

For our organization, we need to take care of Jaspersoft maintenance as well. Google Chrome, the version compatible with Jaspersoft, is vulnerable to threats, so we usually install Google Chrome into Jaspersoft every month. Also, sometimes the Apache Tomcat version is vulnerable, so during that time we feel the need to install an upgraded Apache Tomcat. Those are the two maintenance tasks we regularly perform. I would rate this product seven out of ten.