The report templates can then be used by the clients so they can deploy and set up the templates on their JasperServer or they can use the templates as baseline reports on Jasperstudio and make custom development changes to the reports to fit their business situations or logic.
- Custom design reports in Jaspersoft Studio. There is a lot of flexibility to customize reports. You can create easy reports in a quick time frame or complex report in a bit more time.
- The company does not need a 100% developer to develop reports. Someone with some level of developer experience could use Jasper Studio
- Jasper also provides a stand-alone web server to deploy your reports. This opens up a lot of Jaspersoft Studio files.
- There is a lot of time and effort put into the software. Years of input that improved all levels of the applications. Jasperstudio, Jasperserver, a manual, the community, etc.
- Flexibility is awesome, you can do almost anything. Having well-rounded REST API or you can use the Java Studio.
- There is a lot out of the box functionality. Scheduler, stand-alone reports, report output formats, logging settings, customization of GUI to a degree, permissions, roles, and user setup Studio, etc.
- Easier to customize the Jasper Server GUI. More flexibility with the input controls look and feel and maybe more input control types to select from.
- Have browser event functionality in the reporting itself.
- An easier way to iterate through an object. Maybe an option that tells the report Java run-time to stop following the report sequential flow and first integrate through this stated object many times.
- An easier way to create a list and add values to this list.
- Maybe one could stipulate the process flow of what needs to be computed first in a given field.
- The crosstab is a bit buggy on the Jasper studio side, so if that could be improved.
- Better and more examples of custom components
- The jive functionality on the tables needs an update. It looks so old and outdated.
If one needs a handful of reports and the look and feel is important as well as functionality, just develop your own reports using a report library.
- It has better performance. The first page of a report will be displayed as soon as the data comes, and users can read the first page while waiting for the other pages to load.
- The structure of the reports are in XML format, which makes it easily readable and editable.
- It is Java based, experienced Java developer can tailor the report with their own needs.
- Vague error message. Usually something like "Some error happened, please contact your administrator". It's impossible to locate the root cause quickly.
- Exporting. When exporting report to xlsx, docs, pptx format, the layouts are not perfect.
- Report width cannot be increased automatically.
Less Appropriate: The user asks for an Excel format report and your report is rather complex.
We have used Jasper for complex financial reporting, media calendar reporting, Invoices, purchase orders, estimates, project management reports in our software
It has issues where there is a need for Runtime SQL connection injection, or where a report has multiple main queries, where you have to depend on custom data sources. Custom data sources have to be written in Java and have a ton of memory leaks and garbage collection issues.
- Include the jar files in your project and make the most sophisticated document with HTML5 og PDF output.
- Let your users make their own report in minutes with little or no training, via the self service BI portal.
- The package is missing any prediction or forecast functionality.
- The dashboard need more animated widgets with conditional formatting, like stoplights.
- The Jaspersoft Online reporting software is very complex.
The Jaspersoft Online reporting software is very complex. Sometimes it's hard to figure out what to do in order to get started.
Mainly targeted for Admin users to do the below tasks:
1. Day to day reporting needs
2. Scheduling the reports to end users who look for transactions happening in the parent enterprise system.
3. Customize the reports based on company formats.
4. One part of our company product (acquired) uses Dashboard features of Jaspersoft
Also the Jaspersoft is being used to track the compliance of mandatory readiness attended by internal employees of company.
- Very intuitive tool - An Advanced reporting user can figure out in a day on the end to end operations.
- Easy customization - Simple changes in UI makes it less headache for the end user who maintains the tool. Being an open source product (offers Jasper web services) makes a lot developer friendly compared to SSRS, Cognos etc.
- Easy Connectivity - Can connect to any data source (can connect to multiple data sources) for a single report - can be customized.
- Community - A very strong community available online, videos - on basic how to questions, also provides assistance to use case specific scenarios.
- Ease of Reporting - Can create a reports with in few clicks with out struggle.
- Domain Designer - A very powerful tool you can create a dataset using clicks with out writing SQL code.
- OnDemand Scheduling - A very good scheduling feature and a has got lot more simplistic compared to other popular tools like Cognos.
- Jasper Studio - Very good programmatic tool (desktop tool) lets you customize the reports more company specific, can embed complex coding with 3rd party languages like Java, Groovy (scripting language).
- Inconsistent Errors - Crash dump errors annoys end users while not giving an clue of the actual reason of the failure. Everything has to be manually dealt by admins who need to tediously investigating through the error logs and investigating the crash dump errors or need to enable auditing which will tax the overall system.
- Stability , Performance issues - You can experience a lot of Performance issues with the increase of complexity in programming SQL queries but there are majority of performance bottle necks with in the product architecture on the supportability.
- Scaling - There are lot of hiccup's while scaling the product to huge set of audiences on a large scale mainly due to vagueness on the documentation and test results provided from Jasper support team. Need to invest a lot of internal perf testing before rolling this to large scale users for any reporting needs.
- Data source connectivity issues - You can face multiple connectivity errors across firewall, windows firewall, 3rd party driver issues mainly due to lack of in-house integration of the product. As the entire product is designed in Java and Java has a lot of issues in supporting MS platforms.
- Shortsightedness in Roadmap - Lack of Dynamism in product features - Product Managers at Jasper team dont offer much of the dynamic features offered from Tableau, SSRS, Cognos ex: optional/ forced parameters not available in legacy versions - available only in the recent versions. Also restricting schema to end user has to be dealt at the database level by the DBA teams, this feature available of restricting schema is not available from Jasper team.
- Jasper studio still needs to be scaled up to a lot of extent compared to MS- BIDS - Visual studio, Cognos - Report Studio - especially in terms of supporting multi dataset based queries in a single band of the report, parameters support with multiple datatypes.
- Support model not matching business model of customers - Any complex issue on legacy versions becomes a lot more challenge in dealing with Jasper team as they force you to upgrade with out understanding the dependencies on production environments. Getting a hotfix becomes lot more challenging. The front line of engineers do a basic troubleshooting with out understanding the actual problem, passing through several levels becomes exhausting before the actual engineer shows up who can fix the issue.
- Integration with 3rd party authentications - You can face a lot of challenges with authentication with 3rd party clients as there is no clear cut documentation, steps available from the Jaspersoft
1. Simple reports with few complexities in SQL queries etc.
2. Fits for less no.of users (reporting admins, reporting users). Hardware needs to scaled up accordingly with the increase of usage/ concurrency of the reporting system.
3. Fits for simple scheduling purposes where there are few managers who want reports on a daily basis.
4. Simple dashboards.
5. Monitoring purposes. (Production unit).
in case of implementing for large enterprises need to consider the below aspects.
1. No.of users
2. Need to do perf test every report based on concurrency before moving to production.
3. Constant monitoring of reporting servers when the load/ concurrency goes high.
4. Restrict dashboards to only few reporting admins compared to large scale.
5. Constant changes in hardware based on the usage. (physical resources needs to be beefed up in case of higher usage).
6. Check the costly queries, constant fine tuning.
7. Architecture of Web should be made in such away that you can upgrade Jasper web with out impacting your DB. So that in case if Jasper team informs to upgrade for couple of fixes.
- Very easy to use. Drag and drop.
- Very versatile when using data adapter to our HBase and Oracle backend data bases.
- Reports are easy to read and understand.
- Ad Hoc is not as powerful and flexible as report creation using Studio.
- API is not documented as well as I think it could be. I ended up googling for a lot of questions. Community is great through.
- Error reporting could provide more detailed. I caught myself on several occasions trying to figure out the root of the problem when it should be easily stated.
I believe there are better options for more complex reporting but for what we need Jaspersoft works well.
Visualize, while being a very nice tool with very dynamic reporting, seems to be lacking in the abilities to share data over multiple accounts.
- Charts are very clear and regularly updated
- Scheduling reports is easy
- Reduced number of clicks to access reports
- Scheduling dashboards - should be able to export to Excel, exporting to PDF looks cheap and not correctly aligned.
- Calculated Measures - over-complicated and difficult for new users to get to grips with.
- Admin rights - customers should be able to access other people's reports and schedules if they have admin rights.
- Dashboards - should have more space than one screen.
- Multi tenancy
- Report scheduling
- 3rd party integration
- basic charts
- Chart customisation could be made a lot easier for non-technical users. More control of this through the UI or right click mouse options would make it a lot better to use. Like in Tableau or Power BI.
- The process for creating drill through charts could also be simplified through better UI options without the need to manually enter parameters and report links.
- A better way of dealing with existing fields in already created reports that need to be changed or removed from the domain without having to browse through each report to remove the field manually beforehand.
- The UI and feel of the ad-hoc view/report creator could be made a little more user-friendly with more UI options available without having to refer to a separate website to hunt for the appropriate APIs.
- Have more pre-calculated chart options. Such as Pareto charts that a right click function would enable on a chart. Presently all the data has to be structured very specifically to do this. DevExpress has had this option available for a long time.
- Ability to drill through from a Chart to tabular data instead of having to go to the crosstab view to do so
- The implementation of the reports with Jasper Studio is very friendly and allows us to be more productive.
- We can guarantee quality attributes such as scalability, security, and confidentiality in the presentation of information with TIBCO.
- It is also an essential aid in the management decisions of our clients with their BI tool.
- The implementation of security with visualize took us a long time due to the lack of documentation on the subject.
TIBCO Jaspersoft Community Edition Review: "Powerful Reporting Tool, but requires some Additional Enhancements"
- Exporting Options
- Rendering speed faster than other BI Tools
- Look and feel of reports
- Dynamic column creation/addition based on the query output is not possible
- Dynamic page width/height adjustment is not possible with Jasper reports.
- Input control label cannot be drawn from a query
- Org chart related report creation is not possible with Jasper reports
- Tree view showing up of values in input control is not possible with Jasper reports
- Validations on input controls is not possible for example, start date and end date
- Drill down in the same report is not possible as SSRS Reports support i.e., +/- view in SSRS reports
- Online Education when starting up
- Community site
- Posibillity to develop the reports you need
- Relatively easy to use
- Specially in the beginning I could have used a support function to contact - an online contact could be fine
- Building new reports with e.g Gantt charts is for me very complex
- I'd like a better mobile solution - compared to set up of a PowerBI solution, Jasper is quite complex
I like the way you can develop what you need with almost no limit.
Difficult to use Maps, Charts and Widgets Pro
TIBCO Jaspersoft Community Edition Review: "A very good chance to introduce a reporting server in a company"
The Jaspersoft Report Server entry level version is a very good product, with a very low cost providing a great product with a very effective support.
The community provide an effective way to solve problems and find solutions. I will suggest this product to my colleagues t to manage company that has evolving reporting needs.
- Scripted installation is reasonably simple
- Out of the box drivers for most data sources are good to have
- Can quickly create semantic layers for basic data models
- Re-seller experience is extremely poor. We were almost not able to get a quote!
- Subscription model pricing has very poor visibility and re-seller did not explain this well at all
- The world has moved to SAML and multi factor authentication. Information about configuring to those is very poor.
- Pixel perfect reports
- Highly customized reports using open source technology
- Easy to use dashboard and ad hoc report builder
- Repository interface is a flat structure. Folder or other structure would be best for numerous reports for several different departments.
- Should come fully equipped with all available properties for High Charts
- Better user guides that includes more information about configurations for styles, conditions, etc. that aren't covered in the guide.
- Easy to use portal for end users
- Open source
- Really bad support! Even when you pay for support! You call in, don't get a call back. When you do they tell you go to onto the website and submit a ticket (why the support person can't do that while I'm on the phone is beyond me!). Then nothing is done and you get a notice that it's now a bug and maybe they will fix it on the next release!
- Documentation is ridiculous! You go on their website and enter your product version and do a search and you get info for EVERY version out there! Even though it's irrelevant or wrong for your version! Customer support will even email you invalid documents!
- Nickel and dime you for everything! Need help to tune Java? You'll pay! Need help speeding up queries? You'll pay! Pay for the support and Customer success? they try to sell you other services and consultants! Need a fix for an issue that is a bug ASAP? Sure! If you pay!
- Convoluted portal for product, support, download and training! Took six months to get the account set up correctly! Every time I called to try and fix it, they simply reset the password!
- Integration of Tibco Jaspersoft ETL with realtime apps using Kafka components
- Integration of Tibco Jaspersoft Reporting portal using iFrame into our apps for Reports
- Big data components to integrate with Hadoop ecosystem
- The first thing to improve is proper step-by- step documentation, instead of each service/agent level. Understanding all the product components available and their use, will give a clear picture to beginners.
- The installer says that it includes all components, but at the time of installation we realized that there are some SVN/GitHub components that we had to install separately. And If we install individual services separately, the configuration is different.
- The logging options became worse from Tibco Jaspersoft Big Data ETL 6.0.1 to 6.3.1. The log4 level info was perfect in 6.0.1 but somehow it is messed up in 6.3.1 and it doesn't provide logging detail like in 5.5. It just says started and completed.
- Very easy to incorporate graphics.
- Sub-reports are a very useful feature.
- Using parameters allows for flexible and specialized reporting.
- Emailed reports should be able to be encrypted.
- Dashboards should be easier to set up.
TIBCO Jaspersoft Community Edition Review: "Jaspersoft Pro edition, good for ISVs embedding BI into products"
- Flexible licensing for an ISV
- Can embed, customise and change the look and feel to integrate well with our products to provide a seamless experience
- Usability can be an issue when creating ad-hoc reports for end users, they need to know the capabilities of the domain model and be "power users"
- Expensive for a small ISV, annual subscription
Less useful: Desktop BI analysis
TIBCO Jaspersoft Community Edition Review: "Tibco was a great fit for a growing analytics firm, easy licensing, easy embedding"
- I think TIBCO does a good job of creating a good licensing model.
- They've updated their product with more modern charting libraries.
- We regularly find bugs that we have to report, it may just be our use case.
- The authentication framework is a little tough to master.
- It took us a few years to get it fully implemented.
- Support team is responsive.
- Product has been easy to integrate into our AWS cloud stack.
- We were able to get the product to render the reports we need.
- API documentation is confusing and often missing key details and usage examples.
- We have struggled to find a happy place around performance, and diagnosing performance issues. We are now considering whether to ditch Jaspersoft altogether due to its apparent difficulties in rendering large reports.
- The company made the extra logging diagnoses a paid extra feature... we should not have to pay extra to diagnose performance problems in the product.
- Generic usage of input parameters.
- Adhoc reports.
- User / roles management in Jasperserver.
- I don't like replacement of ireport. But I also agree that it was hard to use.
- There should be a simple way for users to see a dashboard as their home page.
- Printed graphs are sometime unusable.
- Integration with big data databases [could be improved].
TIBCO Jaspersoft Community Edition Scorecard Summary
Feature Scorecard Summary
About TIBCO Jaspersoft Community Edition
TIBCO Jaspersoft Community Edition Technical Details