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.
$2,500
per month
SAP Business Technology Platform
Score 8.5 out of 10
N/A
SAP Business Technology Platform (SAP BTP) is the company's Platform-as-a-Service (PaaS) offering, that brings together intelligent enterprise applications with database and data management, analytics, integration and extension capabilities into one platform for both cloud and hybrid environments, including hundreds of pre-built integrations for SAP and third-party applications.
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.
If you want to use a well-designed SAP technology to shift into the cloud, you will be more than satisfied with the BTP services overall. There are some improvements for beginners to help them get a better overview of what to do and how to start with their account. My recommendation is to take a foundation training course from the SAP learning hub to prepare for the first steps.
All the documentation around it is geared towards the enterprise use case, unlike some other hyperscalers' platforms.
The SAP Business Technology Platform is very good because it's got the SAP customer and their business processes in mind. Probably my favorite thing about it is how easy it is to get up and running with a new use case and how well it natively connects to an SAP solution.
The Automation Integration service has some outdated workflows
New services should be available as entitlements as soon as they are released for a particular region without having to buy them from SAP for zero dollars
Any subaccount should be able to change the IAS tenant. Currently, if you set it up for a particular IAS, you cannot change to another tenant and are required to recreate the services in a new subaccount.
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.
Seamless integration with external system and dashboard to monitor the data flow and analysis are very essential for the business. The way the product is designed and modelled lead to minimum business disruptions. Adopting to the new and modern technology was easy. Keeping the central system as clean and adopting project bases development are advantages.
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.
Okay, so the content that we have built on the platform is limited to specific testing on the iFlows within integration suite. The visualization layer is nice to use and helps with the design elements, however with developers that are more used to markup languages, it doesn't have the same CLI type feel when you want it. Perhaps the majority of users are that deep, but other platforms have a better CLI type developer experience.
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.
The biggest problem we ran into was communication between SAP Business Technology Platform and onsite resources. Unfortunately our SAP Business Technology Platform and Cloud systems are under different customer numbers. I constantly had to open tickets under each customer number because I was unsure of where the issue lied. And having to create a dummy ticket for our ECC systems to open the ECC connections for another ticket under the Cloud customer is a pain.
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
Training material in Developers Community or from Learning hub are really good... also most of the time we route through Discovery center... so materials provided by SAP is really good.
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.
Having a full cloud native environment for devlopment of microservices and digitals solutions while having standardized access to our core data on SAP via cloud connector is one of the main benefits of using BTP over others hypervisors. BTP is the standard hyperscaler as soon as something relies on data from SAP systems in our company now
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 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. Please provide some detailed examples of things that webMethods.io Integration (webMethods Integration Cloud) does particularly well. Easy to usePriced competitivelySupports robust and resilient integration solutions please provide some detailed examples of areas where webMethods.io Integration (webMethods Integration Cloud) has room for improvement. These could be features that are hard to use, missing functionality, or just things that you'd like to see done differently. Complex logic is hard to understand in a simple diagrammatic user interface too simplistic for solutions that are complicated or go against the gain runtime observability could be improved please describe some specific scenarios based on your experience where webMethods.io Integration (webMethods Integration Cloud) is well suited, and/or scenarios where it is less appropriate. 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. What positive or negative impact (i.e. Return on Investment or ROI) has webMethods.io Integration (webMethods Integration Cloud) had on your overall business objectives?webMethods.io Integration is a cost-effective approach to integration in isolationwebMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costswebMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic AppswebMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used describe how webMethods.io Integration (webMethods Integration Cloud) stacks up against them and why you selected webMethods.io Integration (webMethods Integration Cloud). For any organization which is already using Software AG products on-premises, such as webMethods Integration Server and Trading Networks, or Universal Messaging, evaluating and using webMethods.io Integration is the path of least resistance. It will be incredibly easy for your webMethods team to get up to speed on how to use webMethods.io Integration, and start developing new solutions on it. However in my opinion you should only add cloud to your integration product portfolio if you believe you can move 100% of your integration needs to the cloud. Otherwise, you will need to maintain an on-premises integration solution anyway, which means you end up with a more complex IT landscape by adding cloud to supplement on-premises integration for little benefit in terms of cost, complexity, and resourcing requirements. For organizations that are not already a Software AG shop, you should evaluate webMethods.io Integration on its merits, however, it's usually the right decision to double down on your existing products and vendors if you have no big issues with the current state. This is to say that if you are a Microsoft shop then adding Azure cloud products to your portfolio is pretty much inevitable, and avoiding the complexity of multiple clouds should also be something organizations consider.
SAP Concur allows our staff to book, reimburse and remain spend audit compliant. Our Concur system takes feed from Workday and interacts with Credit card vendor. It also makes posting to Accounting and does clearing. SAP Business Technology Platform helped in establishing connection with all these different tools in real time. It helps in getting paid to the card service provider through our Bank through interface, which is built on SAP Business Technology Platform.
Infusing Generative AI capabilities easily into our solutions with existing talent with minimal learning curve, has been very impactful. We have been able resolve several challenges for our clients with AI capabilities, that we could not, previously.
Integration Suite is quite extensive in capabilities for bringing together the IT landscape into a single ecosystem.
