We performed a comparison between SEEBURGER Business Integration Suite and webMethods API Gateway based on real PeerSpot user reviews.
Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."For the tool that we used to have, we had specially trained developers who used to do all the development of EDI maps and the configuration. But with SEEBURGER Business Integration Suite (BIS) now, we were able to train our EDI analysts, and because the tool has very simple, intuitive mapping capabilities, even our EDI analysts are able to develop all the EDI maps, do all the configurations, and do all the setups for any of the trading partners."
"We can use it to script and monitor processes."
"The entire framework is something that is very easy to use, easy to set up, and extremely straightforward. Once you develop a process and once you get it deployed within the process engine, with the latest 6.52 features, the processing engine is actually smart enough to make a decision as to which process engine has less load, and it can exchange messages with that process engine."
"We use Message Tracking, which is a very good feature. Message Tracking has about 300 to 400 business people who can find documents and ask the integration team about them. For example, they looking for a document that the vendor or trading partner tells them that they sent, but they don't see it in the ERP system yet. So, they go to SEEBURGER Message Tracking, which can tell them if we received it already from the outside and what happened, e.g., if it went to SEEBURGER BIS or if it's already in the ERP system. It's a very simple tool to use. They also can use that tool to see the source document."
"The tool's performance doesn't get affected by transformation loads. You can write any number of rules, filtering criteria, transformations, etc."
"Mapping Designer provides excellent flexibility."
"We rarely get hanged processes."
"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."
"The cloud version of the solution is very easy to set up."
"This solution has given us a competitive advantage because we have better automation and insight."
"The developer portal is a valuable feature."
"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."
"The most valuable aspect of this solution for me has been the configuration-based UI. Once you get the hang of it, it enables you to easily develop an API. In addition, it has many in-built policies that are quite handy."
"Within the new version, webMethods API Gateway gives us an end-to-end lifecycle from the creation of the API up into the development, deployment, and promotion into production/live. The current end-to-end lifecycle of the API gives us enough authority and governance of the API. We know what are currently live services, what is in the testing stage of development, and what version that has been commissioned. So, the full life cycle itself gives us full authority and governance of the API."
"I like the solution's policies, transformation, mediation, and routing features."
"It's a good tool, and it has a stable messaging broker."
"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."
"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."
"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."
"I would like there to be a feature that could handle the limited server."
"API connectivity needs improvement as well as the GUI. The GUI hasn't changed that much in 10 years, but of course, that's already been updated. I would say I'm excited about the screenshots but that's about it."
"The integration is not so excellent. While I'm not saying there is a problem, there is no pattern. When we start a new project, we have to work with new people and processes every time. The technical side of their system is very good, but their change process is not repeatable. It needs to be rebuilt each time."
"Java is very old technology and they should move away from it, to anything that's better."
"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."
"It is an expensive solution and not very suitable for smaller businesses."
"The price has room for improvement."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
"They should develop clear visibility for the onboarding."
"In terms of improvements, maybe on the API monetization side, having users able to create separate consumption plans and throttle all those consumption plans towards the run time could be better."
"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."
"With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."
"Understanding the overall architecture is difficult."
More SEEBURGER Business Integration Suite Pricing and Cost Advice →
SEEBURGER Business Integration Suite is ranked 19th in API Management with 37 reviews while webMethods API Gateway is ranked 12th in API Management with 9 reviews. SEEBURGER Business Integration Suite is rated 8.4, while webMethods API Gateway is rated 8.0. The top reviewer of SEEBURGER Business Integration Suite writes "Gives us the flexibility to hook up to systems using any protocol out there". On the other hand, the top reviewer of webMethods API Gateway writes "We developed several services in the cloud using a sandbox environment for our last hackathon". SEEBURGER Business Integration Suite is most compared with SAP Cloud Platform, IBM Sterling B2B Integration Services, Mule ESB, IBM B2B Integrator and Microsoft Azure API Management, whereas webMethods API Gateway is most compared with Apigee, webMethods.io Integration, Kong Gateway Enterprise, webMethods Microgateway and CentraSite. See our SEEBURGER Business Integration Suite vs. webMethods API Gateway report.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
