Share your experience using SWIFTnet FIN

MuleSoft Anypoint Platform was purchased through a lot of third-party vendors that we connect to. It's more of an integration-based solution. We have different connections; my work involves more connectivity between ERPs and data storage such as Azure or AWS from SAP. That's what I use for that integration platform.

The best features in MuleSoft Anypoint Platform for me are transparency between logging in or deploying and using different environments. Managing different environments for the transparency of error logins or how to trace traceability is very important. It's very easy to use and sort, so you can see where everything has gone right and everything has gone wrong.

I'm aware of the drag-and-drop interface in MuleSoft Anypoint Platform, and it's very, very quick. It's very time-saving and very efficient.

The security features on MuleSoft Anypoint Platform help maintain data integrity in my organization; I would say it's second to none. It's one of the best out there that I have worked with because of the encryption and decryption, and there are a lot of security aspects.

I would assess the platform's data mapping and transformation capabilities as amazing. Automation has been straightforward; the transformation and mapping have been easy to use, easy to source, and from the source to the target. I would say it has been very good.

The logs in terms of how the logs are populated could be improved. Error logs might need some work, but I'm just not thinking of anything specific right now.

I've been using MuleSoft Anypoint Platform for almost three years now, or two years.

I am extremely satisfied with MuleSoft technical support and with Salesforce support. I would probably rate the support for MuleSoft Anypoint Platform a nine on a scale from one to ten.

Positive

Usually, three to four people are involved in the integration process for MuleSoft Anypoint Platform.

I am using MuleSoft Anypoint Platform right at the moment. Any challenges with MuleSoft Anypoint Platform so far depend on the integration we're doing. Some integrations can be challenging, depending on having to whitelist some of the URLs and then getting the postman collection or dealing with SAP layers and the different basis layers. Other than that, it's okay. It depends on the challenges. I would say it's an easy, user-friendly tool.

I'm more behind the scenes in terms of deployment for MuleSoft Anypoint Platform. I get everything ready, but I oversee a lot of that part in that regard. The team works on it on a daily basis for any issues with the errors, error logins, and investigation. That's where you can find me. Deployment takes a couple of hours, depending on the integration as well.

My colleagues use the Anypoint Exchange feature, but I don't use it.

I would say it's beneficial in terms of finance to use MuleSoft Anypoint Platform because it's one of the chosen tools we are using in the organization. From what I hear, I'm not in the meetings, but I could say it is beneficial.

I would rate this review a nine out of ten.

I use webMethods.io primarily for the integration of APIs. Could you please describe a few use cases for it?

webMethods.io is a comprehensive box that provides multiple functionalities. I appreciate it because we can integrate many applications and any kind of API we want to integrate. Other functionality includes event-based functionality and a PubSub mechanism. If we want to schedule anything, that is also available. If we want to make a REST API, SOAP, REST, or any other type, all kinds of things are put in one box and we can make anything we want to.

I do not use much of the drag-and-drop interface in webMethods.io; I usually code in it. Flow services and all basically deal with Flow language.

Many connectors are available in webMethods.io. I have worked with adapters and listeners.

Many things are evolving with the AI buzz in the market. What I would like to see improved or enhanced in webMethods.io in the future is that since webMethods.io is already under IBM, I think IBM will introduce and integrate AI into it. Additionally, regarding what webMethods.io can improve is the license cost. Other cloud players are also providing the same kind of functionality, such as AWS and Azure. webMethods.io is being installed on-premises, but AWS is providing it directly in the cloud. When comparing the license cost and request per minute cost, webMethods.io needs to address that. There are many competitors in the market for this.

I have been working with webMethods.io for around three to four years.

This is an area where I think webMethods.io has concerns. If any webMethods.io product is installed on-premises and a company wants to scale its application, either vertical scaling or horizontal scaling is needed. This means we need to procure more infrastructure or purchase it from the cloud and then host it. When it comes to scaling, it requires more RAM and more machines.

There are many resources available regarding webMethods.io technical support. An incident portal is available where we can raise tickets and based on priority, they reply. I would rate the technical support for webMethods.io at around six or seven on a scale of one to ten, where ten is the best.

Neutral

I have been working with webMethods.io for three to four years only and have not worked with any competitors or other products of the same kind.

The initial setup process for webMethods.io is quite straightforward. We need to install it on-premises. We can create an image and install it, and it is quite straightforward without much complexity.

Based on my rich experience with webMethods.io, I can share this advice. When it comes to integration, webMethods.io provides many features, so companies should consider it. However, at the same time, they should also evaluate competitors. If other companies are choosing webMethods.io for their applications, they will definitely compare pricing. They will also look at the scaling capabilities. Based on the scale and all considerations, companies will definitely compare pricing with clouds and MuleSoft, which is another competitor. It depends on what the company wants. Many others are providing similar functionality, so it comes down to pricing and the scaling part.

I work with the on-premises deployment of webMethods.io. I use MWS as a tool for monitoring and analytics in webMethods.io. Apart from that, I usually use logs and create custom logs as I want. We do not use any special functionality, but we create pages for statistics to analyze in Integration Server.

Basically, what we are integrating with webMethods.io determines the functionality provided. If we are integrating with an API, then webMethods.io provides HTTP functionality for integrating. If we are integrating with a database, then it provides the adapters I want. Based on the requirements and what we want, webMethods.io provides different functionality for integration. We do not need to figure out anything. We can use features of webMethods.io and integrate.

My overall review rating for webMethods.io is six out of ten.