IBM Support

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

Fix Readme


Abstract

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

For a New/Fresh install,
  • IBM recommends installing the latest release available, which is: FTM Check 4.0.5.1 interim fix 4 (iFix4) 
For Clients who already have FTM Check 4.0.5.1 OR FTM Check 4.0.5.1 interim fix 1 (iFix1) OR FTM Check 4.0.5.1 interim fix 2 (iFix2) OR FTM Check 4.0.5.1 interim fix 3 (iFix3) installed
  • IBM recommends upgrading to the latest release available, which requires iFixes to be deployed in sequential order:
    • For Clients on FTM Check 4.0.5.1, upgrade to FTM Check 4.0.5.1 interim fix 1 (iFix1)
    • For Clients on FTM Check 4.0.5.1 interim fix 1 (iFix1), upgrade to FTM Check 4.0.5.1 interim fix 2 (iFix2)
    • For Clients on FTM Check 4.0.5.1 interim fix 2 (iFix2), upgrade to FTM Check 4.0.5.1 interim fix 3 (iFix3)
    • For Clients on FTM Check 4.0.5.1 interim fix 3 (iFix3), upgrade to FTM Check 4.0.5.1 interim fix 4 (iFix4)
Back to the list of releases
Common across all 4.0.5.x releases

Entitled documentation fix pack

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

The entitled document fix pack contains the following:

Document

Description

Comments
FTM for Check 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 Check application from 4.0.5.1_iFix3 to 4.0.5.1_iFix4 and rollback the FTM Check application from 4.0.5.1_iFix4 to 4.0.5.1_iFix3. New in 4.0.5.1 iFix4
FTM for Check 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 Check application from 4.0.5.1_iFix2 to 4.0.5.1_iFix3 and rollback the FTM Check application from 4.0.5.1_iFix3 to 4.0.5.1_iFix2.
 New in 4.0.5.1 iFix3
FTM for Check 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 Check application from 4.0.5.1_iFix1 to 4.0.5.1_iFix2 and rollback the FTM Check application from 4.0.5.1_iFix2 to 4.0.5.1_iFix1.
 New in 4.0.5.1 iFix2
FTM for Check 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 interim fix 1 to 4.0.5.1. New in 4.0.5.1 iFix1

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

FTM_Check_DB_Design_Doc_v4051.html 

The Database Design Document that describes the Data Dictionary, Table Entities, and View Entities, as well as an appendix that includes the Table and View Index and Column Index

updated for v4.0.5.1

FTM_DUP_DETECT_DB_Design_Doc_v4051.html 

The Database Design Document that describes the Data Dictionary, Table Entities, and View Entities, as well as an appendix that includes the Table and View Index and Column Index for the Duplicate Detection database

updated for v4.0.5.1

FTM for Check Migration 3.0.5 to 4.0.5.pdf

This document aids in migrating Financial Transaction Manager (FTM) for Check 3.0.5 on a traditional WebSphere Application Server environment to FTM for Check 4.0.5 on Red Hat OpenShift.

updated for v4.0.5.1

DSUMigrationBR_v4.0.5.pdf

This document enumerates the changes to the rules between releases used by the Business Rules Server (BR). 

updated for v4.0.5.1

DSUmigration_v4.0.5.pdf

This document enumerates the changes to the Import/Export workbooks between releases used by the Data Setup Utility (DSU). 

updated for v4.0.5.1

TransactionServerSchedulerChanges_v4.0.5.pdf

This document enumerates the changes to the Transaction Server Scheduler events between releases. These changes can be for specific scheduler events or changes to the SchedulerReference.xml file. 

updated for v4.0.5.1

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.

No updates since 4.0.5.0

IBM_FTM_for_Check_high_availability_information_4051.pdf

This document contains information about the high availability testing done for this deliverable.

updated for v4.0.5.1

IBM_FTM_for_Check_performance_information_v4051.pdf

This document contains information about the performance testing done for this deliverable.

updated for v4.0.5.1

