logo-Linkar

Linkar is a suite of components that facilitates efficient connectivity to MultiValue Databases.

Linkar SERVER works with many MultiValue Database platforms, centralizing connections and optimizing DBMS licence usage.

Client apps use Linkar CLIENT libraries, with bindings for popular languages, to interact with the database through Linkar SERVER.

Summary: With the Linkar suite of components, client-side interfaces are written with a variety of programming languages, to connect to a variety of MV servers.

Download Linkar Live Demo and test it now.

GOT A QUESTION?

Thank You! Your message was successfully sent!
[SMTP] Error! Internal server error!
Sorry! You need to complete all mandatory (*) fields!


All the Linkar Operational components can be installed in Windows, Linux and Mac OS

Windows
Linux
Mac OSX


Existing Client Libraries for different environments:

Clients


Linkar connects with different MV Databases (working in other databases):

OpenQM
D3
Universe
Unidata
jBASE

Linkar SERVER is a service that manages all communications with the different MultiValue databases. It is a sophisticated socket server that listens for CLIENTS requests. By accessing the database through the Linkar SERVER it has these advantages compared to direct access from a client application:

  • Client applications through Linkar do not need an exclusive database licence. Different clients can share a single database licence with session pooling to maximize licence efficiency.
  • Client applications do not need to manage connections with databases. The Linkar SERVER will open connections on demand, as required. The Linkar SERVER is also responsible for releasing open connections on demand when its use is no longer necessary, optimizing the use of licences in the database.
  • Client applications are independently designed from the MultiValue database type that it will use.

You can see the recommended Linkar SERVER connection types in the following table.

Database O.S. where LinkarServer is installed Recommended Connection Type Other Connection Types
OpenQM Windows / Linux / Mac OS Windows / Linux / Mac OS QMCLIENT SOCKET
D3 Windows Windows MVSP TELNET
D3 Windows Linux / Mac OS TELNET
D3 Linux Windows MVSP SOCKET
TELNET
D3 Linux Linux / Mac OS SOCKET TELNET
UniVerse Windows / Linux Windows UNIOBJECTS SOCKET
UniVerse Windows / Linux Linux / Mac OS SOCKET
UniData Windows / Linux Windows UNIOBJECTS SOCKET
UniData Linux Linux / Mac OS SOCKET
jBASE Windows / Linux Windows jAGENT

