Most Helpful Review
Researched Mule ESB but chose Mule ESB: Easy to implement and supports platforms like Windows, Linux, and Mac
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
The most valuable feature is the Salesforce integration.
The most valuable feature of Mule ESB is data transformation, i.e. our interacting with different systems and orchestrating for our business needs.
Once it is started, we don't see any problems on a day to day basis.
The most powerful feature is DataWeave, which is a powerful language where data can be transformed from one form into another.
The architecture based on events has several connectors which allow integration from external and internal applications of the company.
I like that the tool has all the adapters — all the possible protocols that are in the industry. You pay for those adapters but at least it's all in one package. You don't have to get another tool or application to support another partner.
When orders come in they go into our ERP system directly, so there is integration there.
It's the reliability. And the message tracking is quite good, where we can go in and see if we have an issue.
The solution's capabilities in fulfilling our existing B2B integration requirements are brilliant. Among our multiple customers we connect to SAP systems, JDE, all the various ERPs that you can possibly get, Oracle procurement systems, etc. We haven't come across anything yet — and customers are trying to trip us up — that we can't do.
SEEBURGER Business Integration Suite (BIS) has been good at communicating between two applications, changing formats and using the required protocols... We can have one site communicating in an old FTP or SFTP style, or via file transfer. And with other applications, we could have API or a web service call or some other protocol used to send information.
What would have been a manual process of transmitting data items around between us and third-parties has been automated. SEEBURGER BIS handles the automation and mapping side of the communications. The automation, along with the efficiency around time and cost, has improved our organization. Around 20,000 messages a month have been automated. These typically would be financial/order transactions and confirmations in invoicing that have been automated.
One of the things that SEEBURGER always touts is their ability to do "any to any" formatting... it doesn't matter if you want to take a CSV file or an XML file or a flat file or a PDF file or a structure EDI file; you can transform it from one format to another - any to any or even to the same format - which is a really nice feature.
The Anypoint platform consumes a lot of memory, and it would be great for developers if it were more lightweight.
Mule ESB is more into the latest REST APIs, not much into the SOAP web services. Developing is all about web services and not easy with Mule.
We would like to have a built-in logging framework in which we can do auditing.
I would like to see support for BPM in the next release of this solution.
The payment system needs improvement.
It's rather difficult to understand, from the application, what's broken and why it doesn't work. We typically need to get support from them directly, and it's usually in a consulting role, to fix issues.
There might be some improvements they could make to the portal, but they're not anything that stops me from working.
We don't have much access to the logs or what's happening. So we have to log a ticket with SEEBURGER. We only get a message that something has failed... we have to open a ticket with SEEBURGER for them to tell us exactly what the issue is... I would like us to be able to be more self-sufficient.
There are some aspects at the front, the actual queries that you use, that could be improved. They're all very minor to be honest.
We wanted to use API. We were told that in 6.52 we could use API management. Later on, we found that API management wasn't that completely integrated into the 6.52 solution, and if you wanted to have the whole API suite you might have to go to 6.7, the latest one.
The speed of development needs improvement. If you acquire any customization, it can be a slightly slow process. I would like to see more flexibility around customizations. The time frame right now depends on the sophistication and customization, but we have to go through a process of getting them to develop, implement, and test it. This might take a couple of weeks. If it was a simpler system to customize, the time could probably be cut by half or down by even 25 percent of what it would normally take.
The BIS Front End needs a little bit of refreshing, especially when it comes to setting up new trading partners and trading partner agreements or transactions. It can be a bit clumsy to copy and rename and then go in and modify.
On the server side, there are a lot of administration and configuration files that you need to go in and do maintenance on. You have to find them in a certain folder so it's very error-prone and it can be a little time consuming unless it's documented. They could pull some of those individual configuration files into the product itself where there's a better user interface for that.
Pricing and Cost Advice
The various features and components for this solution are no longer free.
We pay maintenance of between $75,000 and $100,000 per year, per box.
There is a standard agreement for the messaging every month. But if we make a change request — a change to a mapping or something like that — then there is a fixed price per hour.
We pay per message we use. We spend about £19,000 a year with them.
On an annual basis, our support costs, which are based on the licensing, are about £120,000.
The cost-based model is slightly different now in SEEBURGER Business Integration Suite (BIS). They changed the licensing, based on adapters and other things. In the old style of licensing, the whole suite was one license...
Our licensing model is based on transactions. We have a base service contract which is priced against a volume of transactions and another volume of individual transactions, which are covered by one service agreement. Then, we have development services on top of that. Our annual spend is around £80,000. It's about mid-priced, as there are some cheaper alternatives out there and some more expensive ones. It's neither cheap nor expensive. It's somewhere in the middle.
We have additional ad hoc development costs, but those vary depending on if we're bringing on another third-party into our systems via the EDI integration. So, that's highly variable.
All the new adapters are individually priced, which is good. You don't buy the whole system and then if you don't use it, you don't use it. You only buy the stuff you want...
out of 24 in ESB
Average Words per Review
out of 31 in Business-to-Business Middleware
Average Words per Review
Compared 27% of the time.
Compared 23% of the time.
Compared 11% of the time.
Compared 23% of the time.
Compared 20% of the time.
Compared 13% of the time.
Also Known As
|Seeburger Business Integration Suite|
|For companies looking to modernize and unlock the value of existing on-premises systems and applications, an enterprise service bus (ESB) architecture serves as a critical foundation layer for SOA. When deployed as an ESB, the Mule runtime engine of Anypoint Platform combines the power of data and application integration across legacy systems and SaaS applications, with a seamless path to the other capabilities of Anypoint Platform and the full power of API-led connectivity.|
The SEEBURGER Business Integration Suite (BIS) is a central platform for all integration activities. It enables you to respond easily, rapidly and innovatively to your digital transformation challenges:
Learn more about Mule ESB
Learn more about SEEBURGER BIS
|Ube, PacificComp, University of Witwatersrand, Justice Systems, Camelot||Altis, Autoliv, Cebi, Cofresco|
Software R&D Company34%
Financial Services Firm9%
Comms Service Provider8%
Software R&D Company30%