Most Helpful Review
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
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 most valuable feature is the Salesforce integration.
The architecture based on events has several connectors which allow integration from external and internal applications of the company.
Scalability and load balancing.
We can use Java expressions anywhere in the flow.
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.
In our landscape, we have a lot of AS/400s or iSeries and SEEBURGER Business Integration Suite (BIS) has a file service listener that allows data to seamlessly be transferred between the SEEBURGER solution and the AS/400.
Among the most valuable features are the EDI translator and a lot of the components which enable creating compliance sets. Having something standard out-of-the-box and being able to use that has been a huge benefit for us.
Another aspect that we employed in the last year-and-a-half has been their CMA platform component, which hooks to the SEEBURGER Business Integration Suite (BIS) front end. We've been able to set up an automatic testing process for our partners.
One valuable feature is the scalability. We have not had to add processing power or hardware since we installed it. Also, we are able to create and deploy maps to migrate from another EDI platform very quickly.
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 Anypoint platform consumes a lot of memory, and it would be great for developers if it were more lightweight.
The payment system needs improvement.
Limitation on external subscribers to listen to the messages on the bus.
It needs more samples. Also, the dependency on Maven should be removed.
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.
They made improvements to the email error alerts that go out, for the EDI technical. Those typically go straight out to the partners. Those messages are significantly clearer and easy to read. The same messages in the front end are not nearly as clear. It's supposed to be the same error, but the message that goes out for EDI is really easy for anybody to read and understand, but you have to be really solution-savvy to understand the message in the system itself.
Some of the functionality for retriggering documents, where you have to step through a termination process and then retrigger it, versus just being able to restart or retrigger more easily, is a bit challenging, depending on the scenario.
A true debugger that allows you to step through the process would be a good improvement. Right now, we are limited to reading the log file generated by the test screen in Mapping Designer.
I would've liked, from day one, to learn how to do my own mapping. That would have saved a lot of time and effort if that had been brought forward earlier. It's there, I just didn't know about it. Also, some tidier, easier-to-use interfaces would help.
Pricing and Cost Advice
The various features and components for this solution are no longer free.
Plan your licensing model (cloud or on-premises or hybrid) that will allow seamless integration with new partners.
This is expensive. In my next project, we had to go to other vendor.
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...
Sometimes it seems a little pricey, especially when some of the stuff is available through freeware, like SFTP communications... It costs a lot more money to buy this stuff from SEEBURGER but I think it's worth it in the long run.
Pricing has always seemed fair.
I find the pricing expensive. But I know that when we evaluated another company, it was about the same. That just seems to be the market. It's probably not expensive overall.
The pricing is cheap. In fact, when I saw the pricing, I thought, "Really? What's the catch?" But the functionality that we get out of it, for the price we pay, is great value.
out of 24 in ESB
Average Words per Review
out of 31 in Business-to-Business Middleware
Average Words per Review
Compared 25% of the time.
Compared 23% of the time.
Compared 10% of the time.
Compared 25% of the time.
Compared 21% 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|
Financial Services Firm21%
Software R&D Company17%
Software R&D Company13%