There are many use cases for webMethods ActiveTransfer, but the main focus for us is transferring files internally between applications or externally between partners. From a technical point of view, it can be seen a tool for file transfer for A2A (application-to-application), and from a market model point of view, it's also a B2B (business-to-business) tool. In terms of extras, it includes an engine for translation, which comes as an add-on, so that customers can translate files as they send or receive them from external partners. We could, of course, also create a custom interface in order to allow physical users to perform file transfer, but this is not a common use case. Using webMethods ActiveTransfer, we can create rules for automatic application-to-application file transfers, and one of our customers in Italy is even using it for both file transfers and as an ESB (Enterprise Service Bus) as part of their supply chain infrastructure where there is a very high volume of messages being exchanged (thousands and thousands of messages per day). If the customer's infrastructure is complex, with high-availability clusters and so on, then we often have to implement not only the basic use case, but also consider other business cases as well, such as in our Italian customer's situation where ActiveTransfer must additionally communicate with their order management orchestrator and other parts of their infrastructure. There are offerings for deployment on cloud or hybrid as well, but most of the customers who have around 1,000 employees prefer the solution to be situated on-premises.
Integration Administrator at Sainsbury's Supermarkets Ltd
Real User
2022-06-06T19:10:00Z
Jun 6, 2022
We use ActiveTransfer to call internal APIs and transfer files from a third party to the cloud for application purposes and from a third party to on-prem. We also send files to the third party sometimes. We have a payments system and transfer files across the system to make customer domains. We have on-prem, cloud, and hybrid deployments and transfer files across all of them. We're working with webMethods cloud, AWS, and Azure. Our eight-member team is using webMethods MFT and other integrations, and we have a shared team to work on multi-technologies, like web issues, Snowflake, webMethods MFTs, etc.
webMethods.io Integration is a powerful integration platform as a service (iPaaS) that provides a combination of capabilities offered by ESBs, data integration systems, API management tools, and B2B gateways.
There are many use cases for webMethods ActiveTransfer, but the main focus for us is transferring files internally between applications or externally between partners. From a technical point of view, it can be seen a tool for file transfer for A2A (application-to-application), and from a market model point of view, it's also a B2B (business-to-business) tool. In terms of extras, it includes an engine for translation, which comes as an add-on, so that customers can translate files as they send or receive them from external partners. We could, of course, also create a custom interface in order to allow physical users to perform file transfer, but this is not a common use case. Using webMethods ActiveTransfer, we can create rules for automatic application-to-application file transfers, and one of our customers in Italy is even using it for both file transfers and as an ESB (Enterprise Service Bus) as part of their supply chain infrastructure where there is a very high volume of messages being exchanged (thousands and thousands of messages per day). If the customer's infrastructure is complex, with high-availability clusters and so on, then we often have to implement not only the basic use case, but also consider other business cases as well, such as in our Italian customer's situation where ActiveTransfer must additionally communicate with their order management orchestrator and other parts of their infrastructure. There are offerings for deployment on cloud or hybrid as well, but most of the customers who have around 1,000 employees prefer the solution to be situated on-premises.
We use ActiveTransfer to call internal APIs and transfer files from a third party to the cloud for application purposes and from a third party to on-prem. We also send files to the third party sometimes. We have a payments system and transfer files across the system to make customer domains. We have on-prem, cloud, and hybrid deployments and transfer files across all of them. We're working with webMethods cloud, AWS, and Azure. Our eight-member team is using webMethods MFT and other integrations, and we have a shared team to work on multi-technologies, like web issues, Snowflake, webMethods MFTs, etc.