ibm-itx-rs Image and Container
The image is named ibm-itx-rs, where rs stands for Runtime Server. The ibm-itx-rs image can be used to create a container in a container runtime such as Docker or Podman. This is in contrast to the use of the image as the image for a container in a pod in a Kubernetes deployment of the Runtime Server.
To design ITX maps to be used by this container, ITX Design Studio or ITX Design Server must be used. To design flows, ITX Design Server must be used.
For the V1 API, the compiled maps must be saved to a volume or a host directory which is bound to the /data/maps location in the container file system.
For the V2 API, packages must be created in Design Server. A package is deployed to an installation of the Runtime Server using the package deployment endpoint of the V2 API.
The image is comprised of the following main components:
- Red Hat Universal Base Image 9 (ubi9 base) operating system as the base image
- Tomcat 10 application server
- REST API service running under Tomcat
- ITX runtime for running maps
- IBM MQ Client
The directories which are the values of the rest.persistence mapping in config.yaml are created at runtime if they do not exist.
The following directories have special significance for the Runtime Server:
Contains compiled maps. By default, the maps must have .mmc file extension. If a map references a file relative to the map directory, that file must reside in the directory relative to this directory. Likewise, if a map creates a file without specifying a directory, that file will be created in the map directory. If a map runs other maps, those maps must reside in the same directory, and must be saved under the exact names, including file extension, under which they are referenced in the main map. To ensure that all instances of the container have access to the same maps when those instances are running on different hosts, this location must be accessible on all hosts, for example, it can be an NFS share.
Contains temporary execution files.
Contains log files produced by the ITX runtime, Tomcat application server and REST API service deployed to Tomcat.
Directory used for cataloged maps.
Directory used for holding configuration files, for example, key store file for MQ purposes. The configuration of a single-container deployment can be customized with a file at /data/config/config.yaml.
Contains any additional shared libraries and JAR files to make available to the running container, such as for example JDBC driver JARs for use with JDBC adapter.
The above locations must be mounted to volumes, or host machine directories, when creating a container. Alternatively, a single volume or a local host directory that contains maps, tmp and extra sub-directories can be mounted to the /data location in the container and a single volume or host directory for logs that can be mounted to the /logs location in the container.