ON EBX Reviews

My basic role in this entire process is in terms of QA, and ours is a data management use case. TIBCO EBX is moreover for a data management tool. It is the master data management tool, MDM tool. We work with different tabular structures, and the basic benefit that I could see was that normally we use databases for all those tabular related details. In terms of TIBCO EBX, it gave us a UI representation of the same.

Normally, if you have to do the same thing in SQL or Oracle or any of the DBs, you need to write those queries for inserting, for creating, for deleting, and all those things. But here in TIBCO EBX, it was much easier because it was all UI representation. Even for business users, it was quite easier; you don't need so much technical skills to work in that particular application. You can just have a plus icon where you can create, then you have an option to delete, save, and all those functionalities.

It also provided flexibility in terms of multiple out-of-the-box functionalities, for example, exporting the files in different formats. It's not only specifically Excel; you can have it in CSV format and many other formats that we have in the tool. This was one of the good features when you compare it with the normal database and when you see it in the UI representation format. It also has some customized perspectives to be built. As per the business requirement, you can build the perspective. If there are certain views that the business wants to see, they can build their own perspective and see it. Similarly, they can make their own customized views. All this flexibility was being provided which made it quite helpful for both the business and IT. I work from the IT point of view, but being a QA, I need to understand the entire functionality of the products. It kind of brought my understanding closer to the business points as well. From the business perspective, it was quite helpful to them.

I have been working with TIBCO EBX for close to five years now. I have worked with different versions because when I joined the organization, I was working with 5.8 version. Then later we switched to 5.9 and then recently we were working on the migration task of 5.9 to 6.1.

I normally have had complex data requirements in my organization where the customizable data model feature of TIBCO EBX has been specifically beneficial. We used to have this kind of parent-child relation creation, and we had also included an Angular framework where the parent-child relation hierarchy pattern was being discussed. We used to have some hierarchy views, and these hierarchy views are inbuilt or out of the box functionality of EBX itself. You can just go to any table, click on the hierarchy view, and it will give you a hierarchy structure of that particular table. If you have a parent-child relation with ten levels below, you can see the complete structure in that hierarchy view. If you go from the tabular format, you won't understand it as easily. If A is a parent of B, B is a parent of C, C is a parent of D, you won't get a clear view to understand the hierarchy deep down. But if you switch your view from tabular view to the hierarchy view, you can see these views very clearly, and it gives an easier understanding to the user to see how deep the hierarchy is.

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.

I have been working with TIBCO EBX for close to five years now.

In terms of evaluating TIBCO technical support, it has been good for us because we have been using their product for a long time. We haven't faced many challenges requiring tickets to be raised. The relationship you build over time also affects this; when you've been with their product for ten years, the support improves as it becomes a personal network you've created throughout your support interactions.

We didn't face many challenges with technical support. We raised tickets via the specific path they established, and someone gets assigned to it to resolve issues and provide solutions. On a scale of 1 to 10, I would rate TIBCO technical support somewhere around seven to eight, with 10 being the highest.

In terms of measurable benefits and return on investment from using the TIBCO EBX solution, I find it an effective solution. Being an MDM and working with this particular solution for the last five years, I have seen many advantages. For example, working with the database and the UI front makes a huge difference. It brings a lot of flexibility for the business users; they don't need to wait for IT personnel to make some changes because a few things are sufficiently easy; as long as they have the required role, they can log in and make the change.

There are admin-related tasks that could be done easily, and many things could be configuration-based. There are also some role-based access configurations, where if a user has a certain role, they should have specific access levels to the tables or the overall application. The first level of access things can be configured, and they can take backups or snapshots of the data. They also have functionalities to forward data to different sources. Hence, TIBCO EBX saves a lot of time and gives considerable flexibility to business users who might not be completely technical but can work on it in specific areas.

Based on my experience with the TIBCO EBX solution, I advise users considering this solution to give it a try. They should explore it further and see if it fits into their requirement. If it does, then surely, it would be a great solution overall for them. I rate this solution 8 out of 10.

