IBM Support

V4.0.5 Release Information for Financial Transaction Manager for Red Hat OpenShift

Fix Readme


Abstract

This document contains release information for Financial Transaction Manager for Red Hat OpenShift 4.0.5.

Content

This release information has the following sections.

Release information

Release 

Channel 

Operator 

Operand 

Supported Operands 

Case 

4.0.5.0 

v4.2 

4.2.0 

4.0.5.0 

4.0.5.0 

v4.2.0 

4.0.5.1 (Fix pack 1)

v4.2 

4.2.1 

4.0.5.1 

4.0.5.0 & 4.0.5.1 

v4.2.1 

4.0.5.1 interim fix 1 (iFix1) 

v4.2 

4.2.2 

4.0.5.1_iFix1 

4.0.5.1 & 4.0.5.1_iFix1 

v4.2.2 

4.0.5.1 interim fix 2 (iFix2) 

v4.2 

4.2.3 

4.0.5.1_iFix2 

4.0.5.1, 4.0.5.1_iFix1 & 4.0.5.1_iFix2 

v4.2.3 
4.0.5.1 interim fix 3 (iFix3) v4.2 4.2.4 4.0.5.1_iFix3 4.0.5.1, 4.0.5.1_iFix1, 4.0.5.1_iFix2 & 4.0.5.1_iFix3 v4.2.4
4.0.5.1 interim fix 4 (iFix4) v4.2 4.2.5 4.0.5.1_iFix4 4.0.5.1, 4.0.5.1_iFix1, 4.0.5.1_iFix2, 4.0.5.1_iFix3 & 4.0.5.1_iFix4 v4.2.5

 

Which release of FTM 4.0.5.x to install?

For a New/Fresh install,
  • IBM recommends installing the latest release available, which is: FTM 4.0.5.1 interim fix 4 (iFix4) 
For customers who already have FTM 4.0.5.1 OR FTM 4.0.5.1 interim fix 1 (iFix1) OR FTM 4.0.5.1 interim fix2 (iFix2) OR FTM 4.0.5.1 interim fix3 (iFix3) installed
  • IBM recommends upgrading to the latest release available, which requires iFixes to be deployed in sequential order:
    • For Clients on FTM 4.0.5.1, upgrade to FTM 4.0.5.1 interim fix 1 (iFix1)
    • For Clients on FTM 4.0.5.1 interim fix 1 (iFix1), upgrade to FTM 4.0.5.1 interim fix 2 (iFix2)
    • For Clients on FTM 4.0.5.1 interim fix 2 (iFix2), upgrade to FTM 4.0.5.1 interim fix 3 (iFix3)
    • For Clients on FTM 4.0.5.1 interim fix 3 (iFix3), upgrade to FTM 4.0.5.1 interim fix 4 (iFix4)
Back to the list of releases
Common across releases
Support
By using the Red Hat OpenShift platform, Financial Transaction Manager (FTM) 4.0.5.1 supports deployment into hybrid multi-cloud environments that include:
  • IBM Cloud
  • IBM Power Virtual Server
 
FTM also supports deployments into private cloud models such as the following models:
  • Red Hat OpenShift running on IBM Power or Intel hardware platforms.
FTM 4.0.5.1  supports the following Red Hat OpenShift versions:
  • Red Hat OpenShift 4.10.x
  • Red Hat OpenShift 4.12.x
Use the latest levels for each Red Hat OpenShift Container Platform version to stay current with security fixes.

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

The entitled document fix pack contains the following documents:

Document

Description

Comments
FTM for Base Upgrade and Rollback guide from 4.0.5.1_iFix3 to 4.0.5.1_iFix4.docx This document describes the steps to upgrade the FTM application from 4.0.5.1_iFix3 to 4.0.5.1-iFix4 and rollback the FTM application from 4.0.5.1-iFix4 to 4.0.5.1_iFix3 Added in 4.0.5.1 iFix4
FTM for Base Upgrade and Rollback guide from 4.0.5.1_iFix2 to 4.0.5.1_iFix3.docx This document describes the steps to upgrade the FTM application from 4.0.5.1_iFix2 to 4.0.5.1-iFix3 and rollback the FTM application from 4.0.5.1-iFix3 to 4.0.5.1_iFix2 Added in 4.0.5.1 iFix3
FTM for Base Upgrade and Rollback guide from 4.0.5.1_iFix1 to 4.0.5.1_iFix2.docx  This document describes the steps to upgrade the FTM application from 4.0.5.1_iFix1 to 4.0.5.1-iFix2 and rollback the FTM application from 4.0.5.1-iFix2 to 4.0.5.1_iFix1 Added in 4.0.5.1 iFix2
FTM for Base Upgrade and Rollback guide from 4.0.5.1 to 4.0.5.1_iFix1.docx  This document describes the steps to upgrade the FTM application from 4.0.5.1 to 4.0.5.1-iFix1 and rollback the FTM application from 4.0.5.1-iFix1 to 4.0.5.1.  New in 4.0.5.1 iFix1
FTM for Base Upgrade and Rollback guide from 4.0.5.0 to 4.0.5.1.docx  This document describes the steps to upgrade the FTM application from 4.0.5.0 to 4.0.5.1 and rollback the FTM application from 4.0.5.1 to 4.0.5.0.  New in 4.0.5.1

