My main use case for Jaspersoft is that we inherited a legacy application that used Jaspersoft. A quick specific example of how I used Jaspersoft within that legacy application is that we would have batch jobs that generated reports for accessories.
Jaspersoft Reporting and Analytics for AWS
Cloud Software GroupExternal reviews
External reviews are not included in the AWS star rating for the product.
Inherited reporting has exposed poor integration and limited flexibility for modern workloads
What is our primary use case?
How has it helped my organization?
Jaspersoft can be improved by having better documentation, better support, upgrading the UI of the tool, and integrating other programming languages, not just Java.
What is most valuable?
In my experience, the best features Jaspersoft offers were not the best. We ended up migrating this legacy application to a completely new tech stack in Python.
What needs improvement?
The challenges or issues I faced with Jaspersoft that led to the migration include the fact that the tech stack is deprecated and it was very troublesome to upgrade the Java version. Additionally, there was no integration with Python, so we ended up rewriting the whole thing in Python. We still use the JRXMLs for the reports, but we are not using Jaspersoft system for Jaspersoft Studio or anything else.
The thing that was particularly frustrating with Jaspersoft was that the code being generated was not exactly following coding standards. A lot of the exceptions were very generic, such as exception one, two, three. It does not have great integration with other systems, which was one of the main reasons that led to the migration. We also struggled with learning how the system worked, and there is not much intuitive documentation or support for that matter.
The needed improvements for Jaspersoft include better big data support and integrations with something such as Hadoop or Apache Spark.
For how long have I used the solution?
I have been using Jaspersoft for roughly about two years.
What do I think about the stability of the solution?
In my experience, Jaspersoft is not stable, and it does not have good community support.
What do I think about the scalability of the solution?
Jaspersoft's scalability is not very good. I ran into issues scaling up or down.
How are customer service and support?
The customer support for Jaspersoft is basically non-existent. I did reach out and did not really hear back.
Which solution did I use previously and why did I switch?
I did not previously use a different solution before Jaspersoft. Jaspersoft was the first one, just because that is the one we inherited, and then we migrated to Power BI.
How was the initial setup?
My experience with pricing, setup cost, and licensing for Jaspersoft indicates that installation was a pain, licensing is not worth the money, and there is no AI integration that I have seen. That is another thing that should be implemented or enhanced.
What was our ROI?
I have not seen a return on investment from using Jaspersoft; not a single one, hence why we are migrating.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for Jaspersoft indicates that installation was a pain, licensing is not worth the money, and there is no AI integration that I have seen. That is another thing that should be implemented or enhanced.
Which other solutions did I evaluate?
Before choosing Jaspersoft, we did not evaluate other options. It was just inherited.
What other advice do I have?
I would rate Jaspersoft overall as a two on a scale of one to ten. I choose that number because of the poor integration with other systems and the performance enhancements that we experienced during the migration. Jaspersoft batch ETL was very slow. My advice to others looking into using Jaspersoft is simple: do not use it. Use anything else instead.
Powerful Functionality, Complex User Experience
So clunky it hurts
Absolutely Atrocious
non stop issues with both Jaspersoft Studio and Jaspersoft Server.
- Tried to reach out to Tibco to determine if it was user error or a known bug and they immediatly tried to get us to pay for their 'support' which is limited to 12 cases per year.. works out to around $500 per case!
- zero support is available for AWS subscriptions. despite it being noted on their website, the only support available to AWS users is their hopeless forum. You need to pay for the 12 month license which is circa $7000 /yr then the $5500-6000 per year for support. For an entry level user, this could quadruple the application cost per year.
- Jaspersoft Studio is plagued with problems, we've been told to use the community version instead of the professional however the community doesnt offer charting etc.
- no ability to apply patches or updates to running instances. you need to back it up and restore it to a new one. This also means that any special configuration, SSL certificates or mail setup also needs to be copied.
No Support for AWS Version
We have been using JasperSoft for more than a year and have just entered our second full year. There are serious issues with v6.4.2 and there is a hot fix available that appears to fix many of the issues. However, as AWS users you cannot access this Hot Fix or apply it. What's worse is that the AWS install instance does not have these fixes applied, virtually making this update worthless. And, who knows when this will be updated.
Overall, we like the product, but we are not ready to take the plunge into purchasing the license directly, for BYOL. This seems to be the primary way to get support and what they push you to get. Just to get standard support with 12 use cases, will run you at least $6,000 a year.
Why can't the hot fix be made available or at least the AWS install for 6.4.2 be updated to include the fixes?
Our only option is to bring back up our v6.3 server!
Very little support for AWS hourly
Installed an instance to test drive the product. Tried to connect it to our production database (which uses a forced SSL connection) and was unable to configure. Tried contacting support, and they informed me that they don't offer support with the AWS hourly product. After emailing twice and chatting with a sales rep, a support rep pointed me to the community forums and gave me a few things to try. Was not able to ever connect to the database, although I am sure it is possible. Was not able to actually evaluate the product due to configuration problems.
The long and the short of it is, if you need help getting up and running, they won't help you unless you have purchased a support contract.
Couldn't get it working with VPC
Spent several hours trying to get both EC2 and CloudFormation versions to work in our VPC without any luck...
There should be a way to configure the CloudFormation with a VPC/subnet parameter the template can use when launching EC2 instances.
Terrible. All I see is Your subscription is pending and should be ready momentarily.
Product is not available live or within 10 minutes of setup.
40 minutes later and I still see:
Your subscription is pending and should be ready momentarily.