The collaborative workflows where we have collaboration of different teams working at the same workflow helps to centralize our work within the organization. Our central team works on different workflows and with the business users. My application doesn't face the direct outside customer, but it deals with internal bank employees, where the four-eye principle needs to be implemented. All those validations and everything in the workflow from an end-to-end process can be configured in the EBX application itself. As an admin user, you can configure everything, including which step needs to come after which step and all configuration details from the development standpoint.

Regarding the integration capabilities of TIBCO EBX, we normally transfer certain data. For instance, if you want to integrate, you can have data from the upstream because in a nutshell, EBX is the master data management tool. It could get data from some interface or deliver data to a certain interface; in the middle, it could enhance the data and implement various logic. You can schedule different kinds of jobs via EBX, and based on your scheduled jobs which you have triggered, it will run. If you schedule it for every day overnight or say a monthly batch job, then accordingly it gets triggered and delivers the data to the required interface.

In terms of evaluating the performance of TIBCO EBX, particularly related to enhanced data quality or governance, when you trigger certain kinds of jobs, you can take a copy of the data and store it. However, it depends completely on the requirement. If the data size is too big and continues to store, it impacts the performance. After a certain time, it somehow impacts the performance due to the bulk of data in your table. But if you want to keep the basic details about when the job was triggered, it works efficiently. You can connect it with the database where you can store the basic details, replicate the tables and store them in the database as well, which you can use for any kind of SOX compliance or data governance matters.

TIBCO EBX was used by one of our clients to manage financial data. It is primarily utilized by the operational and admin teams to keep the application running 24/7.

We have integrated it with SAP systems through which we are getting data loaded from SAP system to TIBCO EBX.

The best feature is that TIBCO EBX is customizable. If you need any feature which is not available out of the box, everything can be designed by writing Java code. It provides custom logic creation which is essential for users who need specific functionalities.

As it is customizable, it is best for handling data quality features. Also, it allows integration with systems such as SAP for effective data management. TIBCO EBX is scalable. You can handle lesser or greater amounts of data by adjusting instances to improve data processing capabilities.

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.

I have used TIBCO EBX for two years.

At times, workflows terminate or the system freezes during data refresh activities, such as loading bulk data from one system to TIBCO EBX.

If you handle a smaller amount of data, then that is acceptable. However, if you want to double the amount of data you handle, then that will be more complex. You need to change some properties of TIBCO EBX and increase the processing power, which is challenging.

TIBCO EBX does not efficiently handle large volumes of data. During bulk data loads or refresh activities, the system may freeze or workflows may terminate unexpectedly.

Tech support is rated around five to six. Support involves reaching out to engineers for sessions, but recently tickets have been assigned to junior engineers who are not solving tickets efficiently.

I mostly work on Informatica and TIBCO EBX. I have compared TIBCO EBX to other MDM tools such as Stibo MDM and Reltio MDM.

Informatica and other MDM solutions such as Stibo MDM and Reltio MDM offer more features out of the box and tend to be more popular, with quicker updates and support systems.

Feedback from other professionals suggests switching from TIBCO EBX to other MDM tools for better career opportunities and functionality.

There is limited documentation or resources to learn about TIBCO EBX online compared to other MDM tools, and the skill set required for its development is very niche.

Organizations using TIBCO EBX have to rely on resources provided by TIBCO due to the limited availability of external developers familiar with the tool.

I would rate TIBCO EBX around five or six overall.

It is basically for managing data and specifically master data for clients, such as big corporations who have multiple millions of data, including clients, products, etc.

The best features of the TIBCO EBX solution would be ensuring data quality by using Match/Merge add-ons. It has multiple add-ons to search for data in TIBCO EBX. It is pretty performant. Matching the new data inserted on the software is done in a timely manner and it is pretty efficient. It is easy to work with as a developer as well. It is easy to code, especially because it is coded in Java. It is pretty clear in terms of documentation and how to use it. It might be a little bit complicated, but when you get used to it, it gets easier and easier.

