webMethods Integration Server Reviews

We primarily use it as an integration server. We have integration use cases, including B2B, et cetera.

It is reliable and works very well. 

The integration with platforms is great.

It's straightforward to set up. 

Technical support has been responsive when we need assistance.

It is a very stable product.

The solution can scale as required. 

We're fine with the product offering.

It is quite expensive. 

I've used the solution for more than a decade. 

The solution is very stable. I'd rate the stability ten out of ten. There are no bugs or glitches. It doesn't crash or freeze. 

It is highly scalable, to my knowledge. The organization has used it for almost two decades without issue. I'd rate the scalability nine out of ten. 

We have about 100 users on the solution. 

We do not have plans to increase the number of users, to my knowledge.

We've used technical support, and they have been fine. They are very responsive. 

Positive

I had used other products previously. I use this solution since it has a lot of use cases, and the organization chooses to use the product. 

It's easy to deploy. It has its own deployment tool, which makes it very fast. We can use it both on the cloud and on-premises. 

We have a 13 to 17-member team of developers that can handle the deployment. 

We handle the initial setup in-house according to the government model. Our IT team handles the process. 

I can't comment on the exact ROI; however, it is a very useful product.

The solution has a yearly licensing fee. It is very costly.

I'm not sure if there are any extra costs involved in using the solution. 

I'd recommend the solution to others, depending on the use case. There are many factors that would be highly dependent on its success. 

I'd rate the solution ten out of ten. 

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.

What I found most valuable in webMethods Integration Server is its strong ESB. It also has strong API modules and portals.

As webMethods Integration Server is expensive, that's its area for improvement.

I've been using webMethods Integration Server for twenty years.

webMethods Integration Server is very stable as a product.

webMethods Integration Server is a scalable product.

I haven't contacted the technical support for webMethods Integration Server yet.

The initial setup for webMethods Integration Server is straightforward. It's just a normal process, so on a scale of one to five, I'd give the setup a rating of four.

webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting.

My company has a partnership with webMethods Integration Server.

My main advice to anyone looking to implement webMethods Integration Server is to figure out the governance target. You also want to aim for a good implementation, so you'll need to know your target.

My rating for webMethods Integration Server is seven out of ten because it could be more innovative and still needs more connectors or adapters.

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. 

The API Gateway is very good.

The Integration Server is very good.

Terracotta is very useful.

There are many components that I have used.

It's very flexible and a good platform to use.

There should be better logging, or a better dashboard, to allow you to see see the logs of the services. 

Also, storing the message bodies in the database and allow you to search them would be a nice feature to have.

These features should be enhanced to facilitate the work for the developer.

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

webMethods Integration Server is a scalable product.

It is being used only by the developers, it's not for public users.

We have three developers in our organization who are using it.

Technical support is very good.

Previously, in another company, I worked with webMethods Broker.

The price is a little bit high, especially regarding their support.

The support fees are very high and we don't need such huge support.

I think anybody who is implementing this product should learn about the balancing and the API portal that is going to be used. You should have a good developer that is able to use the platform and understands most of the capabilities that it provides.

Overall, it's a really good product.

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

I'm using the product every day, and I'm working on many different projects. Most use cases are for using webMethods Integration Server as a middleware software or a middleware platform that is connecting to at least two different endpoints. It can be from one side, for example, database, web service, SAP, or any kind of connection, including Salesforce, and the other side can be the same. We are just establishing connections between these systems and doing some transformations and modifications of data in the Integration Server so it can be sent from one side to another.

Clients are mostly using it in order to connect some of their internal systems or to connect to some external systems and some other partner companies. Its benefit is that it's really useful for monitoring and tracking all the activities. And it's important, due to all the flows, all the data, go through this ESB, Enterprise Service Bus. 

The most important thing when using it is that there is a really good community from the producers, Software AG, and the Empower platform, where you can find almost every kind of error or problem that you face. You can find a solution right there in the community.

There is also typical support where you can create a ticket if you are not able to find the issue on your own. If it's something new, then they will approach you and help you in resolving it. 

The best features are these adapters. Software AG developed many different adapters for the usual databases, et cetera. I was not using Salesforce much. However, it's really handy that you have an adapter for these popular platforms. It's just plug-and-play.

When it comes to the user interface, I'm already really used to it. I cannot say anything against it. For me, it's easy to use.

When there is some issue or bug, they work on the development of that. And then, in the next release, they just fix it. I had a few situations when I faced some issues, and then I had to report them. Within the next three weeks, typically, it just gets fixed.

