The diagram, CONNX Function Block, shown below, is an overview of CONNX installation and operation. The CONNX Administrator and CONNX client components are installed on a selected computer, usually designated as the CONNX Administrator computer, although it can be installed on more than one computer. Installation of the CONNX client provides an interface between the end-user application and databases of several different types and platforms. To the end user, however, the databases, tables, joins, views, and other database elements appear as if all the various data sources were a single database.
CONNX also installs a server component for the RMS, Rdb, and DBMS databases on an OpenVMS server.
DB2, Oracle, SQL Server, PostGres, MySQL, Sybase, Informix, OLE DB Enterprise, OLE DB Desktop, DataFlex, and POWERflex databases do not require a CONNX server component.
The relational data sources Oracle Rdb, Oracle, SQL Server, Informix, Sybase, Adabas, and PostGreSQL are supported on Windows and Unix systems.
VSAM, Adabas, and IMS databases require an IBM mainframe-compatible server.
Adabas is available in mainframe, Windows, and UNIX versions.
C-ISAM, DISAM, and Micro Focus install a server component on the UNIX server. There are also Windows-compatible versions.
The CONNX OLE DB and ODBC server component resides on the client machine. It uses the OLE DB or ODBC driver that exists on the client machine. The CONNX OLE DB server component is automatically installed when required.
OLE DB is not supported when CONNX is run on a non-Windows client machine. In such cases, a third-party ODBC driver manager can be used.
CONNX Function Block
