We performed a comparison between IBM B2B Integrator, SEEBURGER Business Integration Suite, and SWIFTnet FIN based on real PeerSpot user reviews.
Find out what your peers are saying about SAP, MuleSoft, IBM and others in Business-to-Business Middleware."B2B provides a secure communication channel."
"The best feature is that many companies use the solution so there is a lot of peer support."
"It's highly stable, and the redundancy is amazing. B2B Integrator also has a high availability option to work in a cluster environment. You rarely have issues operating it because of the HA."
"The solution is useful for transferring files from one format to another format. Also, the solution is useful in translation."
"The most valuable features assist with understanding data formats and transforming data."
"The most valuable features are the flexibility and the range of EDI standards that IBM Sterling can handle."
"The most valuable feature of IBM B2B Integrator is its security and flexibility."
"It is easy of use and it's easy to maintain. It's also faster to on-board 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."
"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."
"It's the reliability. And the message tracking is quite good, where we can go in and see if we have an issue."
"SEEBURGER BIS helps us automate processes. When something is manual and we have to fix the data, then it is really complicated. However, when it's automated, we trust it and the process in the system, so we don't have to go back and fix it. For example, we had a problem with a partner sending 17 files every week, but a few times a year, they wouldn't send files during a certain window. We would escalate this with them. Then, when they caught up and sent the files again, they weren't authenticated. We had to fix this situation before it became a nightmare because our financials were impacted. Also, it was really messy. So, I worked with SEEBURGER to have something automated to pick up the files within a certain window and validate them as accurate. If the files come outside of this window, then we have to approve the loading of them."
"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."
"Among the most important [features] are the BIC 6 Converter and the communication protocols, which have the newer security features for certificates and encryption."
"We can code in Java, which is really good feature. There is very vast command available, which can be used in mapping."
"The ease of integration of the SEEBURGER product into SAP was pretty seamless. There wasn't any trouble, there weren't any complexities."
"It provides the ability to interact with financial institutions and apply the same rules."
"End-to-end visibility and monitoring application required. The control center is available and covers this area, but it still fails in many monitoring scenarios."
"The web interface of B2B is quite outdated and not particularly user-friendly."
"The tool requires you to write a lot of code in Java and XSLT, which makes development tough."
"Patching or upgrading the product is a bit of a nightmare. It would be nice if they removed the installation manager port. We find it complicates upgrading and patching a great deal."
"API integration could be improved. The legacy system could be on the cloud."
"The reporting features could be better. right now, they are lacking a bit."
"There should be a single place to do things, rather than making it complicated, not moving away and truncating the old features but instead coming up with the new and still keeping the old stuff confuses people sometimes."
"They do not have a solid partner ecosystem, and they do not have a clear roadmap for down the line; they're missing that clear roadmap."
"A person whom I work with, and is not very technical, found the setup complex, as there are a lot of steps."
"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."
"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."
"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."
"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."
"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."
"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."
"Java is very old technology and they should move away from it, to anything that's better."
"I would like for them to work in real-time."
More SEEBURGER Business Integration Suite Pricing and Cost Advice →
Earn 20 points