MFT（Managed File Transfer）

Glossary

「MFT（Managed File Transfer）」

This glossary explains various keywords that will help you understand the mindset necessary for data utilization and successful DX.
This time, let's think about "MFT".

What is MFT (Managed File Transfer)?

MFT is an abbreviation for "Managed File Transfer." It refers to the functions and environment that enable safe, secure, and reliable file transfer, as well as the middleware and file sharing infrastructure that realizes such functions.
MFT is not just about being able to transfer files, but also refers to an environment or infrastructure that includes related functions such as ensuring that the transfer process is carried out correctly and reliably, ensuring secure and safe transfers, and keeping a transfer log that can be checked and managed.

"FTP file transfer" causes many problems

Some people may think that if all you need to do is transfer files, then transferring them via FTP is enough, without the need for a dedicated file sharing platform.

It is true that FTP file transfer may be sufficient if it satisfies loose needs such as "it's ok if the files are delivered roughly," "it's no problem if they don't arrive every now and then," or "it's okay if there are a few accidents." However, when considering using file transfer in an IT system for business purposes, you will face a variety of difficult challenges.

Files (data) may be corrupted during transfer.

Data can become garbled or missing during transfer, or the transfer itself can fail due to communication problems. When using an Internet connection, you have to assume that there is a certain probability that transfers will not go well, and even with TCP/IP, there are rare cases where data corruption caused by errors that occasionally occur on the communication path can slip through the error correction function, and as transfers are repeated, accidents can occur where data actually did not arrive, or data actually arrived garbled.

Security concerns

In particular, when transferring data over the Internet, it is necessary to assume that there is a risk that the data will be viewed during transfer or tampered with along the transfer path. Even in situations where such risks exist, it is necessary to be able to explain to external parties that the system used for data transfer is securely designed.

Support for various destinations

The source and destination of a file transfer can be in a variety of environments. It could be frequent transfers within an IT system, or transmissions across the globe over unstable lines. The transfer destination could be a mainframe or a Windows computer.
In the future, we may need to send and receive data to and from different types of communication partners that we have not yet considered, and we will be challenged to see whether we can properly handle a variety of situations.

Did it arrive properly, or will it be a question of whether it was sent or not?

Let's say you transfer very important data. If it doesn't arrive at the recipient, it will cause serious business problems. Is there a way to determine that it has indeed arrived and that there will be no problems? Or will there be a dispute later about whether or not the file was sent or received?

These are just some of the concerns about file transfers. However, this is not all that needs to be considered. Some people may think that it's just file transfer, but the truth is that there are many challenges when it comes to making file transfer that can be used effectively in business systems.

If you think, "We can just develop and implement it ourselves," you'll face a lot of hardship.

Some people may be thinking, "Well, why not just create file transfer function with such functionality ourselves?" It is certainly possible to develop one yourself, but once you start, you will encounter many unexpected difficulties.

How do you ensure that the system you have created is "really safe and secure" and "has sufficient functionality"?

How can you be sure that the file sharing platform you've implemented is truly well-built? You'll need to go to great lengths to verify this, including conducting extensive software testing. This can be a huge amount of work.

Adaptation to a wide variety of environments and ongoing adaptation in the future

When file transfer between various environments, it is necessary to confirm that it works properly in those environments, such as mainframe, Windows, Linux, etc., as well as Japanese and English environments, use within a system or on the cloud, communication via the Internet or dedicated lines, etc. Not only is it time-consuming to carry out file transfer work that thoroughly covers all of these environments, but even just considering what needs to be confirmed can be quite a hassle.

Even if you have completed a single operation check, you will need to continue to perform additional checks every time a new environment appears, such as when a new version of the OS is released.

Management and operation functions such as logging

The need for implementing management and operational functions, such as "logging" and "permission-related management," is often overlooked. If you need a function that allows you to check who sent what files and when, then of course you'll need to provide such a function. Sometimes, line failures can occur during transfers, and if you can't check how far the process has progressed and what happened, it can lead to issues such as liability issues between the source and destination. To ensure a platform that can continue to operate smoothly even in such situations, you need to create a system that keeps practical logs that are necessary for status confirmation and decision-making. As you can see, it's often too difficult to build this on your own.

Will the system be able to be maintained in the future?

Ten years after creating a system, the business may still be running and the system may still be in use, but the person who created it may no longer be around, and even the person who created it may have forgotten the details of when it was created. In that state, would you be able to respond if you were asked to expand its functionality (while of course maintaining a high level of safety and security)?

How do you prove that file transfer system you created is safe and secure?

If you were to create such a system, how would you prove to a third party that it is "sufficiently safe and secure" and has a full set of functions? Or, if you were the one having a system created, how would you confirm that there would be no problems when using that system? It must not be easy.

"MFT" (Managed File Transfer) solves all these problems at once.

So, even if you just want to transfer files, it turns out that it can be quite a hassle to think about "building a solid file sharing platform that you can entrust with your work." And the above is not all the concerns about file transfer. I hope you understand that it's quite difficult.

It would be a hopeless situation if you thought you had to do it yourself, but if you decide to use MFT products as your foundation, you can solve these problems immediately by simply purchasing and installing them.

