Remote mode

The client application and CICS® Transaction Gateway can be on different machines and the Gateway daemon listens on a specific port for incoming client requests. The Gateway daemon runs as a standalone process, handles the management of connections and threads, and forwards client requests to CICS.

In a remote mode configuration, the CICS Transaction Gateway runs a process known as a Gateway daemon which receives requests from client applications and forwards those requests to CICS servers. Client applications send requests to a Gateway daemon using TCP, SSL, HTTP, or HTTPS.

This figure shows CICS Transaction Gateway for IBM z/OS in remote mode.
Figure 1. An example of CICS Transaction Gateway for IBM z/OS in remote mode

Features of remote mode

Remote mode is best suited to large-scale systems and has the following features:

  • A common point of access to CICS for different applications and operating systems
  • A common point of configuration and administration for connections to CICS
  • High availability with workload balancing across multiple CICS servers
  • A lightweight client footprint
  • Access to statistical information
  • Supports the use of applets to connect to a Gateway daemon