webMethods.io Reviews

There are actually a lot of valuable features. Terracotta is a very good component that enables us to arrange data caching and look at the solid state. Also, the API gateway is a very good component that can handle relevant caching and integrations and also load permitting. There is a message term for this. There are many components that we are currently using and all of them are very important. Also, we will use the DPM for workflow management and digital user transformation in the future.

I think they need to improve the API gateway to be able to replace F5 for example. Also, handling the certificates and their implications with other applications needs some improvement.

We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics.

It is stable, but it depends on the development team, not the platform itself. The platform itself is stable and has been used before by a lot of big companies and entities, but the old integration services are not related or tightly coupled with the platform itself. If you don't have good developers that can implement a good architecture or a good design, you will have issues.

It is easy to scale. We can really scale it up. We have had no issues with this.

Right now, we have an establishment of one organizer per platform but our plan is to use it as the only, single point of integration. The entire enterprise, all applications through all departments, and all IT will use the platform.

We are planning to increase the usage of the platform continuously over the next five years.

Currently, we have an incident open with them, but I think we need to give them more clarifications about it. There may be an issue with the product itself or perhaps it is from the implementation side. We couldn't reach a conclusion yet. We are supported 24 hours a day, it's full support.

Overall we are satisfied with the support because the main advantage is actually that you find someone to help you in time. Anything after is solvable; you will reach a solution. The ability to find someone dedicated is the main advantage.

I have an establishment of the IT department and the solution team but we were migrating from an old architecture and old application integration. It wasn't a platform, but rather a mix of solutions including webMethods but an older version. Now we have migrated from this older version to our new version. But we are migrating among a different integration solution.

Some parts were straightforward, but installing the platform was a little complex, especially since we use Linux instead of Windows. Opening ports, network restrictions, managing the network, and managing the users and components were all a little bit complex.

We did it on our own here, in our company. We have installed it over about four environments: development, SIT, production, and pre-production. All of this has taken about one month to finish.

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.

My advice is to put more focus on implementation rather than on the platform itself. This is more important than the platform because finding someone that knows how to fit the components is more important than having very good components that no one knows how to use.

I would rate this as eight out of ten, because of the scope we have already implemented. We didn't face many complex issues or troubles.

• Traditional ESB solutions using multiple adapters
• API development and management.

• The time to market is relatively less.
• It's simple to learn for Java users.
• Its administration is easier.
• Extensive toolset: out-of-the-box libraries support.
• DevOps could be better.

• API development
• Traditional ESB development
• B2B development.

• DevOps support
• Java services debugging.

I've been developing with SAG webMethods in Telco industries for integrating provisioning (CRM) end-to-end Billing, BSS and OSS, Banks/Insurance/Finance integrating bancassurance, provisioning, Switching&Allocation and Government Instance (Oil and gas) integrating B2B oil company to government reporting.

Time effective by cutting down development time and resource efficient to developer burden, enhance agility and integration between end-to-end applications, platform

The Integration Server

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).

Universal Messaging

Universal Messaging is a Message Orientated Middleware product that covers JMS, MQTT, AMQP.

Universal Messaging design supports both broker-based and umTransport communication, and thus comprises client and server components. The server component has specific design features to support each of these classifications of client, as well as Scheduling and Triggers, Plugins, Federation, Clustering, and Low Latency IO.

The Java Service section, which is probably needs more different manners for a new developer. It doesn't represent OOP very well, just a method and proprietary interface for input parameter called IData, which consists of Maps (key, value). You can still be creating classes under the shared section of the methods. But also the documentation of webMethods Java API it doesn't cover much clarity for the usage

Regarding the Stateful session inbound to ESB (Integration Server). It seems that the Stateful session sometimes doesn't die out when the transaction is finished, but waits until the timeout expires (although quite often it doesn't even died even after timeout expires, which eventually would flooding the server).

You have to buy another license for clustering named Terracotta which also had several different license, basically it was acting as a multicast and a cache, so if one of your node is processing something it would write into Terracotta, and then the other node would recognize some process going on so it wouldn't try to do the same processes which would be make double transaction for instance. It also can be use for data cache so you could have better performance fetching frequently data called rather than query it somewhere else e.g Database or REST Resources

Around 6 on a scale of 1 to 10. They don't help much enough actually, if there's any bug we have to wait for another patching rather than get emergency help

No, they won the PoC in the beginning. And mentioned as Leader in Gartner

Quite complex in setting up the BPM environment, the UDDI service (Centrasite), and also the API Management. But nonetheless there's documentation for each product 

I've been in vendor/consultant so I have enough experience to do it my own in-house.

I never done the accounting, I'm an engineer ?

I suppose webMethods aim for large-scale enterprises which is why the price is high, but with high output and better outcomes.

Some of the licensing is "component-ized," which is confusing to new users/customers.

