Celigo is an iPaaS integration platform for companies to easily connect apps, sync data, and automate processes. Integration wizards, templates, and other tools help help business users integrate NetSuite to any application or data sources. Celigo is available in four editions, and aims to meet the integration needs of all companies -- whether it is to implement a single use case to company-wide adoption of the platform. According to the vendor, the unique flow-based pricing is aligned…
N/A
IBM webMethods
Score 8.7 out of 10
N/A
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.
We demoed some of these other integration options. The learning curve seemed a bit steeper and the offerings less robust, so we did not pursue very far. I cannot speak to the others much. We have not had a reason to stray from Celigo.
This is night and day. In my experience, MEC had poor customer support, we had no idea where anything lived and all integrations were hidden. It was impossible for us to find root cause of anything.
Celigo works well in the small to medium organisations where the need for integration is tactical to support business operations, when there's no appetite for large investment in the integration space, and when the integration team is minimal or non-existent. Celigo is easy to …
Celigo handles errors much much better. Celigo stores templates all in one place making them much easier to find. Celigo interacts with your database as you are working allowing you to pull picklist values right from your db
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.
Celigo is great for transaction-based integrations (which is most), but not great for when you want to replicate data from one system to a database. For example, if you are trying to get all of your NetSuite data into a Snowflake database. However, if you are trying to get data out of NetSuite and create transactions in another system, it's perfect.
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.
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.
There is a bit of a learning curve, but not bad. Once you get a flow or two under your belt, there will be no stopping you. You will start to see possibilities and ways to apply automation and integration throughout your business. It becomes fun to look for additional ways to save money, time, and improve accuracy
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.
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.
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.
We demoed some of these other integration options. The learning curve seemed a bit steeper and the offerings less robust, so we did not pursue very far. I cannot speak to the others much. We have not had a reason to stray from Celigo.
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.
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
