The support portal needs improvement. Tickets are handled by junior engineers who struggle to solve issues in a timely manner. Frequent updates to the software are necessary, yet a number of features are not yet supported. The tool is not as popular, which limits resources available online or through the community. TIBCO EBX faces limitations in handling large volumes of data efficiently. At times, workflows terminate or the system freezes during data refresh activities. Scalability requires changing complex properties, unlike other tools where loading bulk data is easier. TIBCO EBX lacks certain features, such as tracking user login and activity within the application, which are more commonly found in other tools. These gaps might be addressed in future releases, but they currently present challenges for users.
Tibco EBX developer at a energy/utilities company with 1,001-5,000 employees
Real User
Top 20
Aug 22, 2025
AI could be implemented in TIBCO EBX. Currently, most tools are moving in that direction, so this could be added. The performance in our company, which has a multi-tenant setup, is an issue because there are many companies using it. We configure it as multi-tenant, and due to that multi-tenancy, we experience some slowness which could be improved. Regarding stability and performance, I have seen lagging multiple times, especially when we upgraded from version five to six. That was a major difference, and during that time, we faced many production restarts. If there are more records, or if the association tables and fields are more numerous for a particular table, it takes considerable time to load the records. With complex data models, there is noticeable slowness.
MDM Tibco EBX Consultant at a insurance company with 51-200 employees
Consultant
Top 20
Jul 16, 2025
Some optimization on the database and how it is handled would be beneficial. Currently, we have a lot of data that takes up significant space on the database server. Some optimization in that regard would be a plus to the software as a whole. Some enhancements could be made in terms of how the documentation is structured. Sometimes we struggle to find explanations for some features in the documentation. If they can work on that, it would be great. Overall, I think it is good.
Associate Director at a financial services firm with 10,001+ employees
Real User
Top 20
Jun 27, 2025
Regarding improvements or enhancements in TIBCO EBX, when it comes to 5.8 to 5.9, there was a really good feature added, which is the hyperlink. When you click on a table, you navigate to deeper tables. If there is a table with ten fields, those ten fields are taken from a second table and interrelated to a third table, you can keep clicking on each field and go deeper and deeper. To come each level above, there is a hyperlink created on the top. You just need to click on the hyperlink and keep navigating back, similar to certain websites. However, there were some drawbacks I noticed with the latest version 6, particularly in terms of performance, where in a few cases, the performance was impacted, necessitating work to get things sorted. Additionally, the logout from the application happened randomly or sometimes it wasn't logging out, which is a compliance issue since users expect to log out after a certain time. Version 6 introduced a strong filtration logic. All EBX versions have a separate section for filters that offer text search and advanced search options. In EBX 6, they enhanced the search feature deeply, including conjunctions and, or, else, allowing you to create your own logic for how you need the filter to work. They also introduced a top-level search feature, where you enter some text, and it searches the entire table. With the latest update of TIBCO EBX, there are a few issues with the workflow that need improvement. When going through a workflow, there are functionalities to upload files, and sometimes you need to attach files for evidence. That section of EBX had certain issues. We dropped the plan to switch to EBX 6 due to other technical limitations on our side. Those were a few pending items we had raised to them, and they were working on resolving them. From a usage point of view, those were the main concerns, but they introduced a good idea about the side panel. The pagination concept was introduced to navigate among different domains, and in the left panel, you have search capabilities and pagination functionality.
System Engineer at a consultancy with 10,001+ employees
Real User
Top 20
Jun 26, 2025
Nothing strikes my mind about other features I would like to see included in TIBCO EBX. We have this task scheduler with different tasks scheduled, and it will trigger automatically based on the planned schedule; that is one improvement part here.
There was a resource issue, so TIBCO did not prioritize the Turkish market. They lacked patience to create local partners, which was necessary for markets like Turkey. Marketing could be improved, as EBX wasn't well-presented in Turkey.
Currently, users can't use Plain SQL queries in TIBCO EBX. It would be great to use Plain SQL queries in TIBCO EBX. Right now, TIBCO EBX only supports Java, but I believe that it should support SQL queries on its interface. In short, certain areas in the UI area can be improved to support SQL queries.
TIBCO EBX could improve by making the building of rules less complex and the repository is not robust. In a future release, it would be beneficial to have a Match and Merge feature.
Senior Presales Consultant at a computer software company with 1,001-5,000 employees
Reseller
Oct 19, 2022
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. We would also like to see support added for the mobile MDM, so that the solution can be integrated with handheld and IOS devices.
Everything is updated through forms, and working with UI web forms. It's more record-based processing. It is not mass-based processing. This is one of the things that are not good for TIBCO EBX. Another problem is we cannot join tables and prepare a view where the tables are joined. Someone can code it but it is not a feature of the solution without code. You have to take data from a table, combine it with data from another table and then present it. This could be done better. TIBCO EBX should improve the UI, to allow users to easily mass change the data a bit more. We should not have to click the records one by one to change the data. The filter is in a form, and if one is to filter the data based on a form, you have to click every single attribute. It is difficult with the UI. However, one could be inspired by mobile phone UIs, how they are doing it because they are more efficient and this is missing in TIBCO EBX.
Sr Technical Architect at a computer software company with 10,001+ employees
Vendor
Oct 22, 2021
There are some areas when I compare this to other products where it could be better. The data quality, workflow, integration of data quality, and the force to master data attributes can be enhanced. The performance could be better. The initial setup can be a bit complex. I would like to see higher-level filters.
Data Architect at a pharma/biotech company with 10,001+ employees
Real User
Jul 24, 2021
We are currently using TIBCO EBX, however, we are not very happy with the performance of that tool. The product does not scale well horizontally particularly in the cloud. We find the scalability to be quite inferior to other options. The product has some compatibility issues with Azure SQL also. We heard that it works best with PostgreSQL which is not an ideal Cloud Database as it has scalability issues. The business team is not very happy with the product's UI/UX. It could be a lot more clear. Right now, they struggle, for example, with creating certain views from the UI. A lot of irrelevant questions are asked during the view creation which actually confuses a Non Technical user. Also, simple things like copy, paste, bulk copy, and bulk paste features are not available(one has to insert separators manually between the different data elements manually). The multi-index search feature is either not there or not very useful. These are some other problems which the business users have mentioned, as they don't have the technical knowhow to manage these tasks. If they directly want to change a particular set of data within EBX, they cannot do it directly as direct editing in EBX is not available - it may be for a good reason, but the tool still should allow this with the check and balances in place. This involves a Data Engineer in between which slows down the process a bit . The hierarchy, in terms of downward or upward drilling, is not great as the links are not well preserved. Sometimes when you are searching multiple tables, child tables or linked tables in a particular Dataset, there is a possibility that you might get lost and struggle to go back to some upstream table. The bread crump needs further improvement. The learning curve is pretty steep, as you need to learn a lot of things in Java and do some coding to implement certain customizations. Some other modules have also been removed in future version. For example, Information Governance, which we were using , will no longer be available in Version 6 is what we heard. Without that, the integration of Data Governance Rules with the transformations might be impacted.
Sometimes it is a little difficult to find an architect for certain developments. You kind of have to be like technicians to work with this product if you want to make some specific development. So perhaps it could be simplified. The design should also be easier and more visual.
ON EBX is a comprehensive tool for data management that combines customizable data modeling, seamless API integration, and AI capabilities to enhance data governance and facilitate complex data tasks with a user-friendly interface.
Designed for enterprise needs, ON EBX offers support for Master Data Management, data governance, and quality checks, allowing organizations to manage reference, operational, and metadata seamlessly. Its integration with systems like SAP and Oracle ensures data...
The support portal needs improvement. Tickets are handled by junior engineers who struggle to solve issues in a timely manner. Frequent updates to the software are necessary, yet a number of features are not yet supported. The tool is not as popular, which limits resources available online or through the community. TIBCO EBX faces limitations in handling large volumes of data efficiently. At times, workflows terminate or the system freezes during data refresh activities. Scalability requires changing complex properties, unlike other tools where loading bulk data is easier. TIBCO EBX lacks certain features, such as tracking user login and activity within the application, which are more commonly found in other tools. These gaps might be addressed in future releases, but they currently present challenges for users.
AI could be implemented in TIBCO EBX. Currently, most tools are moving in that direction, so this could be added. The performance in our company, which has a multi-tenant setup, is an issue because there are many companies using it. We configure it as multi-tenant, and due to that multi-tenancy, we experience some slowness which could be improved. Regarding stability and performance, I have seen lagging multiple times, especially when we upgraded from version five to six. That was a major difference, and during that time, we faced many production restarts. If there are more records, or if the association tables and fields are more numerous for a particular table, it takes considerable time to load the records. With complex data models, there is noticeable slowness.
Some optimization on the database and how it is handled would be beneficial. Currently, we have a lot of data that takes up significant space on the database server. Some optimization in that regard would be a plus to the software as a whole. Some enhancements could be made in terms of how the documentation is structured. Sometimes we struggle to find explanations for some features in the documentation. If they can work on that, it would be great. Overall, I think it is good.
Regarding improvements or enhancements in TIBCO EBX, when it comes to 5.8 to 5.9, there was a really good feature added, which is the hyperlink. When you click on a table, you navigate to deeper tables. If there is a table with ten fields, those ten fields are taken from a second table and interrelated to a third table, you can keep clicking on each field and go deeper and deeper. To come each level above, there is a hyperlink created on the top. You just need to click on the hyperlink and keep navigating back, similar to certain websites. However, there were some drawbacks I noticed with the latest version 6, particularly in terms of performance, where in a few cases, the performance was impacted, necessitating work to get things sorted. Additionally, the logout from the application happened randomly or sometimes it wasn't logging out, which is a compliance issue since users expect to log out after a certain time. Version 6 introduced a strong filtration logic. All EBX versions have a separate section for filters that offer text search and advanced search options. In EBX 6, they enhanced the search feature deeply, including conjunctions and, or, else, allowing you to create your own logic for how you need the filter to work. They also introduced a top-level search feature, where you enter some text, and it searches the entire table. With the latest update of TIBCO EBX, there are a few issues with the workflow that need improvement. When going through a workflow, there are functionalities to upload files, and sometimes you need to attach files for evidence. That section of EBX had certain issues. We dropped the plan to switch to EBX 6 due to other technical limitations on our side. Those were a few pending items we had raised to them, and they were working on resolving them. From a usage point of view, those were the main concerns, but they introduced a good idea about the side panel. The pagination concept was introduced to navigate among different domains, and in the left panel, you have search capabilities and pagination functionality.
Nothing strikes my mind about other features I would like to see included in TIBCO EBX. We have this task scheduler with different tasks scheduled, and it will trigger automatically based on the planned schedule; that is one improvement part here.
One aspect that could be improved in TIBCO EBX is the latency.
There was a resource issue, so TIBCO did not prioritize the Turkish market. They lacked patience to create local partners, which was necessary for markets like Turkey. Marketing could be improved, as EBX wasn't well-presented in Turkey.
Currently, users can't use Plain SQL queries in TIBCO EBX. It would be great to use Plain SQL queries in TIBCO EBX. Right now, TIBCO EBX only supports Java, but I believe that it should support SQL queries on its interface. In short, certain areas in the UI area can be improved to support SQL queries.
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. In a future release, it would be beneficial to have a Match and Merge feature.
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. We would also like to see support added for the mobile MDM, so that the solution can be integrated with handheld and IOS devices.
Everything is updated through forms, and working with UI web forms. It's more record-based processing. It is not mass-based processing. This is one of the things that are not good for TIBCO EBX. Another problem is we cannot join tables and prepare a view where the tables are joined. Someone can code it but it is not a feature of the solution without code. You have to take data from a table, combine it with data from another table and then present it. This could be done better. TIBCO EBX should improve the UI, to allow users to easily mass change the data a bit more. We should not have to click the records one by one to change the data. The filter is in a form, and if one is to filter the data based on a form, you have to click every single attribute. It is difficult with the UI. However, one could be inspired by mobile phone UIs, how they are doing it because they are more efficient and this is missing in TIBCO EBX.
There are some areas when I compare this to other products where it could be better. The data quality, workflow, integration of data quality, and the force to master data attributes can be enhanced. The performance could be better. The initial setup can be a bit complex. I would like to see higher-level filters.
We are currently using TIBCO EBX, however, we are not very happy with the performance of that tool. The product does not scale well horizontally particularly in the cloud. We find the scalability to be quite inferior to other options. The product has some compatibility issues with Azure SQL also. We heard that it works best with PostgreSQL which is not an ideal Cloud Database as it has scalability issues. The business team is not very happy with the product's UI/UX. It could be a lot more clear. Right now, they struggle, for example, with creating certain views from the UI. A lot of irrelevant questions are asked during the view creation which actually confuses a Non Technical user. Also, simple things like copy, paste, bulk copy, and bulk paste features are not available(one has to insert separators manually between the different data elements manually). The multi-index search feature is either not there or not very useful. These are some other problems which the business users have mentioned, as they don't have the technical knowhow to manage these tasks. If they directly want to change a particular set of data within EBX, they cannot do it directly as direct editing in EBX is not available - it may be for a good reason, but the tool still should allow this with the check and balances in place. This involves a Data Engineer in between which slows down the process a bit . The hierarchy, in terms of downward or upward drilling, is not great as the links are not well preserved. Sometimes when you are searching multiple tables, child tables or linked tables in a particular Dataset, there is a possibility that you might get lost and struggle to go back to some upstream table. The bread crump needs further improvement. The learning curve is pretty steep, as you need to learn a lot of things in Java and do some coding to implement certain customizations. Some other modules have also been removed in future version. For example, Information Governance, which we were using , will no longer be available in Version 6 is what we heard. Without that, the integration of Data Governance Rules with the transformations might be impacted.
Sometimes it is a little difficult to find an architect for certain developments. You kind of have to be like technicians to work with this product if you want to make some specific development. So perhaps it could be simplified. The design should also be easier and more visual.
In terms of improvements that this solution needs, it should support big data.
EBX should target becoming horizontally scalable. Currently, it supports vertical scalability only.