UniObjects can only be used for connections to UniVerse and UniData (U2). UniObjects is the recommended Connection Type for these databases, though Socket and Terminal connections can also be used in some environments.
UniObjects can only be used when Linkar SERVER is installed over Windows. At this time Linkar uses UniObjects.NET, which cannot yet be used with .NET Core over other platforms. The UO.NET client from Rocket Software is only available over Windows at this time. Because Linkar is built over .NET Core, and not Java, it is not likely that UniObjects for Java (UOJ) can be used. Kosday will continue to research the best possible tools to effectively support all possible configurations.
From Linkar SERVER over Windows, the UniObjects Connection Type can connect to any U2 database, regardless of the OS on which the database is installed.
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.
As much as we at Kosday try to help with connection issues, ultimately it is the responsibility of the developer/administrator to install and configure the platform-specific connectivity tools. Kosday supports the Linkar product, and our ability to "support" usage of other products is limited. Therefore, our recommendation for all connection types, is for the developer to install and test the tools according to the guidelines provided by the vendors. When successful connections have been confirmed, configure Linkar to work with that environment.
(Screenshots on this page show the bottom part of EntryPoint Configuration)
In Linkar MANAGER, properties with a green label do not need a restart of the EntryPoint after a change.
Database Host
|
Display Only |
|
Shows the database server host from the Profile. |
Database Port |
Mandatory
|
|
TCP port on which UniObjects is listening. By default, this is 31438. |
Timeout in Database Answers
|
Mandatory |
hot-change New received requests |
The maximum time in seconds to wait for a response from the database. The operation is canceled and an error is returned to the Linkar Client when there is no response after this time period. The Database Session remains until closed by the client or other normal processes. If an expiration time of 0 is defined, requests default to never timeout. It would therefore be strongly recommended to set a timeout in the Linkar CLIENT application code.
|
Database Username |
Mandatory
|
|
The U2 database user that opens the connection. (Possibly OS user.) |
Database Password (URL)
|
Mandatory |
|
Password for the U2/OS User. Or URL to obtain the password via REST web service |
Database Account
|
Mandatory |
|
Data account on which the requests will be executed. The data account must already be enabled for use with Linkar SERVER. It is recommended to use the full OS path to the U2 data account, or as otherwise recommend in UniObjects documentation. |
