Version 2.3.9 05 DEC 2024
Linkar Server
0001921: Fixed error in Telnet/SSH connection type. Failure in reception TimeOut.
Timeout in Database Answers (0 No Timeout)” value was not refreshed on Telnet/SSH type receptions.
Version 2.3.8 14 OCT 2024
Linkar Server
0001896: Improvement in sending email alerts when there are no database lines available.
Linkar Manager
0001897: Bug fixed in Get Activation Data button
Version 2.3.7 08 AUG 2024
Linkar Server
0001871: Bug fixed in Uniobjects against Linux databases
When using Uniobjects with Linux databases the database lines die after a period of inactivity. Linkar Server sends an activity refresh every 240 seconds in keepalive style to avoid this situation.
The refresh time can be configured in the KEEPALIVE_INTERVAL attribute within the PROFILE node. Values in seconds greater than 10 seconds indicate the new refresh time and values less than 10 disables the refresh.
Version 2.3.6 10 JUN 2024
Linkar Manager
0001837: Remove all calls to external urls, to avoid problems on servers with outbound limitations.
For the correct execution of Linkar Manager on servers with limited internet access, all calls to style and javascript urls have been removed.
For a correct working, it is only necessary to have access to the following urls:
https://siarkosday.com.es
Version 2.3.5 04 MAR 2024
Linkar Server
0001751: Bug Fixed. Line CLOSED but open in QM
0001700: Send and Receive Timeout Management in Linkar REST API
The REST API operations of LinkarManager against LinkarServer were running with fixed timeouts of 8 seconds on both send and receive.
Now the same timeout values are being used as the EntryPoint associated to the APIKEY.
Version 2.3.4 15 DEC 2023
WARNINGS (if you already have Linkar Suite installed)
You must upgrade D3 database MV Components
Linkar Framework. If you are using any Linkar Framework Library, you must upgrade to version 2.3.1 to fix the error shown below.
Linkar Server
0001683: EntryPoint Logs. Added more data to locate the cause of the error.
0001691: Fixed communication error between Client and Linkar Server in cases of multiple requests at the same time.
0001688: New Timeout settings in Database operations.
Timeouts extended to check if a Database session is available to run the operation.
Linkar Manager
0001692: Close Database Session button. End of operation control
Closing a database session now checks if an operation is in progress, and waits for it to finish before beginning the logout process.
Linkar Framework
0001694-0001695: Fixed communication error with Linkar Server Sockets.
Linkar Framework sometimes crashed when it did not receive responses from Linkar Server and caused CPU spikes.
MV Components
0001684: D3. Added new condition for killing operation Kill lines
Added a new condition to disconnect a line that is disassociated from Linkar Server in waiting status, in MVSP and Socket connection types
Version 2.3.3 10 NOV 2023
WARNINGS (if you already have Linkar Suite installed)
MV Components must be installed to use QM database
Linkar Server
0001669: Fixed bug in QMClient type Connections.
Call generate an abort even” errors occurred
0001668: Fixed bug in incoming operations with Temporary Sessions.
Incoming transactions may snuck in during the temporary logout process due to inactivity.
0001667, 0001657: Increased CPU usage and memory consumption.
Fixed several errors that caused high CPU and/or Memory consumption.
0001652: Error in CRUD operations with XML/JSON input format and containing ORIGINAL_RECORD
Occurred in UPDATE, UPDATEPARTIAL and DELETE operations
0001635: GetArguments from the LinkarSERVER XMLParser class.
Fixed error in the GetArguments method of the LinkarSERVER XMLParser class.
MV Components
0001673: QM. Added new condition for killing operation Kill lines.
Added a new condition to disconnect a line that is disassociated from Linkar Server in waiting status, in QMCLient type connections
Waiting QMClient action request
QMVbSrvr processor
Version 2.3.1 10 NOV 2022
WARNINGS (if you already have Linkar Suite installed)
You must upgrade the MV Components.
Linkar Server
0001320: Linkar Server ready to accept requests from Linkar Web Services
0000902: Fixed Bug. EntryPoint Lite Version with on-demand lines only not starting.
0000908: Errors in the line counter of opened databases on Pro version when there is a connection problem.
0000942: Alarms. Data validation on email sending, Mailto, smtp server.
0000945: Fixed Bug on statistics with large operations.
0001025: Added new option to build JSON with numeric and boolean types.
New option in Master and EntryPoint parameters to activate JSON generation with numeric and boolean types. If not activated, all JSON values generated will be of string type.
0001028: Different IP listener for each EntryPoint.
Now an IP listener can be defined for each EntryPoint. If not assigned, Linkar Server IP will be used. Especially useful to avoid exposing all EntryPoints to public network, or vice versa.
0001158: Socket type connections. Reconnection attempts extended to 5.
Before current version, 3 connection attempts to the Socket were made when opening an EntryPoint. Now, 5 attempts extension increases connection success.
0001175: High CPU usage in Linkar Server
Two new parameters included in EntryPoint configuration, named SOCKET_RECEIVE_TIMEOUT and SOCKET_SEND_TIMEOUT.
Before current version, both were configured to 0 value, and in situations like attack or failed connections, that would generate an endless reception thread, causing high CPU usage.
It is recommended to put SOCKET_RECEIVE_TIMEOUT value to 10 seconds and SOCKET_SEND_TIMEOUT to 60 seconds in order to avoid endless waiting times that would originate high CPU consumption.
Two new input boxes have been created in Linkar Manager / Configuration / EntryPoints.
0001194: New Low message to inform about attacks made to Linkar Server IP
**S0016 - WRONG HEADER RECEIVED** (Includes information of the IP that sent the petition)
0001235: UTC date to local change in Linkar Server and Manager logs.
Local Date of the server where Linkar Suite is installed will be used in order to ease reading.
Linkar Schemas
0000980: Improved EqualTO property from Schemas' Properties.
schemaname|propertyname syntax is no longer needed. Indicating Schema Name is enough to define EqualTo.
MV Components
0001252: New version MV Components 2.3.0.
MV Components update required.
0000903: Fixed Bug in "Use Common Blocks for the 100 most used files" feature
Only when using the "Use Common Blocks for the 100 most used files" switch in the EntryPoint configuration.
Now the files that are out of the ranking of the 100 most used files are closed with CLOSE statement.
0000922: Fixed Bug in GetTable method.
Reading MV or SV tables was generating two extra columns to the right.
0000947: Fixed Bug in GetTable function SQL Mode plane table
Now we make sure to always take the first multivalue in those fields defined as flat.
0000958: Fixed Bug when ItemID was empty in Select from LkSchemas and LkProperties methods.
0000964: Improved data type calculation.
The calculation of integer and decimal datatype has been improved. MRx conversion and decimal separator value in ENTRYPOINT PARAMETERS are taken into account.
0000966: Fixed Bug in Update Function in JSON or XML format
If any xml or json tag is missing the attribute is not modified. Previously it was being saved empty.
0000978: Extended LKPROPERTIES functionality to JSON_DICT, JSON_SCH, XML_DICT, XML_SCH.
Now the result in these formats will create Multivalue and Subvalue field objects. The output in JSON and XML format have not changed.
Linkar Framework version 2.xx or higher is required.
0000979: LK.CHECKDICTS command is now executable from data account.
0001198: UpdatePartial function. Use of Write instead of WriteV.
UpdatePartial function enables recording one or more attributes from a register. Before this change, WRITEV sentence was used for each attribute on recording.
Now the WRITE sentence is used in order to optimize recording and letting execution of possible Triggers.
0001203: Added boolean field in LK.ITEMS demo file.
0001236: Linkar Logs Database. Added End Time.
New column added with the petition execution's final date and time in the database. Useful for calculating execution times.
Date and Time in log are indicated according to local time of the server where the database is allocated. Previously, it was being converted to UTC time.
Linkar Manager
0000905: New button to download configuration files in Linkar Config.
0000967: Solved Kestrel log generation with serilog.
Logs were not generating.
0001099: Fixed bug on Linkar Manager / Linkar Config /Users. Autogenerate password button didn't work.
0001200: Master and EntryPoint Parameters forms.
New specific validations for each property.
Master Parameters is now a dependant of Linkar Config menu instead of Linkar Schemas.
EntryPoint Parameters is now a dependant of Configuration/EntryPoints menu (wrench icon).
Linkar Framework
0001002: Bug on Linkar Framework was preventing the execution of ClickOnce applications.
0001052: Fixed bug on Linkar Framework NodeJS.
Wrong sub value mark insertion in LkReplace function.
0001053: Fixed bug on Linkar Framework Java.
Wrong sub value mark insertion in LkReplace function.
0001054: Fixed bug on Linkar Framework NodeJS. Linkar.Functions.Persistent.LinkarClient.js.
outputformat and inputformat from GetTable method.
0001055: Fixed bug on Linkar Framework NodeJS. Linkar.Functions.UpdateOptions.js.
Error on OptimisticLock property of GetString method.
0001056: Fixed Bug on Linkar Framework NodeJS. Linkar.Functions.Direct.TABLE.
0001057: Fixed bug on Linkar Framework NodeJS. Linkar.Functions.Persistent.TABLE.
0001059: Fixed bug on Linkar Framework NodeJS. LinkarClient.js.
0001060: Fixed bug on Linkar Framework NodeJS. Linkar.Functions OPERATION_CODE.js.
0001064: Fixed bug on Linkar Framework NodeJS. Linkar.Functions.Direct.XML samples.
0001070: Fixed bug on Linkar Framework Python. Demo linkar_test.py
0000978: Extended LKPROPERTIES functionality to JSON_DICT, JSON_SCH, XML_DICT, XML_SCH.
Now the result in these formats will create Multivalue and Subvalue field objects. The output in JSON and XML format have not changed.
Linkar Framework version 2.xx or higher is required.
Linkar Framework updated 08 MAR 2022
Linkar Framework
0001073: New Linkar Framework for PHP
Linkar Framework updated 24 SEP 2021
Linkar Framework
0000918: New Linkar Framework for Python
0000931: New Linkar Framework for Java 2.2.1
Added support for programming assistance for compatible development environments (IntelliSense)
Version 2.2.1 11 AUG 2021
WARNINGS (if you already have Linkar Suite installed)
You must upgrade the MV Components.
If you want use the new UpdatePartial function you must upgrade to Linkar Framework 2.2.0
Linkar SUITE
0000810: Migration to .NET 5.0
Linkar Manager on all platforms and Linkar Server on Linux and MacOS platforms now use .NET 5.0
New Linkar DOCKER License
0000791: Linkar Suite can now run on Docker platforms.
Linkar SERVER
0000819: Bug fixed in the creation of the new statistics files.
When it is necessary to create new statistics files, if there are multiple requests at the same time, it could be the case that two or more threads detect that the statistics files do not exist and try to create them at the same time, causing an error that the file is being used by another process.
0000779: New LinkarServerConsole command (Windows/Linux/IOS)
Added new LinkarServerConsole application to run LinkarServer as a normal console process.
The program terminates by pressing Ctrl+X.
Added new parameter --ip to overwrite the ip specified in config.xml
0000751: Implementation of 3 retries of database connection
At the starting of a database session, up to 3 confirmation retries have been implemented with a delay of 1 second in each attempt.
The first attempt has no delay, but if it fails, wait 1 second and lkping is sent again, and so on up to three times.
0000750: Correct resizing of the data buffer size on reception.
In some occasions the reception was crashing because the EOT character was not found. This has been solved by correctly resizing the size of the data buffer in reception.
0000830, 0000860: New automatic license update service
Linkar Server makes backgroud calls to a Kosday service that checks the license data. If the license has been updated, the data is changed on the fly, without the need to stop Linkar Server.
A button has also been created in Linkar Manager/Configuration/Activation called "Check and update license".
0000832, 0000836, 0000889: Improvements in the opening and closing of database sessions.
Until now, database sessions were opened one at a time using the same thread. When the first one was opened, the second one was started and so on. Now one thread is used for each session opening so we gain processing speed in the EntryPoint opening. The speed of the opening will also depend on the CPU of the database.
The same happens in the closing process.
Linkar MANAGER
0000780: Linkar user passwords can now be displayed.
0000781, 0000782: Added new validations on deletion of Profiles or EntryPoints
- It is not allowed to delete a Profile if any of its EntryPoints is on.
- It is not allowed to delete an EntryPoint if it is turned on.
0000787: A new port has been created to receive https requests.
In this way http and https requests can coexist. The default port for https is 11202.
A new switch "Require SSL" has been added to force https requests.
0000804: LinkarManagerControl OPENBROWSER. Opening http or https
The LinkarManagerControl program with the OPENBROWSER option, always opened the web browser with the LinkarManager access url in http mode. Now, according to the configuration found in the Config.xml file, it will use http or https url.
0000784, 0000785, 0000823: New Management of password collection via web service
Every time LinkarServer has to open a line in the Database, if the "Get Passwords From Web Service" feature is enabled in the EntryPoint, before opening the line, the web service indicated in "Database Password URL" is consulted to obtain the password to be used.
The URLs for obtaining passwords, token requests and their parameters are stored encrypted.
Capture fields in Linkar Manager do not display data unless the show button is pressed.
0000854: Added new menu "Kestrel" in Linkar Manager/Linkar Logs
To view, download or delete the logs generated by the kestrel web server.
0000890: Bug Fixed in ResetCommonBlock of Linkar Manager
If there were no open sessions, Linkar Manager would wait forever for a response.
0000825: Bug fixed when removing database sessions on hot
When removing lines in a started EntryPoint, one less line was removed.
Linkar REST API
000842: Bug fixed in REST API Index out of array bounds
In functions such as EXECUTE, CONVERSION, etc. this error was caused in the REST API when the result was empty.
0000796, 0000797: Improvements in swagger documentation in Linkar Rest API
0000826: New Linkar REST API Manager.
New endpoints have been created to manage and monitor Linkar. Now you can query the status of an EntryPoint or a session, you can add or reduce database lines on the fly, etc.
0000843: Bug fixed in XML type calls from Linkar REST API Tester
0000790: Added UpdatePartial endpoint
Modifies one or more attributes of one or more file records. Emulates databasic WRITEV statement
Linkar FRAMEWORK
0000752: Improved UPDATE and NEW functions with XML and JSON formats
Now, when using the UPDATE or NEW methods in any of the XML or JSON formats, it is not necessary to remove tags from the Calculated dictionaries. They will not be used in the recording process because they are calculated data. No error will be launched.
0000789: Added UpdatePartial function
Modifies one or more attributes of one or more file records. Emulates databasic WRITEV statement
Linkar SCHEMAS
000731: Improved automatic generation of properties in Linkar Schemas
Multivalue groups are now automatically calculated and generate friendly names. The main property of the MV group is also marked as mandatory.
LinkarTRAINER
0000792: Added UpdatePartial function in Linkar Trainer
MV Components
000862: Bug fixed in Universe. GET.LIST in PreselectClause of the Select function did not work.
MV Components updated 10 FEB 2021
WARNINGS (if you already have Linkar Suite installed)
You must upgrade the MV Components.
MV COMPONENTS
0000691: Added locking control on writings
In the New and Update functions, the MV components will now return an error when trying to write a record locked by another user in the database.
Error number 132: Operation Cancelled. Record %1 is locked by user %2
Previously, it was returned by Timeout.
Revision 2.1.5 20 JAN 2021
WARNINGS (if you already have Linkar Suite installed)
You must upgrade the MV Components.
LINKAR DOCUMENTATION
0000663: New structure in the Linkar documentation.
There are two new Manuals for Linkar Framework and Linkar Trainer.
Linkar Clients section has been removed in the Linkar Suite manual. Now it is a new independent manual.
There are new links to the rest of the manuals from the Linkar Suite manual.
Linkar SERVER
0000648: Solved memory release problems using QMClient
0000661: Reality has been included in the list of supported Linkar databases,
working with Terminal and Socket connection type
Linkar REST API
0000532: New documentation for Linkar REST API with Swagger
From the Linkar Manager, Linkar REST API menu you can access the Swagger environment for testing and help.
You also will find static documentation at https://kosday.com/Manuals/en_web_linkar_restapi_developer
MV COMPONENTS
0000641: Solved Error in Dictionaries Method with D3 and MvBase
0000671: Solved Error in New Method with Itemid empty
LINKAR FRAMEWORK
0000430: New Linkar Framework
Linkar Framework for .NET, Core , Java, C and Node.js
Soon, Python, PHP, COM...
0000664: Added Linkar Framework for .NET to Nugget repository for use in Visual Studio
LINKAR TRAINER
0000662: New utility Linkar Trainer for developers
This utility helps developers to test Linkar Framework different functions and to see the source code in different environments.
Revision 2.1.4 27 NOV 2020
WARNINGS (if you already have Linkar Suite installed)
You must upgrade the MV Components.
Linkar SERVER
0000629, 000635: Bug in broken lines management
0000633: EntryPoints that uses a SOCKET type connection do not start after stopping them.
Linkar MANAGER
0000639: EntryPoint Configuration. Change in "Maximum string size in database memory" parameter.
Now the size is chosen through a combo.
This parameter is important for improving the response speed performance of the MV components.
MV COMPONENTS
0000637: Packet size error when the database encoding is different than the Linkar Server encoding.
0000638: Improved the processing speed when the database encoding is different from the Linkar Server encoding
In SOCKET, QMCLIENT and JBASE connections, special character mappings have been improved by reducing processing time.
Revision 2.1.3 16 OCT 2020
WARNINGS (if you already have Linkar Suite installed)
You must upgrade the MV Components.
You must execute LK.DEMOFILES DELETE and LK.DEMOFILES to create them again if you want to use the Demo files.
If you use Automatic Classes in .NET you must update the Linkar Client DLLs.
Linkar SERVER
0000617: New Broken Lines Management. More Details here
0000616: New Refresh Settings behaviour.
Now all of the EntryPoint's "green" properties are updated at the time of EntryPoint recording. The following properties have been removed: Disable Refresh settings and Time interval to refresh settings
In Linkar Manager the option to perform a manual refresh has been removed.
0000614: New alarm system to send by email
Three categories of alarms: ERRORS, WARNINGS, INFO. More details here
0000554: Fixed: Lowercase letters in the EntryPoint name cause failures
Linkar CLIENTS
0000612: Automatic Classes. HotFix with Calculated option in false
Linkar SCHEMAS
0000558: Leading zero in dict items results in LKFLDn in schema results
Fixed, now appears the name of the dictionary
Linkar REST API
0000543: Solve wrong access to port 0 when EntryPoint doesn't exist. 192.168.1.x:0
MV COMPONENTS
0000610: corrected selection for an ADI in D3 as "A]" "S]"
0000591: New LK.TRACE File in Linkar Account
One record from each database line conected with Linkar Server, with two states: Waiting or Running. More details here
0000613: Calculated Option. HotFix when calculated is true and there is not calculated dictionaries in file
Previously the entire calculated field was sent empty without register separators. Now the record separator is sent
Revision 2.1.2 27 AUG 2020
Only for installations using MVSP on D3 10
WARNINGS (if you already have Linkar SERVER installed)
You must upgrade the D3 MV Components.
Linkar SERVER
0000555: Fixed MVSP connection issues in D3 version 10
Revision 2.1.1 21 AUG 2020
WARNINGS (if you already have Linkar SERVER installed)
You must upgrade the MV Components.
Linkar SERVER
0000552: Fails Automatic Start with database in another machine
LinkarServer in Windows: restarting the computer was not stopping the LinkarServer service properly.
So if there were open EntryPoints with established connections to the Database, these connections were not closed properly.
This can cause that once the LinkarServer restarts, the EntryPoint could not reopen the connections correctly.
0000551: Database encoding. Fixed malfuncions
LinkarServer in Windows, having the Encoding of the profile configured as "Default", connects and works with most of the databases.
LinkarServer in Windows uses code page 1252 as the Default Encoding. However, Linkar Server in Linux uses code page 651001 (UTF8) as the Default Encoding. And Linux databases don't work well with this code page,
Therefore, in the Profile configuration, it is necessary to indicate the correct Encoding of the Database. In most Linux databases the code page is 437 or 850.
In some scenarios, LinkarServer did not make the correct conversions between the encoding of the LinkarServer application (Windows / Linux) and the Database. This could cause MV marks and/or accented characters not been sent or received correctly. This had different consequences :
oWhen opening an EntryPoint, the connection with the Database could not be established, because the MV marks were not arriving correctly.
oIn some cases, the MV marks were sent and received correctly, but there could be problems when interpreting some special characters (accents, ñ, ...)
oWhen opening an EntryPoint, the connection with the Database could not be established, because the MV marks were not arriving correctly.
oIn some cases, the MV marks were sent and received correctly, but there could be problems when interpreting some special characters (accents, ñ, ...)
