ibm-itx-rs V2 Usage Example

The following example demonstrates how to deploy a flow into the ibm-itx-rs container and then invoke it with input overrides. The example Timesheet flow is described further under the Flow section of the Examples Readme, which is located in the examples sub-directory of the ITX Runtime Server Helm chart. The Timesheet flow enables employee work hour information to be extracted from a list of employee timesheets.

1. Load the ibm-itx-rs image into Podman.

   podman load -i ibm-itx-rs_11.0.3.0.20260625.tar.gz

2. Configure the V2 Runtime REST API.

   echo -e "rest:\n  mode: fenced" >/tmp/config.yaml

3. Install the ITX Runtime Server.

   podman run --name itx-rs-v2 -it -d -p 8080:8080 -e ITX_RS_LICENSE_ACCEPT=true -v /tmp/config.yaml:/data/config/config.yaml ibm-itx-rs:11.0.3.0.20260625

4. Deploy the flow.

   curl -X POST "http://localhost:8080/tx-rest/v2/packages" -H "accept: */*"  -H "Content-Type: application/octet-stream"  --data-binary @Timesheet_linux.sqlite

5. Run the flow.

   curl -X PUT -F "1=@allempslf.txt" -F "2=@employee1.txt" "http://localhost:8080/tx-rest/v2/run/WorkHours"

   curl -X PUT -F "1=@allempslf.txt" -F "2=@employee2.txt" "http://localhost:8080/tx-rest/v2/run/WorkHours"

   The first flow invocation returns 50 hours for employee1 while the second returns 90.45 hours for employee2.

   Note: The sqlite package and input files are available in the ITX Runtime Server Helm chart under the examples\flow sub-directory. Once the container is stopped, no mapping and logging artifacts are retained because external mount points were not used in the example. If external mount points are used during the Install, the Deploy need not be run again. The ITX Design Server provides a graphical way to re-deploy changes and monitor flow executions.