Folder: yaml 

 OpenAPI documentation for FTM web services provided in YAML format.
 
 updated for v4.0.5.1

Folder: swagger

No updates since 4.0.5.0

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

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:

IBM FTM 4.0.5 documentation

The IBM FTM 4.0.5 documentation.

FTM 4.0.5 deployment

For more information about deploying FTM for Check, see FTM for Check deployment overview in the FTM online documentation.

Back to the list of releases
4.0.5.1 interim fix 4 (iFix4)

The upgrade path for clients on FTM for Check 4.0.5.1

Clients on FTM for Check 4.0.5.1 must

  • first, upgrade from FTM for Check 4.0.5.1 to FTM for Check 4.0.5.1 interim fix 1, then
  • upgrade from FTM for Check 4.0.5.1 interim fix 1 to FTM for Check 4.0.5.1 interim fix 2 and then 
  • upgrade from FTM for Check 4.0.5.1 interim fix 2 to FTM for Check 4.0.5.1 interim fix 3
  • upgrade from FTM for Check 4.0.5.1 interim fix 4 to FTM for Check 4.0.5.1 interim fix 4

The following document describes the steps to upgrade FTM for Check:
  • FTM for Check Upgrade and Rollback guide from 4.0.5.1 to 4.0.5.1_iFix1.docx
  • FTM for Check Upgrade and Rollback guide from 4.0.5.1_iFix1 to 4.0.5.1-iFix2.docx
  • FTM for Check Upgrade and Rollback guide from 4.0.5.1_iFix2 to 4.0.5.1-iFix3.docx
  • FTM for Check Upgrade and Rollback guide from 4.0.5.1_iFix3 to 4.0.5.1-iFix4.docx
These documents are provided in the Entitled documentation fix pack.
Support
By using the Red Hat OpenShift platform, Financial Transaction Manager (FTM) for Check 4.0.5.1 interim fix 4 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 for Check 4.0.5.1 interim fix 4 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.

Database migration

There is no database migration between:

  • FTM for Check 4.0.5.1 and 4.0.5.1 Check interim fix 1.
  • FTM for Check 4.0.5.1 interim fix 1 and 4.0.5.1 Check interim fix 2.
  • FTM for Check 4.0.5.1 interim fix 2 and 4.0.5.1 Check interim fix 3.
  • FTM for Check 4.0.5.1 interim fix 3 and 4.0.5.1 Check interim fix 4.

New and changed features

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

Known Issues

  • same as for 4.0.5.1 below
Back to the list of releases
4.0.5.1 interim fix 3 (iFix3)

The upgrade path for clients on FTM for Check 4.0.5.1

Clients on FTM for Check 4.0.5.1 must

  • first, upgrade from FTM for Check 4.0.5.1 to FTM for Check 4.0.5.1 interim fix 1, then
  • upgrade from FTM for Check 4.0.5.1 interim fix 1 to FTM for Check 4.0.5.1 interim fix 2 and then 
  • upgrade from FTM for Check 4.0.5.1 interim fix 2 to FTM for Check 4.0.5.1 interim fix 3

The following document describes the steps to upgrade FTM for Check:
  • FTM for Check Upgrade and Rollback guide from 4.0.5.1 to 4.0.5.1_iFix1.docx
  • FTM for Check Upgrade and Rollback guide from 4.0.5.1_iFix1 to 4.0.5.1-iFix2.docx
  • FTM for Check Upgrade and Rollback guide from 4.0.5.1_iFix2 to 4.0.5.1-iFix3.docx
These documents are provided in the Entitled documentation fix pack.
Support
By using the Red Hat OpenShift platform, Financial Transaction Manager (FTM) for Check 4.0.5.1 interim fix 3 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 for Check 4.0.5.1 interim fix 3 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.

Database migration

There is no database migration between:

  • FTM for Check 4.0.5.1 and 4.0.5.1 Check interim fix 1.
  • FTM for Check 4.0.5.1 interim fix 1 and 4.0.5.1 Check interim fix 2.
  • FTM for Check 4.0.5.1 interim fix 2 and 4.0.5.1 Check interim fix 3.

