Products
- TOP
- Products
- HULFT IoT TAKEBISHI
- Release Note
Release Note
Ver.2.1.0 - 2020 November
Added features
HULFT IoT TAKEBISHI Manager and HULFT IoT TAKEBISHI Agent
| Release No | Contents |
|---|---|
| HIPJ-1307 | An available format of the product media is added |
| HIPJ-699 | HULFT over TLS is added |
| HIPJ-516 | Release of a region edition |
| HIPJ-174 | Settings for a time period when Agent and Manager can communicate |
| HIPJ-164 | Data verification function for transfer data |
| HIPJ-159 | Initial settings for Agent |
HULFT IoT TAKEBISHI Manager
| Release No | Contents |
|---|---|
| HIPJ-1154 | Searching Receive Logs by specifying a period of reception start date and time and reception completion date and time |
| HIPJ-564 | Operation without HULFT screen |
| HIPJ-530 | Detection of events that are occurred in HULFT IoT TAKEBISHI by using an OS log monitoring system |
| HIPJ-228 | Controlling the HULFT IoT TAKEBISHI from an external service |
| HIPJ-545 | Event detection function is added |
| HIPJ-531 | Email notification function is added |
HULFT IoT TAKEBISHI Agent
| Release No | Contents |
|---|---|
| HIPJ-621 | Release of MIPS-II module for HULFT IoT TAKEBISHI Agent |
Improved features
HULFT IoT TAKEBISHI Manager and HULFT IoT TAKEBISHI Agent
| Release No | Contents |
|---|---|
| HIOT-92 | Usage of HULFT IoT TAKEBISHI in the environment using an SSL accelerator |
HULFT IoT TAKEBISHI Manager
| Release No | Contents |
|---|---|
| HIOT-296 | Manager operation improvement when the number of tasks in the Receive Task Queue is maximum |
| HIPJ-1367 | Parameters that are unnecessary or do not return any value are deleted from the REST API |
| HIPJ-1354 | Installer options of HULFT IoT TAKEBISHI Manager for Linux are changed |
| HIPJ-1321 | Usage that is displayed by the installer of HULFT IoT TAKEBISHI Manager for Linux is improved |
| HIPJ-1319 | The installer screen is improved |
| HIPJ-1318 | Log messages are improved |
| HIPJ-1312 | JRE 8 is removed from the necessary software |
| HIPJ-1311 | The installation module of HULFT IoT TAKEBISHI Manager for Windows is changed to ZIP format |
| HIPJ-1308 | The directory structure of the product media is revised |
| HIPJ-1153 | API response parameters are added |
| HIPJ-1137 | Deletion of unnecessary parameters |
| HIPJ-512 | Specification improvement for installation |
| HIPJ-703 | Change of a search condition on Unit List screen from complete match to partial match |
| HIPJ-652 | End of Java installation path restrictions for Manager in Linux environment |
| HIPJ-628 | The term of API function is specified by seconds, but not by milliseconds |
| HIPJ-475 | Deletion of a setting of Transfer Encoding from Profile |
| HIPJ-434 | Change of a method to specify a Manager home directory |
| HIPJ-487 | Log message is improved |
HULFT IoT TAKEBISHI Agent
| Release No | Contents |
|---|---|
| HIOT-306 | Dividing the output directory for the Agent system files and the temporary storage directory for the log files |
| HIPJ-1426 | Windows service name of HULFT IoT TAKEBISHI Agent for Windows is variable |
| HIPJ-1253 | The user experience for introduction is improved |
| HIPJ-447 | Specification of an IPV4 address |
Issues
HULFT IoT TAKEBISHI Manager
| Release No | Contents |
|---|---|
| HIOT-484 | Resources will leak when Manager refers to the product information |
| HIOT-473 | Even if the product key update failed, the screen might show as if the product key is updated correctly. |
| HIOT-338 | If HULFT fails to start by some reasons during the users install HULFT IoT TAKEBISHI Manager, the installation fails. |
| HIOT-297 | Files can be distributed to the HULFT IoT TAKEBISHI Agent instance whose status is Standby. |
| HIOT-288 | The deletion of HULFT IoT TAKEBISHI Agent might fail |
| HIOT-200 | When the users update HULFT IoT TAKEBISHI Manager, if the application.properties file includes commented out lines, HULFT IoT TAKEBISHI Manager may convert only the rows that are commented out. |
| HIOT-159 | The file upload to HULFT IoT TAKEBISHI Manager might fail. |
| HIOT-113 | If the value of the particular items in a transfer log includes one or more commas, HULFT IoT TAKEBISHI Manager cannot register transfer logs that HULFT IoT TAKEBISHI Agent output. |
| HIOT-108 | Next Scheduled Sync Time might show the later time than the intended schedule. |
| HIOT-107 | The Change Profile screen might show the unintended profile. |
| HIOT-103 | HULFT IoT TAKEBISHI Manager might fail an API authentication. |
| HIOT-99 | When the incorrect value is set to the register a whitelist entry API function, the returned HTTP status code is not appropriate. |
| HIOT-97 | The logs other than the target of truncation might be deleted by using the log truncation function. |
| HIPJ-1574 | The registered job might not run |
| HIPJ-1502 | Backup of PostgreSQL may fail when the user updates HULFT IoT TAKEBISHI Manager |
| HIPJ-1404 | Services of HULFT IoT TAKEBISHI Manager for Windows might not start |
| HIPJ-1375 | A login user who has an admin privilege cannot change own password |
| HIPJ-1179 | HULFT IoT TAKEBISHI Manager does not restart after the change of host name |
| HIPJ-1148 | If the characters that are longer than the specifiable length are written in a successful job or an unsuccessful job by using the Modify Transfer Settings details API function, the returned HTTP status code is not appropriate |
| HIPJ-1098 | Unavailable characters can be set to the user password by using the Create User API function |
| HIPJ-860 | The maximum values for session timeout written in the User’s Guide are wrong |
| HIPJ-824 | If you update Manager when an uploaded module is there, the module becomes unavailable |
| HIPJ-808 | If an auto resend retry is repeated more than 255 times, you may not refer or delete the receive logs correctly on the management screen of HULFT |
| HIPJ-748 | A MAC address of which the length is not 48 bits (6 bytes) can be registered to the whitelist |
| HIPJ-707 | You can register an incorrect MAC address to the whitelist |
| HIPJ-620 | You can specify transfer settings by using the existing file ID when you register transfer settings |
| HIPJ-528 | If Agent fails to connect Manager just after Agent started, the information that an Agent status display command (huliotinfo) outputs is incorrect |
| HIPJ-249 | On the Change Module Version screen, Change Version button is valid when no module is selected |
| HIPJ-147 | The Unit list on the Permission Settings tab cannot be sorted |
| HIPJ-145 | Access Log Type column in the Access Log screen cannot be sorted |
| HIPJ-142 | File Name at Send Destination column in Reception Settings cannot be sorted |
| HIPJ-140 | Symbol characters can be entered in the Agent Operation Settings screen |
| HIPJ-136 | The whitelist entry that includes colons cannot be registered |
| HIPJ-135 | Alphanumeric characters using 2 bytes codes for MAC address can be entered |
| HIPJ-134 | When you maximize or minimize the browser screen while the list of Units is displayed in the Change Unit screen, a part of the pulldown menu is displayed across the frame |
| HIPJ-133 | User name or password is incorrect. is displayed when you log in Manager while the process of the database (PostgreSQL) has been stopped |
| HIPJ-132 | When you change Unit, no errors are displayed if you select the deleted Unit |
| HIPJ-131 | When you display the Transfer Settings Details screen by using FireFox, the long monitored file name is displayed across the frame |
| HIPJ-109 | Even if DEFLATE compression was specified for a transfer, No compression was displayed in the Compression Ratio field of the Transfer Log Details screen when the transfer failed |
| HIPJ-108 | No Units are displayed in the Unit list on the Permission Settings tab under Security |
| HIPJ-104 | When you search Unit by using Port Number on Receiver in the Unit List screen, an error does not occur even if you enter characters other than numerals |
| HIPJ-103 | When you change a Unit name, even if the number of entered characters exceeds the 64 characters, the text box appears without changing to red |
| HIPJ-102 | When you search trace logs by using a date and time on the Trace Logs screen, the Trace Logs of the unexpected date and time is displayed |
| HIPJ-101 | The messages to inform that an error occurred for the specific operations are not displayed while the connection to the database is disconnected |
| HIPJ-99 | The candidate names that do not coincident with the characters that are entered as a search condition in the Agent List screen are displayed |
| HIPJ-97 | If you enter multiple spaces in sequence when you specify a monitored file name, the monitored file name in which the multiple spaces become one space is displayed in the Transfer Settings screen |
HULFT IoT TAKEBISHI Agent
| Release No | Contents |
|---|---|
| HIPJ-1559 | In the Windows environment, when 2,147,483 seconds (approximately 24.8 days) elapses after OS starts, HULFT IoT TAKEBISHI Agent might continuously execute file triggers and polling processing without waiting time |
| HIPJ-1512 | HULFT IoT TAKEBISHI Agent might fail to register the log to HULFT IoT TAKEBISHI Manager and it cannot record logs anymore |
| HIPJ-1274 | If HULFT IoT TAKEBISHI Agent fails to establish a connection to HULFT at a start of file transfer, HULFT IoT TAKEBISHI Agent might not perform according to the Connection retry count that you set by using Operation Settings |
| HIPJ-1273 | HULFT IoT TAKEBISHI Agent might execute a send processing of log information to HULFT IoT TAKEBISHI Manager every second |
| HIPJ-1259 | If a file that is used by Agent is broken, Agent might not start |
| HIPJ-872 | When you specify one or more tags without an equal sign (=) in the settings file for Agent, start of Agent fails |
| HIPJ-867 | Remote Update is not executed very rarely |
| HIPJ-826 | If you specify a path that includes one or more spaces when you execute new installation, Remote Update fails |
| HIPJ-624 | Agent remarks information is once registered, you cannot erase it |
| HIPJ-570 | If you specify a path that includes one or more spaces when you execute new installation, automatic start may fail |
| HIPJ-569 | If you specify an existing directory for the installation directory, new installation may fail |
| HIPJ-529 | If a file whose data includes one or more '¥0' characters is transferred by using a text transfer, the data is not transferred correctly |
| HIPJ-509 | When Agent activation fails, the information that an Agent status display command (huliotinfo) outputs is incorrect |
| HIPJ-96 | A monitored file may be detected repeatedly |
| HIPJ-92 | When you specify job_exec_module in the settings file (lockdown.conf), if one or more spaces are included in the path to the execution module, execution of the job fails |
| HIPJ-701 | When Agent automatically resends files, duplicate data might be transferred |
| HIPJ-521 | Agent might perform unexpectedly when a job before or after transferring files or a job after receiving files is executed |
| HIPJ-520 | When job_exec_module is specified in the settings file (lockdown.conf), the parameters that are used for starting a user command are not divided by spaces |
| HIPJ-518 | When job_exec_module is specified in the settings file (lockdown.conf), Agent might not transfer or receive files |
Lost compatibilities
HULFT IoT TAKEBISHI Manager and HULFT IoT TAKEBISHI Agent
| Release No | Contents |
|---|---|
| HIPJ-808 | Change of maximum value for Auto Resend Retry Count |
| HIPJ-564 | Differences of operations and confirmations that could do on the HULFT screen |
HULFT IoT TAKEBISHI Manager
| Release No | Contents |
|---|---|
| HIOT-487 | Change of the response operation if Manager failed to connect the database |
| HIOT-135 | Change of names and notation for distribution file size in environment settings file |
| HIPJ-1397 | Deletion of the API URLs that are used only for keeping compatibility |
| HIPJ-1367 | Deletion of the parameters that are used only for keeping compatibility |
| HIPJ-1354 | Change of installation parameters for Linux from capital letter to small letter |
| HIPJ-860 | Change of a unit of session time out |
| HIPJ-688 | Change of the setting name in the environment settings file |
| HIPJ-582 | Change from Send Logs screen to Transfer Logs screen |
| HIPJ-475 | Deletion of Transfer Encoding on the Transfer Settings screen |
HULFT IoT TAKEBISHI Agent
| Release No | Contents |
|---|---|
| HIPJ-1253 | Starting Agent just after installation with default settings |