Deploying container

Use the following sections to deploy CICS Transaction Gateway container.

CICS Transaction Gateway for container image
This section explains how the IBM® CICS® TG container image is loaded into the local docker repository.
Preparing to deploy CICS Transaction Gateway Container
The CICS Transaction Gateway container image is available for the x86 and s390 platforms. The disk space requirement to deploy a container image is 1 GB. The container images are built by using the Red Hat Universal Base Image (UBI minimal).
Configuring a CICS Transaction Gateway container
This section describes the additional configurations that are required for container deployment. For more information about CICS Transaction Gateway configuration, see Configuring.
Configuring CICS Intercept plug-in
The default configuration file (ctg.ini) has only minimal configuration that is required to bring up the gateway.
Running sample client application
This section describes steps for running a sample client application inside the container and outside the container.
Configuring SSL
You can enable SSL Handler in the ctg.ini file using the following parameters and make the gateway available for SSL communication.
Configuration for multiple containers
Multiple containers can be configured to access the same KeyStore by mounting the KeyStore location to the container specific location.
JWT Section Configuration for Secret Keys
The SecretKey field of the JWT Section (HMAC Algorithms) is scrambled by the configuration tool. For containers, the configuration tool is not available. However, with the docker container, you can achieve the same using the environment variable.
Configuration using Docker Compose
Docker compose helps for defining and running all the required containers for CICS TG application to run.
Deploying CICS TG container in IBM zCX
IBM z/OS Container Extensions (zCX) is a z/OS feature that enables clients to deploy Linux applications as Docker containers on z/OS as part of a z/OS workload. This maintains operational control of the Linux environment within z/OS, brings z/OS qualities of service to the application deployment, and does not require the provisioning of separate LPARs or system images.