IBM Support

V4.0.6 Release Information for Financial Transaction Manager Check for Red Hat OpenShift

Fix Readme


Abstract

This document contains the Release Information for Financial Transaction Manager (FTM) Check 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 Check 4.0.6.0 to install? 

For a New/Fresh install,

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

For Clients who are already on FTM Check 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 Check 4.0.6.0 interim fix 6 (iFix6)
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 Check 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: Entitled documentation fix pack for FTM Check 4.0.6

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

Document Description
FTM Check changes between 4051 and 406.docx Describes the deployment changes made in 406 from 4051.
FTM_Check_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.
FTM_DUP_DETECT_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, view, and column index for the Duplicate Detection database.
FTM Check Migration from 3.0.5 to 4.0.6.pdf This document aids in migrating Financial Transaction Manager (FTM) for Check 3.0.5 on a traditional WebSphere Application Server environment to FTM Check 4.0.6 on Red Hat OpenShift
DSUMigrationBR_v4.0.6.pdf This document describes the changes to the rules between releases used by the Business Rules Server (BR).
DSUmigration_v4.0.6.pdf This document describes the changes to the Import/Export workbooks between releases used by the Data Setup Utility (DSU).
TransactionServerSchedulerChanges_v4.0.6.pdf This document describes changes to the Transaction Server Scheduler events between releases. These changes can be specific to scheduler events or to the SchedulerReference.xml file.
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
folder: FTM3054-Fix

Clients migrating from FTM 3.0.5.4 must apply this fix.
This fix addresses the problem that the Gateway Server auxiliary database properties do not work because "databaseURL" was uppercased when it should not have been.

Important FTM Check 4.0.6 document links

IBM Java Runtime Environment (JRE)

An IBM Java Runtime Environment (JRE) must be installed in your development environment to run programs such as the Data Setup Utility (DSU). If you are entitled, you can download one of the supported JREs from Fix Central at these links:

The OFAC Simulator is a Technical Preview in this release and is disabled by default 
The OFAC/Vetting simulator is disabled by default. This simulator will only be deployed if simulators are enabled and "vetting" is in the include list, as in the example below.
spec:
  config:
   instance:
    referenceImplementations:
     simualtors:
      enabled: true
      include:
        - vetting
To enable the OFAC simulator after deployment, several manual steps are required. You must manually execute the associated DB and MQ scripts, as well as update the barUrl of the simulator IntegrationServer. For more details, see the "Deploy the FTM reference implementation" section of the IBM Documentation.
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 upgrading, as they 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_0.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
New requirement when installing 4.0.6.0 iFix6
Reminder: 
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.
To support the installation of different versions of FTM in separate 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 iFix6
For a list of all the fixes included in 4.0.6.0 iFix 6 see: 4.0.6.0 iFix6 defect Fix List
Back to the list of releases
4.0.6.0 interim fix 5 (iFix5)
Upgrading from FTM Check 4.0.6.0 iFix4 to FTM Check 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 Check 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.
To support the installation of different versions of FTM in separate 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 Check 4.0.6.0 interim fix 1 (iFix1):
Upgrade from FTM Check 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 Check 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 Check 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)
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.
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 Check 4.0.6.0 interim fix 1 (iFix1):
Upgrade from FTM Check 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 Check 4.0.6.0 iFix1 and 4.0.6.0 inFix3.
For Clients who are currently on FTM Check 4.0.6.0 interim fix 2 (iFix2):
Upgrade from FTM Check 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 Check 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)
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: 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 Check 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 Check 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 Check 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 Check 4.0.6.0 and 4.0.6.0 interim fix 1.

Back to contents Migrating to 4.0.6.0 Check from an earlier release
MIGRATION

FTM Check migration 3.0.5 to 4.0.6
The following documentation helps you migrate Financial Transaction Manager (FTM) for Check 3.0.5 (on a traditional WebSphere Application Server environment) to FTM for Check 4.0.6 on Red Hat OpenShift.

  • FTM Check migration from 3.0.5 to 4.0.6.pdf

This document is provided in the Entitled documentation fix pack.

ATTENTION: Clients migrating from FTM 3.0.5.4 must apply this fix

This fix is to address that the Gateway Server auxiliary database properties do not work because "databaseURL" was uppercased but should not have been.

This fix is provided in the Entitled documentation fix pack in the folder named: "FTM3054-Fix" and the file name is "izxfix.jar"

How to apply this fix:

in 3.0.5.4 the file "izxfix.jar" is in the Component "lib" folder. so for the Gateway server, it will be in:
    Windows e.g D:\App1\IBM\ftm\shared\v305\pfs\Gateway\lib
    Linux e.g /app1/IBM/ftm/shared/v305/pfs/Gateway/lib

