CONNX Data Integration Suite 14.8.0 | Enterprise Planning Guide | CONNX Planning | Component Configuration
 
Component Configuration
Consider the following when planning the CONNX install service configuration:
*The CONNX Client must be installed on every machine that accesses data. This means that you could need many CONNX Client installations for a desktop application, or only a few installations for organizations using a distributed or web service framework. Each configuration has its particular installation, administration, and maintenance constraints.
*The CDD repository location is very important. The CDDs must be available to every client machine; you could need to open a share on a file server and set appropriate access permissions. You could need multiple CDD copies (the development, test, and deploy cycles could each require a separate copy). This increases administration complexity.
*A CONNX Remote server must be installed on remote hosts when a local server DLL cannot access data. You may have to open up a range of firewall ports and coordinate across departments to gain access to a particular machine.
*The CONNX License server must be installed on a single server that has access to the LAN. Choose a dedicated server to ensure uninterrupted access to CONNX features.
The following discussion will be broken down into the aspects of a typical CONNX installation. Refer to the organizational chart of CONNX Client and Server Components in View from 10,000 Feet throughout the discussion to help facilitate a clearer understanding.