Prerequisites

ITX Runtime Server requires Red Hat OpenShift cluster version 4.14. It is supported on Linux 64 clusters only. ITX maps can be designed and compiled for the Linux 64 platform by using either ITX Design Studio or Design Server. ITX Design Studio and Design Server are available as separate download options and must be installed locally. Design Studio is only supported on Windows. Design Server is supported on Linux and Windows. Refer to the information provided with your entitlement for instructions to download and install ITX Design Studio and Design Server. Refer to the ITX Documentation for startup instructions and technical guidelines on using both ITX Design Studio and Design Server. For more information about the product release, see IBM Sterling Transformation Extender for Red Hat OpenShift 11.0.1.

When compiling maps in ITX Design Studio, you must choose the option to compile them for Linux 64 platform. Alternatively, you can use multi-platform composite maps, which will increase the size of the map while enabling the same map to run on both Windows and Linux platforms.

A Redis installation is required to use the ITX Runtime Server in fenced mode, to invoke REST APIs for asynchronous map invocations, or to use the V2 REST API. Flow execution is part of the V2 REST API. For more information, see the Redis Configuration section.

Two filesystem-based persistent volumes must be provisioned for the ITX Runtime Server to be operational. For a Kubernetes installation, if you plan for the ITX Runtime Server pods to be distributed across multiple nodes, the volumes must support the ReadWriteMany access mode option so that they can be bound by all pods in the installation. For more information, see the Storage section.

In those cases where only maps need to be run, the two file-based persistent volumes are not required as long as S3 or GCP Cloud Object Storage (COS) is accessible. The ITX Runtime Server can leverage COS for both V1-based map executions and V2-based flow executions. When running V1-based map executions, however, the deployment no longer requires these persistent volumes. By decoupling from persistent volumes, the REST service can become highly available and fault tolerant without any dependencies on one single file system.