How file transfers work

The following figure shows how HULFT IoT transfers files.

Specification of files to be monitored

You can monitor a particular file by specifying its file name. You can also monitor multiple files in a directory by specifying the path name or by using an asterisk (*) as a wildcard in a file name.

Specification of transfer conditions

Specify the conditions that will trigger the transfer of a file to HULFT. One of the following can be specified for each transfer setting:

• Transfer a file when the file reaches a certain size.
• Transfer a file when a certain period of time has elapsed since the last update.

Note

When you specify the size as a trigger, the file will not be sent to HULFT if its size does not meet or exceed the specified size at the moment that the Agent checks the status of the file, even if the file size once reached the specified size at some point during the monitoring period.

When multiple files are being monitored in a directory, only the files that satisfy the conditions are transferred.

Note

Unless they are deleted from a monitored directory, files that satisfy the specified transfer conditions are transferred to HULFT whenever Agent checks the status of the files, even if the files have already been sent.

To delete files after they are transferred to HULFT, specify transfer settings so that the files are deleted, or set up a Successful Job to delete the files.

Specification of the transfer order

When multiple files are transferred to HULFT at the same trigger fire, you can specify the transfer order. For each transfer settings, you can specify pairings of the search targets and sequence of files as follows:

• Specify the update date of the file as a search target and transfer the files in an ascending order.

  Files are transferred from the oldest one to the newest one.

• Specify the update date of the file as a search target and transfer the files in a descending order.

  Files are transferred from the newest one to the oldest one.

• Specify the file name as a search target and transfer files in an ascending order.

  For example, A.txt, B.txt, and then C.txt are transferred in order.

• Specify the file name as a search target and transfer files in a descending order.

  For example, C.txt, B.txt, and then A.txt are transferred in order.

Specify for [Search Target] on the Transfer Settings screen whether Agent searches the file by using an update date or using a file name. Also, specify for [Search Order] whether Agent searches the file in descending order or in ascending order.

The [Search Target] and [Search Order] is valid within each transfer setting.

For example, if [File name] is set for [Search Target] and [Ascending] is set for [Search Order] in both transfer settings A and B, the files monitored by using transfer settings A are transferred by sorted in its names in ascending order, and the files monitored by using transfer settings B are transferred by sorted in its names in ascending order, individually.

Therefore, depending on the order of Agent processing, the sequence of files which Agent transfers is not in series.

If there are multiple files that become a transfer target in transfer settings A and B, the relationship between transfer settings and transfer order is as follows:

Figure 2.2 Relationship between transfer settings and transfer order.

This is the same if the [Update Date] is specified in the [Search Target]. According to the order of Agent processing, the order of the transferred files may not be in sequence.

If the trigger of transfer settings A and B fire at the same time, files are transferred by using each transfer settings, the file name or update date of transferred files may not be in sequence.

Pairings of the send process multiplex level and the search order

If the number of the files to be transferred exceeds the send process multiplex level when triggers of the multiple transfer settings fired at once, Agents delays sending the extra files until the next trigger fire. In this case, even if you specified the [Search Order] on the Transfer settings screen, according to the order that Agent executed the transfer settings, the files that you wanted to send at first were not sent and remained in Agent.

For this cases, you may take the following actions:

• Modify the [Send Process Multiplex Level] on the Agent Operation Settings screen, so that all files can be sent at the same time, even if the triggers of the multiple transfer settings fired at once.
• Modify the [Monitoring interval] on the Transfer Settings screen, so that the triggers of the different transfer settings can be fired at the different time.

For details about [Send Process Multiplex Level], see (2) Agent Operation Settings.

Specification of socket read timeout

If Agent failed to get a response from HULFT before the specified time elapsed, the Agent judges that the communication error occurred. This waiting time is called "Socket Read Timeout". [Socket Read Timeout] is specified on the Agent Operation Settings screen.

Specification of automatic resending

Agent automatically resends files to HULFT if an error occurs in the communication with the receiving instance of HULFT. Configure [Auto Resend Retry Count] and [Auto Resend Retry Interval] on the Agent Operation Settings screen.

Resend processing uses a checkpoint resending method, which resends a file from the point at which the transfer was suspended. Checkpoint resending can be executed only when all of the conditions are satisfied by the receiving instance of HULFT. If even one of the conditions is not satisfied, resend processing is executed from the beginning of the file.

For details about the relevant conditions, see the Operation Manual for HULFT.

Specification of send process multiplex level

You can specify the maximum number of send processes (huliotsend process) that Agent can start at the same time. This maximum number is called "Send Process Multiplex Level".

The maximum number of the send processes that Agent starts at the same time becomes the maximum number of the files that Agent can transfer to HULFT at the same time. The more the number of send processes which are started at the same time increases, the more the number of the files to be transferred at the same time increases, and the heavier the workload of the system and communication lines become.

[Send Process Multiplex Level] is specified on Agent Operation Settings screen. Specify an appropriate value with the state of the system in use. If the number of transfer files in the Agent instance exceeded the send process multiplex level that was specified on the Agent Operation Settings screen, Agent delays the extra files transferring to the next trigger fire after the time of the monitoring interval that is specified on the Transfer Settings screen elapsed.

The change of the send process multiplex level is detected and applied when Agent polls Manager.

• When the send process multiplex level is decreased during Agent is running:

  New send processes will not be started until the number of files that are being transferred will be less than the number specified by the send process multiplex level.

  In this case, the number of the send processes that are executing might exceed the number that is specified by the send process multiplex level until the file transfers are completed.

• When the send process multiplex level is increased during Agent is running:

  Agent will apply the new send process multiplex level when Agent transfers the next file.