CONNX Data Integration Suite 14.8.0 | Enterprise Planning Guide | The CONNX Architecture | A Typical Architecture Example
 
A Typical Architecture Example
The following diagram outlines a typical (moderately complex) customer site.
The CONNX .NET Data Provider resides on a Windows machine and has direct connections to a C# .NET Data Entry Form (a user application) and the CDD. It has remote connections to the CONNX License Server, the SQL Server and a DB2 database.
This typical scenario has four machines:
*The user application (C# .NET Data Entry Form) resides on Windows. The CONNX Client is installed on the user application machine.
*The DB2 database resides on a z/OS machine.
*The SQL Server database resides on a Windows machine.
*The CONNX CDD and License server service reside on a Windows machine. This machine has a shared folder (with read/write access permissions) for CDD access.
In this scenario, the customer selected a machine to run the CONNX License server with a guaranteed uptime level. Due to the CONNX networked architecture, there are no CONNX specific components required on either database machine.
This diagram does not show the development configuration and any test and production environments. In those environments, the CDD may not reside on the same machine as the license server; if it did, each deployment phase might have its own directory.
This example illustrates some of the typical architectural and management challenges in a real-world scenario. This gives us a view of the architecture that we can refer to in the following sections as we begin to unravel the complexity of Enterprise Planning. A comprehensive examination of typical deployment scenarios is outlined in the CONNX Scenarios section.