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.
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.
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.
Security is very important in enterprise environments. How does CONNX keep unauthorized users from getting access to sensitive corporate information?
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 compliant application such as the following:
Microsoft Visual Basic
Microsoft Visual C++, Microsoft Visual Studio
Microsoft Excel (MSQuery) and Excel
Microsoft Visual Basic for Applications (VBA)
Paradox for Windows
Dharma ODBC Integrator
Visual FoxPro for Windows
Microsoft Visual Foxpro
Any ODBC or OLE-DB compliant application
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. Starting in CONNX 8, CONNX supports the SQL UNION command, which allows the result sets of multiple queries to be combined into one.
Yes CONNX has wizard driven assistance for configuring a datasource and importing meta data.
Does CONNX have a silent or unattended installation option for deployment to a large number of users?
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.
Does the tool allow the user to limit execution time, cancel at any time, limit rows returned, and specify estimated time to generate information?
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.
Many ODBC drivers exist for accessing a single type of database. If you were to acquire several of them you would be able to access multiple databases. The catch here is that each would appear as a separate data source. Many front end applications are unable to or make it difficult to access multiple datasources. Thus your choice of front end applications or even development tools is limited. Even if your application is able to access multiple data sources you will typically take a performance hit as each driver is separately interrogated and data is staged on the client to perform a join. Your data access capabilities are also limited by the functionality of the weakest or least capable driver. In addition a multi driver solutions suffers from multiple points of failure, multi vendor support responsibility, and vendor bias. CONNX is truly different because all of the data sources accessed are presented to the client application as if they came from ONE SINGLE Relational Database. A Data Access Engine also provides functionality such as meta data management, security, advanced SQL and data conversion that simply are not core components of a simple ODBC driver.
Yes, CONNX allows access to multiple heterogeneous databases concurrently. This allows you to join data from disparate datasources regardless of their type or location. All of the tables in your enterprise databases are represented as if they are contained in one enterprise spanning database.
Yes. Please click here for more information.
All new releases go through a stringent market study. Suggestions for product enhancements (Request for Change) are collected from a variety of sources including our feedback form on this site, focus groups, site visits, contact with technical support, and direct contact with our sales executives.
Yes. CONNX respects the existing security of the database accessed. CONNX also allows storage of database logins to automate authentication. In addition CONNX allows further user, group, application, field and record (through views) level security.
CONNX can act as a “datapump”, but it is much more. A “datapump” simply moves data from one location to another. The need for a datapump usually arises when an application is being migrated from one platform to another.
CONNX is a unique data connectivity tool, that provides access to multiple heterogeneous databases through a single driver. CONNX “pumps” data from disparate data sources and combines the raw data into meaningful information. CONNX accomplishes this through its data dictionary, containing detailed information about the tables and files accessed from the remote databases.
SolutionsIQ is committed to supporting all major databases on all platforms. This also include newer databases such as SQL Server, Oracle, DB2, Sybase, Informix. The CONNX 8 family of products will deliver on our commitment to support these databases, and round out or support for all data on the enterprise.
Our commitment to support all major databases means that CONNX provides you a “technology buffer” that provides you with a consistent and reliable method of accessing your data, no matter where it is located.
No. CONNX works with your existing database structure.
Yes, the CONNX Administrator allows system administrators and developers to configure and maintain metadata, security, data sources, and views.
Yes. CONNX provides a Windows application called the Data Dictionary Administrator, which allows the user to create and maintain the metadata, create views, and establish additional security.
The CONNX user reference guide is available through online help.
CONNX Client installation takes about 5 minutes. Typically installation time on the server can take up to 30 minutes depending on the number of servers and data sources involved.
Yes. As the Euro is simply a type of currency, CONNX is capable of storing and retrieving any type of monetary value.
How is CONNX different from a more traditional data warehouse? What are the advantages of providing organizations with access to real-time decision support information from an on-line system?
Traditional data warehouses store a static copy or snapshot of the data. The CONNX approach is to provide real-time access to the disparate data. Within companies where data is time-critical, the warehouse approach is undesirable because of the static nature of the data. Until CONNX, there was no simple or efficient way to access data from disparate data sources. CONNX is the key to real-time access to multiple data sources.
Yes. CONNX has several features that can help in data warehousing projects.
Typically, in a data warehouse, a company is bringing several disparate data sources into a common repository. Once the data is there, then additional tables can be created for fast cubing of the data.
The CONNX heterogeneous join technology, and the CONNX Insert/Select feature make CONNX an ideal tool for the creation and maintenance of data warehouses.
CONNX can also be used in conjunction with CASE Tools to reverse and forward engineer data structures.
CONNX now supports every significant database on the Digital platform. Why is that important for organizations that have systems from a range of suppliers, in addition to Digital?
Most large corporations have several databases on mainframe systems. One of our goals is for CONNX to provide a single source for native support for all major databases in use by organizations today. Digital is a significant portion of the legacy mainframe database market, and it is key that we support the databases on the Digital platform.
CONNX provides users with access to transactional database information, without requiring the time-consuming task of converting that data from one format to another. Why is that important?
Data conversion is one of the most underestimated tasks in database projects. If a company cannot properly decipher the data stored in a remote database, then the data is useless. Data conversion is key to providing seamless access to disparate databases.
I see that in the future plans to support a comprehensive range of database environments with CONNX. Why would an organization use CONNX to provide access to Oracle through a PC, when Oracle already provides this type of functionality to users?
One of the goals of CONNX is not only to provide connectivity, but to provide access to all data on the enterprise. Most corporations have many types of databases. CONNX provides access to all of those databases without the time and inconvenience of configuring separate ODBC drivers for each database, and the uncertainty that they will all work together properly. Most desktop applications do not allow the use of more than one data source or do so inefficiently. CONNX removes that limitation. Additionally, the CONNX Data Dictionary allows customers to create applications that are database-independent by creating views in the CONNX Data Dictionary instead of in the database itself. As a result, CONNX is not just an ODBC driver but an enterprise-wide data connectivity product.
By providing easy, cost-effective access to legacy database systems, CONNX significantly increases the value and longevity of these existing systems. Are you finding that CONNX enables organizations to extend the life of their legacy systems?
Most definitely. We have had several customers who initially purchased CONNX to assist in a migration off their legacy system; however, CONNX worked so well that they postponed indefinitely their migration plans. Once customers realize that they can access their data in real-time from the desktop, they begin to understand they can solve their immediate business problems without a costly migration.
CONNX is a ODBC level 2 driver. CONNX was developed with the ODBC 2.5 specification.
Will CONNX work with applications that were developed with the ODBC 3.x specification? Yes!
CONNX is compatible with all ODBC 1.x, 2.x and 3.x applications.
The CONNX Data Dictionary functions as the metadata repository. This is a PC file that has the extension of (*.CDD). It can reside either on a server (for centralized access), or locally on the client machine. This sensitive information is encrypted using a 128bit key.
Yes. CONNX can be installed in a Client/Server and n-tier configurations. In either case CONNX distributes the workload to minimize network traffic and processor load. CONNX also works in 3-tier web application environments, including Microsoft Internet Information Server. CONNX also works with development tools designed for n-tier distribution including Borland C++ Client/Server edition, and Borland Delphi Client/Server edition.
Is there anything special that needs to be done with CONNX when there is a firewall(s) in our environment for RMS RDB or DBMS?
Yes. By default, CONNX communicates to the VMS Server using port 6500. This port must be opened or proxied in order for CONNX to work properly though a firewall.
Please see our Firewall white paper for more details.
CONNX is designed to have a minimal impact on application databases.
When used in a read/only mode – CONNX does not perform any locks on the data, allowing existing applications to process normally. Also, the CONNX Distributed SQL Engine is designed to take some of the workload off of the database server.
Typically, applications that use CONNX have less of an impact on database servers than applications that use some other method of accessing the database.
Yes. CONNX will work with the RDO, DAO, ADO and Jet engine data wrappers.
Yes. CONNX is capable of working with any database model for relational databases.
Yes. The CONNX SQL Optimizer automatically takes advantage of keys & indexes on the tables in the queries.
Using ODBC and OLE-DB, you can create different types of resultsets.
If you create a “STATIC” resultset, the results are cached on the Client.
If you create a “DYNAMIC” or “KEYSET” resultset, then the results are re-retrieved from the database when requested
Yes. CONNX has an advanced SQL Optimizer which will quickly determine the best way to execute your queries.
No. Currently, CONNX does not allow administrators to set processing resource limits for query execution.
CONNX has a distributed SQL Engine that will examine several factors when performing joins.
CONNX uses the following four major factors to determine the best way to process joins:
1) Join Direction (Left outer Joins, or Right outer Joins)
2) Indexes available on tables in the query that match criteria columns
3) Indexes available on tables in the query that match join columns
4) Table cardinality
The CONNX SQL Engine analyzes this data to determine the best way to process the query. This is done dynamically for each query executed.
You say that CONNX supports high-performance SQL "joins", even across multiple database sources. What does this mean? Why is it important?
CONNX includes a unique high-performance, disparate database join technology that allows CONNX to join tables together from separate databases. This functionality means that if data is stored in two or more different databases, CONNX will join the data from the separate databases as if the database were one physical database. This is extremely important when developing mission-critical, enterprise-wide applications that span several physical databases.
Yes. CONNX Versions are backward compatible except where noted in the CONNX documentation.
CONNX has been fully re-architected to support multiple, heterogeneous data sources from a single driver, and to enable CONNX to quickly add new data sources. Why is this important?
Database technology is changing at a rapid pace. CONNX has a solid core on which the additional features and extensions are built. By ensuring our core architecture would fulfill our current requirement and future needs, we also reduced the time to market with these new features. Our new core architecture allows us to quickly add support for other databases and open access technologies.
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