Good data modeling would help. Maintaining a purging process for unused data or closed data spaces is important because we can take a copy on a data space and work on it and then merge it or not. If we are testing, we do not merge. Purging those unused data spaces would be good for performance and for leaving some space in the database as well. That could enhance performance.

It has an indexing mechanism that indexes because you have the database on a server and you have the application in another server. What TIBCO EBX does is it has an index. It indexes the data on the current server, on the application server. This can enhance the performance in terms of searching, altering the data, and accessing the data. It is pretty quick, thanks to the indexing, because it does not have to go to the database server in each consultation of the data. It can point to the index and get the data.

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.

I have been working with the TIBCO EBX solution for five years now.

It is a little bit complex. Setting up is probably one of the hardest tasks to work on with TIBCO EBX. It is not extremely complicated, but it is understandable in terms of the volume of the data they can manage. It has to have its own server, database server, etc. You have to work with Tomcat to set that up and data models in the first step. After that, the customization depends on the needs, but it is more or less easy.

I think it is pretty stable. It does not have many bugs, and if we have a bug, the display of the error is quite straightforward. Sometimes we get some issues, but we figure out later that the issue was something we did not set up correctly. In terms of production deployments, we did not have many issues. It is pretty stable. We do not have bugs in production. Sometimes out of nowhere you get something, but with TIBCO EBX it is quite stable.

It is pretty scalable. With my current clients, we have over 150 million records managed by TIBCO EBX and it is pretty stable, even with a huge database. We are working with the editor to find a way to make that shrink through optimization. They promised that within the next releases, they would find some solution to that. My only concern is the actual database and its volume. That is the only thing in terms of scalability. Otherwise, in terms of performance, consultation of data, and APIs, it is still pretty stable even with the huge amount of data.

They are pretty helpful. They have a policy where each client has a reference that you can call and reach out to if you have any issues. They also have an online platform to submit cases if we have any issues to the support. In terms of response time, it is pretty reasonable. It does not go beyond four hours or something similar. They get back to you quickly.

Positive

I am new in MDM. Since I got out from the university, I started with TIBCO EBX and it stayed that way.

Setting up can be a little bit complicated, but once we get through that, it is a pretty straightforward and stable software.

I did a training with them which was paid by my company. In terms of business, personally, I do not have any business with them.

I know there is Informatica and Semarchy. I am not quite sure if Salesforce does the same thing, but it can do that as well. I have not worked on any of them.

It provides significant time savings and helps with data management, particularly in how data is matched between other data to prevent duplicates. You can do matching with millions of records pretty quickly. That could save data and you can do it in real time as well. Through the indexing, we can access data quickly.

It is pretty integrable. With my clients, we have integrated it with multiple systems that gather data from external sources or internal sources. We can connect with APIs, REST API or SOAP APIs. It can get integrated and connected with other systems. It is a little bit complicated, but it gets the job done.

Good data modeling helps, and maintaining a purging process for unused data or closed data spaces is important. TIBCO EBX has an indexing mechanism that enhances performance in terms of searching, altering data, and accessing data.

Based on my current client and client feedbacks, I would rate TIBCO EBX an eight out of ten.

We are using TIBCO EBX for our data management solutions.

TIBCO EBX is our solution for Master Data Management for supply chain and commercials, which we use extensively.

Our organization mostly uses TIBCO EBX for data quality checks and governance processes, and many parts of it we do not even utilize match and merge functionalities because we have a single source system. We do not require to merge and create a golden record out of it, as we already have those checks on legal name fields that it is always going to be unique.

What I find most valuable in the TIBCO EBX solution is its customizability, which is the best thing about it.

