We are using IBM webMethods for translating the data in required format for systems and send it. We work for supply chain product is warehouse management and we use IBM webMethods primarily to translate the data which is required for host systems for example xml,txml,json so it converts the data into required format and transfers it to other systems. also, we integrated it with IBM MQ as well to pull messages from other systems.
Pros
Translate the data into required format based on system
Handles good amount of load and tranefer data into chunks and very much accurate
Administration is very easy and easily understable and it has goos secuity features
Schedulers works well for pub/sub message pulling and pushing
Cons
Majorly schedulers go to hung many times due to load issues
Datasource connectivity also problematic for small glitch also we see huge impact so auto healing is needed
User management is not that secure
Likelihood to Recommend
webMethods perfectly works for data translation and make systems to talk each other in required format and its very much easy to manage also we using it for supply chain almost 200 clients happily using it and no major issues with it and easy to integrate with multiple systems.
VU
Verified User
Engineer in Information Technology (Logistics & Supply Chain company, 501-1000 employees)
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.
Pros
Easy to use
Priced competitively
Supports robust and resilient integration solutions
Cons
Complex logic is hard to understand in simple diagrammatic user interface
User interface too simplistic for solutions that are complicated or go against the grain
Runtime observability could be improved
Likelihood to Recommend
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.
VU
Verified User
Professional in Information Technology (Logistics & Supply Chain company, 5001-10,000 employees)
