We performed a comparison between OpenLegacy and SEEBURGER Business Integration Suite based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Google, Amazon Web Services (AWS) and others in API Management."OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"The biggest advantage of OpenLegacy was how simple the technology was. We were able to build out the OpenLegacy parts very quickly. We put together a couple hundred APIs in six months."
"Opens the door to connect modern web products to an old legacy system."
"OpenLegacy provides a way to go from the outside world to the legacy mainframe, to move the old standard application to a REST API application. New digital services can be created in a few clicks and this can be done easily by COBOL programmers."
"Using OpenLegacy, the exposure of services is far easier and quicker. In many cases, exposure of services requires just a few clicks and takes only minutes. In very complex cases, it still only takes half a day. Without OpenLegacy, it would take us several months to create the same services."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"One of the most valuable features is the option to have all integration patterns constantly updated in one platform. That is the main strength I see in using SEEBURGER Business Integration Suite (BIS). It means I can use a very old-fashioned pattern, combined with a very modern pattern. There are no limitations in terms of combining components because all the components simply fit together."
"It's a very robust solution and it's very configurable. Before this product we would use an ESB-type of solution which required us to write code and go through a process. We can configure the SEEBURGER solution much more easily, instead of writing code... It can handle large files very well."
"The solution is flexible when it comes to adding integrations. It is much easier to use than the other tools we have to move the files. Across the board, we can move files in a short amount of time compared to our other existing tools."
"The solution helps us automate processes, more on the insurance side. Where they used to have to babysit monthly files, because of size, they don't have to do that with SEEBURGER BIS. They just run the monthly process. Files get collected, translated, and sent to the proper systems, so the babysitting is gone."
"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."
"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."
"SEEBURGER BIS can reconcile documentation, like our accounts payable and statements within the system. If you are manually doing it, then it is really time consuming with a lot of errors. Whereas, SEEBURGER BIS allows for a lot of basic level programming within the documentation, filtering, and sorting out VLOOKUP. It lets us get two database tables from two different systems, then merge them based on the logic that we provide. So, it is a very helpful product."
"It used to take half an hour to move one file from one location to another. Now, it takes 10 minutes."
"We would also be more than happy if the product had the option to work in the opposite direction – the ability to consume REST/SOW services in the outer world from the mainframe."
"I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be."
"I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case. We are currently working with OpenLegacy to cross the SSL bridge and suspect that most users will want to do the same."
"Debugging and logging for programmers could be better."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"We occasionally get ZIP files. Sometimes the ZIP file has one file inside of it, and sometimes the ZIP file might have 30 files inside of it. We have been working with SEEBURGER to enhance their PKUNZIP process to be able to unzip multiple files in a single workflow instead of just one file. This is still something that is in process."
"Java is very old technology and they should move away from it, to anything that's better."
"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."
"The ability to bind a mapping to an agreement seems a bit clunky. It would be nice to have a better way of navigating to a map name rather than using a drop down list."
"Their traditional model is a vendor flow. We are looking to do a customer-based flow, which which require significant development from SEEBURGER Business Integration Suite (BIS). We are working with them to do this using their WebEDI. It is a brand new area for them, but it could be an option in the future."
"I find the solution quite confusing to use, especially when looking at the tree structure."
"Difficult in handling large amounts of data, like when the file has more than 100MB in size."
"The product is not integrated very well with different cloud providers. We did work with the vendor to build a solution for Amazon, but there is no solution for other cloud providers like Google or Azure. The vendor needs to create adapters so that if we have a requirement to transfer data from our data center to another cloud, outside of Amazon, we would be delighted with that."
More SEEBURGER Business Integration Suite Pricing and Cost Advice →
Earn 20 points
OpenLegacy is ranked 37th in API Management while SEEBURGER Business Integration Suite is ranked 19th in API Management with 37 reviews. OpenLegacy is rated 7.6, while SEEBURGER Business Integration Suite is rated 8.4. The top reviewer of OpenLegacy writes "The biggest advantage is how simple the technology was". On the other hand, the top reviewer of SEEBURGER Business Integration Suite writes "Gives us the flexibility to hook up to systems using any protocol out there". OpenLegacy is most compared with Kong Gateway Enterprise, IBM API Connect and MuleSoft Anypoint API Manager, whereas 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.
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.