New and changed features

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

Known Issues

  • same as for 4.0.5.1 below
Back to the list of releases
4.0.5.1 interim fix 2 (iFix2)

The upgrade path for clients on FTM for Check 4.0.5.1

Clients on FTM for Check 4.0.5.1 must

  • first, upgrade from FTM for Check 4.0.5.1 to FTM for Check 4.0.5.1 interim fix 1, and then
  • upgrade from FTM for Check 4.0.5.1 interim fix 1 to FTM for Check 4.0.5.1 interim fix 2.

The following document describes the steps to upgrade FTM for Check:
  • FTM for Check Upgrade and Rollback guide from 4.0.5.1 to 4.0.5.1_iFix1.docx
  • FTM for Check Upgrade and Rollback guide from 4.0.5.1_iFix1 to 4.0.5.1-iFix2.docx
These documents are provided in the Entitled documentation fix pack.
Support
By using the Red Hat OpenShift platform, Financial Transaction Manager (FTM) for Check 4.0.5.1 interim fix 2 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 for Check 4.0.5.1 interim fix 2 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.

Database migration

There is no database migration between:

  • FTM for Check 4.0.5.1 and 4.0.5.1 interim fix 1.
  • FTM for Check 4.0.5.1 interim fix 1 and 4.0.5.1 interim fix 2.

New and changed features

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

Known Issues

  • same as for 4.0.5.1 below
Back to the list of releases
4.0.5.1 interim fix 1 (iFix1)

The upgrade path for clients on FTM for Check 4.0.5.0

Clients on FTM for Check 4.0.5.0 must first upgrade to FTM for Check 4.0.5.1, and then upgrade from FTM for Check 4.0.5.1 to FTM for Check 4.0.5.1 interim fix 1

The following document describes the steps to upgrade FTM for Check:
  • FTM for Check Upgrade and Rollback guide from 4.0.5.0 to 4.0.5.1.pdf
  • FTM for Check Upgrade and Rollback guide from 4.0.5.1 to 4.0.5.1-iFix1.pdf
These documents are provided in the Entitled documentation fix pack.
Support
By using the Red Hat OpenShift platform, Financial Transaction Manager (FTM) for Check 4.0.5.1 interim fix 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 for Check 4.0.5.1 interim fix 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.

Database migration

There is no database migration between FTM for Check 4.0.5.1 and 4.0.5.1 interim fix 1.

New and changed features

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

Known Issues

  • same as for 4.0.5.1 below
Support
By using the Red Hat OpenShift platform, Financial Transaction Manager (FTM) 4.0.5 Fix Pack 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 Fix Pack 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 OpenShift Container Platform version to stay current with security fixes.
FTM for Check 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 for Check 4.0.5.0 to FTM for Check 4.0.5 Fix Pack 1:
  • FTM for Check Upgrade and Rollback guide from 4.0.5.0 to 4.0.5.1.pdf
This document is provided in the Entitled documentation fix pack.

Database installation and migration documentation

Database installation and migration instructions are found in the artifacts container for FTM for Check.
  • The FTM for Check artifacts pod is called: ftm-artifact-check-*
  • The file with the database instructions is called: /home/ftmuser/ftm/artifacts/ftm-db2-check-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.
  • For FTM, the database migration scripts are in ../ibm/ftm/ftm/v405/admin/scripts/db2/migration.
  • For FTM for Check, the database installation and migration instructions are in ../ibm/ftm/shared/v405/pfs/Database/db2/{os}/doc.
For more information about the artifacts containers and database migration, see the following links to the FTM online documentation:
After the FTM (core) database is migrated, use the installation and migration instructions to run the FTM for Check database migration scripts from the artifacts container.

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.5.pdf
  • DSUMigrationBR_v4.0.5.pdf

These documents are provided in the Entitled documentation fix pack.

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

  • TransactionServerSchedulerChanges_v4.0.5.pdf

