IBM Support

V4.0.6 Release Information for Financial Transaction Manager T2/EURO1, Common Services and CBPRPlus for Red Hat OpenShift

Fix Readme


Abstract

This document contains release information for
- Financial Transaction Manager T2/EURO1 for Red Hat OpenShift 4.0.6.
- Financial Transaction Manager Common Services for Red Hat OpenShift 4.0.6.
- Financial Transaction Manager CBPRPlus 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

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 4 (iFix4) 

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):

  • upgrade to FTM Check 4.0.6.0 interim fix 4 (iFix4)
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.14.x
  • Red Hat OpenShift 4.16.x

on architectures:

  • amd64
  • ppc64le

Although we haven’t fully tested all options, this means you can deploy on Azure, AWS, IBM Cloud, Google, and on bare metal servers. This is aligned with IBM’s hybrid multi-cloud strategy. 

Note:  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.

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

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:

Important documents:

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.
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 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)
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 until a fix is available for this issue.
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 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
  • None
 
Back to contents 4.0.6.0 iFix4 Known Issues

13279 The newly upgraded MQ version 9.4.1 does not support older CipherSpec, for example, SSL_RSA_WITH_AES_128_CBC_SHA256. See MQ doc for more info here

Mitigation: There are two possible options for handling ciphers deprecated in 9.4.1:

  1. Change cipher on client end to ANY_TLS12_OR_HIGHER or other ciphers that are supported by MQ 9.4.1 (MQ operator 3.3.0)

  2. Enable deprecated cipher as described in MQ documentation here.

Additionally, if any scripts are used to connect to IBM MQ instance using MQ Client, the client libs may need to be upgraded to the latest version.

 
13122 The MQ pod may emit events that it is unable to retrieve some image pull secrets. These events are harmless and will not affect MQ functionality.
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.
10369:  Do not install an earlier version of the FTM operator after a later version is installed.
Do not install an earlier version of the FTM operator after a later version is installed. Even though the operator has namespace scope and can support multiple versions in the same cluster, the custom resource definition (CRD) for the IBM FTM Operator applies to the whole cluster. Reinstalling the operator overwrites the existing CRD, which might adversely affect any existing deployments of FTM on the cluster.
Mitigation: If you want to use an earlier version of the operator, uninstall the later version first.
 

150991: Unable to create the FTM operator instance using the Forms view
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.
10776: If the OpenShift cluster is restarted, the ACE pods will fail when trying to access the artifacts with the error: “404”.
Also, when executing into the artifacts pod and navigating to the “/share” directory, the error “No such file or directory” will occur.
Mitigation: Restarting the artifacts pod will resolve the issue.

150684: Crystal report server
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
Back to contents 4.0.6.0 iFix2: Defect Fixed List (defects fixed in this release)
 

 
Fix number
 Type Description

151767

Batch rejected after doing DB2 failover with no reason given.
During db2 failover, on very rare occasions, a batch is rejected without an error code assigned, and it is marked as not overrideable. 

151811

Issue when overriding a file (or batch) using "Accept" with revalidation

After file (or batch) ingestion, if an error occurs (example: duplicate file/batch); if you try to override the file/batch using "Accept" with revalidation, then items in this file are marked incorrectly with the validation error flag.

5151585/6022

A Db2 Pod restart (failover) during ingestion, may cause some ingested files to be flagged as duplicaes
A Db2 Pod restart (failover) during ingestion, may cause some ingested files to be flagged as duplicates because the auto-recovery process does not clear the gateway duplicate detection records before restarting the ingestion of these files.

152023
Metering Service fails to upload usage details
The following metering service alert can be caused by an issue with the NetworkPolicy configurations.
FTMMT013S: Unknown exception while trying to upload usage details to the license server metric upload service. Please check the log for details.
If the metering pod logs show "javax.ws.rs.ProcessingException: java.net.SocketTimeoutException: SocketTimeoutException" in the ibm_stackTrace field, then the issue is likely caused by the FTM NetworkPolicies preventing communication with the ibm-common-services namespace.

