IBM Support

V4.0.6 Release Information for Financial Transaction Manager (FTM) for Red Hat OpenShift

Fix Readme


Abstract

This document contains release information for Financial Transaction Manager (FTM) for Red Hat OpenShift 4.0.6.

Content

This release information has the following sections.

Release information

Release Channel Operator Operand Supported Operands Case
4060 v4.4 4.4.0 4.0.6.0 4.0.6.0 v4.4.0
4060_iFix1 v4.4 4.4.1 4.0.6.0_iFix1 4.0.6.0 & 4.0.6.0_iFix1 v4.4.1
4060_iFix2 v4.4 4.4.2 4.0.6.0_iFix2 4.0.6.0, 4.0.6.0_iFix1 & 4.0.6.0_iFix2 v4.4.2
4060_iFix3 v4.4 4.4.3 4.0.6.0_iFix3 4.0.6.0, 4.0.6.0_iFix1, 4.0.6.0_iFix2 & 4.0.6.0_iFix3 v4.4.3
4060_iFix4 v4.4 4.4.4 4.0.6.0_iFix4 4.0.6.0, 4.0.6.0_iFix1, 4.0.6.0_iFix2, 4.0.6.0_iFix3 & 4.0.6.0_iFix4 v4.4.4
4060_iFix5 v4.4 4.4.5 4.0.6.0_iFix5 4.0.6.0, 4.0.6.0_iFix1, 4.0.6.0_iFix2, 4.0.6.0_iFix3, 4.0.6.0_iFix4 & 4.0.6.0_iFix5 v4.4.5
4060_iFix6 v4.4 4.4.6 4.0.6.0_iFix6 4.0.6.0, 4.0.6.0_iFix1, 4.0.6.0_iFix2, 4.0.6.0_iFix3, 4.0.6.0_iFix4, 4.0.6.0_iFix5, 4.0.6.0_iFix6 v4.4.6

Which release of FTM for 4.0.6.0 to install? 

For a New/Fresh install,

  • IBM recommends installing the latest release available, which is: FTM 4.0.6.0 interim fix 6 (iFix6) 

For Clients who are already on FTM 4.0.6.0 interim fix 1 (iFix1) OR interim fix 2 (iFix2) OR interim fix 3 (iFix3) OR interim fix 4 (iFix4) OR interim fix 5 (iFix5):

  • upgrade to FTM 4.0.6.0 interim fix 5 (iFix5)
Back to contents Common across all 4.0.6 releases

Support

FTM 4.0.6 supports the following Red Hat OpenShift versions:

  • Red Hat OpenShift 4.16.x
  • Red Hat OpenShift 4.18.x

on architectures:

  • amd64
  • ppc64le

Running on OpenShift allows you to deploy on Azure, AWS, IBM Cloud, Google, and on bare metal servers. This is aligned with IBM’s hybrid multi-cloud strategy.

Notes:

  1. Consistent with IBM’s hybrid multi-cloud strategy, testing is performed on standard OpenShift reference configurations and is not independently run in the lab for every native cloud deployment pattern.
  2. IBM recommends installing the latest levels for each Red Hat OpenShift Container Platform version to stay current with security fixes.

Power Deployment

Financial Transaction Manager for Red Hat OpenShift is available for IBM Power Systems. This support continues the available hardware platform options and lets organizations take advantage of Power Systems' many benefits.

Power Systems help organizations respond faster to business demands, protect from core to cloud, and streamline insights and automation while reliability is maximized in a sustainable way.
Power Systems can modernize applications and infrastructure with a frictionless hybrid cloud experience to provide the agility organizations need.

Communications between FTM application components

All direct RMI/IIOP communications between FTM application components is performed over SSL/mTLS connections.  Insecure connections are not supported.

 
IBM MQ prohibited components
The following IBM MQ 9.4 components are prohibited from use:
  • MQ Telemetry Server (of IBM MQ)
  • MQ Native High Availability Cross Region Replication (of IBM MQ)

Entitled documentation fix pack

Entitled documentation can be downloaded from Fix Central at: Common Entitled documentation fix pack

The entitled documentation fix pack contains the documents that are shown in the following table

Document Description
FTM_DB_Design_Doc_v406.html The database design document describes the data dictionary, table entities, and view entities. It also includes an appendix with the table and view index and column index.
Using_Database_for_Problem_Resolution.pdf This document contains solutions for different product problems that can be resolved only by updating the database. A database administrator needs to run the database scripts.
folder: yaml OpenAPI documentation for FTM web services provided in YAML format.
folder: swagger

Important FTM Base 4.0.6 document links

Airgap support - When you are doing an air-gapped installation, make sure that you closely follow the documentation. A step was added to update the image digest values in the mirroring procedure for this interim fix.
Caution: The FTM Operator is set to auto-deploy by default. IBM recommends changing this to manual deploy (installPlanApproval: Manual). See the following page in the IBM Documentation for details on how to make this change.
Caution: You must remove all hotfixes before you upgrade, as hotfixes are not compatible across releases.
Back to the list of releases
4.0.6.0 interim fix 6 (iFix6)
Upgrading from FTM Check 4.0.6.0 iFix5 to FTM Check 4.0.6.0 iFix6 by following the instructions in the attached document:
FTM Upgrade and Rollback guide from 4.0.6.0_iFix5 to 4.0.6.0_iFix6_1.docx
NOTE: If FTM is using a non-TLS connection to Db2/Db2U, then after the upgrade, the FTM custom resource must be updated so that spec.config.database.enableTLS is set to false.
Database migration 
There is no database migration between FTM Check 4.0.6.0 iFix5 and 4.0.6.0 iFix6
Back to the list of releases
4.0.6.0 interim fix 5 (iFix5)
Upgrading from FTM 4.0.6.0 iFix4 to FTM 4.0.6.0 iFix5
Upgrade from FTM 4.0.6.0-iFix4 to 4.0.6.0-iFix5, by following the instructions in the attached document:
FTM Upgrade and Rollback guide from 4.0.6.0-iFix4 to 4.0.6.0-iFix5.docx
NOTE: If FTM is using a non-TLS connection to Db2/Db2U, then after the upgrade, the FTM custom resource must be updated so that spec.config.database.enableTLS is set to false.
Database migration 
There is no database migration between FTM 4.0.6.0 iFix4 and 4.0.6.0 iFix5
New requirement when installing 4.0.6.0 iFix5
 
