IBM webMethods Integration Pros and Cons

It's UI is very decent. Have multiple drag and drop option which I really liked about it. Review collected by and hosted on G2.com.

I think configuration options can be more or in other words configurations can be more customisable. Review collected by and hosted on G2.com.

Creating integrations with wM.io is easy enough, specially if you already know the on-prem product. Documentation is also very good and helps while performing those tasks. Review collected by and hosted on G2.com.

I think some features need to be polished. Also I had the feeling that some things would be readier, but when trying to use then it appears that they are somewhat more complicated than they should be. Also lack a tool to convert on-prem flows to wM.io, which would facilitate migrating. Review collected by and hosted on G2.com.

Most helpful function of webMethods.io is to expose services via API in a circumstance in which you don't have any API Gateway.

Exposing APIs in this way is really quick and easy, also the performances are really good. Review collected by and hosted on G2.com.

Writing flow services is quite complicated and it hasn't most of the functions available in the wmPub on premise package.

Also, dealing with the documentation, is not really easy to understand if it is possible to apply the publish-subscribe pattern fully on cloud and how it is possible. Review collected by and hosted on G2.com.

webmethods.io is based on proven technology and solid architectural choices. The web interface is modern and easy to use. In the future on premise and cloud will work together and expert developers will be able to use Designer, where low code or occasional users can use the web interface. Review collected by and hosted on G2.com.

As an integration expert I'd like to have full control over all components and logging and sometimes the clean interfaces hides information. For instance the queuing (UM) mechanism can't be accessed directly, but is configured and used as a background service. Lastly I'd like the Trading Networks (TN) interface to observe Transactions and their activities and I think it's currently easier to use than the webmethods.io end-to-end monitoring. Review collected by and hosted on G2.com.

The large and growing number of connectors, the ease of creating new ones and the simplicity of connecting securely with on-premises webmethods systems Review collected by and hosted on G2.com.

As long as the platform continues to work well and the connectors continue to evolve, no objections Review collected by and hosted on G2.com.

With webMethods.io Integration is easy to create workflows to integrate with different partners and applications, this application has a lot of different connectors that help you create integration faster and easier. There are connectors available for a varied set of applications and technologies, you can also build REST and SOAP API connectors using WSDL files or from scratch. There are several recipes that you can use as examples of integrations. Review collected by and hosted on G2.com.

There are some missing connectors, like RabbitMQ, MQTT and Kafka. You cannot have common objects between projects, which is complicated because you need to replicate common assets across different projects or make an HTTPS call to the workflow or flowservice you want to use. Review collected by and hosted on G2.com.

comparing SoftwareAG webmethods.io to its direct competitors, it is totally on another level, the experience of creating an integration flow is guided and much simpler Review collected by and hosted on G2.com.

Actually there isn't a thing i don't like, being on cloud it's a little frustating that I cannot use and have any type of governance over the virtual machines, but that's understandable Review collected by and hosted on G2.com.

Good documentation, great product development, listing to the customer. Multiple methods to reach and goal. Low code first, java code in development. Review collected by and hosted on G2.com.

Support for OAS 3.0. The "old" documentation (on premise version). Sometimes there's something posible there which is not available in the .io version. Review collected by and hosted on G2.com.

stability, availability, enough consultants, quick immplementation Review collected by and hosted on G2.com.

price, complexity, lack of BPMS solutions which was before and now not available Review collected by and hosted on G2.com.

Lots of connectors for Saas integration for used Review collected by and hosted on G2.com.

New flow language need to learn for legacy webMethods Integration users Review collected by and hosted on G2.com.