The customizable data model feature of TIBCO EBX has helped in addressing the complex data requirements of our organization, as its customizability is not only limited to the UI functionality, but also provides extended functionality to use external APIs within the code on the data model level and workflow model level. You can utilize different script tasks to write your different level of code and also even use some built-in API connections. If you have your own API, AI APIs which you can utilize to fetch more difficult data and search outside of the TIBCO EBX to fetch the data directly without even going to a separate tool to do so.

We are talking about integration with different data sources and different applications within the APIs, and it is not only the different data sources; that is the basic functionality which it provides. When onboarding a supplier or any other customer domain data, and you want it to be integrated with some AI tool and automatically generate more data about it, you may only provide specific location detail, but you want to populate other details without manual effort. You can integrate it with Melissa address validations, and also you can utilize some AI tool. From the backend, you can call your AI agent, provide them the data, and they will search, make it a standard format, and provide you back in a systematic format, which you can utilize during your onboarding process, thereby reducing management workload.

Regarding collaborative workflows in TIBCO EBX that help synchronize our team within their organizational tasks, we apply different governance policies in the workflow models. We provide different kinds of permissions based on roles. Earlier, every person used to have every kind of access, either read or write. Now, a user needs a specific set of write permissions on specific values depending on another value. For instance, a financial user needs write permission only if a particular supplier is related to a specific supplier type, such as a remit address; then they can provide financial information and have update permission. Such specific complex logic can be provided by TIBCO workflow models, where you can write your own user scripts and customize them, or also write your own script tasks to automatically perform those actions. Based on user roles, you can provide different sets of permissions in the data model schema extension, available only in the workflow model based on their tracking information. Users will have different permissions depending on their specific step in the workflow, enhancing the advantages of TIBCO workflow model.

TIBCO EBX has the functionality of highly customizable models, but making changes requires going to the backend, implementing changes, and then restarting the server to affect those changes on the UI side. If that can be resolved, in the newer version of 6.2.1 and after, they have improved significantly by introducing JavaScript directly on the data model level. You can deploy the data model directly, import it into your upper environment, and publish that model without restarting. However, there are still issues in the indexes; sometimes, you are not able to see the proper record on the table level or the proper attribute name when you open a record. These kinds of challenges persist, as TIBCO EBX doesn't provide full access from the UI without backend intervention.

It has been more than five years since we have been working with TIBCO EBX.

I was involved in the initial setup of the TIBCO EBX solution.

The experience with the initial setup was straightforward because we were not using any MDM tool beforehand. We implemented everything from scratch based on requirements, but migrating from other tools would be challenging since TIBCO EBX still uses RDBMS databases while other vendors use a graph-based approach that offers more flexibility in data modeling.

I find TIBCO EBX generally stable.

There are stability issues, particularly when a huge volume of work items is run, whether it's a data load or multiple workflows launching. When over 3,000 users are active, we experience significant slowness in the environment. Sometimes, Lucene's indexes get corrupted, necessitating a restart and a cleanup of all indexes, causing downtime for our business side. These challenges are noteworthy.

Attempting to scale it up results in these stability issues.

Even if there are fewer stewards, while onboarding large data payloads through APIs, it creates slowness. When workflows are launched during this data load, it exacerbates the issue; users experiencing a slow system may repeatedly attempt to log in, refreshing the data, thereby creating multiple threads, again causing the system to slow down and potentially crash.

If I evaluate TIBCO EBX technical support, it depends entirely on the kind of support provided, as they have different packages. The type of package you have determines the quality of service. They usually don't provide gold support to most businesses, and most opt for silver support, which means waiting longer for responses. When we raise concerns, they occasionally take several days to inform us that there is a known bug fixed in a newer version rather than providing a hotfix, making it a pain because you have to migrate to the new version after experiencing issues, necessitating further changes in the data model.

Positive

Apart from TIBCO EBX, I have worked on two different tools as well, Stibo and Reltio.

