Oracle Data Relationship Management vs TIBCO EBX comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Oracle Data Relationship Ma...
Ranking in Master Data Management (MDM) Software
10th
Average Rating
9.0
Number of Reviews
4
Ranking in other categories
No ranking in other categories
TIBCO EBX
Ranking in Master Data Management (MDM) Software
3rd
Average Rating
8.2
Number of Reviews
14
Ranking in other categories
Cloud Master Data Management (MDM) Solutions (2nd)
 

Mindshare comparison

As of June 2024, in the Master Data Management (MDM) Software category, the mindshare of Oracle Data Relationship Management is 2.4%, down from 4.3% compared to the previous year. The mindshare of TIBCO EBX is 11.9%, down from 12.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Master Data Management (MDM) Software
Unique Categories:
No other categories found
Cloud Master Data Management (MDM) Solutions
8.2%
 

Featured Reviews

DW
Dec 7, 2021
Extremely flexible tool that can be customized to meet business needs
We use the solution extensively across our organization With this application, if data was entered manually with a system whose data we migrated onto the DRM system, we can automate 90% of that manual entry. The feature I find most valuable is the ability to use JavaScript in formulas because…
AH
Apr 1, 2021
Good workflow models and pull-down lists with very good data modeling
It's a pretty steep learning curve, I find. And not really fluid and flexible. There is some graphical rendering of the workflows, however, you can't really develop them in terms of the graphical picture. Whereas a lot of BPM-type tools will give you that kind of capability. The workflows need improvement. You need to develop, kind of conceptually, what you want. It's basically a web app generator, so there's a lot of magic under the covers. When you're trying to promote the changes through a version control system, it's hard to know what to expect as far as all the content. For example, if we were building and writing Java code, we would know what's changing. However, due to the fact that we're just putting in models and embedding some business logic in the models and such, it generates a web app, a job of whatever. It generates XML and some other stuff. And that's XSD. Then when you go and say, "Okay, let's push these changes," in Git or in Eclipse, et cetera, it's tricky to have a multi-developer environment where you're not stepping on each other a little bit. You're not as aware of the repercussions of your design changes. The documentation needs improvement. It would be helpful to have more during implementation, for example. It would help make the initial setup more straightforward. In a workflow, you can't set default values for certain columns, which would be nice. If you're handy with Java, you can create your own services and such and do something there, however, it should be out-of-the-box functionality. If you have a generic system, you should be able to say, "Hey, this structure supports A, B or C." Yet, if you launch it, if department A launches it, assume that certain values are set to their preferences. As department D launches assume that the department is B and you know, certain values are set, et cetera. Otherwise, everybody comes in generically, and then they have to know more than they want to know. There's this thing called replication. You could replicate the XML database to SQL Server on Oracle. That replication doesn't happen if you use certain features of the product. For example, with one of these features, you can do calculations or calculated fields. You could say it's X, then do a sum, et cetera. If you have a calculated field, you're not allowed to replicate it. It would be better if they could allow the replication, even if maybe they have to limit the functionality to those columns. There's an item called inheritance. You could say, I don't want to, if I asked for your name, I don't want to ask for your name three more times. So when I get to another file on the table, it's already there. It will carry information by inheritance, so you're not going to enter it wrong three different ways, however, once you have inheritance, you can't replicate. It would be better to ignore the inherited fields, just nix those columns, yet allow the table to replicate. Then you can have an SQL server go in and read the data in a relational way, which is very helpful to make it acceptable to developers and business analysts, et cetera.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable feature is the ability to use JavaScript in formulas."
"The most valuable features of TIBCO EBX are the workflow and interface."
"The tool's UI is good and easy to understand."
"This solution allows the user to have complete control, and is 100% customizable."
"The data quality is very good."
"The initial setup is easy and straightforward."
"It is a very stable solution...It is a scalable solution."
"There are a lot of possible use cases for this Master Data Management tool."
"The API and the data model are very valuable features."
 

Cons

"When we moved to the cloud, it was extremely complicated."
"The tool has to improve mapping and workflow. It should be made more robust."
"TIBCO EBX could improve by making the building of rules less complex and the repository is not robust."
"We would like to see the community an documentation for this solution be developed. At present there is very little tutorial documentation available, and limited community support for issues with the product."
"Currently, users can't use Plain SQL queries in TIBCO EBX."
"The design should be easier and more visual."
"The support isn't great and takes too long. And the pricing can be improved."
"The product does not scale well horizontally. We find the scalability to be quite inferior to other options."
"The documentation needs improvement."
 

Pricing and Cost Advice

Information not available
"The price of TIBCO EBX is too high. The solution can only be used in a project that has good sponsorship that can afford it."
"I'm just involved in technical, but I understand that its pricing is similar to HP so it is quite expensive."
"TIBCO EBX is cheaper than Informatica."
"TIBCO EBX is a very expensive solution. There is an annual fee to use the solution."
"This solution is costly compared to other products on the market, but this is due to the complete functionality that is provided. The pricing model is very straightforward, and is worked out on a pay-per- instance basis, and only applies to active instances."
report
Use our free recommendation engine to learn which Master Data Management (MDM) Software solutions are best for your needs.
787,817 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
15%
Manufacturing Company
8%
Insurance Company
8%
Financial Services Firm
20%
Computer Software Company
12%
Insurance Company
8%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about TIBCO EBX?
The most valuable features of TIBCO EBX are the workflow and interface.
What needs improvement with TIBCO EBX?
We would like to see the community an documentation for this solution be developed. At present there is very little tutorial documentation available, and limited community support for issues with t...
What is your primary use case for TIBCO EBX?
I am using TIBCO EBX to build a business and administrator EBX tool.
 

Also Known As

No data available
TIBCO MDM, Orchestra Networks EBX
 

Learn More

 

Overview

 

Sample Customers

MTN, SITA
BNL, SunGard, TUI Group, Uti Worldwide, Yellow Pages Group
Find out what your peers are saying about Oracle Data Relationship Management vs. TIBCO EBX and other solutions. Updated: June 2024.
787,817 professionals have used our research since 2012.