webMethods.io Reviews

We don't use webMethods Integration Server directly, but we use another offering from one of our vendors. They have built a layer on top of the webMethods Integration Server and that's a solution we have been using.

webMethods Integration Server is the underlying component, but our software vendor, has made some enhancements to the webMethods Integration Server and they offered it to us. That's what we are currently using along with some of the other solutions in the supply chain space.

Their offering is more of an integration framework across all their systems and this is how we have been using the system. webMethods Integration Server is our primary integration tool across all the solutions that we have in our supply chain.

The most valuable feature of webMethods Integration Server is all the capabilities it provides. We leverage most of the features, that they have offered to us. Our vendor has made some additional features on top of the webMethods Integration Server and we use all the features together.

webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve. 

The migration of the code between environments could be better. If they come up with some kind of a continuous integration process to promote the code from one life cycle to the other, that may ease the day-to-day activity for us.

I have used webMethods Integration Server for approximately seven years.

webMethods Integration Server is a stable solution for our usage.

The scalability of the webMethods Integration Server is good.

Our IT team is using the solution in my organization.

We plan to increase our usage in the future.

I have not needed to use webMethods Integration Server support.

We used other solutions before using webMethods Integration Server.

The maintenance team needed for webMethods Integration Server is minimal.

We have seen a return on investing using webMethods Integration Server.

I rate our return on investment for webMethods Integration Server a four out of five.

The solution has been doing the job for us, at least with respect to the landscape and the integrations we have in place. However, it is on a case-by-case basis.

I rate webMethods Integration Server an eight out of ten.

I like the solution's policies, transformation, mediation, and routing features.

The product should provide more customization options. Application of policy management is not easy. We have to do a lot of customization and configuration. Documentation is also a problem. Understanding the overall architecture is difficult.

I have been using the solution for five years.

I rate the solution’s stability an eight out of ten.

I rate the scalability an eight out of ten. Ten people in my organization are using the solution.

I rate the ease of setup a seven out of ten. The installation is pretty much easy, but there are some obstacles. The interoperability of the components is not that easy.

The time taken for deployment depends on the knowledge of the people deploying the solution. Three to four people from our organization took about a month to set up the entire stack. It had a lot of components. It had an API portal, Command Central, CentraSite, Trading Networks, and Active Transfer.

I rate the pricing a ten out of ten. The product is very expensive.

I am using the latest version of the solution. The improvements depend on the vendors. MuleSoft has got different areas of improvement. Software AG has different areas of improvement. We are planning to move the product to the cloud. My advice for the product users depends on their business model, the scale of their business, how much volume they have, and what kind of transaction management they need. Overall, I rate the product an eight out of ten.

The solution's most valuable features are web services, XML transformations, and adapters.

The solution's release management and JSON services need improvement.

We have been using the solution for 20 years.

The solution is stable. I rate the solution's stability a nine out of ten.

The solution is scalable. We have enterprise customers using the solution. I rate its scalability a nine out of ten.

The solution's technical support needs improvement. It could be more accessible in terms of communication.

Neutral

The solution is easy to set up. I rate the process a seven out of ten. It takes two months to complete. 

I recommend the solution to others and rate it an eight out of ten. It works fast and is easy to adapt.

We had quite a heavy use case in terms of transactional traffic, and webMethods was quite fantastic in processing all of those workloads.

Some of the key features are the integration platform, query mechanism, message handling within the bus, and the rules engine. We've had a really good experience with webMethods Integration Server.

On the monitoring side of things, the UI for monitoring could be improved. It's a bit cumbersome to work with.

I've been using webMethods Integration Server for about five years.

The current version is in our private cloud, and we implemented the same solution on-premises and in the cloud. So, we have implemented a hybrid solution.

The initial setup was straightforward.

We implemented it through an in-house team, and it took about four weeks.

There are no hidden costs in addition to the standard licensing fees for webMethods.

For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses.

A slightly watered down version would be nice so that small, growing businesses could afford it.

We tried to use Oracle, and it just didn't do it for us. We explored MuleSoft, but it was a little bit expensive because of their pricing model, which is per transaction. So, it was also not a viable option for us.

You just need to find the right skills. In our country, we don't have people with qualified webMethods skills, so that's a problem for us in terms of resources. Depending on where you are from and if you don't deal with resource scarcity, webMethods could be a good option for you.

On a scale from one to ten, I would rate webMethods at eight. 

By linking apps and services, the webMethods Integration Server allows you to automate processes.

I like the stability of the webMethods Integration Server.

I would like to see the price improve.

I have been working with webMethods Integration Server for eight years.

We are currently using version 10. x.

webMethods Integration Server is quite stable, especially given the amount of load it has been handling.

webMethods Integration Server is a scalable solution.