FTM now contains two OpenShift operators, and both must be installed when upgrading to the new iFix.
The FTM CRD has been moved into a separate operator from the FTM controller.
In order to support installing different versions of FTM in different namespaces, the FTM CRD has been moved into a separate FTM operator from the FTM controller.
 
Mitigation:
See the FTM documentation on how to install both FTM operators and the instances in which the FTM API operator should not be installed.
Fixes included in 4.0.6.0 iFix5
For a list of all the fixes included in 4.0.6.0 iFix 5 see: 4.0.6.0 iFix5 defect Fix List
Back to the list of releases
4.0.6.0 interim fix 4 (iFix4)
For Clients who are currently on FTM 4.0.6.0 iFix1:
Upgrade from FTM 4.0.6.0-iFix1 to 4.0.6.0-iFix4, by following the instructions in the attached document:
NOTE: If FTM is using a non-TLS connection to Db2/Db2U, then after the upgrade, the FTM custom resource must be updated so that spec.config.database.enableTLS is set to false.
Database migration 
There is no database migration between FTM 4.0.6.0 iFix1 and 4.0.6.0 iFix4
For Clients who are currently on FTM Check 4.0.6.0 interim fix 3 (iFix3):
Upgrade from FTM 4.0.6.0-iFix3 to 4.0.6.0-iFix4, by following the instructions in the attached document:
NOTE: If FTM is using a non-TLS connection to Db2/Db2U, then after the upgrade, the FTM custom resource must be updated so that spec.config.database.enableTLS is set to false.
Database migration 
There is no database migration between FTM Check 4.0.6.0 iFix3 and 4.0.6.0 iFix4
Back to the list of releases
4.0.6.0 interim fix 3 (iFix3)
The following defect is resolved in iFix3: 
Issue: Customizations made in the spec.resources section of the FTM CR (such as adding environment variables or updating resource requests and limits) are not applied by the FTM operator in iFix2. Deployments that depend on these customizations should not upgrade to iFix 2. This issue is resolved in iFix 3. You can upgrade from iFix1 directly to iFix3 or do a new/scratch deployment of iFix 3.
For Clients who are currently on FTM 4.0.6.0 interim fix 1 (iFix1):
Upgrade from FTM 4.0.6.0-iFix1 to 4.0.6.0-iFix3, by following the instructions in the attached document:
Database migration 
There is no database migration between FTM 4.0.6.0 iFix1 and 4.0.6.0 inFix3.
For Clients who are currently on FTM 4.0.6.0 interim fix 2 (iFix2):
Upgrade from FTM 4.0.6.0-iFix2 to 4.0.6.0-iFix3, by following the instructions in the attached document:
 
Database migration 
There is no database migration between FTM 4.0.6.0 iFix2 and 4.0.6.0 inFix3
Back to the list of releases
4.0.6.0 interim fix 2 (iFix2)
Caution: Customizations made to individual containers in the spec.resources section of the FTM CR (such as adding environment variables or updating resource requests and limits) are not applied by the FTM operator. Deployments that depend on these customizations should not upgrade to iFix 2. This issue is resolved in iFix 3. You can upgrade from iFix1 directly to iFix3 or do a new/scratch deployment of iFix 3.
 
Upgrade from FTM 4.0.6.0-iFix1 to 4.0.6.0-iFix2, by following the instructions in the attached document:
FTM Upgrade and Rollback guide from 4.0.6.0_iFix1 to 4.0.6.0_iFix2.docx

Database migration

There is no database migration between FTM 4.0.6.0 interim fix 1 and 4.0.6.0 interim fix 2.

Back to the list of releases
4.0.6.0 interim fix 1 (iFix1)
Upgrade from FTM 4.0.6.0 to 4.0.6.0-iFix1, by following the instructions in the attached document:

Database migration

There is no database migration between FTM 4.0.6.0 and 4.0.6.0 interim fix 1.

Back to contents 4.0.6.0 release

 

Enhancements from FTM Base 4.0.5.1 to 4.0.6

The following sections provide information about the enhancements from the previous version of FTM Base.

Enhancements
  • Standardization on a single GO-base Operator for deployments
  • Middleware updates - for currency and security 
  • ACE Standalone (Operator) Support
  • External (outside OCP) MQ Environment Support 
Back to contents Known Issues (the iFix that they have been fixed in)
10393: IBM Cloud does not support Airgap.
 
10393: Airgap: Filtering capability ("--filter-by-os ") does not work using the IBM-Paks "mirror" command.
Mitigation: Omit using the parameter "--filter-by-os " and all images, for both architectures (amd64 and ppc64le), will still be mirrored.
 

150991: Unable to create the FTM operator instance using the Forms view (Fixed in iFix6)
The YAML view approach is the most common way to create the FTM operator instance. In this release, it is not possible to create the FTM operator instance using the Form view.
Mitigation: Create the FTM instance using the YAML view.
​​​​​​

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"ARM Category":[{"code":"a8m50000000ClaTAAS","label":"Product Documentation"}],"ARM Case Number":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"4.0.6"}]

Document Information

Modified date:
19 August 2025

UID

ibm17129877

Page Feedback