The architecture of the CONNX JDBC Driver has five components.
CONNX JDBC (Thin Client) Driver
The CONNX JDBC Driver is located in a Java .jar file named connxjdbc.jar. The JDBC driver is a thin JDBC driver that communicates
to the CONNX JDBC Server through the use of a socket. JDBC calls are translated to socket requests to which the CONNX JDBC
Server responds. The .jar file must be copied to Java Virtual Machine (JVM) platforms other than Windows.
CONNX JDBC Server
The CONNX JDBC Server component communicates with the CONNX JDBC Driver. It resides on the machine on which CONNX is installed.
It is a Windows executable that opens a socket and listens for new connections. When it accepts a new connection, it creates
a new thread that is dedicated to communicating to that client. Installing the CONNX JDBC Server component on every machine
is an optional task since only one server is required for communication with all CONNX JDBC client machines.
When the CONNX JDBC Server component is installed with the CONNX client component on a non-Windows platform (Linux, HP-UX, AIX, Solaris, etc.), run the CONNX JDBC Server as a daemon process.
CONNX JDBC Router
The CONNX JDBC Router is a Java application placed on the non-Windows Web server. It is stored in the ConnxRouter.jar file
which is located in the redistributable Java jar file, C:\CONNX32\CONNXJDBC\JAVA\ftp\connxjdbcftp.jar
The CONNX JDBC Router must be run on the machine that hosts a Web server but does not have CONNX installed. If JDBC applets
are used, the following environments must include a CONNX JDBC Router:
Non-Windows Web servers (Linux, Solaris, HP-UX)
Windows Web servers running on a system on which CONNX is not installed.
CONNX DSN Registry Tool
The CONNX DSN Registry tool enables JDBC connections to locate and refer to the logical name of the data source. It must be
installed on the same machine as the CONNX JDBC Server.
CONNX Engine
This component is the CONNX ODBC Driver, responsible for interacting with data sources.
Registering the Data Source Name