The main differences between TIBCO EBX and the other products I worked with are that they're SaaS-based applications with less downtime during deployments, whereas on TIBCO EBX's side, deployment is a complex process requiring caution, as you must restart the server to see changes on the UI. Other tools also have limited functionality compared to TIBCO EBX, which offers better customizability in data models and workflows. However, when comparing pricing and SaaS capabilities, TIBCO EBX lags behind other competitors.

I cannot say anything about ROI, any return on investment, or cost effectiveness from the TIBCO EBX solution.

Advice for users looking to implement TIBCO EBX depends on their business use cases. If they are not concerned about downtime and have basic requirements, I'd recommend alternative tools. If they need complex functionalities, embracing automation, I think they should opt for this option if downtime isn't an issue, as you have more control and can enable more functionalities.

I would rate TIBCO EBX as a six or seven as a product, as a solution. The overall rating for this review is 7 out of 10.

The most common use cases for TIBCO EBX include creating data models, data spaces, data sets, workflows, REST services, triggers, constraints, value functions, schema extensions, and access rules. I have completed a POC for Match and Merge, though it wasn't a specific requirement. I have also used DAMA for POC purposes.

The feature I appreciate most about TIBCO EBX is the UI, which is quite simple and user-friendly. The data exchange add-on and the information search are quite helpful.

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.

I have been using TIBCO EBX for 3.5 years.

I have experienced lagging multiple times with TIBCO EBX, particularly when we upgraded from version five to six. During that time, we faced numerous production restarts. With complex data models or when there are more records and association tables, the system experiences noticeable slowness in loading records.

TIBCO EBX demonstrates excellent scalability. As its backend is Java, we can add various elements such as SQL and JavaScript, making it highly scalable.

I have contacted TIBCO's technical support and customer support. We have a Platform Support Team (PST) that handles these matters. Whenever we encounter issues, we directly raise a ticket with TIBCO.

Positive

I have not worked extensively with alternatives to TIBCO EBX, but I have conducted a POC on Reltio.

Learning to use TIBCO EBX was straightforward. Once you gain hands-on experience with each API and understand how it works, there isn't much difficulty in learning the system.

In my experience with Reltio, I found the UI to be richer. While TIBCO EBX has Match and Merge as an add-on, Reltio performs all data quality validations and Match and Merge automatically before creating a golden record when data comes from multi-system sources. These features are optional add-ons in TIBCO EBX, but they are built-in functionalities in Reltio.

I am not part of the PST team, so I have not been involved in that aspect. On a scale of 1-10, I rate TIBCO EBX an 8.

The solution is used for managing a Master Data Management tool. Instead of storing the data in the database, we are using this tool to organize the data based on the domain, such as organization reference, master data, and product-related information.

I am working as a support executive. We deploy a new feature every month and provide support for it. For the development part, I am not much aware of it. The developer develops it and gives us that file, and we deploy it on this platform.

In a database, we create the tables manually and set the data types while creating it, such as VARCHAR and integer. However, in TIBCO EBX, it automatically lists it out for us to select the data type we want to create for that particular table. Additionally, maintaining the access part is overall manageable; we have a separate section for maintaining access for different user groups, and we can segregate it based on this.

We have separate data models, such as organization reference. If we want to update the data for that particular domain, we can use that particular perspective. We have this workflow, and if we hit launch, we can access all existing data space. We add the new data and review it before submitting it for approval, so the reviewer can check what changes have been made.

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.

I have been working with TIBCO EBX for three years now.

We faced some synchronization issues at the back end. TIBCO EBX syncs the data at the back end as well. Since we have not yet completely moved into this tool, end-users still use the old system to consume the data. After updating the data, it syncs with another system too. At that time, we faced issues due to some stored procedure logic, but after that, we analyzed it and corrected the stored procedure.

We observe performance issues lately. If we perform any bulk update or use the bulk functionality to update the data, during that time, the index rebuild happens in the back end. The operations team faces issues, including downtime or slowness, and we monitor it, performing any required actions such as restarting applications.

