Export (0) Print
Expand All

Transaction Integrator Architecture

Transaction Integrator (TI) integrates the IBM Customer Information Control System (CICS), Information Management System (IMS) transaction programs (TP), and OS/400 applications with the Component Object Model (COM) and the .NET Framework by doing the following:

  • Creating interfaces to the CICS, IMS, and OS/400 transaction programs.
  • Invoking those transactions on the mainframe or midrange computer (also called the host computer) from a Microsoft Windows–based application.

The primary function of TI is to manage the process and data conversions necessary to allow input data to be provided to the host TPs from a COM or .NET Framework application and to send any output data generated from the TP to the Windows-based application. TI provides data type conversion, tabular data definition, and code page translation. The following figure shows an overview of the role that TI plays in the communications between the application and the host.

TI provides the data conversions between a Windows-based application and a host
Aa771479.b3cb122d-7d83-4a7f-b8f5-f42892c12e2b(en-US,BTS.10).gif

An example of this type of distributed application is reading a DB2 database on the mainframe to update data in a SQL Server database on Microsoft Windows 2000 Server.

Because all TI processing is done on the Windows 2000 Server or Windows Server 2003 platform, no TI-related executable code (or footprint) is required on the mainframe or midrange computer. TI uses SNA (APPC/LU 6.2) and TCP/IP standard communication protocols for all communications between Windows and the host computer. You can use TI Designer to build TI components, and you can use TI Manager to deploy, configure, and manage those TI components and the TI run-time environment.

Show:
© 2014 Microsoft