IBM_FTM_V40_Security_Configuration.pdf

This document augments the IBM FTM documentation security configuration sections to describe the steps needed fully secure the deployment. 

updated for v4.0.5.1

Tactical approach for DR support for FTM 4.0.5.1 IBM MQ usage.pdf

 This document describes the steps to

 1. Take a manual backup of the IBM MQ transaction messages from the primary cluster.

 2. Manually restore the IBM MQ transaction messages into a secondary cluster.

 New in 4.0.5.1

IBM MQ behavioral differences between 4050 and 4051 documents:

  • MQ behavioral differences between 4050 and 4051.pdf
  • Comparing_Native_HA_MQ_Operator_to_standalone_MQ_Container.pdf

New in 4.0.5.1
 4.0.5.1_from_4.0.5.0.zip  Fix needed when migrating database from 4.0.5.0 to 4.0.5.1 (Fix pack 1)  Fix needed in 4.0.5.1
Deployment
Refer to the FTM online documentation for deployment instructions.
Back to the list of releases
4.0.5.1 interim fix 4 (iFix4)
FTM Upgrade and Rollback from 4.0.5.1 interim fix 3 to 4.0.5.1 interim fix 4
The following document describes the steps to upgrade from FTM 4.0.5.1 iFix3 to FTM 4.0.5.1 iFix4
  • FTM for Base Upgrade and Rollback guide from 4.0.5.1_iFix3 to 4.0.5.1_iFix4.docx
This document is provided in the Entitled documentation fix pack.
Database installation and migration documentation
There is no database migration required between:
  • FTM 4.0.5.1 iFix3 and FTM 4.0.5.1 iFix4.
Known Issues

None

Feature changes

For information about the fixes in 4.0.5.1 iFix4, see Fix List for Financial Transaction Manager for Red Hat OpenShift 4.0.5.

High Availability

Significant progress was made in this release. Focus continues on improving resiliency, handling error detection, and auto-recovery scenarios.

Back to the list of releases
4.0.5.1 interim fix 3 (iFix3)
FTM Upgrade and Rollback from 4.0.5.1 interim fix 2 (iFix2) to 4.0.5.1 interim fix 3 (iFix3)
The following document describes the steps to upgrade from FTM 4.0.5.1 iFix2 to FTM 4.0.5.1 iFix3
  • FTM for Base Upgrade and Rollback guide from 4.0.5.1_iFix2 to 4.0.5.1_iFix3.docx
This document is provided in the Entitled documentation fix pack.
Database installation and migration documentation
There is no database migration required between:
  • FTM 4.0.5.1 iFix2 and FTM 4.0.5.1 iFix3.
Known Issues

None

Feature changes

For information about the fixes in 4.0.5.1 iFix3, see Fix List for Financial Transaction Manager for Red Hat OpenShift 4.0.5.

High Availability

Significant progress was made in this release. Focus continues on improving resiliency, handling error detection, and auto-recovery scenarios.

Back to the list of releases
4.0.5.1 interim fix 2 (iFix2)
FTM Upgrade and Rollback from 4.0.5.1 interim fix 1 (iFix1) to 4.0.5.1 interim fix 2 (iFix2)
The following document describes the steps to upgrade from FTM 4.0.5.1 interim fix 1 (iFix1) to FTM 4.0.5.1 interim fix 2 (iFix2)
  • FTM for Base Upgrade and Rollback guide from 4.0.5.1_iFix1 to 4.0.5.1_iFix2.docx
This document is provided in the Entitled documentation fix pack.
Database installation and migration documentation
There is no database migration required between:
  • FTM 4.0.5.1 interim fix 1 and FTM 4.0.5.1 interim fix 2.
Known Issues

High Availability

Significant progress was made in this release. Focus continues on improving resiliency, handling error detection, and auto-recovery scenarios.

Feature changes

For information about the fixes in 4.0.5.1 interim fix 2, see Fix List for Financial Transaction Manager for Red Hat OpenShift 4.0.5.

Back to the list of releases
4.0.5.1 interim fix 1
FTM Upgrade and Rollback from 4.0.5.1 to 4.0.5.1-iFix1
The following document describes the steps to upgrade from FTM 4.0.5.1 to FTM 4.0.5.1 interim fix 1:
  • FTM for Base Upgrade and Rollback guide from 4.0.5.1 to 4.0.5.1_iFix1.docx
This document is provided in the Entitled documentation fix pack.
Database installation and migration documentation
There is no database migration required between FTM 4.0.5.1 and FTM 4.0.5.1 interim fix 1.
Known Issues

High Availability

Significant progress was made in this release. Focus continues on improving resiliency, handling error detection, and auto-recovery scenarios.

Feature changes

