cdiConnect enables direct CICS access to CICS transactions and CICS data. cdiConnect eliminates the need to change or rewrite your CICS applications to expose a mainframe interface. This allows you to quickly transform your existing CICS business systems into web services, exposing them to your Service Oriented Architecture (SOA).

cdiConnect extends your existing CICS applications by exposing existing BMS and COMMAREA copybooks as standard interfaces, callable as standard APIs through a variety of communication protocols. cdiConnect builds XML and HTML documents in real-time and reflects changes in the host applications automatically.

Frequently, organizations need to retrieve information directly from CICS data sources as part of an integration process. cdiConnect can read and write directly to VSAM files, DB2, or DL/I databases. Developers can rely upon a single product and interface to access all CICS resources, which saves organizations time and money.

cdiConnect supports HTTP, SOAP, WebSphere MQ, and LINK (ECI/EXCI) connectivity options, which allows it to communicate with virtually any type of distributed application.

Running a CICS transaction or program through cdiConnect is just as secure as running it from a 3270 terminal. This is because the software runs within the CICS environment and leverages the security-related services provided by your existing security system (e.g., RACF, ACF/2, TopSecret).

A CICS-based engine allows developers to create process automation scripts using ECMAScript and run the scripts in compiled form on the mainframe. Middle tier applications can send a single HTTP request to invoke the new process using .NET, Java, or any other middle tier technology. This eliminates multiple round-trip HTTP requests for each step in a process reducing latency and reducing MIPS consumption on the mainframe host.