Most Helpful Review
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
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.
It has a lot of basic EDI already established for all the main users. Also, it lets me share setups that I had already set up for my first plant. I was able to use them for my second one which was very helpful. I didn't have to start from scratch for my second facility.
The ease of integration of the SEEBURGER product into SAP was pretty seamless. There wasn't any trouble, there weren't any complexities.
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.
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.
When we got SEEBURGER Business Integration Suite (BIS), it was clear that it was going to take more of a technical person. It does take a technically-rooted individual to operate it. It's not something for your everyday guy to do. For what it's doing for us, a dedicated resource is required.
In some of the other tools out there in the market, you can create one service and use that service without creating a copy. That kind of capability currently doesn't exist in this solution.
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
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.
Pricing, compared to the tool that we had earlier, is cheaper.
The way they have their licensing structure set up, they have a lot of different modules. For us, we did not really know if we were licensed for certain things or not. We had to reach out to them multiple times to tell them that we were looking for this or that capability. We had to buy licenses for different things at different points in time, not knowing that we could have it bundled initially.
It has a very goofy pricing model in the sense that they have so many components and it's not very clear what components you require to do your work. When you ask for that, you learn that there's a surcharge for them. It's not that you buy a product and you can use all the compatibilities. They have all these different bits and pieces of it and you have to pay extra for all those things.
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.
Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials.
out of 25 in Cloud Data Integration
Average Words per Review
out of 73 in Business Process Management
Average Words per Review
Compared 25% of the time.
Compared 21% of the time.
Compared 13% of the time.
Compared 35% of the time.
Compared 8% 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 Company10%
Comms Service Provider10%
Financial Services Firm15%