Estimating License Requirements
For a graphic representation of the CONNX architecture, see the organizational chart of CONNX Client and Server Components.
License usage for the CONNX product family is based on database access. Each defined in a CDD database represents a separate connection (no matter what database type) and requires one license seat per back-end type (even if the database definition is actually a clone of an existing database) when a connection has been made to the CDD. Connection count may be limited to a subset of defined databases within the CDD by using the application field on the CONNX Integrated Logon screen, or during the CONNX Data Source setup. More information on the use of the application feature can be found in the CONNX User Guide.
For web server or distributed access, you can purchase an NTIER license for each server; this allows unlimited connections to that server. NTIER licensing is appropriate for web based enterprise applications, or applications distributed in a large-scale SOA project.
You can also consider purchasing redundant or fail-over licenses, so that you have a primary and back-up license server; this can help ensure uninterrupted access to CONNX features. It can also make sense to purchase separate licenses for your development and testing systems, as well as your production system.