In general, I contact technical support if we are experiencing any problems. They are extremely helpful.

Previously, I had not used another solution.

The installation is straightforward. It's easy.

It can take thirty minutes to deploy depending on the number of components.

It can be installed both on-premises and in the cloud. It has been migrated to the cloud, and we also use it on-premise.

You can complete the installation yourself.

I would like to see better pricing for the license.

We are researching cloud-based solutions, such as AWS and MuleSoft.

I am a user, so I'm not entirely familiar with everything this solution has to offer. I am utilizing one of the technologies that they provide.

Using this solution is dependant upon each area's perspective. I can't exactly say, if you had only one user that it's only for this solution or that solution, but it actually depends upon each other's perspectives.

WebMethods is the recommended solution if you want a stable integration, an ESB platform, and a B2B.

I am unfamiliar with cloud-based solutions or their environment. We are exploring their options and services.

I would rate webMethods Integration Server a nine out of ten.

Most of our customers are real estate development companies, and they build many projects in Saudi Arabia. Most of their projects are about Smart Cities or Smart destinations. The use case was about integrating different Smart City technologies and enterprise applications. For government services, the use case was integrating webMethods.io Integration into different government systems serving residents. For example, the Ministry of Interior uses the solution for passport and ID services, so different government systems are integrated.

We used webMethods.io Integration as an integration platform. It accommodates Enterprise Service Bus, integration server and API gateway. We took the complete platform and the integration server as part of the platform to integrate or receive data from the API gateways, integrated with the Enterprise Service Bus.

The solution allowed us to integrate applications and IoT devices because it has an IoT event processing layer. It provides a flexible integration within the IoT systems because most of the applications we work with are related to the IoT and Smart City technologies. So, there's hardware, software and application integration, providing hosting flexibility.

Some platform providers host their applications in Amazon AWS or Microsoft Azure, which sometimes creates challenges for data governance because of regulations.

Any solution needs continuous development in integration and processing.

We used the solution for more than a year for different projects. We used the latest version and stopped using it four months ago. It was deployed on private cloud in the customer cloud infrastructure.

The solution is stable. If there were any minor problems, we resolved them.

It can be scaled up and support multi-tenancy. However, it is difficult to maintain.

I rate the technical support a six out of ten.

The initial setup was straightforward.

They don't have a fixed price, and the pricing model is transaction-based. I rate the pricing a seven out of ten, with one being the worst and ten being the best.

I rate this solution a seven out of ten. I recommend it, but it depends on the use case. I do not see any gaps with the platform.

webMethods provides the ESB backbone for us since more than 8 years without any hick ups

High throughput and excellent scalability.

Programming model with flow is hopelessly outdated. Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS

ESB is rock solid. Products on top of Integration Server have much less stability.

No. Absolute top.

Webmethods ESB works, but support is layered an requires escalation every so often

We used IBM MQ Series and migrated due to licensing issues.

Significant topics with bespoke programming model (FLOW language), difficult to find experts and if, they are expensive. Wouldn't do it again.

Mixed team with vendor.

N/A

Initialy good pricing and good, if it comes to Enterprise license agreements.

It's a rather mature solution with lot's of design choices we would not accept in 2017. We are in fact considering to leave to other products.

We are looking to use webMethods as part of our business process management solution. We have a mainframe and it facilitates connectivity with our database.

The designer is very helpful in developing services.

Interacting with and developing services is very fast. As long as the requirements are clear, developing service will take no longer than one or two working days.

The tool is very powerful and user-friendly. For example, I have a new team member and within one or two months, they are able to write and deploy services. Once you have a basic understanding of it, you can begin developing.

We would like to have a gateway server included, where we can control the number of requests.

There is an interface in webMethods for building a portal, but we are not using it because the price of the license is too high.

I would like to have a dashboard where I can see all of the communication between components and the configuration. As it is now, it is a lengthy search process. When a request comes in, sometimes you have to go to the administration page and then search the web after that. I need to be able to trace the flow from the port to the service to find the issue and there is no diagram to show me the parts. This is something that would be helpful.

I have been working with WebMethods for more than seven years, since 2012.

We have no complaints about stability.

Scalability has not been a problem for us.

We have not needed to contact technical support.

Our in-house team is responsible for maintenance.

This is an expensive product and we may replace it with something more reasonably priced.

We are considering switching to WSO2 Enterprise Integrator because the pricing is better.

My advice to anybody who is considering this product is that it is a very powerful tool that will empower the development of services. If there is a proper plan then it can be achieved within a short period of time. After a service has been developed and tested, it is moved to the staging environment. Once it is tested, we move it to production. Moving it will not take more than a few minutes.

It is definitely a product I recommend to people who have the money to pay for it.

I would rate this solution an eight out of ten.