mvBase clients are applications that communicate with the mvBase Server. An mvBase client application establishes a relationship with an mvBase Server by requesting a connection to a line on that Server. Connections are made by one of two methods:
The core functionality in the mvBase Workstation
Similar functionality in the mvTerm client or mvBase API routines
NOTE |
The mvTerm client is the only standard mvBase client not configured or managed by the mvBase Workstation. |
Clients delivered with the mvBase system include:
The mvTerm client, which is a virtual terminal client that runs on Windows systems. The mvTerm client supports two mvBase Term types:
I: Mentor PRO IBM PC console compatible emulation.
V: ADDS Viewpoint terminal emulation.
A COM port terminal server, which connects COM ports to mvBase lines. These connections can have static line assignments (so that the terminal attached to the COM port x is always connected to mvBase line y), or dynamic line assignments (where each new connection just takes the next available line).
COM port clients also have options for handling serial printers.
A Windows printer client, which maps and supports the connection of any available Windows printer, whether it is locally attached to the mvBase Server system, or to remote network print servers, or to other networked Windows systems.
mvTelnet, which is not an mvBase client itself, but creates mvBase clients on behalf of users’ Telnet clients. These mvBase clients (called mvTelnet Servers) are in fact Telnet servers to which the Telnet clients will connect. The mvTelnet Servers support the industry standard Telnet protocol and, like the COM port clients, support both static (also known as one-to-one mapping) and dynamic (consumes the next available) line allocation. They also support line pooling so that a range of mvBase lines can be assigned to each mvTelnet Server. mvTelnet allows third party terminal emulators, and any other application that uses the Telnet protocol, to connection to mvBase Servers.
See Also