• CONNX Security is ideally suited to handle cross platform security issues.
    There are two major areas of security when dealing with multiple database platforms:
    Area 1) Managing multiple database logins
    Area 2) Managing secure access to the data in each system.

    Area #1
    CONNX handles issue #1 through a technology called the CONNX integrated logon. CONNX facilitates the connection to multiple databases through a single “CONNX” logon. Underneath the covers . . . The CONNX logon maps to one or more database specific UserID and password combinations. This database logon information is stored in the CONNX Data dictionary, and is encrypted using 128bit keys.

    The first time a user logs into CONNX, they will be prompted to created an “Integrated account”. The next time the user logs into CONNX, they only need to specify their CONNX UserID and password.

    The CONNX Integrated logon also takes into account that the database password will change on a periodic basis. This could potentially be a maintenance nightmare for some administrator.

    However, CONNX makes the maintenance of passwords simple.

    Let’s go through and example of what happens when a user’s database password has changed:
    1) The user specifies their “CONNX” User ID and Password
    2) CONNX attempts to log into the database using the stored database UserID and Password.
    3) The database login fails, because the password has changed
    4) CONNX display a logon box prompted for the new password.
    5) CONNX again attempts to log into the database using the new database UserID and Password.
    6) If the logon is successful, then CONNX stores the new password for future use.

    By using the CONNX Integrated logon technology, zero maintenance is required to keep the CONNX UserIDs and Passwords in sync with those of the databases on multiple platforms.

    Area #2
    Security to data can be handled in several ways.

    1) Security can be established in the database itself. However, RMS and DBMS do not support column level security .. This can only be accomplished through CONNX.

    2) Additional security can be established on Tables in CONNX using the CONNX Data Dictionary. CONNX can restrict access at the table or column level for any user, or all users.

    3) CONNX Views can be used to limit what columns or rows a user can view. Also, CONNX security can be applied to CONNX views. This mechanism allows a database administrator to establish security on a cross platform view, consisting of tables in different databases.

  • Comprehensive security capabilities have been designed into the core CONNX architecture to ensure maximum data protection. All information, regardless of which database it is stored in, is protected through the table and user level security. Users are given access to certain datasets, depending on their job classification and other factors. Degrees of access can be specified for individual users or for groups of users. A 128-bit encryption algorithm is used to protect vital information in the password-protected CONNX Data Dictionary. CONNX validates the user name and password supplied in the connection against the database or system being accessed.

  • CONNX integrates with any ODBC, OLEDB, JDBC®, J2EE® or .NET® compliant application, report writer or development tool, giving you a full view of your enterprise data no matter where it is held.

  • Yes. CONNX supports TCP/IP across LAN’s, WAN’s, Intranets, Extranets, and the internet as well as through DECnet. Additionally, CONNX also has data compression capability which will increase performance when using the CONNX client over a slow or remote connection.

  • Yes. CONNX allows you to combine multiple disparate data sources in one query. Basically CONNX presents all of your data as one single relational database. CONNX will also optimize query processing by distributing the load between client and server to reduce processor load and take into account the capabilities of each data source in doing so.

  • Yes, the CONNX Administrator allows authorized users to define data views which join tables, select data and restrict access. These views are then available to front end applications and are presented as logical tables. Because the views are defined centrally they are available across the enterprise to authorized users regardless of the front end tool chosen.

  • Yes. CONNX supports the SQL UNION command, which allows the result sets of multiple queries to be combined into one.

  • Yes CONNX can import the following metadata:

    COBOL FD (File Definition)

    Oracle Codasyl DBMS database




    Formatted DDL (Data Definition Language)

    Powerhouse PDL (Powerhouse Definition Language)

    VAX Basic MAP files

    Oracle Rdb database


    Specification text file (RMS)

    VAX, ALPHA, or Itanium (RMS only) CDD

    OLE DB- and ODBC-compliant data sources

    DB2 data sources

    Oracle data sources

    VSAM data sources

    IMS data sources

    Sybase data sources

    Informix data sources

    Adabas data sources

    PostgreSQL data sources

    SQL Server data sources

    Redshift data sources

  • Yes CONNX allows for a silent installation. The product must first be installed once and installation choices made and recorded. It can then be installed without prompting for choices.
    Please refer to the Appendix in the CONNX Installation Guide.

  • Your CONNX CDD does not automatically get updated.

    If you have several users of CONNX, it may take time to upgrade each CONNX client to the new version. New versions of CONNX will work against older version of the CONNX CDDs. However, the CDDs are treated as read only by the new CONNX versions. Once all client PCs have upgrades to the new version of CONNX, then if you open the CONNX cdd using the new Administrator, and then re-save it, the CDD will be converted to the latest format.

  • Using the new CONNX Wizard technology, the time required to setup a CONNX data dictionary has been reduced to approximately ten minutes.

  • Yes. The ODBC & OLE-DB Specifications permit users to limit query execution times (Query Timeout), and limit the number of rows returned. Currently, CONNX does not return a “time estimate” for query execution. However, CONNX can return a “query execution plan”, which describes how CONNX will attempt process a query.

  • The Insert/Select features allows you to insert the request of one query into another table. This capability is useful when developing complex reports where the creation of temporary tables is necessary to store intermediate results. The Insert/Select also facilitates the transfer of data between database platforms using a single SQL statement:

    Example: Insert into Customers_Oracle select * from customer_rms

  • Yes CONNX enables ODBC access to CA-MANMAN through our Oracle DBMS Driver.
    CONNX will read the MANMAN metadata directly, and create a CONNX data dictionary from this information.

  • Yes CONNX provides access to SCT Plus application data through our RMS Driver. There is specific functionality built into CONNX to handle the data access requirements of SCT users.



Any other questions?

If you have a CONNX query that isn’t covered here, please don’t hesitate to get in touch with the Generix team.

Contact us