Introduction

Edit online

IBM Sterling Transformation Extender for Red Hat OpenShift, formerly known as IBM Sterling Transformation Extender Runtime Server, is a packaging of the IBM Sterling Transformation Extender (ITX) runtime product in the form of a Linux container image. The container image, ibm-itx-rs, is an IBM distributed container image that exposes REST API endpoints to deploy and invoke ITX compiled maps and packaged flows.

This document describes deploying the container to a Red Hat OpenShift cluster through a Helm Chart. It also describes using the image to run in a container runtime such as Docker or Podman.

This document supplements the information provided in the CASE (Container Application Software for Enterprises) bundle documentation for ITX Runtime Server (ITX-RS).

Information about Industry and Enterprise Packs distributed by the product and setting up those Packs for the ITX Runtime Server has been provided for Packs users.

For additional high-level overview of the ITX Runtime Server product, see IBM Support page.

The following is a list of high-level features provided by the ITX Runtime Server:

  • Uploading, listing, downloading, and deleting compiled ITX maps and other files.
  • Listing and downloading generated REST API server and map execution engine log files.
  • Fenced (REST API server and map execution engine running in separate processes) and unfenced (REST API server and map execution engine running in same process) run modes.
  • Synchronous and asynchronous map executions.
  • Cataloging support for the maps, with the REST API endpoints automatically generated for the produced map catalog entries.
  • Direct map execution and execution via cataloged map REST APIs.
  • Ability to override map inputs and outputs with the REST API request and response data.

In addition to the previous features, which are specific to Version 1 (V1) of the ITX Runtime REST API, the following is a list of additional capabilities that are provided by the ITX Runtime Server:

  • Integration with Design Server. Using the Design Server graphical interface, both maps and flows can be deployed to a Runtime Server installation and monitored.
  • Flow and map executions are supported by using Version 2 of the ITX Runtime REST API.
  • The watch functionality of flows allows listeners to be deployed to a Runtime Server.
  • Automated map and flow deployments are available via Cloud Object Storage (COS).
  • Synchronous and asynchronous map and flow executions.
  • Horizontal pod autoscaling with support for custom metrics and behavior policies.