For code version control, you need to use some external software. It would be good to have it just built into the product so that you don't have to use anything external.

The interface could be modernized. 

I've been using the solution for about five years. 

If it's set up properly and if you do it in a good way in large-scale organizations, you need to have a maintenance team that is doing the maintenance and support. If it's working properly and updated properly with the latest versions of updates, then there should be no issues with using it. It is reliable. One of the main benefits of Integration Server is that it is reliable.

Our entire company uses the solution. There might be 100 people using it on a daily basis. 

Scalability is one of the main purposes of the product - scalability meaning that it can adapt to small customers, clients, and even to bigger systems and clients with a lot of data going through the Integration Server. 

Technical support is really good. They are replying really quickly. In a day or two, you can get a response for your issue, or probably even quicker if you mark it as urgent. 

For me, it's fine. I had some contact with Software AG support. They wrote really helpful. And a few times we even had some meetings with screen-sharing sessions so they could help and see the issue. It was really nice. 

I know there are a few really great options on the market; however, I do not have experience with them. 

When it comes to deploying the Integration Server, you just need to follow the documentation, which is really good. The documentation created by Software AG for using and working with each of the products is really nice, and I'm satisfied with that. For the first time you use it, you need to install the Integration Server on Windows or Linux machine or whatever, and if you follow the steps via the documentation, it should not create any issues.

The deployment can be done by one person. It might take an hour or two.

If you are installing many Integration Servers in a cluster, then these things take time to configure the clusters and all other setups related to the network. That said, for the basic product, if you want to use it just for your own purposes, if it's just one instance, it does not take much of your time to get it up and running.

There isn't much maintenance needed after the solution is live. 

The solution was deployed in-house. It's not rocket science. It's easy, and you can do it just by following the instructions. It's a really user-friendly installation.

I'm working in the development part of the company. I'm not aware of the prices.

I would say it's an affordable product. When it comes to big organizations, it's for sure affordable.

We are a Software AG partner.

I'm mostly using the latest version. I was using version 9.9 when I started. Then I was going through all the versions, including 10.1, 10.3, 10.5, and 10.7. Now, 10.11 is the latest one. However, I'm not sure that I started working on that one in any of my projects. 

We are a partner company of Software AG, the producer of webMethods.

New users should look for a list of references and companies that are using this product. 

For a large-scale organization, this is a must-have product. When it comes to Integration Server and the Enterprise Service Bus as the product which needs to be implemented in an organization, it has many benefits like properly monitoring, tracking, and controlling all the flows in the company and outside the company. It's a great product to have.

I'd rate the solution eight out of ten.

We are using it to orchestrate and configure our APIs.

I believe we are using its latest version.

We needed a tool that was able to orchestrate and help us configure our APIs so that we could maintain and see the heartbeat, traffic, trends, etc.

A while ago, they were hacked, and it took them a very long time to open their website again in order to download any service packs or any features. I don't know what they could do differently. I know that they were vulnerable, and there was some downtime, but because they were down, we were unable to download any potential service packs.

I have been using this solution for about three years.

I would rate it an eight out of 10 in terms of stability and scalability.

We used Dollar Universe or Dollar U. It was more for batch scheduling. We didn't have anything for maintaining, configuring, or hosting our APIs. It was more of a manual process before that.

It is a little complex, but we're okay with that. MuleSoft is obviously the Cadillac and the best of the best, but we just didn't want to pay that sort of price for what MuleSoft can do.

We partnered with our implementation partner to do the install for us. 

Its maintenance is more of a shifting of duties. There are no new FTEs for it. It is just a shifting of duties.

I signed a three-year deal with them. It is a yearly locked-in price for the next three years.

I was the architect of it, and I wasn't personally the one who went deep into it. My advice would be to just partner with an implementation team and make sure that things are documented so that for upgrades, you're not married to them, and you don't have to use them all the time.

I would rate it an eight out of 10.

Currently, we're using this solution for the integration server which helps us to integrate with the mainframe.

This solution could be improved by offering subscription based licensing.

We have been using this solution since 2012. 

This is a stable solution.

This is a scalable solution. 

I would rate the initial setup of this solution a three and a half out of five. 

I would like to have training for my team members, but the training offered is a little bit expensive.

When we started using this tool, we compared it with different tools like IBM message broker and Method. 

Some who consider this solution often avoid it due to its price. Overall, webMethods offers a good user experience and is easy to use for our company. 

I would rate this solution an eight out of ten.