We performed a comparison between Oracle OBIEE and TIBCO Jaspersoft based on real PeerSpot user reviews.
Find out in this report how the two Reporting solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable feature of Oracle OBIEE is its ease of use."
"The most valuable feature of Oracle OBIEE is it's designed for Oracle. It works well in the Oracle environment and can sit on top of any application."
"Easy to create ad hoc reporting for different solutions."
"We have scheduled reports delivered automatically to our business users using enterprise features."
"The most valuable feature is the openness of the solution. It helps us integrate some of our clients."
"Its robustness is most valuable. It can handle massive amounts of data quickly. If it's properly configured and tuned, it can handle massive amounts of data very quickly to produce results. That to me is the number one feature."
"In terms of features, everything is good. It is also stable and scalable."
"The scalability of the product is good."
"We find the access restrictions on different user groups valuable."
"We can set any property dynamically."
"I give the stability of the solution a nine out of ten."
"The designer is the most valuable feature."
"With the online view, it's easier to create Ad Hoc reports. It has inbuilt reports so we can easily get data from the system and customize the fields."
"Stability-wise, I rate the solution a ten out of ten...The deployment process of TIBCO Jaspersoft is easy."
"The end-user reporting is very handy and the standard reports that can be achieved by using Jaspersoft Studio are quite impressive."
"You can do quite a lot with it in terms of automated reports and dashboards."
"Its overall organization as an analytical tool, the layout of OBIEE, is not very good."
"Oracle products have a lot of complications...Oracle has a history of not really providing great support."
"Expanding beyond pure data reporting and into analytics, or expanding data science, would be areas for improvement."
"In the on-premises version, the feature for connecting and selecting the data between the databases looks a bit cumbersome, but I am not sure. The person who is using it takes a lot of time to design a data warehouse. When I ask him why is it taking this long, I get a response that this is something that he has to design, and there are different tools that are available. He has to write the ETL and design the warehouse according to the customer's requirement, which takes a lot of time. Its visualization should be enhanced, and there should be a feature where you can easily create your custom data warehouse."
"While it is a user-friendly, data-driven tool, the data modeling should be easier to use."
"Oracle OBIEE could improve by having better integration and compatibility with other vendors."
"Even though we have a feature to enable the physical query to be seen in the log, in case of any issues, it is challenging to debug and see or identify where is the issue. For example, we designed the OBIEE repository and deployed it into the server, and we are now accessing and creating a report. For some reason, if the report is not working as expected, it is very difficult to identify the issue. We have a feature to see the physical query that is being generated in the central OBIEE server. I feel that this feature should have been available at the repository level so that while designing the repository, we can select the presentation columns and the query it is going to create. This will avoid the additional task of deploying a feature into the server and then testing the report. It will also make the implementation process friendly if, while designing the repository, we can see: How is a feature working? Are any of the presentation columns selected? How is the query being generated? Which query is being generated? Are any joints used? What kind of joints are used? Having this kind of information will make Oracle OBIEE more powerful and developer-friendly."
"Supply chain and finance."
"The upgrades are not easy."
"The stability of TIBCO Jaspersoft needs improvement."
"Currently, JSON format is the main format we use, however, in TIBCO Jaspersoft, XML format is the default and JSON did not work because TIBCO did not fix it."
"I would like to see some analysis done prior to data extraction. The data extraction itself could also be improved."
"The reporting templates have room for improvement."
"The Ad Hoc Report Writer does not include as many features as Tableau and needs to be improved to meet expectations."
"A better focus should be put on self-service reporting."
"TIBCO Jaspersoft would benefit from enabling you to run multiple reports in one file and incorporating more options related to multiple reports."
Oracle OBIEE is ranked 3rd in Reporting with 154 reviews while TIBCO Jaspersoft is ranked 7th in Reporting with 28 reviews. Oracle OBIEE is rated 7.8, while TIBCO Jaspersoft is rated 7.4. The top reviewer of Oracle OBIEE writes "A solution that is easily accessible, scalable and requires a straightforward initial setup process to get started". On the other hand, the top reviewer of TIBCO Jaspersoft writes "Provides a LMS reporting system and inbuilt reports so we can easily get data from the system and customize fields". Oracle OBIEE is most compared with Microsoft Power BI, IBM Cognos, SAP BusinessObjects Business Intelligence Platform, Tableau and Oracle Analytics Cloud, whereas TIBCO Jaspersoft is most compared with Microsoft SQL Server Reporting Services, SAP Crystal Reports, Microsoft Power BI, Tableau and Qlik Sense. See our Oracle OBIEE vs. TIBCO Jaspersoft report.
See our list of best Reporting vendors.
We monitor all Reporting reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.