The main reason my company decided to replace webMethods.io Integration is because of the integration capabilities in the newer versions of the tool. Whenever there is a new version of webMethods.io Integrations, there is a lot of work to be done by our company since the newer versions don't offer seamless integration. The aforementioned reason can be considered for improvement in webMethods.io Integrations. With the solution, our company has experienced sudden outages at times. The product's stability is an area of concern where improvements are required. Not just the cost related to licensing but also the cost of introducing new versions need improvement in the product. When you have an OS like Windows or Apple, in which some new features are installed when you restart your system, after which everything works fine, with webMethods.io Integration, the new features introduced in the tool don't just need you to stop and restart your application but expects you to update the whole application to be able to use the new functionalities, which is something that is good. My company does a business in which we have to create a complete project which costs a lot of money. In the future, I expect to not be paying a lot of money or extra work to be able to update the product, and webMethods.io Integration needs to update the product automatically.
I am not satisfied with the solution because it takes too much effort to migrate and add new information. The migration could be easier. There's a lot of rework that needs to be done if you go to a newer version.
Programm Manager at a computer software company with 1,001-5,000 employees
Real User
2022-01-04T21:13:01Z
Jan 4, 2022
The products, at the moment, are new and there should perhaps be support for the older version of the protocols. While I know that they have the new versions, which are actually needed, I don't believe they have that capacity when it comes to any integration with older systems. This is because I believe us to be more advanced nowadays, with what they are doing for the roadmap of new technologies.
I think rules engine processes and BPM processes should be improved. I think they must accommodate the future of the communication between systems and that is related to web services and the like.
API (application programming interface) management is the process of managing different API functions, such as designing, releasing, documenting, analyzing, and monitoring APIs in a safe environment.
The main reason my company decided to replace webMethods.io Integration is because of the integration capabilities in the newer versions of the tool. Whenever there is a new version of webMethods.io Integrations, there is a lot of work to be done by our company since the newer versions don't offer seamless integration. The aforementioned reason can be considered for improvement in webMethods.io Integrations. With the solution, our company has experienced sudden outages at times. The product's stability is an area of concern where improvements are required. Not just the cost related to licensing but also the cost of introducing new versions need improvement in the product. When you have an OS like Windows or Apple, in which some new features are installed when you restart your system, after which everything works fine, with webMethods.io Integration, the new features introduced in the tool don't just need you to stop and restart your application but expects you to update the whole application to be able to use the new functionalities, which is something that is good. My company does a business in which we have to create a complete project which costs a lot of money. In the future, I expect to not be paying a lot of money or extra work to be able to update the product, and webMethods.io Integration needs to update the product automatically.
webMethods.io Integration's installation is complex. It should also improve integration and connectors.
The solution's release management and JSON services need improvement.
Any solution needs continuous development in integration and processing.
I am not satisfied with the solution because it takes too much effort to migrate and add new information. The migration could be easier. There's a lot of rework that needs to be done if you go to a newer version.
The products, at the moment, are new and there should perhaps be support for the older version of the protocols. While I know that they have the new versions, which are actually needed, I don't believe they have that capacity when it comes to any integration with older systems. This is because I believe us to be more advanced nowadays, with what they are doing for the roadmap of new technologies.
I think rules engine processes and BPM processes should be improved. I think they must accommodate the future of the communication between systems and that is related to web services and the like.