IBM® webMethods offers a hybrid, enterprise-grade integration platform as a service (iPaaS) that allows users to securely control applications, APIs, B2B and files across environments and locations.
N/A
Anypoint Platform
Score 7.8 out of 10
N/A
The Anypoint Platform developed by MuleSoft and acquired by Salesforce in early 2018 is designed to
connect apps, data, and devices anywhere, on-premises or in the cloud. This platform was built to
offer out-of-the-box connectors as well as tools that architects and developers can adopt quickly to
design, build and manage the entire lifecycle of their APIs, applications, and products.
N/A
Pricing
IBM webMethods
MuleSoft Anypoint Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM webMethods
Anypoint Platform
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM webMethods
MuleSoft Anypoint Platform
Considered Both Products
IBM webMethods
Verified User
Anonymous
Chose IBM webMethods
IBM webMethods lags in terms of iPass offering as compared to mulesoft and dell Boomi. In terms of api management Apigee is much better than webMethods.
IBM webMethods is far superior when compared to competition like Microsoft Azure. In functionality and capabilities. Better visibility, uptime, efficiency, etc.
webMethods does better for end to end integrations whereas Azure is more focused on APIs. We selected webMethods because we felt their integrations, especially to mainframe environments, were much better than the others. IBM has been in this space for a long time and know it …
Oracle Integration Cloud vs IBM webMethods, hands down IBM webMethods is way better. Lots of features and ease of doing webMethods and super stable stack.
webMethods.io IntegrationDescriptionWe uses 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 …
IBM webMethods was selected vs WSo2 for the reachness of the correspondign features regarding Mulesoft, the flexibility of IBM webMethods compared to the other platform, in relation to the existing architectural landscape was preferred
The two branches of the IBM integration portfolio are coming together nicely, and it's more a question of fully mapping the specific implementation requirements to the respective platform of choice when selecting between IBM Cloud Pak for Integration and IBM webMethods. …
I have seen that other products have different UI to address various business problems like messaging, EDA, MFT. IBM webMethods has unified platform and can also support hybrid Integration. I think it is all rounded iPaaS tool with ease of development and ease of operation. The …
The webMethods platform ranks higher in our ranking because it has more features and has proven itself in many CAC 40 companies in particular.The key elements are robustness, ease of use, a clear business model, and a wide range of features covering all types of enterprise …
IBM webMethods combines all the essential functions for information system integration in its platform. All products are interconnected to facilitate implementation (ESB, API, BPM, message bus). All tools are easy to use.
AWS is a very good tool but still evolving and offers a small set of API management features. The main reason why we chose MuleSoft Anypoint Platform API Manager is because it is well suited with the APIs developed in Mule ESB.
Once we have moved all of our system integration APIs to the MuleSoft Anypoint Platform, we will need to communicate with a wide variety of external systems. All of our business and service logic is stored in the aforementioned core systems. Anypoint Platform (and all of our …
Overall a better experience in pricing negotiation with the Sales team. The breadth of services offered by Mulesoft was really important and the expertise offered by our consulting partner influenced the decision. The overall deployment was completed well within the timelines. …
Once we use [MuleSoft] Anypoint Platform to host all our system integration APIS, we need to exchange data with a lot of different resources. Those listed systems are our main systems that hold all business and logic behind our service. The integration from Anypoint Platform …
We selected Mulesoft for speed of implementation. We did not have the luxury of time and needed a solution that can be learned and implemented within weeks so we can take advantage of newly formed partnerships. The training that was provided to use during our pre-sales and …
We believe Anypoint Platform is best in breed and has features that match nearly any other iPaaS offering. It also allows for accomplishing much more challenging and complex integrations due to the ability to connect to nearly any system, use custom connectors, and embed …
The main problem with this software is the different connector type that is used for different protocols except for a different SAP connector. There is only one connector called SAP. It will be great if there will have a different connectors like idoc, RFC, proxy, etc.
Anypoint has tons of capabilities baked in one platform, and other competitors like Built.io or Workato may not have all those like Anypoint Exchange. However where these products shine are in usability, as it's ridiculously easy to build integrations using Built.io. I was …
Anypoint Platform is really very easy to adopt for application integration. Simple UI and easy data weave language allows user to focus on business portion only. The API management and deployment of application are hassle free. We have selected Anypoint platform because it is …
Dell Boomi is kind of similar in drag and drop implementation. However, it doesn't have as many connectors (shapes in Dell Boomi). Moreover, it also doesn't have deployment stuff on its own.
Informatica is way behind Dell Boomi and Anypoint Platform, but users are still using it …
Compared to Dell Boomi the API management suite of Mulesoft is much mature, however if its only about the integration , then i would always go for Dell Boomi, as there is no infrastructure setup that needs to be done from the developer's end.
The main reason why we chose Anypoint API Manager is because it is well suited with the APIs developed in Mule ESB. AWS, on the other hand, is a very good tool but still evolving and offers a small set of API management features.
API led architecture focus with a decent API ecosystem for developer collaboration, policy management and declarative implementation. Batch processing, visualization, Anypoint MQ and ObjectStore leave a lot to be explored. Multiple deployment models make it worth considering.
It enables customers to expose their APIs in a very simple and fast way. It can be used by non-expert developers. It is compliant with all major connection and data representation world standard.
We provide options to customers to choose from the best tools. Customers are the decision makers. Personally, because of open-source and large community base, MuleSoft is the repo in the market.
It is a powerful tool with smart intelligence. The drag and drop feature makes my work easy. The tool has great connecting support which is the best reason to use the tool on a daily basis. Powerful functionality with designing and implementing APIs. Hosted on public IP.
With its world-class proven technology, the IBM webMethods products are best suited for solving integration needs, including application connectivity, data aggregation, and data synchronization. The business use cases expand across Healthcare, Aviation, Banking, Insurance, etc., and many other mission-critical systems. Though I feel there is room for improvement where webMethods products are utilized in a containerized platform, especially with the API Management suite of products.
MuleSoft Anypoint Platform is best tool in the market for developing APIs with complex structures communicating with various different types of applications including web applications as well as legacy applications. Also applications including database connectivity for fetching and updating data in the DB tables. I cant think of any scenario which MuleSoft Anypoint Platform could not be used for developing the integrations.
Provides wide range of popular connectors like salesforce, netsuite, sftp and many more. A user can easily integrate with those services using specific connector.
Support API development using RAML and desing tool. The platform is very good in data type classification.
Cloud deployment and post deployment monitoring is easy. A user can configure application worker as per need. Alert and notifications are real time.
Has more features than what we really need so we're paying for more than we use. Sort of like paying for an Abrams tank when all we really need is a Toyota Corolla.
Not a value product, tends to be expensive.
Takes a while for developers to learn to use Mulesoft Anypoint.
The webMethods platform is a fantastic tool for modernizing information systems. It's easy to use and delivers rapid results.The platform is focused on innovation and is accelerating its improvement with the acquisition by IBM.
The webMethods product has a very user-friendly and easy-to-use interface.A weak point is the My webMethods Server portal (administration and monitoring portal for the on-premise platform). This weakness has been addressed thanks to the control plane on the hybrid version of the product. This version should be highlighted and used to ensure a very fluid and functional interface.
MuleSoft Anypoint Platform is really very easy to adopt for application integration. Simple UI and easy data weave language allows user to focus on business portion only. The API management and deployment of application are hassle free.
The webMethods platform is very stable and does not cause incidents: if it is well configured and tailored at the base. Infrastructure incidents represent 20% of incidents (full disk, memory peaks, etc.) 80% of incidents come from the implementation of the code in the platform. If a code is not optimized and a high volume is observed in production, this can cause incidents. Similarly, if all error cases or conditions are not handled in the code, this can cause errors. Finally, there can be common errors if the applications connected to the platform do not return quality data or are unavailable.
The webMethods platform is designed to handle a high volume of small messages. It's a tool for continuous processing.The incidents I've seen involving application performance declines are caused by: - Code optimization issues - File size issues or fragmentation of the transmitted file - Misuse of the platform (batch processing) - Monitoring data was not purged, and the user was working with millions of data points
In the majority of the tickets I've created, support has been very responsive and provided the right solutions or solutions.Resolving a ticket also depends on the information provided by the creator. It's important to provide the technical context and information about the environment, as well as information to help the support team reproduce the incident.
Anypoint Platform support is very responsive. There is also a huge knowledge base and an active online forum where answers to most questions can be found. When needed support engages the engineering group so adequate solutions or workarounds are always provided.
We received in-person training from the webMethods team. We received standard training from the vendor and custom training on specific security topics.The training sessions went well but remained very standard and did not adapt to the client's specific business. In-person training is more suitable for rapid skill development. It is necessary to practice for a few weeks to ensure familiarity with the tool.
I found clear and easy-to-follow training with realistic use cases for quick understanding and a 360° view of the features. The lesson format allows you to progress and learn by breaking down the allocated time.The technical courses are described step by step, allowing you to quickly get to grips with the products
When implementing webMethods, it's essential to have the right support and guidance.It's important to map out the interactions, document them, prepare test cases, and implement them while making maximum use of the product's native features.Additional tools must also be planned to automate deployments, visualize logs, and monitor the platform.
The two branches of the IBM integration portfolio are coming together nicely, and it's more a question of fully mapping the specific implementation requirements to the respective platform of choice when selecting between IBM Cloud Pak for Integration and IBM webMethods. Pricing and licensing model, cloud strategy, and level of distributed responsibilities and ownership of integration in the organisation can be deciding factors.
Once we have moved all of our system integration APIs to the MuleSoft Anypoint Platform, we will need to communicate with a wide variety of external systems. All of our business and service logic is stored in the aforementioned core systems. Anypoint Platform (and all of our APIs) makes it easy to connect to various other platforms. In order to link to these many other systems, connectors and/or components are utilized, and they are simple to configure and integrate.
webMethods.io Integration is a cost effective approach to integration in isolation
webMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costs
webMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic Apps
webMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used