Most Helpful Review
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
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 connection between Facebook lead forms and MailChimp integrations is the most valuable feature.
The ability to connect web applications to trigger actions in another app after having enriched, formatted, delayed, grouped, and filtered is really valuable for many businesses.
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.
Some apps are not available yet. For instance, a connection with Joomla! would be great. In general, all the most-used apps are available, but I bumped into Joomla! with a client.
Being able to share Zaps and organize them with teammates would allow sharing and refining scenarios and even combining steps that require different people's credentials.
Pricing and Cost Advice
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.
Think your Zaps through to make sure you don't use more Zaps than you need.
There is a free plan that is, of course, limited. However, it allows you to understand and check true scenarios for a while.
out of 73 in Business Process Management
Average Words per Review
out of 26 in Cloud Data Integration
Average Words per Review
Compared 35% of the time.
Compared 8% of the time.
Compared 6% of the time.
Compared 25% of the time.
Compared 17% of the time.
Compared 12% of the time.
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.
Zapier is a tool for primarily non-technical users to connect together web apps.
An integration between two apps is called a Zap. A Zap is made up of a Trigger and one or more Actions or Searches.
Whenever the trigger happens in one app, Zapier will automatically perform the actions or searches in another app in order.
Zaps are very lightweight and easy to set up. Zaps do not import or export old data (they only operate on new items created after the Zap is enabled). Zaps are also not kept in sync ("two way syncing") after the Zap is triggered.
Zaps are deceivingly simple if you're used to dealing with complex and difficult integrations. Their simplicity is what enables anyone to create them.
Learn more about webMethods Integration Server
Learn more about Zapier
|Fujitsu, Coca Cola, ING, Credit Suisse, Electrolux, GTA, CosmosDirekt||BuzzFeed, Groupon, Spotify, Columbia University, FOX|
Financial Services Firm10%
Software R&D Company10%
Comms Service Provider10%
Financial Services Firm14%
Software R&D Company11%
Comms Service Provider8%
Marketing Services Firm29%
Leisure / Travel Company14%