Boomi is a cloud-based, on-premise, or hybrid integration platform. It offers a low-code/no-code
interface with the capacity for API and EDI connections for integrating with external organizations and
systems, as well as compliance with data protection regulations.
$550
per month
IBM webMethods Hybrid Integration
Score 8.1 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.
$2,500
per month
Oracle WebLogic Server
Score 7.0 out of 10
N/A
Oracle WebLogic Server is a unified and extensible platform for developing, deploying and running enterprise applications, such as Java, for on-premises and in the cloud. WebLogic Server offers a scalable implementation of Java Enterprise Edition (EE) and Jakarta EE.
Boomi is one of the best integration platforms out there, but it still has its niche. It is suitable for most integration scenarios especially those that doesn't require very high throughput. The runtime could be hosted on-prem and in the cloud or even in a hybrid mode, which …
Mulesoft was evaluated by [and] definitely was not the right fit for the organization considering the type of integrations which were built in the enterprise historically. Dell Boomi on the other hand was more graphical and was more easy to use and is the best ipaas at the …
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.
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 …
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 …
Oracle Weblogic Application Server is very robust and has good features and stability. It is a very sought-after tool for deploying many kinds of applications.
Legacy systems often need to be replaced or integrated with new applications in order to modernize businesses. A strong API strategy that avoids custom coding and third-party programs is essential to enable this integration. Boomi's new-age connectivity and integration solutions ensure safe, secure, and robust integration. In the age of information, businesses are under more pressure than ever to be able to collect and manage large amounts of data. This data comes in from a variety of sources, including personalized devices such as voice assistants and wearable tech. While this data can be immensely valuable to businesses, they often lack the infrastructure necessary to handle it effectively. This can lead to data build-up in databases or silos, and can eventually lead to problems with integration and security.
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 need to have complex options in place you can count on Weblogic to be a robust Applicational Server you can rely on. But you would need to keep an eye on maintaining the framework updated quite frequently to avoid security breaches and subsequent severe situations. If you don't have other infrastructure for test purposes, I wouldn't advise you on having devs and QA installing this heavy application in their local machines, there are other lightweight solutions that would be a better fit for that.
The brand relation between Java and WebLogic Application Server usually provides a quicker access to programming features and their availability for the applications deployed.
The access to centralized configuration both from console and command line WLST eases the implementation of changes major or not in an organized and expedite way.
The maturity of the product is also visible in the available tools provided by the product itself, for both monitoring of resources and alerting for availability and thresholds
More from a development perspective. It is always difficult to use the properties features. It takes a while to understand how the data/variables can be used across an integration.
Dell Boomi should also invest more on API Management and not just seen as a ETL,ESB tool.
Should roll out features more often based on users reviews.
Debugging issues has been difficult sometimes, the documentation is too dense and finding the the root cause for an specific issue takes time.
The Oracle WebLogic Server console UI feels old and gives a sense of lack of innovation even though it provides so much functionality.
I'm not sure if Oracle WebLogic Server supports more modern frameworks, but it feels more like a Java EE specific, maybe there's an opportunity there to appeal to newer application platforms
Dell Boomi has provided us with the ability to connect our campus together using our various existing platforms. There are many supported features and have yet to run into something that we cannot do. Its user interface is very intuitive which would allow users to begin developing fairly easily. There is a myriad of resources available
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.
My IT and Finance teams have noted that setting up the tool is a breeze. Dell Boomi has never caused an issue during a system implementation that I am aware of. We are pleased with the tool and recommend others consider it.
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.
Oracle WebLogic Server has so many features that sometimes it's hard to find the right place to setup things, I think the dated user interface does not help with that either. This has a direct impact when deciding to use it as your application server, you'd need to have the right people and invest the time needed to master it. If you're application justifies it then it will definitely be a great choice in the long run.
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 atom sphere takes a time to load, when I open a process or when I open a log. One more slow processing is when I import objects from NetSuite.
About the performance of processing, it looks like Boomi takes a time to initialize some things such as connectors before starting the process. This is also performance we have.
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
Boomi support was responsive and knowledgable, however being a closed cloud service, it doesn't have good community support. We found the learning curve to be steep and there aren't avenues like google, forums, or blogs that provide community driven insight into the product or how to go about designing solutions using the tool
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 decided to go with Dell Boomi because another department in our company was already using the software. We did not research competitor applications to use as our business solution. Dell Boomi was very easy and quick to set up, so once we decided to use Dell Boomi for systems integration, we had it set up and running within a few working days.
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.
I believe the Oracle WebLogic Suite is probably a better all encompassing suite of development tools for the IT department. [It] is probably a bit more expensive than other competitors like Apache Tomcat or NGINX, but is worth the investment if you consider the savings from time to get code into production.
It has allowed us to scale significantly without having to add headcount, specifically those geared towards data entry. We went from a $10m ARR business to $200m ARR business with the same amount of Order Processors and 12x amount of transactions by leveraging Boomi to perform a lot of the work, and then having the Order Processing team to simply review that the transaction was processed successfully.
WebLogic Application Server definitely had a positive ROI since all the applications are deployed on a single platform and making maintenance extremely cost effective.
Since all major cloud vendors support and maintain WebLogic, it gives us an opportunity to explore possibilities to move the organizational infrastructure on to the cloud without too much effort.
