Jaspersoft Community Edition is a free product that offers embeddable pixel-perfect reports for Java apps and small workgroups.
$0
per month
Looker
Score 8.2 out of 10
N/A
Looker is a BI application with an analytics-oriented application server that sits on top of relational data stores. It includes an end-user interface for exploring data, a reusable development paradigm for data discovery, and an API for supporting data in other systems.
Any scenario where you need to reach back into TIBCO support is something I would highly avoid. Most responses at the second round get you pointed to engaging their professional services. The general mentality seems to be "since our product acquisition cost is low, why don't you engage PS to get the value you need" If you are looking at enterprise scenarios, I would highly recommend looking at other more established products.
Quick dashboards from Google Sheets - Easier to do the graphs than in Google Sheets - Operational dashboards to be used in the day-to-day work - It is good both for retrospective data and to do a pulse check of the current status - Better for not giant amounts of data and not multiple data sources. - If you need a lot of graphs to be displayed on the same page, it can be a bit glitchy during configuration (then the use works fine).
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).
Filtering - you can filter across different dimensions and metrics to get a more specific "cut" of data
Refreshing - data automatically ingests into Looker which allows reports to be updated and backfilled in real time
Conditional Reporting - you can leverage Looker's reporting features to flag when a given metric or KPI falls below or above a specified threshold. For example, if you had a daily sales benchmark in a SAAS organization, you could use Looker to flag whenever daily sales falls above or below the benchmark
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.
Looker is less graphical or pictorial which makes it less attractive
Consumes a lot of memory when there are multiple rows and columns, impacts performance too
At times when we download huge chunks of raw data from Looker dashbords, the time taken to prepare the file is enormous - The user fails to understand if Looker has frozen or if the data is getting prepared in the background for downloading. In turn, user ends up triggering multiple downloads
Even though there are challenges with Architecture, sizing and other areas with Jaspersoft provided that Jaspersoft comes up with the right set of innovation, performance, scalability, and documentation in future it will be great expansion (win-win) situation for the clients and as well as Jaspersoft.
We've been very happy with Looker so far, and all teams in the organization are starting to see its value, and use it on a frequent basis. It has quickly become our accessible "source of truth" for all data/metrics.
The overall performance of this platform has been excellent. It is easy to work with the user interface. Creation of digital content and publishing on our social media platforms during marketing has been easy. Running our applications and upgrading our system to meet international standards has been successful. The user dashboard displays reports and performance of all departments effectively.
Looker is relatively easy to use, even as it is set up. The customers for the front-end only have issues with the initial setup for looker ml creations. Other "looks" are relatively easy to set up, depending on the ETL and the data which is coming into Looker on a regular basis.
We have only had a couple of tickets to be open while using Jaspersoft. Each time we have a very prompte responses that would meet our expectations. We always felt that our issues were being address in a timely manner
Never had to work with support for issues. Any questions we had, they would respond promptly and clearly. The one-time setup was easy, by reading documentation. If the feature is not supported, they will add a feature request. In this case, LDAP support was requested over OKTA. They are looking into it.
While the training was somewhat beneficial, a lot of what was taught to us was what we managed to figure out in the weeks prior. It did provide some useful tips and reference material, but overall something more tailored to our requirements would've been better.
New releases can be very buggy, also lacking when it comes to standard time zones and formats that are outside the US. As a company we never feel comfortable implementing a new release for at least 3-6 months due to errors that are found
Crystal reports is very expensive and does not integrate well with java based servers. Jasper also provides community edition, if we every want to downgrade the use, we always have the option of eliminating the server and using the reports as they are. Jasper also give you the opportunity to build BI on case by base basis including Dashboards.
Looker is an off-the-shelf, free tool for Google business users. Other than the internal cost of time to build, we had no costs to set up what we needed to do. Knowledge sharing internally and using templates greatly reduced this cost, making the overall cost very low.
Jaspersoft Community Edition has not had any significant impact on our ROI as we have purchased the commercial edition of the product.
The only impact on ROI is that when we bring on new developers, he or she can begin work using the community edition while awaiting the installation of the commercial edition.
Allowing others to self-serve their own analytics and connect it to Looker simply and easily has helped unblock the central data team so they can instead focus on validated dashboards whilst stakeholders manage their day-to-day analysis themselves. Countless engineering hours have been freed up by not having to manage every user permission for each BI tool; we have a BYOBI approach; Bring Your Own BI
Creation and management of a semantic layer (LookML =Looker Modeling Language ) allows peoples sandboxes and production databases to become clutter free. Minor adjustments, conditional fields, and even some modelling can all be done in LookML which doesn't need oversight or governance from the central data team.
LookML, specifying drilldown fields and their sub-queries, as well as generally creating dynamic parameters with Liquid are all great features, but can have a steep learning curve. it may take some time to understand how to create this middle layer correctly, or even pose a risk of inheriting complex code from another source which can be unmaintainable if it becomes too big. Some level of governance is recommended if Looker is used by a large number of editors.