This document is provided in the Entitled documentation fix pack.

FTM for Check migration 3.0.5 to 4.0.5
The following documentation aids in migrating Financial Transaction Manager (FTM) for Check 3.0.5 on a traditional WebSphere Application Server environment to FTM for Check 4.0.5 Fix Pack 1 on Red Hat OpenShift.

  • FTM for Check migration 3.0.5 to 4.0.5.pdf

This document is provided in the Entitled documentation fix pack.

New and changed features

Upgraded the IBM MQ deployment from an FTM operator controlled IBM MQ to an IBM MQ HA operator

When you are migrating from a single IBM MQ container to the native HA IBM MQ Operator, several behavioral changes occur. For more information, see the following IBM MQ behavioral differences between 4.0.5.0 and 4.0.5 Fix Pack 1 documents in the Entitled documentation fix pack.
  • MQ behavioral differences between 4050 and 4051.pdf
  • Comparing_Native_HA_MQ_Operator_to_standalone_MQ_Container.pdf
Note: FTM 4.0.5 Fix Pack 1 uses queue manager storage and recovery logs storage. However, recovery logs storage is to be disabled and replaced with persistent data storage in future releases. To avoid any potential issues customizing the queue manager without impacting persisted data, use separate storage for persisted data and the queue manager.

Usage Reporting Tool (URT) enhancements

The URT was enhanced to generate two reports when both production and nonproduction transaction volumes are in the selected calendar window.

Db2U HA support

FTM integrated with HA support is provided with the Db2U container deployment.

Support the ability to set the ISN sequence ID and sorter ID within AutoAdjust and Transaction Correction and Reconciliation (TCR)

For more information, see the FTM online documentation.

Extended the supported network storage classes

The following network storage classes are now supported.
  • Portworx
  • IBM Spectrum Scale
  • ODF in IBM Cloud
For more information, see the documentation for the storage that you are using.

FTM deployment considerations on IBM Cloud Secure Landing Zone, HPCS, and Portworx

FTM provides a description of an example FTM deployment that uses the Secure Landing Zone (SLZ), HPCS service, and Portworx service on IBM Cloud. You can use it as a reference when you are designing your own FTM deployment on IBM Cloud. It is at the following link:

Implemented FTM service and communication that uses CCDT JSON

Enabled FTM application to use a JSON formatted CCDT file to store connection properties. For more information, see the FTM online documentation.

Implemented SAML SSO for FTM Control Center and FTM OAC applications

FTM users can now use SAML SSO for the FTM Control Center and FTM OAC applications. For more information, see the FTM online documentation.

Known Issues

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-Check Operator and IBM FTM-Base Operator operators 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.

High Availability (HA)

Significant progress was made in this release. Focus continues on improving resiliency, handling error detection, and auto-recovery scenarios.
Specific Manual Recovery steps can be found in the High availability manual recovery procedures topic of the FTM online documentation.

Duplicate Detection

121542 - For large transmissions, the last page of the Inbound Transactions page in the Control Center intermittently does not complete the display of all transactions.
Mitigation: When loading completes, click refresh.

Gateway user exit

139141 - When a Gateway Server property userInsertItemClass is configured for user exit SampleUserInsertItem, it might insert the item in the wrong record order. As it is not being validated during ingestion, it is not an issue. However, if the transmission is being revalidated or released, this record is sent to Business Rules Server for validation, which causes the context validation failure. If the user exit is not configured, no issues occur with revalidation or the release of a transmission.
Mitigation: To avoid the validation context error on revalidation or release, comment out this property:
userInsertItemClass = com.ibm.icpcs.gatewayserver.samples.SampleUserInsertItem.

CDC datastore connection

139480 - An SSL enabled CDC datastore is not detected as Dual Type.
Mitigation: Users must ensure that their Db2 SSL host port is open for CDC to connect to the database successfully.

Failover shows an increased number of rejects and warnings