Yet you can also choose between perpetual or periodically terms, in case you do not want to be bothered to buy another version once the newer version released you should consider periodic license.

Yes, TIBCO (was good enough IMHO) and Oracle Fusion Middleware (it's quite complicated IMHO).

I have to say that all SoftwareAG products are tightly proprietary, which means you can't just download and install for study purposes or to play around with them. You have to call their partner/product representative just to download the trial, which is quite different from their competitors. That makes the product unfamiliar to mid-low enterprises.

Also, their products are "componentized" in terms of licensing and tightly coupled, which means that some components may be licensed while some are a prerequisite to other components. So it could be that you have to buy two to get one and a half (pretty amazing isn't). But overall it is a great product.

Another thing is that made me bit upset was that the certification/training in South East Asia (which is my region) is not "individual friendly," meaning that if you want to get developer certified, you have to join to one of their partner companies or bulk order.

We're using it for managing secure file transfers for the company.

We have a reusable code that we can replicate for any new interfaces.

Ease of use.

The newest version, which we are not on, has all the features that we are looking for, meaning managed files transfer adapter.

It is stable. They are rather aggressive in their patches and upgrades.

It seems to be doing very well.

We got the product via a reseller, and the support from the reseller has been less than desirable.

We did not use another solution previously.

The initial setup was straightforward.

We enlisted help from the reseller with the initial setup.

I have only heard of Software AG, Talend, and MuleSoft.

Look at the stability of the company, and also take a close look at the pricing. Lower pricing doesn't necessarily mean it's a better product.

Most important criteria when selecting a vendor:

• Price
• Features
• Support.

webMethods, in my current client's environment, is used to provide solutions based on SOA (web services) and BPM (Business Process Management).

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.)

• SOA
• BPM
• Trading Networks (B2B)
• Active transfer (MFT)

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.

Segregation of deployment for the environments is the most valuable feature of the solution.

The product must improve the performance of Designer. The product must add more compatible connectors. The solution should provide more customization options.

I have been using the solution for about ten years.

I rate the solution’s stability a ten out of ten.

I rate the scalability a nine out of ten. Seven users are using the solution in our organization.

The technical support team is not so good.

Neutral

The initial setup is not difficult for me. I rate the ease of setup a seven or eight out of ten.

The deployment process took around two weeks. We need a team of seven people to deploy the solution.

I rate the pricing a nine out of ten. The product is expensive.

I am using the latest version of the solution. My advice to product users depends on their organization's scale. If an organization is a medium to large enterprise, I would recommend the solution to them. If the organization is small, it should consider other solutions in the market. Overall, I rate the product a nine out of ten.

The API Gateway is very good.

The Integration Server is very good.

Terracotta is very useful.

There are many components that I have used.

It's very flexible and a good platform to use.

There should be better logging, or a better dashboard, to allow you to see see the logs of the services. 

Also, storing the message bodies in the database and allow you to search them would be a nice feature to have.

These features should be enhanced to facilitate the work for the developer.

I have been working with webMethods Integration Server for four years.

webMethods Integration Server is a scalable product.

It is being used only by the developers, it's not for public users.

We have three developers in our organization who are using it.

Technical support is very good.

Previously, in another company, I worked with webMethods Broker.

The price is a little bit high, especially regarding their support.

The support fees are very high and we don't need such huge support.

I think anybody who is implementing this product should learn about the balancing and the API portal that is going to be used. You should have a good developer that is able to use the platform and understands most of the capabilities that it provides.

Overall, it's a really good product.

I would rate webMethods Integration Server a nine out of ten.

The primary use of the webMethods platform is to communicate with multiple applications and integrate them. webMethods provides business process integration, B2B partner integration, and also uses Web services to connect software applications. My client acquired another company and we are integrating the partners of the acquired company with their clients, using various data communication standards like EDI, EDIFACT, and Rosettanet messages. 

In my previous project we used it to bridge communications between a front-end application and the back-end, connecting them with Web services through SOAP requests and SOAP responses, using JMS queues and broker.

When my organization wanted to migrate the front-end applications from a Genesys framework to .NET for various security reasons, webMethods was used for ESB integration. At the time of migration, there was no work being done on the ESB side, which reduced developers' efforts and all the services were re-used as we used Web services to connect the front-end with mainframes.

When my business client  acquired another business and we were integrating the services, as B2B uses standard communication messages, i.e. EDI, the work made the developers' task simpler, in handling all the interfaces.

All of the following three features provided by webMethods are valuable:

1. Application integration
2. Business process integration
3. B2B partner integration

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.

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.

On a scale of one to 10, I would rate this product an eight. 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.

I have been using this solution for two years and four months and I haven't had any difficulty using it for building the interfaces and connecting various business processes, once I had acquired basic knowledge of the solution.