TIBCO EBX is much better in terms of scalability. However, if multiple users are using it simultaneously, that could cause slowness in the application.

Before TIBCO EBX, we used MS Access as a front end to update the data, which synced the data with the database at the back end.

I have been involved in the initial setup process with TIBCO EBX.

We decided to switch to TIBCO EBX because we can organize the data, and it helps manage this data for an accurate and consistent view of the physical business data. When I compare it to MS Access, I'm not entirely sure, as I haven't used MS Access much.

Every feature will have different requirements; during every sprint, we implement different features based on business requirements and then push from non-prod to production environment.

I would advise other organizations considering TIBCO EBX that it is a new technology. This new tool can be used for data management perspective; unlike the old database, we are not heavily dependent on the SQL team for activities. Using TIBCO EBX, we maintain the application easily, ensuring high availability; if one goes down, we can activate the other one.

I'm only working with this one tool. On a scale of 1-10, I rate TIBCO EBX a seven out of ten.

TIBCO EBX us used for master data management.

What I find best about TIBCO EBX is its workflow modeling capabilities, which is a very good for a master data management tool. It has good match and merging capabilities, which are essential features in a master data tool. There are numerous out-of-the-box capabilities as well.

One aspect that could be improved in TIBCO EBX is the latency.

I have been using TIBCO EBX for few years now.

In recent times, I have not faced any issues with the stability of TIBCO EBX. In general, TIBCO EBX is a stable product.

It scalable and stable product.

The support team operates similarly to other support teams. You can raise a ticket with them and they should respond within a day or two.

I would rate their support a seven.

Positive

I have not used a different tool before using TIBCO EBX.

Regarding TIBCO EBX pricing  I'm unsure of this

TIBCO EBX is straightforward to use. Anybody with prior knowledge of using any web application can use it. It is essentially similar to filling out forms and submitting requests. On a scale of 1-10, I rate TIBCO EBX an 8.

Currently, we are using TIBCO EBX for MDM purposes. We get data from different sources and perform sanity checks on this data. Then we store and publish the data.

The features of TIBCO EBX are highly customizable, which is something I appreciated. We can customize every part of it. We can set where the labels appear, how they appear, and their order. We have all of these capabilities readily available.

We can implement rules, regulations, and constraints that are highly customizable. Everything is in Java, which could be considered a drawback. Currently, they are implementing some normal use-on-the-go rules, but most functionality remains in Java.

TIBCO EBX really helps because not everyone uses the same structure. Some use similar models, while others use different ones or might need changes in the future. We can have any sort of data model, any kind of data structure, table format, and we can reuse them. For instance, instead of a single country field, some might need multiple variables such as primary country and secondary country.

We can import data directly from files. If not, we can use SQL views or queries for importing. These are the main integration capabilities in TIBCO EBX.

The workflow functionality is excellent in TIBCO EBX, including the UI. In workflow, we can have multiple steps and implement rules and regulations within the workflow itself. If something is incorrect, specific actions can be triggered. This helps data stewards by implementing sanity checks that can throw errors or redirect the flow, preventing incorrect data from being populated.

The UI has improved, and while the matching scenario still has some challenges, it performs better than before.

TIBCO EBX can be challenging to handle due to its customizability. While it is good to use, it is not particularly easy to use. We still somewhat struggle to implement new features or use something on the go, though things are improving gradually.

TIBCO EBX has performance issues, particularly with speed. Replicating data can take several hours even with normal median data. When multiple users are accessing data and if a particular table contains more than 15 million records, the system struggles. These issues might be resolved by increasing RAM or improving performance, but there is still room for improvement. It was worse in version 5.9, but version 6 shows some improvement.

Previously, there was a relational model in data spaces directly connected to TIBCO EBX and the UI. Now that has been removed and replaced with a semantic model where everything is encrypted by TIBCO EBX by default. For replication, we need to use an additional module.

However, they are making positive changes regarding permissions and the UI has significantly improved compared to previous versions. They have announced plans to introduce new features such as parallel import and parallel jobs.

