Most Helpful Review
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
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.
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.
A product with good API and EDI components.
We can arrange data caching and look at the solid state. Also, the API gateway is a very good component that can handle relevant cachings and integrations, as well as and also load permitting.
It's obvious that the heart of the product lies here. It's comprised of all aspects of ESB (Enterprise Gateway, Adapter, TN, Java) and BPM (task, rules engine).
We have a reusable code that we can replicate for any new interfaces.
The main assets are its flow language, debugging, and Broker. Flow language is far better and more flexible for debugging.
The MFT component of webMethods, for example, is easy to set up and convenient to use. It handles files very efficiently and it is easy to automate tasks with complex schedules. Monitoring is centralized to MWS which can be used to monitor other products as well (Trading Networks, BPM, MFT, etc.)
Application integration, business process integration, and B2B partner integration are valuable. But among these, I feel B2B partner integration is the most valuable. This module integrates two business partners and exchanges data through electronic data interchange messages in the form of specific standards, without any manual process needed.
I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well.
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.
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.
The interface needs some work. It is not very user-friendly.
We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics.
t doesn't represent OOP very well, just a method and proprietary interface called IData.
We got the product via a reseller, and the support from the reseller has been less than desirable.
Documentation needs tuning. There is a lot of dependency with SoftwareAG. Even with the documentation at hand, you can struggle to implement scenarios without SAG’s help. By contrast, IBM’s documentation is self-explanatory, in my opinion.
When migration happens from the one release to an upgraded release from Software AG, many of the existing services are deprecated and developers have to put in effort testing and redeveloping some of the services. It would be better that upgrade releases took care to support the lower-level versions of webMethods.
The stability of the various modules of the product suite have been a bit of a concern lately. Though their support team is always easy to reach out to, I would prefer it not come to that.
The product needs to be improved in a few ways. First, they need to stabilize the components of the whole platform across versions. Also, they should stop replacing old components with brand new ones and, rather, improve by evolution.
Pricing and Cost Advice
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...
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.
It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one.
Some of the licensing is "component-ized," which is confusing to new users/customers.
Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client.
out of 26 in Cloud Data Integration
Average Words per Review
out of 75 in Business Process Management
Average Words per Review
Compared 24% of the time.
Compared 20% of the time.
Compared 14% of the time.
Compared 36% of the time.
Compared 7% of the time.
Compared 6% of the time.
Also Known As
|Seeburger Business Integration Suite|
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:
The award-winning webMethods Integration Server, our Enterprise Service Bus (ESB), is a complete enterprise application integration solution. It's standards-based so it "speaks" any technology. You can integrate any technology from any vendor: ERP systems, databases, mainframes and legacy apps. SaaS platforms, Web services, JMS messaging systems and packaged apps.
Learn more about SEEBURGER BIS
Learn more about webMethods Integration Server
|Altis, Autoliv, Cebi, Cofresco||Fujitsu, Coca Cola, ING, Credit Suisse, Electrolux, GTA, CosmosDirekt|
Software R&D Company30%
Financial Services Firm11%
Software R&D Company11%
Comms Service Provider11%
Software R&D Company36%
Financial Services Firm8%
Comms Service Provider7%