Linkar Suite 2.3.7

Linkar supports a number of industry-standard mechanisms to connect into MV DBMS servers. Some of these Connection Types are provided by the DBMS vendor. "Terminal" protocols like Telnet and SSH are not defined by MVDBMS vendors, but may be subject to platform-specific nuances. For added benefits, Linkar has also developed platform-specific Socket connections using tools provided with the specific MV platforms. In all cases, Linkar "wraps" these components, adds and manages functionality, and exposes a consistent API, eliminating the need for application developers to support different protocols for different server types.

But Linkar still needs to connect to the underlying DBMS platforms. This requires a specified connection type to be installed and configured, so that Linkar, as a client application, can connect to the DBMS.

This table shows the possible Connection Types from Linkar SERVER to MV databases, and the recommended connection type for supported configurations.

*The TERMINAL connection can be Telnet or SSH if the database and the operating system allow it.

As a guideline:

•Use Terminal connections when required and when it's desirable to have a minimal number of DBMS processes pre-started, with occasional temporary sessions created during peak time. This is the slowest connection type.

•Use DBMS-specific connection library types where possible in preference over the others, for performance and to better support temporary sessions. This is generally considered to be the fastest and most direct connection type.

•Use Socket connections when it is acceptable to pre-define the maximum number of expected DBMS licenses for high performance. This is faster than Telnet connections, but benchmarks are not yet available to compare with DBMS-specific types.  

See also: Supported Databases

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.