This documentation strives to consistently use this set of Terms.
Linkar Suite consists of four primary components which need to be installed to support a client/server topology:
1.Linkar MANAGER is a background service with a built-in web server, accessed with a browser client, for management and configuration.
2.Linkar SERVER is another background service, processing inbound transactions, brokering requests between client applications and databases
3.MV Components consist of BASIC code which receives and processes inbound transactions.
4.Linkar Framework are language-specific libraries for client applications to connect to Linkar SERVER and process responses.
In the simplest installation, all of these components can be on one system. In a more complex environment, all of these components can be installed in separate systems.
Linkar Suite installers are available for Windows, Linux and macOS, in 32 and 64 bits versions. This means each of the components, together or separately can be installed in any of these operating systems. Further, the Linkar SERVER can connect with a variety of MV DBMS platforms over these operating systems.
The challenge of the installation is to understand each component, what it does, where it is installed, and to ensure that it can communicate with other components. A solid grasp on these concepts will streamline the installation process.
Let's consider different installation scenarios help explain where components can be installed
•A developer installs the Manager and Server over a Windows laptop. UniVerse is also running locally. The developer is writing a C# application to connect to the localhost DBMS. The MV Components must be installed in UniVerse.
•The same developer then needs to support jBase running on a different Windows system. The MV Components are installed to jBase. The developer's browser connects to the Manager, which sets the configuration for the Server to connect to the new DBMS.
•An application provider installs the Manager and Server over a cloud Linux system. MV Components are installed to a D3 DBMS on a different Linux server is processing transactions. A browser-based application, perhaps WordPress with the Linkar Framework for PHP, is running on a third Linux system, accepting remote browser requests, and passing them to the system with the Linkar SERVER service.
•Install the Manager and Server over Windows. The Server will connect to the MV Components in D3 over Linux, and the MV Components in QM over macOS. The administrator uses a browser over Windows elsewhere to access the Manager. Client connections might come in from a .NET application running over IIS/Windows, and from an Android/Java application.
•A developer installs the Manager and Server over a Linux laptop. UniData is also running locally. The developer is writing a Python application. A browser is opened on the localhost Linux desktop. This connects to the local web server of the Linkar MANAGER service. "EntryPoints" are defined in the Manager for the Linkar SERVER service, to connect to QM installed locally and to another QM instance in macOS. The MV Components must be installed in both of the QM instances.
As we think about these scenarios, security Permissions need to be considered. For example, it may be necessary to configure firewalls. Other permissions may also need to be considered for the Linkar MANAGER service and the Linkar SERVER service, to ensure they have the rights to read and write configuration data, and to open socket servers.
Decide where to install the Manager and Server components : Linkar MANAGER and Linkar SERVER are installed together but can be separated later. As noted above, a central, middle-tier server is required to host the services for remote connections. The "Installation" process is really just about installing these components.
Go through The Basics : This only installs the Manager and Server, not MV Components and not Clients. In Windows, the Manager service should start automatically, listening to port 11201. (Details for Linux and macOS depend on the desktop.) The Server service (which will listen on 11200) does not start yet because there is no configuration data to manage inbound connections to databases.
Connect with a browser to the Manager. A Successful Installation ends with the ability to browse to the Manager Dashboard.
With the Manager and Server installed, use the Manager/browser to configure access to a database. Please familiarize with the topics Linkar SERVER and Linkar MANAGER, and their sub-topics, and then proceed to Configuration. After configuration, Linkar SERVER can be started and actual connections can be tested.