Axway solution for Internal File Transfer

In this video you will learn about Axway's solution to move files between internal applications at high speed, high security and a robust protocol that guarantees file delivery and payload integrity - regardless of source and target platforms.
Hello, I'm Jose Villanova, Solutions Architect at Axway. In this video, we'll talk about Axway's approach to internal file transfer.
Our internal file transfer capabilities are a key pillar of our overall MFT platform offering. Please refer to some of our other videos that discuss B2B external file transfer, self-service concepts, central governance of your MFT deployments, as well as monitoring and operational visibility components.
Let's understand why a peer-to-peer solution is a critical part of your MFT strategy. But first, how many categories of file transfer are there? Axway looks at managed file transfer from three key perspectives:
The first perspective is external B2B file transfer. This involves secure file exchange between your internal departments, file shares, servers, applications, and your external partners, clients, banks, regulatory agencies, to name a few.
The second perspective is internal peer-to-peer file transfer. This addresses the need to exchange files between internal users, servers, and applications without routing through a B2B gateway.
The third perspective is ad hoc or human dynamics file transfer. This is the need for secure file sharing and collaboration, often in non-standard, non-automated formats.
Many who have a file transmission gateway but haven't adopted a peer-to-peer solution for internal file transfer frequently ask the following two questions:
If our current file exchange gateway has all the protocols and processing capabilities to handle internal and external file transfer, why do we need an internal file transfer solution? What value does a peer-to-peer solution provide on top of our investment in a file transmissions gateway?
I will answer both questions in the next few minutes. Let's start by looking at this from a bird's eye view.
Currently, you rely on your file transmission gateway to exchange files with your external business partners, and you likely use it for many internal transfers too. Many transfers consist of small or medium-sized files between 5 and 20 Megs. However, companies across all industries are seeing internal file transfer volumes increase in size and quantity. This puts a necessary load on the gateway, which must always be available and run efficiently to process files quickly and adhere to your SLAs.
So, what happens to your operations if your file transmission gateway were to go down? Here are a few scenarios:
You can't exchange files with your partners, and costly SLAs could be breached if it's not brought back up promptly.
Your internal operations and business processes, which depend on the gateway for internal file transfers, would be paralyzed.
Now, let's take a closer look at what's happening. A connection is made from an internal server to the file transmission gateway (whether on-prem or in the cloud). The file is transferred, undergoes necessary processing like virus scanning, consumes storage and network bandwidth, and if encrypted, decryption and re-encryption processes occur. Finally, a new connection is established to the target system. Some protocols, like SFTP or SSH, are resource-heavy, which consumes valuable processing power.
Imagine this process happening hundreds, thousands, or even several million times per month. To handle this, some scale their gateway, even if inconsistently, due to the critical files being exchanged. This inefficiency undermines the ROI one expects from moving to the cloud.
#managedfiletransfer #mft #data