Steps:
1. First, copy the existing izxfix.jar to a safe location, then move the fixed file into the 3.0.5.4 folder.
2. Next, shut down the Gateway server.
3. Then restart Gateway server.

Data Setup Utility (DSU) migration
The following documentation describes the changes for the data setup utility (DSU) and the import and export workbooks:

  • DSUMigration_v4.0.6.pdf
  • DSUMigrationBR_v4.0.6.pdf

These documents are provided in the Entitled documentation fix pack.

Transaction Server Scheduler XML 4.0.6
The following documentation describes the changes to the scheduler XML for the Transaction Server component:

  • TransactionServerSchedulerChanges_v4.0.6.pdf

This document is provided in the Entitled documentation fix pack.

 

Enhancements since FTM Check 4.0.5.1

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

Enhancements
  • Standardization on a single GO-base Operator for deployments
  • Archive Server Replacement (CIFF, NCR, ViewPointe, OnDemand, CMOD, Titan) - see IBM Docs
  • Restored ViewPointe Support 
  • Support for external Vault - see IBM Docs for details
  • TIFF Corrections enhancements
  • Support for Fragmented Transaction Server Scheduler XML
  • Add Supplemental Groups to v4 Operator - see IBM Docs for details
  • Middleware updates - currency and security - see Support Matrix
  • ACE Standalone (Operator) Support (does not apply to FTM Check) OR Switch to ACE Standalone Container Usage - (not for Check)
  • External (outside OCP) MQ Environment Support 
Back to contents Known Issues (the iFix that they have been fixed in)

18198: Control Center UI Login Authentication failure when using OIDC configuration. (Fixed in iFix5)

Description:
Customers using OIDC configuration for Control Center UI login Authentication might run into an authentication failure noted below in the pod logs.

CWWKS1520E: A request to [https:\/\/xxxx\/oidcclient\/redirect\/ftm] is not valid. A required cookie with a name that begins with WASReqURLOidc is missing. The host name that is used to access the client might not match the name that is registered at the provider. A response code of 500 is returned.

Mitigation:
Control Center UI Liberty configuration runs with a default of Strict for the sameSiteCookie attribute in the webAppSecurity stanza. As per the liberty documentation here: https://www.ibm.com/docs/en/was-liberty/nd?topic=messages-cwwks, customers may override this via control-center-check-dropins ConfigMap. A restart of the control-center-check pod is necessary for the changes to take effect.

18497: When updating a presentment group without a currency code attached, an exception can occur, preventing the update of the totals. (Fixed in iFix6)
ABP00022S: Unable to process request from PFSUpdateEmitter. Failure updating presentment totals
Mitigation:
A test fix can be provided at request by contacting support.
18514: EntryAllocationTask not generating CPCS Entry Numbers  (Fixed in iFix6)

Description:
EntryAllocationTask runs on a given UOW. However, no CPCS Entry Numbers are generated.
 
Mitigation:
A test fix can be provided at request by contacting support.

15184: Restart fails when Gateway is in pause state.  (Fixed in iFix6)

Description:
Restarting adds the additional control total property, although the status for Gateway is invalid for restarting.
Mitigation:
Manually remove the new control total attribute added in the FW_FILE_STATUS_PROP table and do a restart after the gateway is resumed.

18446: Installing 4060 iFix5 when a later version (e.g. FTM 4.0.5.x) of the FTM operator is installed (Fixed in iFix6)

Description/Mitigation:

If a later version of the FTM operator is installed on the cluster (e.g. if the FTM operator from channel 4.5.0 has been installed in a separate namespace on the OCP cluster), then the following fields must be explicitly defined in the custom resource when deploying an instance of FTM 4.0.6 iFix 5:

Under spec.config.mq:

cipherSpec: ANY_TLS12_OR_HIGHER
cipherSuite: ANY_TLS12_OR_HIGHER

Under spec.config.mq.create:

version: "9.4.2.0-r1"
license: L-QWBN-T3PKLE
use: NonProduction

Under spec.config.ace

version: "12.0"
license: L-XRNH-47FJAW
use: AppConnectEnterpriseProduction
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.
151066/13351: Business Day Activation
Using the Automatic Business Day Activate feature when ingesting multiple files in parallel, may result in a business day status of "Activate failure".
Mitigation: Open and activate business days prior to ingesting work.


150991/4634: 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.
150684: Crystal report server (Crystal Report 2020 is no longer supported, support has moved to Crystal 2025 for FTM 4.0.6)
The Crystal Server/Report2020 requires SP3 patch level 4 or above. In addition, copy cryptojce.jar, cryptojFIPS.jar and jcmFIPS.jar to the Service Framework. For details see: 
https://www.ibm.com/docs/en/ftmfm/4.0.6?topic=library-crystal-reporting-task

[{"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

ibm17129577

Page Feedback