151995
Issue with Cognos Reports where Database view GET_OPERATIONAL_TZ_TIME_NOW_V is improperly created by the FTM operator 
Db2 produces the following error when view FTMPUB.GET_OPERATIONAL_TZ_TIME_NOW_V is accessed by Cognos Analytics reports for a database built by the FTM operator:
SQL Error [42724]: Java stored procedure or user-defined function "FTMPUB.J_GET_OPERATION", specific name "GET_OPERATIONAL_TZ_TIM" could not load Java class "com/ibm/fxh/base/util/ud", reason code "".. SQLCODE=-4304, SQLSTATE=42724, DRIVER=4.26.14

152304

Setting the environment variable TZ in the FTM operator yaml file is not working for j2se pods

8083

FTM operator is ignoring the spec.scheduling configuration

User is not able to set spec.scheduling to configure the OpenShift scheduling for FTM pods.

8100

“oc explain” command not working for FTM CRD

The user is unable to run the “oc explain” command to get a description of the fields in the FTM CRD.

9131

The user is not able to mount custom volumes in FTM pods.

A user cannot mount custom volumes, such as config maps, secrets, PVCs, or other types of volumes, into any of the FTM pods.

9597

The FTM operator ignores the exclude clause once the FTM instance is deployed.

Once FTM is deployed, the FTM operator ignores the init container exclude clause. If a user adds a pod to the exclude clause, the FTM operator will not remove the init container from that pod.

9603

Users cannot scale down individual pods after deployment.

Users cannot scale down individual pods after deployment. If they try, errors show up in the FTM operator log.

9712

Unable to customize FTM pod security context.

Users are not able to customize the security context for FTM pods. For example, it is not possible to specify the uid or gid that the FTM pods run as.

9721

FTM documentation erroneously includes quotes around the values in the sample vars.env file.

The values in the vars.env file must not be enclosed in quotes. The FTM documentation erroneously includes quotes around the sample vars.env file.

9778

FTM instance status stays as Ready when the user makes updates to the instance.

When FTM is deployed and the operator has finished reconciling the custom resource, the CR's status changes to "Ready." If the customer updates the CR again, the status stays as Ready. Once the instance is reconciled, the status should change to NotReady and then back to Ready.

10057

FTM web-server is not getting TLS secret from the external vault.

If the user is getting the TLS certificates from an external vault, then the artifacts web server needs to configure TLS with those certs. Currently, it only configures TLS with certificates from OpenShift.
152304
 Setting the environment variable TZ in the FTM operator yaml file is not working for j2se pods

152095

Updated AdjustmentRuleUtility.getAdjustmentRule(long,long,short).

There is a line of code where we retrieve the user default value for the insert amount, but we weren't passing the configured default amount to the method, so it wasn't recognizing the need to use the configured default amount instead of the current amount.
Back to contents 4.0.6.0 iFix1: Defect Fixed List (defects fixed in this release)
Fix number
 Type Description

151071
The FTM operator pod crashes due to a missing required custom resource definition (CRD). [Fixed in 4.0.6.0 iFix1]
When installing the FTM operator, a custom resource definition needed by the operator does not get installed, resulting in the FTM operator pod crashing.

151122
Warning message with cloudctl commands during AirGap deployment [Fixed in 4.0.6.0 iFix1, by replacing "cloudctl" with "ibm-pak"]
During the AirGap process, the cloudctl commands are used for FTM instance setup and deployment. However, the cloudctl commands are now deprecated and every execution of cloudctl command gives the following warning message:

WARN[0000] DEPRECATION NOTICE:
'cloudctl case' commands are deprecated in favor of ibm-pak. Support for them will be
removed in a future release. More information is available at https://ibm.biz/cloudctl-case-deprecate

149882
Warning messages in Simulators ACE pods [Fixed in 4.0.6.0 iFix1]
The following warning messages appear continuously on simulator pods after the pod starts. Note: that this does not impact processing.
2023-12-29 12:17:24.393602: BIP4361W: Java node warning: [com.ibm.fxh.profiling.messages:General.Error]General Error : Common.UsageCountFlow: Application not initialised.
2023-12-29 12:17:24.393776: BIP4361W: Java node warning: [com.ibm.fxh.profiling.messages:General.Error]General Error : Common.UsageCountFlow: Schema not initialised.

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"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:
05 November 2024

UID

ibm17130989

Page Feedback