For information about the fixes that are in 4.0.5.1 interim fix 1, see Fix List for Financial Transaction Manager for Red Hat OpenShift 4.0.5.

 
Back to the list of releases
4.0.5.1 release
FTM Upgrade and Rollback from 4.0.5.0 to 4.0.5 Fix Pack 1
The following document describes the steps to upgrade from FTM 4.0.5.0 to FTM 4.0.5 Fix Pack 1:
  • FTM for Base Upgrade and Rollback guide from 4.0.5.0 to 4.0.5.1.docx
This document is provided in the Entitled documentation fix pack.
Deployment
Refer to the FTM online documentation for deployment instructions.

Database installation and migration documentation

Database installation and migration instructions are found in the artifacts container for FTM.
  • The FTM artifacts pod is called: ftm-artifact-base-*
  • The file with the database instructions is called: /home/ftmuser/ftm/artifacts/ftm-db2-base-4.0.5.1-latest.zip. Download this file from the container and extract its contents.
The database installation and migration scripts are located in the following folders.
  • The FTM database installation and migration instructions are in ../ibm/ftm/shared/v405/pfs/Database/db2/{os}/doc.
  • The FTM database migration scripts are in ../ibm/ftm/ftm/v405/admin/scripts/db2/migration.
 
A last-minute fix was made in the FTM database migration script. The updated script is included in the Entitled Documentation fix pack. The instructions to use to apply this script are in FTM Base Upgrade and Rollback guide for 4.0.5.1.pdf.
Known Issues
This release contains the features and known issues that are in 3.2.9. For more information, see the Release notes for IBM Financial Transaction Manager for Multiplatforms 3.2.9.
This release contains the features and known issues that are in 3.2.10. For more information, see the Release notes for IBM Financial Transaction Manager for Multiplatforms 3.2.10.
Potential Data Loss when you are using Db2U

146318 - If you are using Db2U for new deployments, you can choose to load the sample data and restore the database from the sample schema that is provided with your FTM offering. This function can be enabled by setting the "Load Data To Db2U" parameter to true. If an internal server error occurs as the database is being monitored later, the IBM FTM-Base Operator might incorrectly assume that a new deployment is taking place. In this scenario, the operators replace the existing data in your database with the sample data if the "Load Data To Db2U" parameter is still set to true.
Mitigation - If you are using Db2U, make sure that the "Load Data To Db2U" parameter is set to false after you do a new deployment. This problem will be addressed in the 4051 iFix1 release.
145776 & 145708 Usage Report and Metering 
IBM is investigating potential adjustments in the Usage Report and Metering to address discrepancies in the numbers that are reported.

High Availability

Significant progress was made in this release. Focus continues on improving resiliency, handling error detection, and auto-recovery scenarios.

Feature changes

For information about the fixes that are in 4.0.5 Fix Pack 1, see Fix List for Financial Transaction Manager for Red Hat OpenShift 4.0.5.

Back to the list of releases
4.0.5.0 release
Known Issues
This release contains the features and known issues that are in 3.2.9. For more information, see the Release notes for IBM Financial Transaction Manager for Multiplatforms 3.2.9.
This release contains the features and known issues that are in 3.2.10. For more information, see the Release notes for IBM Financial Transaction Manager for Multiplatforms 3.2.10.

High Availability

More resiliency is needed in some scenarios to improve the handling of error detection or auto-recovery. This issue will be addressed in the delivery of future deliveries.

 

Feature changes

For more information about the fixes that are in 4.0.5, see Fix List for Financial Transaction Manager for Red Hat OpenShift 4.0.5.

The following sections provide information about the new and changed features from the previous version of FTM for Red Hat OpenShift.
Power deployment
Financial Transaction Manager for Red Hat OpenShift is now available for IBM Power Systems. This support expands the available hardware platform options and lets organizations take advantage of the many benefits of Power Systems.

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.

135956 – FTM Server Pod to support (S)FTP for data file transfers into Red Hat OpenShift

Starting from 4.0.5.0, Financial Transaction Manager now deploys a File Transfer Protocol server pod. The server is built by using the UBI minimal Red Hat Universal Base Image (UBI) container image. The FTP server uses the secure version of FTP, which is called SFTP. SFTP is done over SSH. Due to the nature of SSH, extra security is added to ensure that only FTP is allowed. The FTP pods have the root file system set to read-only mode. All Linux capabilities are dropped. It ensures that the process has no capabilities and can also work with security context constraints (SCC) that are set to restricted. In a Red Hat OpenShift deployment, the User and UID of the FTP are controlled by the SCC that is used.

 

135814 – Static and dynamic storage provisioning changes required for IBM Cloud

You have the following options to create the required persistent volumes (PV) and persistent volume claims (PVC) for the application:

  1. Dynamic provisioning: The operator creates the required PV, PVC, and folder structures.
  2. Static provisioning: The user is responsible for creating the PVs and the PVCs. The PVC names need to match the names that are required by the operator. The operator creates the folder structure on top of the provided PVCs.

For more information about the persistent volumes, see the Financial Transaction Manager for Red Hat OpenShift 4.0.5 documentation

Back to the list of releases

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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.5"}]

Document Information

Modified date:
18 January 2024

UID

ibm16610643

Page Feedback