Notifications
Notifications
CDW Logo

Proline Linksys MFEBX1 Compatible SFP TAA Compliant Transceiver - SFP (mini

Mfg # MFEBX1-CDW CDW # 2456831

Quick tech specs

  • SFP (mini-GBIC) transceiver module
  • 100Base-BX-U
  • up to 12.4 miles
  • 100Mb LAN
  • LC single-mode
  • 1550 (TX) / 1310 (RX) nm
View All

Know your gear

Proline Linksys MFEBX1 Compatible SFP TAA Compliant Transceiver - SFP (mini-GBIC) transceiver module - 100Mb LAN - 100Base-BX-U - LC single-mode - up to 20 km - 1550 (TX) / 1310 (RX) nm.

This item was discontinued on October 06, 2022

Enhance your purchase

Proline Linksys MFEBX1 Compatible SFP TAA Compliant Transceiver - SFP (mini is rated 4.20 out of 5 by 11.
Rated 5 out of 5 by from Beneficial flexible data models, effective GUI workflows, and feature rich application What is our primary use case? We are using TIBCO EBX for the data governance of our accounting system. How has it helped my organization? 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. What is most valuable? 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. What needs improvement? 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. For how long have I used the solution? I have been using TIBCO EBX for approximately three years. What do I think about the stability of the solution? 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. What do I think about the scalability of the solution? 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. How are customer service and support? 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. What's my experience with pricing, setup cost, and licensing? 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. What other advice do I have? 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. Which deployment model are you using for this solution? Private Cloud Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-03-28T00:00:00-04:00
Rated 5 out of 5 by from Scalable and customizable but needs to offer better performance What is our primary use case? We are trying to achieve is to have customer vendors fill in various master data. It will be used across the enterprise and will be used for sourcing from a different data sources. Currently, we are working through this process and providing master requests. What is most valuable? The match and merge features are very good. They help for, for example, validating visas. We also use a lot of add-ons. The data quality is very good. The solution is stable. You can customize the product. It can scale if you need it to. What needs improvement? 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. For how long have I used the solution? I've been using the solution for the last two years or so. What do I think about the stability of the solution? The performance could be better. We're not 100% happy with it at this time. That said, it is a stable product. What do I think about the scalability of the solution? We have more than 48 users at this time. The solution is scalable and customizable. How are customer service and support? While I haven't been in direct communication with technical support, we do have teams that are able to reach them if they need to. How was the initial setup? The initial setup can be a bit difficult. It's not easy to configure it actually. We need some experience and configuring it right now is an issue. It's not so easy we can start using it on day one. The process is complex due to the level of customization. The deployment process was long. It took us about three months in total. There is a bit of maintenance required. It's periodical. It may require patching every once in a while, for example. What about the implementation team? We had a third-party vendor that helped us implement the product. What's my experience with pricing, setup cost, and licensing? I don't handle any aspect of the pricing or licensing. I'm not sure how much the solution costs. What other advice do I have? We're a customer and an end-user. Currently, we are one version behind. We're going to upgrade to the latest version maybe in two months, however, I'm not sure of the exact date. I'd advise new users to ensure they understand the scope of their implementation and applicability in their observation. I'd rate the solution at a seven out of ten. Which deployment model are you using for this solution? On-premises Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2021-10-23T00:00:00-04:00
Rated 5 out of 5 by from An MDM tool that offers stability, scalability, and an easy setup phase What is our primary use case? I use TIBCO EBX as an MDM tool in my company. What is most valuable? REST API interfaces can be considered to be the best feature of TIBCO EBX. The tool offers a good user interface. What needs improvement? 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. For how long have I used the solution? I have been using TIBCO EBX for eight years. What do I think about the stability of the solution? It is a very stable solution. What do I think about the scalability of the solution? It is a scalable solution. There are thousands of users of the solution in my company. If we want to expand the use of the solution in our company, then we can create space for any number of users we want. How are customer service and support? I am a part of the tech team in my company, so I am responsible for providing technical support to my company's clients. Which solution did I use previously and why did I switch? My company has past experience with other solutions in the market. How was the initial setup? TIBCO EBX follows the simple and standard Tomcat architecture and deployment, so it is easy to set it up. The solution can be deployed in two or three days. You can deploy the tool in a development environment within a few minutes, in less than an hour. For a production environment, the deployment phase takes two or three days. You need a skilled admin in your organization to take care of the deployment phase of TIBCO EBX. The solution is deployed on the cloud and on an on-premises model. What's my experience with pricing, setup cost, and licensing? My company's clients negotiate directly with TIBCO when it comes to the cost attached to the licensing part. Which other solutions did I evaluate? My company did evaluate other options against TIBCO EBX. What other advice do I have? I am the person who is responsible for caring for the deployment process for my company's clients, and I have noticed that most of my clients have been moving to TIBCO EBX from other solutions. I recommend the solution to those who plan to use it. I rate the overall solution a ten out of ten. Which deployment model are you using for this solution? Hybrid Cloud Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2023-11-10T00:00:00-05:00
Rated 5 out of 5 by from A good master data management solution that gives complete functionality control to the user, but lacks in community support resources What is most valuable? This solution allows the user to have complete control, and is 100% customizable. Plus, this gives us a multi-domain tool. Meaning that we can manage both our own, and our customers product, and create interlinks between them, letting us analyze the data more easily. What needs improvement? 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. For how long have I used the solution? We have been working with this solution for six months. What do I think about the stability of the solution? The latest version of this solution has increased the stability of the product, and removed the need for higher-spec hardware. What do I think about the scalability of the solution? This solution allows for horizontal scaling, where more machines are added, or vertical scaling where data is transferred to a larger host machine. Which solution did I use previously and why did I switch? We switched to this solution because the level of control available is higher than other comparable products. With this solution you have access to 100% of the functionality and unlimited configuration availability. Also, you are not restricted with the OEM for this. That means you can do your own upgrades, without the need for the vendor to be involved. How was the initial setup? The initial setup for this solution is very easy, with the setup and deployment takes less than a day to complete. What's my experience with pricing, setup cost, and licensing? 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. What other advice do I have? We would recommend this solution to enterprise sized companies, as well as midsized organizations that have sufficient available budget. There is also a cloud-based version of this solution, however, the on-premises version allows for greater control over the data environment, and so may be preferable for certain geographical locations. I would rate this solution an eight out of ten. Which deployment model are you using for this solution? On-premises Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2022-11-06T00:00:00-04:00
Rated 5 out of 5 by from Beneficial workflow and good interface What is our primary use case? I am using TIBCO EBX to build a business and administrator EBX tool. What is most valuable? The most valuable features of TIBCO EBX are the workflow and interface. What needs improvement? 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. For how long have I used the solution? I have been using TIBCO EBX for approximately five years. What do I think about the stability of the solution? The newer version of TIBCO EBX is not stable. However, the older version is stable. What do I think about the scalability of the solution? TIBCO EBX cannot scale vertically. We have approximately 20,000 people using this solution in my company. We have approximately 26 domains and every domain has an administrator. Which solution did I use previously and why did I switch? I previously used Semarchy xDM. What's my experience with pricing, setup cost, and licensing? TIBCO EBX is a very expensive solution. There is an annual fee to use the solution. What other advice do I have? I rate TIBCO EBX an eight out of ten. We have four administrators that maintain the solution. Which deployment model are you using for this solution? Public Cloud If public cloud, private cloud, or hybrid cloud, which cloud provider do you use? Google Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2022-10-23T00:00:00-04:00
Rated 5 out of 5 by from Highly customizable and good Data Modelling feature, stable workflows but performance is below par What is our primary use case? We have multiple sets of data coming in from various upstream systems, SAP being one of the main and most dominant systems. We have non-SAP as well, such as Microsoft systems, Oracle Database, and some other legacy databases. We need an MDM tool where we can merge the data and get the main records out of it after merging and matching everything. The tool has merge and match features and allows us to get the golden record out of it as a single source of truth and then use it as a master of our data, as a Master Data Management tool. We also stored the Data Governance Rules using the information Governance Add On. How has it helped my organization? We have used EBX to collate data from multiple source systems, a majority of them are SAP systems to create and update the Master Data and Reference Data. Also to to perform the Match and Cleanse activities and then store the set of Golden Records to feed the various downstream BI and ML systems. What is most valuable? The product is highly customizable. The product is extremely flexible. The Data Model view and compare feature. The Workflow once created is very stable. If not much customization is needed the product overall is quite stable and runs consistently. They are working at adding in match and merge capabilities in future versions . There is also an expected good amount of improvement on the UX . What needs improvement? 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. For how long have I used the solution? We have been using the solution for three years at this point. Initially it was fitting our Bill as the SAP data was handled separately at that time using SAP MDM and MDGM. What do I think about the stability of the solution? The tool is quite stable and very rarely goes down or crashes. What do I think about the scalability of the solution? The solution doesn't scale as well as we would expect. Although it has some dependency on the underlying database but still we would expect better MPP features and also the tool should be able to optimize the underlying clusters more effectively. How are customer service and technical support? As our SI partner interacted and we did not interact directly with the TIBCO support we would not be able to comment on this. As our SI partner takes care of the further upgrades and patches so we would not exactly know about the effective of TIBCO's support as the SI themselves handle that. But at times we felt that it could have been a bit faster. How was the initial setup? The initial installation is not very complex, however, it was not extremely straightforward either. Our SI partner did it for us and it was on time. Also after the initial installation and configuration we were happy with it overall. What about the implementation team? We implemented it though our SI partner who are preferred Implementation partner of TIBCO. What's my experience with pricing, setup cost, and licensing? This is one area where I think EBX scores well. There licensing is quite straight forward. Which other solutions did I evaluate? As we are not totally happy with this product in the present scenario, we've been looking into alternatives that may be better suited to our needs and the needs of the company. We are trying to shortlist tools at this time. We're doing some research around it right now from both ease of implementation and Use and Licensing terms. What other advice do I have? We're just customers and end-users. Whether I would advise another company to choose this solution or not depends a bit on the use case they are going to develop. I would say that, if a company has a basic use case, a basic means of getting data from a few sources like Oracle, SQL Server, Teradata etc., then maybe it is sufficient. However, if you are having an enterprise-level situation for SAP or Oracle Apps , it might scale up that well. Performance is also an issue as it does not optimize the underlying clusters to a great extent as compared of its competitors. One good thing is that, with the data model, you can just go and see the data model very well, to the most granular level and identify if there are any gaps. It also has a rich compare data model feature. However, again, for the workflow, you cannot edit it in the visual editor. You have to go back to that tree setup and there after complete editing during compile only one would be able to see if any errors has crept in or not. Having said that I would say the Workflows once created are very robust. There are some competing tools that allow the editing of workflows in the visual setup itself. That is very easy for users. If you can edit it in the visual setup, you can directly see the impacted upstream and downstream tasks or jobs in that workflow and conflicts if any. This speeds up the updating of the workflows by the data engineers or data stewards. I'd rate the solution at a six out of ten. The solution is average from an enterprise standpoint. Which deployment model are you using for this solution? Public Cloud If public cloud, private cloud, or hybrid cloud, which cloud provider do you use? Amazon Web Services (AWS) Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2021-07-25T00:00:00-04:00
Rated 5 out of 5 by from Offers good policies and has many possible use cases What is our primary use case? There are a lot of possible use cases for this Master Data Management tool. What is most valuable? In terms of most valuable features, the policies are really good. What needs improvement? The support isn't great and takes too long. And the pricing can be improved. For how long have I used the solution? I have been using TIBCO MDM for two years. What do I think about the scalability of the solution? We have 510 people using the solution. How are customer service and technical support? In terms of technical support - it can be improved. I would give support a 7 out of 10. How was the initial setup? The initial setup is not too complex, it's okay. It is medium complexity. What other advice do I have? I would advise interested people that you need to understand what it is used for, what the use cases are. It takes money and effort, but it could be very good for you. On a scale of one to ten I would rate TIBCO MDM a nine. Which deployment model are you using for this solution? On-premises Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2020-02-18T00:00:00-05:00
Rated 5 out of 5 by from Good workflow models and pull-down lists with very good data modeling What is our primary use case? We're using the solution for reference data, master data management. To basically implement data governance around the reference data. One of the big initiatives is to capture all the information that the branch operations team is looking to capture. Or operational information or reference data. We're a credit union. We're like a bank. It's all about managing the data of the branches, and the ATMs, and some of the business partners that are at the branches. How has it helped my organization? There used to be a lot of handholding by ISD. This kind of solution gives control to either ISD or business units to do what they need to do. We don't have to play the game of telephone or do any handoff. We don't have to specify "Here's what I want" and then get it translated unnecessarily by the ISD people that don't understand the business. That's why the business is entering the information. They're verifying the information for files or tables or whatever that aren't really controlled by that department. Then the ISD can kind of step in as custodians and handle some of that for them. Typical stuff like stuff that's sourced externally - like an ISO country table. They don't want the department saying that there is such and such a country, and adding to the country table. We basically want to pull it from the internet, from the ISO International Standards Organization, and say, "These are the official, full list of countries and country subdivisions," which are states and provinces and such. What is most valuable? The data modeling is very good. It creates for you a GUI interface, which are the forms that the stewards would fill out to add or modify data. That works fairly well. I like the features of that, especially with regard to the product key relationships, which result in pull-down lists in the forms. The workflow models are great. We use them a lot. It's text-based and you can basically add different kinds of steps right into the workflow. There are different parameters for each kind of step. What needs improvement? 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. For how long have I used the solution? I've been using the solution for almost two years now. What do I think about the stability of the solution? We just recently ran into an issue in one of the test environments. The jury is still out on stability. It's been fairly good and pretty reliable. I believe I haven't seen the system come down on production really, other than when some of the teams involved make mistakes on rolling out the next deployment. It gets a little rocky if they don't know what they're doing, however, that's just an operations issue. What do I think about the scalability of the solution? The scalability may be somewhat limited. Basically, the application is designed to run on a single application here. You can have it hooked to various different databases. It works with Oracle or SQL Server. We implemented a SQL Server. SQL Server itself is not horizontally scalable. You can't add servers. They're just replications. It's good for high availability, however, not for scalability. That said, it also can run in SQL Azure, and SQL Azure in my understanding is scalable both vertically and horizontally. The tool is not limited. On the database tier, the database isn't limited. It's only limited by your implementation choice. If we're in Oracle or SQL Azure, we can scale. For reference, data is probably not that relevant because it's relatively small volumes in the grand scheme of things. However, for the application, if we rolled this out across the organization and had a lot of activity, we could get into potential trouble as you can't run with load balancing and such. You basically have an active-passive failover. You have some high availability and not the scalability of the applications. That could be designed in various ways. We haven't tried that yet. We only have a handful of people who have access to the solution. They're either stewards such as subject matter experts or they are some kind of reviewers, approvers, overseers. There are also developers that are functioning like admins. There are two main departments that are using it currently. How are customer service and technical support? When it comes to technical support, most of the challenges have been at development time on production, and therefore we haven't really had much opportunity to test their response in a production outage situation. However, in development, it's a lower bar. Sometimes we don't get a quick response. It depends on who is helping us, who's been assigned to support us. Some guys have been great and other guys are out of office and they don't seem to have anyone backing them up and we need to wait for them to return. We don't know what the answer is. Sometimes getting answers has been challenging. The technical support is average, or slightly above. On a scale from one to ten, I'd rate them somewhere between five and seven. We had a contact that was really good and then, after the acquisition, when Orchestra sold to TIBCO, TIBCO started migrating some of their functionality to direct with some of their other products. Things shifted a bit and after they were solidified, with COVID, they've cut resources and we've ended up losing one of the good resources that was giving us pretty good answers to technical challenges. Which solution did I use previously and why did I switch? We didn't really use a different solution previously. For data governance, we used some homegrown stuff, basically. We're still doing that in some areas. How was the initial setup? The initial setup can be a challenge due to the fact that there is not enough examples to model after. There isn't enough documentation to go off of. They gave us some templates and things to work from, and that helped those artists. We also had to dumb down some of the templates and start from almost scratch to kind of get the workflow actually working. It would be great if there were some standard items to work off of. It would be nice if there was a bigger community where you could share ideas with other customers about the product. The deployment took a while. We were refocused three times on different aspects. Then there were multiple organizational changes, department changes, et cetera. The first production implementation took almost a year. After that, we've probably handled seven or eight subsequent releases. We're rolling out to different grou... Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2021-04-03T00:00:00-04:00
Rated 5 out of 5 by from The support is fast and good, and the program is user-friendly What is our primary use case? I use this program in my work in the pharmaceutical industry. We develop projects around a product master in the company. What is most valuable? The program is very user-friendly and the .com order is easy to design. What needs improvement? 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. For how long have I used the solution? I have been using Orchestra Networks EBX for three years now. What do I think about the stability of the solution? We haven't had any issues or technical problems so far, so I believe the program is stable. How are customer service and technical support? The technical team takes care of the customer and they usually responds quickly. I think we are very satisfied with the support. How was the initial setup? The initial setup is easy and straightforward. What's my experience with pricing, setup cost, and licensing? The solution is not that expensive because we use JavaScript sometimes for specific developments. What other advice do I have? This is a rather technical solution and you must know that it takes some preparation before you can start working on it. In the future I would like to have a clean proof of the design of the data modem. It should be easy and visual. I will rate the solution an eight out of ten because I think there are some things to improve and that could be better. Which deployment model are you using for this solution? On-premises Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2019-11-20T00:00:00-05:00
Rated 5 out of 5 by from Everything is in one place, is easier to use, and it has good API features What is our primary use case? I am a consultant, my job is to implement this solution. I deploy the on-prem and cloud models. What is most valuable? The API and the data model are very valuable features. What needs improvement? In terms of improvements that this solution needs, it should support big data. For how long have I used the solution? I have been using this solution for three years. What do I think about the stability of the solution? It's extremely stable. What do I think about the scalability of the solution? It can scale, you need the scalability. How are customer service and technical support? They provide very good support. Which solution did I use previously and why did I switch? I previously used several solutions but I couldn't find all the solutions in one place, so I had to piece together lots of separate systems to do the same thing. Now EBX does everything for me. I used the hybrid model but I switched because EBX does everything. Everything is in one place and easier to use. How was the initial setup? The initial setup is a little complex. It's not something that users can just quickly do themselves. What about the implementation team? I am the consultant that does the deployments. What's my experience with pricing, setup cost, and licensing? I'm just involved in technical, but I understand that its pricing is similar to HP so it is quite expensive. What other advice do I have? I would recommend this solution to others who are considering it. I would rate it a ten out of ten because it's the best. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2019-08-08T00:00:00-04:00
Rated 5 out of 5 by from Captures business metadata and comes with good UI What is our primary use case? TIBCO EBX comes with the capability to capture business metadata. What is most valuable? The tool's UI is good and easy to understand. What needs improvement? The tool has to improve mapping and workflow. It should be made more robust. For how long have I used the solution? I have been using the solution for one year. What do I think about the stability of the solution? TIBCO EBX is stable. What do I think about the scalability of the solution? 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. What's my experience with pricing, setup cost, and licensing? TIBCO EBX is cheaper than Informatica. What other advice do I have? I rate the product a six out of ten. If public cloud, private cloud, or hybrid cloud, which cloud provider do you use? Amazon Web Services (AWS) Disclaimer: I am a real user, and this review is based on my own experience and opinions.customer
Date published: 2023-10-11T00:00:00-04:00

This page was printed on 4/24/2024 8:09:59 PM.