Read IOAGATE installation and configuration considerations for a complete explanation of IOAGATE, its components and its configuration. This section also includes information on all aspects of IOAGATE installation and configuration.

For information about installing the Control-M Configuration Manager Application Server (CTMCAS), see Step 21 – Install Control-M Application Server.

The following is a general overview of the components of IOAGATE.

IOAGATE is a mainframe software communications gateway (middleware) that enables IOA mainframe applications to communicate with other mainframe and non-mainframe applications over the network.

The Application Server is a separate address space distinct from the IOAGATE address space. It is started by IOAGATE according to IOAGATE parameters. The responsibility of the Application Server is to handle the application logic, while IOAGATE performs the actual communications and passes the messages between the clients and the Application Servers.

Client applications access INCONTROL products through an IOAGATE Application Server. Each Application Server address space communicates with its corresponding INCONTROL product either directly or by means of files.

IOAGATE does not support access to INCONTROL products from 3270-mode terminals or 3270-mode terminal emulation.

Figure 25 IOAGATE as middleware for INCONTROL products

The following INCONTROL products are supported:

Table 34 INCONTROL products supported by IOAGATE

IOAGATE supports multiple concurrent application servers of different applications and their clients. A single IOAGATE can support all the Application Servers shown above.

When you have read IOAGATE installation and configuration considerations mark this step complete.