I have been working with TIBCO EBX for four years.

The initial setup of TIBCO EBX presents challenges when there are multiple modules that need to be transferred between environments. There is no straightforward method for transferring permissions and configurations. We need to use staging modules for this purpose. While this setup process can be time-consuming, it is typically a one-time task per environment.

TIBCO EBX is stable, though there are occasional bugs. When these are reported to the company, they work on resolving them and release new versions.

TIBCO EBX requires additional RAM for scaling, and performance can be slower when scaling up.

I would rate the technical support and customer service of TIBCO EBX 3.5 or 4 out of 5.

Positive

We have been using TIBCO EBX from the beginning, starting with version 5.9 before upgrading to version 6.

The initial setup of TIBCO EBX presents challenges when there are multiple modules that need to be transferred between environments. There is no straightforward method for transferring permissions and configurations. We need to use staging modules for this purpose. While this setup process can be time-consuming, it is typically a one-time task per environment.

I cannot provide a proper comparison as I am not familiar with other products.

TIBCO EBX can be challenging to handle due to its customizability. While it is good to use, it is not particularly easy to use. We still somewhat struggle to implement new features or use something on the go, though things are improving gradually.

I am working with the on-premises version of TIBCO EBX. While I am not familiar with the exact pricing, I know that TIBCO EBX is positioned in the higher end of the market.

I would recommend TIBCO EBX for organizations that require extensive data customizations. However, if the data structure is simple without complex requirements, TIBCO EBX might not provide significant additional value.

On a scale of 1-10, I rate TIBCO EBX an 8.

TIBCO EBX comes with the capability to capture business metadata. 

The tool's UI is good and easy to understand. 

The tool has to improve mapping and workflow. It should be made more robust. 

I have been using the solution for one year. 

TIBCO EBX is stable. 

I rate the product a six out of ten. My company has around 100 users for the product. We have plans to increase usage since we will roll out tools in more countries. 

TIBCO EBX is cheaper than Informatica. 

I rate the product a six out of ten. 

We are using TIBCO EBX for the data governance of our accounting system.

TIBCO EBX has centralized several master data tables, which were very often in private Excel sheets of accountants. With EBX it was possible to put a data governance process for the core accounting application, which was otherwise not possible.

The most valuable features of TIBCO EBX is its completeness. Everything can be done inside the tool, including data governance. We are able to model everything according to the needs of the company. If the company needs five people to agree to a change in data, they can do it with TIBCO EBX. They can model it with any particular rules. Additionally, there is dynamic data modeling, workflows editing directly using the GUI that comes from the server.

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.

I have been using TIBCO EBX for approximately three years.

Sometimes it's a problem of how people implement the TIBCO EBX solution. Elementary errors can potentially cause long-term instability of the system, We have had some issues with performance because of this.

I was not only working as a business analyst, but I was also programming with TIBCO EBX. TIBCO EBX is not always scalable, because if you start to process high amounts of data, you need a better UI. You can only display a limited amount of data on the screen. For example, 100 rows on the screen. If you have a lot of rows on the screen it's taking a long time until it gets displayed. There are some things, such as background validation that, at a certain point, have to be turned off because over a certain amount of records it slows down the system. However, it takes more than 30,000 to 40,000 records per table to start to have problems.

We have a preferred line to TIBCO EBX for support. Their response is very good but their efficiency could improve.

I rate the support from TIBCO EBX a four out of five.

Before, the accountants were using custom excel sheets individually maintained. 

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 would advise others that are wanting to implement TIBCO EBX they should try to build the data model from the beginning until the end. Take the time that they need, try to build as much as possible in the data model. It is best to build the workflow that they want at the beginning. They have to decide if they want history or data governance, or exactly which other part they want. It is important to build what they have and want on paper regarding the functionality of their core system before implementing it into TIBCO EBX. 

I rate TIBCO EBX a ten out of ten.