IBM webMethods Reviews & Insights

I am Integration Architect and lead the IBM webMethods integration team for one of our client

IBM webMethods is doing good in doing integration as ESB layer. It has good robust stable integration platform with help of integration server and universal messaging. B2B integration using Trading Network is I think one of the full stack offering in current market.

We use IBM webMethods as an integration platform that allows us to connect our different systems and applications, from different data sources and monitor them. Being a new joiner using it for the first time was quite overwhelming, however, with time it's now really great.

In cases of large data handling from different sources and different applications, with systems, IBM webMethods is extremely helpful.

We use it to to streamline and automate integration processes, connecting disparate systems, applications, and data sources across on-prem, cloud, and hybrid environments. We use it to create a seamless integration between our CRM, ERP and other systems.

Very well suited for:
- Legacy modernization especially with mainframe applications
- B2B transactions
- High volume messaging and ability to scale well

Not well suited:
- Budget minded organization (expensive unless you're a big player
- AI/ML based automation require additional products
- Devops workflows not well supported.

Unifying applications, build digital Integration Hub, modernisation, technology stack like api management, Integration, mft and b2b and bpm made digital Integration with variety of applicatiob using single platform.

Because it is consistent and reliable product

IBM webMethods is used by our customers in many ways for A2A and B2B applications. EDI, API gateway, and data persistence are a few of the strongest points of IBM webMethods software. This allows real-time data to be transmitted in less than a few seconds or a fraction of a second. Also, it is a very reliable and consistent product. A lot of ERP and 3rd party systems can be integrated using IBM webMethods.

I have personally used and implemented IBM webMethods, Oracle Integration Suite, SAP XI, and many more. I find that IBM webMethods, once implemented, has a super low maintenance cost. I have seen IBM webMethods implemented and not upgraded for 10 years, yet it works smoothly.

We use webMethods.io Integration to solve some of our application to applications and business to business integration needs. It is the Integration Platform as a Service solution that we use in a mix with our continued use of webMethods Integration Server and Trading Networks on-premises. For any solutions that meet the use cases that we deem an appropriate fit for running in the cloud, we build those solutions using webMethods.io Integration. More specifically, we use webMethods.io Integration to synchronize changes in one application or system, in another application or system, by shipping data mutations via integration messaging and API calls. We also use webMethods.io Integration to integrate with external organizations. Our trading partners and supply chain partners provide APIs that we consume, and vice versa, to notify each other of business process events as they occur in the respective organizations.

We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios.

webMethods Trading Network is being used by our whole organization. It allows us to set up our suppliers and distributors as trading network profiles. This allows us to exchange business documents such as EDI, RosettaNet, and CXML with our partners electronically. Transaction search is also helpful to track any document for analysis if needed.

webMethods Trading Network is efficient for multiple partner onboarding and maintenance. Document tracking is one great feature. Resubmission of documents with data modifications is very helpful.

My organisation is a service oriented company which use IBM webMethods every day to answer my customers’ needs. My customers are from a lot of business domains like retail, bank or public administration. Our main business problems are to help systems to communicate correctly between each other. IBM webMethods is a useful software for data governance.

No doubt IBM is cooking something great for v11, but in v10 IBM webMethods has weaknesses : - There is no offer for smallest companies (the licences are expensive) - WebMethods.io is not that easy to take in hand, so it's not for "beginners". You need to develop Flow Services for most of the cases.

IBM webMethods is in use to support and fasten the integrations leveraging on APIs. The product enables to decouple applications, abstracting the connection pattern (avoiding the 1:1, spaghetti architecture) and to link also heterogenoeus environments (e.g. on-pre- and cloud). All of these, supporting scalability and change in volumes

Pro:
B2B and complex integrations scenarios. Especially in corporate, well regulated markets

Less appropriate
simple architecturale landscapes with light needs of monitoring and limited number of data to be exchanged. The overhead coming from the learning curve and powerfullness of the solution (and the connected sourcing) negatively impact the advantages of using the platform

IBM webMethods (IWMI) is used as our go-to product and platform to solve enterprise integration related business requirements where data needs to be exposed in a reliable, efficient and secure manner - regardless if it is messaging based, using API based integration patterns or if an event driven architecture approach is the appropriate solution. IBM webMethods solves all of these requirements, regardless if it is on premise, in the cloud, or a hybrid infrastructure situation.

In any scenario where a distributed enterprise IT landscape needs a unified approach to solve the challenges of enabling a common information supply chain where different stakeholders as well as citizen developers can be empowered to contribute, participate and own their own parts of the integration landscape - IBM webMethods offers a capable, architecturally sound and cost efficient way of supporting a wide range of enterprise system integration needs.