Files (data) may be corrupted during transfer.
Simply ask the MFT product to "send a file" and the file will arrive safely at its destination without being corrupted or distorted.
Security concerns
MFT products can be trusted to provide a level of support that meets security certification standards, including proper encryption and properly erasing any unnecessary temporary data.
Support for various destinations
Our MFT products support a variety of environments, including mainframes, Linux, various UNIX systems, Windows, and the cloud.
Did it "arrive properly" or will it be a case of "sent or not sent"?
Transfer logs are kept, so even if the transfer doesn't go smoothly due to a line failure or other reason, you can check how far the process went, where it failed, and what the results were.
How do you ensure that the system you create is truly safe and secure?
The MFT product has been tested to ensure that the product can file transfer safely and securely.
Not only responding to the current diverse environment, but also continuing to respond in the future
You can leave it to the MFT product to handle OS upgrades, new OSes, and cloud services. You no longer need to create everything yourself every time.
Management functions such as logging
If you create your own forwarding function, you will also need to create logging functions, user permissions, and management functions, but complete functions are provided from the start.
Will the system be able to be maintained in the future?
file transfer function is maintained on the MFT product side, and the IT system has been simplified, making it easier to understand and modify. When modifying the system in the future, recruiting engineers will be as simple as "We are looking for people who understand XX in MFT products," and training for engineers will be as simple as "Please take the official training course for XX product."
How can you prove to a third party that file transfer system you have created is safe and secure?
Even when a customer asks, "Is your system safe?", I can simply explain, "We use the widely used MFT product XX as our file integration platform," and "That means it's safe."
If you are the party having a system created, all you need to do is say, "Please use MFT product XX as the file integration platform."

These advantages make a big difference when proving that official standards are met when transferring data that requires a high level of care or when linking with systems that require a high level of safety and security, such as when handling credit card information or data integration with financial institutions.

Furthermore, when file transfer, both the sender and receiver of the data may need to perform various processes before and after the transfer, such as system integration and backup processing. Simply being able to transfer data would ultimately require the development of these aspects. MFT products can efficiently perform the various processes related to file transfer, and many of them provide an environment in which file sharing can be smoothly and comprehensively utilized.

MFT in various usage forms

So far, we have been explaining MFT from the perspective of its main feature of "ensuring reliable transfer," but file transfer use cases are becoming more and more diverse.

System-to-system (application-to-application) file transfer (A to A):
For example, it can be used to share files between different systems, such as data integration from an "order management system" to an "accounting system."
User-to-user file transfer:
For example, if you want your boss to review a document you have created, this is a usage scenario that requires file transfer between people.
file transfer between distant locations or between companies (B to B):
For example, it can be used for long-distance transfers between a Tokyo headquarters and an overseas branch, or for transferring files with business partners. Because communication is often long distance, there are difficulties in that it must go via the Internet rather than a closed communication network, and the sender and receiver are different organizations with separate responsibilities for the transfer.
Scheduled file transfer and ad-hoc file transfer (Ad-hoc MFT):
While some usage patterns require transfers to be made correctly according to set rules, such as transferring order data between systems at a set time every day, other usage patterns require flexible use, such as the transfer of files between people as needed.
High-speed transfer of large file transfer or frequent file transfer:
Some uses involve transferring very large files, such as video data, while other uses involve transferring files that are not huge but are transferred frequently.
Transfer needs that transcend different technologies:
For example, in file transfer between the cloud and a mainframe, the source and destination technologies are very different. In such situations, if you create your own system without using MFT, you may need engineers with a deep understanding of both technologies, which can be difficult to secure.

A distinctive feature of MFT products is that they often provide comprehensive support for these various usage patterns.

Related keywords (for further understanding)

File Linkage
- Now that you understand MFT, if you're wondering why "file transfer" is used as a means of collaboration, please take a look here.
EAI
- This explains how important and meaningful it is to be able to data integration from various systems.
iPaaS
- A cloud service that "connects" various clouds with external systems and data simply by operating on a GUI is called iPaaS.
Cloud integration
- Using the cloud in conjunction with external systems and other cloud services. In order to successfully introduce and utilize cloud services, achieving cloud integration is often as important as introducing and utilizing the cloud itself.
Excel Link
- Excel is an essential tool in the use of IT in the real world. By effectively linking Excel with external IT, you can make the most of Excel's strengths while smoothly promoting IT use.

If you are interested in MFT

Please try out HULFT, the de facto standard and pinnacle of Japanese MFT products. It has an overwhelming track record, meeting the needs of financial institutions, which have strict requirements for IT systems, as a platform product.

HULFT: The de facto standard for MFT

In addition to supporting both new and old operating environments, from mainframes to Linux and Windows, we are also working to enhance functionality that will be useful in the cloud-native era, such as file integration with cloud services (supports transfers with major clouds such as Amazon S3) and support for container technology.

It also has the functionality to efficiently handle the various processes that inevitably occur before and after file transfer is also used as a means to combine new and old IT technologies, such as by freely linking mainframes and clouds without the need for engineers who are knowledgeable about both.

The de facto standard for Managed File Transfer (MFT): Latest version

Learn about file transfer mechanisms through HULFT product introduction and online seminars

"HULFT WebConnect" enables safe and secure transfer via the Internet

File sharing with HULFT can be done safely and securely via the internet. There is no need for costly dedicated lines or VPNs, and because it is a cloud service, there is no need to build your own system. File sharing with domestic bases as well as overseas bases can be done safely and securely with the reliable HULFT quality.