ibm-itx-rs Image and Container

To design and compile ITX maps to be run by this container, ITX Design Studio or ITX Design Server, on-premises tools must be used. The compiled maps then must be saved to the volume, or a host directory, bound to the /data/maps location in the container file system.

The image is comprised of the following main components:

• Red Hat Universal Base Image 8 (ubi8 minimal) operating system as the base image
• Tomcat 9 application server
• REST API service running under Tomcat
• ITX runtime for running maps
• IBM MQ Client

The image specifies the following directories created in the container file system when the container is started:

Contains compiled maps. By default, the maps must have .lnx 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 holding configuration files, for example, key store file for MQ purposes.

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.

Directory used by the bundled IBM MQ Client.

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.

The image exposes port 8080 on which the container is accepting REST calls. Only HTTP scheme is supported. No authentication and authorization is supported, it is expected that the caller of the APIs has been authenticated and authorized elsewhere, as required.