HULFT Short Stories

Vol.9 Differences between FTP and HULFT transfers: Three cases

Hello.
My name is Okazaki and I am in charge of HULFT seminar.

It's March now. Although it's already spring according to the calendar, the weather is still cold.
March is the time when plum blossoms are beautiful.
In China, plum blossoms, which endure the cold and bloom beautifully, are beloved as a symbol of perseverance and the fruition of hard work.
I hope that all your efforts this year will bear fruit, just like the plum blossoms.

March is a time of transfers and other reassignments.
Some of you may be in charge of HULFT for the first time, or are planning to become so.
For those of you who will be taking charge of HULFT for the first time, you may be thinking, "Why don't I just use FTP and file transfer is free?
You may be thinking, "Why not just use FTP if I want to use ?
The difference from FTP was introduced in HULFT Small Talk Vol. 1 and 2, but this time, we would like to reintroduce the difference between FTP and FTP.
I would like to review the basics of HULFT transfer with the theme of the difference between FTP and transfer.

Here are three cases of differences between FTP and HULFT transfers.

1. What to do when the received data is missing?

Like HULFT, FTP is a communication method that uses TCP/IP, so transfer reliability is generally ensured, but it does not check the integrity of the transferred files, that is, the consistency between the files on the sending side and the files on the receiving side.
So if the network connection is lost or a timeout occurs during transfer, the transfer itself may be completed successfully, but the data inside may be missing.
If you use FTP, you will need to send a separate check file, check it, and then resend it if it is incomplete, which can be a bit of a hassle and time-consuming.

HULFT comes standard with a function to check data integrity, so there is no need to create a system for checking.
In addition to checking the number of records and size, you can also check by hash value.
If a mismatch is found with the data on the sending side, an error notification will be sent to the sending side.
With HULFT, you can check completeness with just one setting, so there is no need to spend a lot of time on development.

2. How can I notify the operations staff by email when an error occurs?

file transfer You need to build error detection and recovery handling mechanisms into the infrastructure in case errors occur during transfer.
If you build the file transfer infrastructure via FTP, it is quite difficult to implement those mechanisms.
You need to build a monitoring mechanism, then an error handling mechanism such as sending e-mails, and then a recovery processing mechanism such as resending process.
Since the method of recovery processing differs depending on the business, it may be necessary to think about it from the time when the specifications are being finalized.

HULFT If this is the case, the mechanisms for error detection and recovery processing are functions originally provided by HULFT.
When an error occurs, the system notifies the user of the error code corresponding to the error, so the cause of the error and how to deal with it can be immediately understood.
Even if an e-mail is sent to the operation staff when an error occurs, the mechanism can be easily created using the HULFT function.
In addition, HULFT will automatically resend and terminate normally if the transfer is interrupted due to a network error, so there is no need to bother the operations staff.

3. How can I transfer emails at exactly 5:00 PM every day?

When it comes to file transfer operations, I think most of the time it is done automatically based on a schedule or the status of the file.
However, FTP does not have a function for automatic execution.
If you want to run it at a certain time every day, you can use the Task Scheduler in Windows to set it up, but unfortunately it does not allow you to set it up for holidays, so you cannot set it up if you do not want it to transfer on holidays, for example.
If you want to set such flexible schedules, you will need to invest additional development time.

HUFT also has a scheduling function, so it's easy to specify a date and time for automatic execution.
You can also set holidays, so it's flexible.
In addition, there is a trigger function that transfers files when they are created in a certain folder, so you can send files at any time you want.


As you can see, there is a big difference in efficiency between FTP and HULFT when it comes to building and operating file transfer infrastructure.
With FTP, it would take a lot of time and effort to build it, but with HULFT, it's already a feature so it can be easily implemented.

Furthermore, with HULFT, changes can be easily made during operational maintenance.

If you want to change the timing of automatic execution, you can easily change it from the settings on the GUI screen.

We also provide detailed explanations of HULFT and FTP at our monthly seminars.
If you think of file transfer as FTP, please join us!

Click here for the "Create from Scratch! Hands-on Seminar on Building file transfer System"

We also hold monthly seminars for people who are working with HULFT for the first time.
This seminar will introduce the basic functions of HULFT Products, so it is recommended for those who have little knowledge about HULFT.

Click here for the "First-time HULFT Products Introduction Seminar"

I look forward to seeing you all at the seminar! Please look forward to the next HULFT Short Story!

Inquiry

We look forward to receiving your opinions, comments, and letters regarding this column.
Contact:hulseminar@hulft.com

Experience HULFT Products.

Related Content