Linkar MANAGER is responsible for the configuration and monitoring of the Linkar SERVER. It is possible to configure the entry points to different databases with this tool, using a GUI interface, indicating the number of sessions to be used, when and how to open those sessions (permanently at the start of the service or on demand when working conditions require more sessions to meet customer requests, the connection form, etc. It also allows “warm” open sessions to be monitored and managed.

Linkar Schemas allows file definitions and dictionaries to be increased with a set of properties that you can later use in different environments or platforms like .Net, Java, etc.

Likewise, it will allow us to define our database files so that they are visible by the relational world, converting the groups of multivalues or subvalues ​​into independent relational tables among themselves, and related amongst each other.

The Schemas are defined by each EntryPoint and their data is saved in the data account associated with it.

Linkar Schemas do not alter the dictionaries defined in the Database. All data is stored in native files of Linkar, in the data account associated with the EntryPoint. Linkar Schemas do not create any dictionary in the database either.

Linkar Schemas have three components:

  • Schemas: Database file extended definitions.
  • Properties: Database file Properties for file atributes.
  • EntryPoint Parameters: EntryPoint exclusive Schemas parameters.

Schemas enlarge the file definition. With them, the MV files can be operated in other environments.

The Schema code must be the same as the database file name and MUST exist in the account.

Properties increase the file attribute definition. With them the file can be used in other no mv environments. File Schema must exist in order to define their properties

Set of Libraries that allow the communication of an application with the Linkar SERVER and through it with the different databases. The programmer can request and receive the information needed by the application through its functions.

Depending on the selected programming environment or the language used, the application communicates with the Linkar SERVER through the different Client Libraries and then the application accesses the databases.

Your applications do not need different versions depending on the MV database with which you are going to work with. They communicate with the Linkar SERVER and this is responsible for everything that is necessary.

There are Linkar CLIENT versions compatible with different programming languages and environments:

  • NET (C#, Visual Basic, F#,...) for Windows x64 and x86 environments.
  • CORE and MONO for multi-platform development (Linux, Mac,...).
  • Java (all OS types).
  • All languages and environments that can use C Libraries, such as PHP, Python and NodeJS.
  • COM-compliant languages like Excel VBA and PHP (windows).
  • A console application, so as to carry out operations from it, for example a command script from the OS.
  • From BASIC to another remote database, regardless of which this is.
  • Linkar comes with a console application, embedding Linkar CLIENT, to perform operations from the OS command-line and scripts. For example, you can write a .bat file or shell script that sends and retrieves data to/from the MV server for any purpose.
  • Linkar also includes an MV-side client to connect with other MV servers that can read, write, or execute commands on a remote system, even with a different MVDBMS type.

This Video Shows how to create a simple appication in C#

LINKAR Libraries and Platforms from where they can be used:

LinkarClient.dll .NET Framework Client
LinkarClientCOM.dll Languages compatibles COM (php, office VBA, ...)
LinkarClientMono.dll Mono Framework Client (Windows, Linux, Mac)
LinkarClientCore.dll .NET Core (Windows, Linux, Mac)
LinkarClient.jar Java Client
LinkarClientC.dll / LinkarClientC.lib C libraries for Windows
libLinkarClientC.so / libLinkarClientC.a C libraries for Linux

Linkar can use four types of Functions:

PERSISTENT FUNCTIONS

Exclusively from OOP (OBJECT-ORIENTED PROGRAMMING) and allow the creation of a LinkarClt object that manages all the operations.

After creating the object, it is necessary to Login that, through a Session code; this allows it to make all the desired operations until a call to the Close method is produced or until the session expires because of inactivity. This is defined on its EntryPoint.

They are useful for applications that require user identification, for instance, to log into an ERP session.

DIRECT FUNCTIONS

Used for direct and independent communication with the database. Its arguments contain the necessary information to identify the user before returning the required information. Unlike persistent functions, these do not have a Session Code, each call is completely independent of the others and does not have Login or Close functions.

They are used for database access from public websites, for instance online shops.

TEXT FUNCTIONS

This type of function does not need to access the database. They are executed in the client and their goal is to ease the management of the MV buffers.

C AUXILIARY FUNCTIONS

C auxiliary Functions are exclusive for C libraries.

They are executed in the client and their goal is to allow easier management of other complex C functions.

There are no classes in C, or objects , these functions are used to create encoded strings that emulate other languages.

Linkar also supplies other types of calls:

SYNCHRONOUS CALLS

They are executed in the same thread of the main application, so they block the execution of the application until they finish.

ASYNCHRONOUS CALLS

They are executed in a new thread, so they do not block the execution of the application. A return method is required when a call is made (Callback) which is triggered when the operation is completed. C libraries do not implement this type of calls.

With the other programs that make up the LINKAR suite, the following tools are included to help you test and exploit all the qualities of this product.


Verifying the database configurations may help you to familiarize with how to connect and work with Linkar SERVER from client applications. It allows you to graphically test the library functions through an application. Just like the times measuring and the commands execution. It is not an end user application. Its function is educational allowing you to explore all the options and possibilities of the Linkar SERVER library functions.

This executable commands line provides an easy way of executing the SendCommand function from different environments. For example, from a Windows bat file or from a Basic Program to access the data from other remote databases.

LITE

This is a free Licence and does not require any activation, registration, etc. for it to work.

The LITE licence can only maintain one session with the Linkar SERVER and the database simultaneously.

Multiple configurations are allowed (EntryPoints) with databases, but only one of them will be operational at any time.

Only one Linkar CLIENT can connect with the Linkar SERVER and access the database at any time. When one client logs out, another client will be able to log in.





PRO

This is the Linkar commercial licence. This licence can be registered by number of sessions or database lines. You can configure all the sessions, or database lines that you require at each EntryPoints that you define. The more database lines an EntryPoints, has, the greater its capacity to process concurrent operations, and therefore the Linkar SERVER performance will also be greater and the answers will be faster for LinkarClients.

The number of sessions assigned to all EntryPoints is unlimited, but a greater number of sessions than those acquired in the Licence may not be simultaneously active. In Linkar Clients the number of simultaneous sessions is unlimited without any restriction except those inherent to the features and performance of the application itself.

PRO Licence can be updated with new versions during the life of the subscription.


Select the number of Sessions you wish. Each session allows opening a single DataBase line.
With the Lite Version you have a Free Session. Download it and start using it.

We recommend you installing the Lite Version and test it before purchasing it.
From Linkar Manager you can get the SystemID and attach it to your order.

If you prefer, you can make your order by email, to the sl@kosday.com address.


Sessions Price
From 1 onwards $ 58.00 per each session.
Subscriptions Price
From 1 onwards $ 14.00 per each session.
If you are a Software Company, sign in and ask us about conditions
Ask us for other quantities

The System ID is necessary for Activation. If you do not have it now, you can send us the serial number and the System ID by email to sl@kosday.com, and we will return the Activation codes.

RETURN GUARANTEE

During the first 30 days from the date of purchase, if you have technical problems or errors that prevent you from using the product on your computer, contact our support. We will do our best to solve the problem. If we do not get it, and you can not make it work, we'll give you back the money.




LINKARLite FreePro
DataBase sessions or Lines opened simultaneously1According to Purchase
Maximum number of Client Sessions1UNLIMITED