139951 - Occasionally, the number of rejects and warnings in Inbound Processing and Batches appears to double when a failover occurs. This problem occurs when the Transaction Server processes messages from the Duplicate Detect Engine, where items were marked as duplicates and assigned an error code. The message might get processed more than once and inflate the number of rejects and warnings for those transactions and the batches that contain them.
Mitigation: The inflated numbers do not cause any issues with the processing of the work - the transaction were rejected. This known issue is to explain why the numbers are higher than expected.

142746 - Unable to process files on secondary site (DR) after ingestion

Approach: IBM MQ support for disaster recovery (DR) is limited. One tactical approach is described in a document that is called Tactical approach for DR support for FTM 4.0.5.1 IBM MQ usage. This document is available in the Entitled documentation fix pack.

Accessing the IBM MQ web console can result in a "file not found" error

143895 - This error can occur when you use the Red Hat OpenShift Container Platform console to select Networking, Routes, and then the link to access the IBM MQ web console.

Alternate method: Select the "Operator", select the "OperatorHub", and then select "installed operators". Then, click the "UI Admin" option to access IBM MQ web console with no errors.
Excessive Core dumping in Java Platform, Enterprise Edition applications

144170 -  If you are running an FTM instance in an IBM Cloud cluster and you are using the IBM Cloud Sysdig Monitoring Tool, a workaround is required to prevent continuous core dumping in Java Platform.

Mitigation: Customers that use IBM Cloud Monitoring (Sysdig) need to do the following updates to avoid the FTM Core Dumps:

Update the sysdig-agent configmap in the ibm-observe namespace to contain the following:
      jmx:
      jvm_exclude:
      - property: java.vm.name
      pattern: IBM J9 VM

Settlement Service Manager request is not getting set to complete

144636 - After a transmission is loaded, some payments remain in the messaging state after settlement processing. This problem can be identified by seeing the ABP00005W warning message on the System Logs page. Also, check the Service Manager page for records with a state of messaging and Settlement as a description.
Mitigation: Use the Service Manager page to restart the UOW that is in the messaging state and has Settlement as a description.

Items slow to leave the messaging state (Service Manager)

144669 - Work-in-progress records appear to remain in the messaging state on the Service Manager page after the status was marked as complete on the Inbound Batches / ICLs page.
Mitigation: None. A fix for this problem is planned for a future release.

144917 - PowerVS/Power: Database timeouts in Distribution with high thread counts

Mitigation: This problem is caused by NUMA misalignment of the Db2 LPAR on the Power VS environment. The impact of this problem is causing higher memory allocation overhead and higher lock contention. A support case (CS3314341) and defect (SW560575) were opened with PowerVS/Power Support.

145273 - Outbound Transmission build and release failed due to lock timeout

Mitigation: Run the rebuild and release action to transmit the transmission.

145330 - CPCS Sequence Number for TCR item can show an incorrect value untill the TCR item is approved

Mitigation: This problem resolves itself when the TCR item is approved.

Not able to configure LDAP authentication for IBM MQ web console

145578 - IBM MQ Support ticket TS012917264 is open for this problem.

Crystal Reports and Crystal Server 2020 incompatibilities

145738 - IBM tested with Crystal Reports 2020 SP02 Patch 900 and Crystal Server 2020 SP02 Patch 100, and the results showed incompatibilities. This problem is being investigated.
Control Center Online Help - Search does not work

146101 - In the Control Center help screen, typing in the search field and clicking "Go" results in error: Error 500: org.apache.jasper.JasperException: org.apache.jasper.JasperException: Unable to load class for JSP

Mitigation: We are investigating how to resolve this issue and will provide a solution in a future release.  In the meantime, the same online help content and similar search capabilities exist in our online help here https://www.ibm.com/docs/en/ftmfm/4.0.5
New features and feature changes from previous releases of FTM Check
 
The following sections provide information about the new and changed features from the previous version of FTM for Check.
Power deployment
Financial Transaction Manager for Check 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 - Storage and Dynamic 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 the provided PVCs.

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

ibm16610651

Page Feedback