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 either TCP/IP or SSL.

This figure shows CICS Transaction Gateway for Multiplatforms in remote mode.
Figure 1. An example of CICS Transaction Gateway for Multiplatforms 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

Information Information

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tg_latest/help/topic/com.ibm.cics.tg.doc//ctgunx/ctg_remote.html