For a graphic representation of the CONNX architecture, see Organizational chart of CONNX Client and Server Components.

 

As you install the CONNX component installation across the enterprise, you may have to coordinate with other departments.  

 

Server or mainframe administrators may have to install the CONNX Remote server component; network administrators may coordinate the CONNX Client rollout. Depending on your organization's environment, you may need to plan for a phased CONNX component rollout - first  to a test environment and then from test to production.

 

The CONNX API is used to communicate between the CONNX Client and the CONNX Remote server; it determines the compatibility between client and server components. Compatibility breaks occur when an incompatible version is installed.

 

• The CONNX Client is backwards compatible

• The CONNX Remote server is not forward compatible.

• For JDBC users, the client jar is not forward compatible but the JDBC/RCI server is backwards compatible.

 

For the best performance and feature quality, the CONNX Client and the CONNX Remote server should be on the same version level, although this is not a system requirement.