CONNX Modernization Guide

CONNX provides SQL access to legacy data sources, such as VSAM, IMS, and ADABAS, enabling distributed applications to interact with mainframe data. It acts as middleware, bridging the gap between modern systems and older mainframe environments.

CONNX is middleware. It provides connectivity and data access services, allowing applications to interact with mainframe data sources using standard protocols like ODBC, OLE DB, JDBC, and .NET.

Organizations that rely on mainframe systems for critical data storage and processing, but need to integrate that data with distributed applications, commonly use CONNX. This includes enterprises in industries like banking, insurance, and government.

A company should consider CONNX when they need to provide real-time or near real-time access to mainframe data for distributed applications, reporting tools, or business intelligence platforms. It is especially useful when migrating data is not feasible or desirable.

Alternatives to CONNX include other data integration tools and methods such as data replication, ETL (Extract, Transform, Load) processes, and other middleware solutions designed for mainframe connectivity. Examples include IBM Data Virtualization Manager and Rocket z/Direct.

CONNX typically runs on the mainframe operating system (z/OS or z/VSE) and requires TCP/IP connectivity. It also requires the presence of the data sources it will be accessing, such as VSAM, IMS, or ADABAS.

CONNX runs in an LPAR (Logical Partition) on the mainframe. It is dependent on the z/OS or z/VSE operating system and requires TCP/IP services to communicate with distributed systems.

CONNX supports standard SQL syntax for querying mainframe data. It uses configuration files to define the data sources and their mappings to SQL tables. The specific syntax for accessing data depends on the underlying data source.

CONNX exposes APIs through ODBC, OLE DB, JDBC, and .NET. These APIs allow applications to connect to CONNX and execute SQL queries against the mainframe data sources. The specific API calls depend on the chosen technology.

The main components of CONNX include the CONNX Server, which runs on the mainframe, and the CONNX client drivers, which are installed on the distributed systems. These components communicate over TCP/IP using a proprietary protocol.

CONNX solves the business problem of accessing and integrating mainframe data with distributed applications. Without CONNX, organizations would face challenges in leveraging their legacy data for modern business needs.

The primary business value of CONNX is enabling organizations to leverage their existing mainframe investments by providing access to legacy data for new applications and business intelligence initiatives. This reduces the need for costly data migration projects.

If an organization did not use CONNX, they would likely need to implement alternative data integration solutions, such as data replication or ETL processes. These alternatives can be more complex, costly, and time-consuming.

CONNX integrates with enterprise ecosystems by providing standard data access interfaces like ODBC, OLE DB, JDBC, and .NET. This allows it to connect to a wide range of applications, reporting tools, and business intelligence platforms.

CONNX supports authentication methods such as mainframe security systems (e.g., RACF, ACF2, Top Secret) and Windows authentication. It uses an access control model based on user roles and permissions to control access to mainframe datasets.

CONNX uses encryption to protect data in transit between the client and the server. The specific encryption algorithms used depend on the configuration and the capabilities of the underlying systems.

CONNX provides audit logging capabilities to track user access and data modifications. These logs can be used for security monitoring and compliance purposes.

CONNX leverages the security features of the underlying mainframe environment, such as RACF, ACF2, or Top Secret, to control access to data. It also provides its own access control mechanisms to further restrict access based on user roles and permissions.

CONNX is typically deployed on-premise, within the organization's data center. It requires technical expertise to install, configure, and maintain the software. Ongoing operational requirements include monitoring system performance, managing user access, and applying software updates.

CONNX provides administrative interfaces through a command-line interface (CLI) and a graphical user interface (GUI). These interfaces allow administrators to manage users, configure data sources, and monitor system performance.

Common implementation challenges include configuring the network connectivity between the mainframe and distributed systems, mapping mainframe data structures to SQL tables, and ensuring that the security settings are properly configured.

CONNX provides monitoring and logging capabilities to track system performance and user activity. These logs can be used to identify and resolve issues, as well as to monitor security and compliance.