Fix Readme
Abstract
This document contains V4.0.4 release information for Financial Transaction Manager for Red Hat OpenShift.
Content
V4.0.4 Release Information for Financial Transaction Manager (FTM) for Red Hat OpenShift
Contents
| Back to top |
4.0.4.1 release
|
Entitled Documentation
Entitled documentation can be downloaded from Fix Central at:
122221 – Client_Cert authentication support for user interface applications
Starting from 4.0.4.1, Financial Transaction Manager now supports CLIENT_CERT authentication for all Liberty-based components. This authentication includes the Liberty-based user interface components, FTM OAC and FTM Control Center. General instructions on how to configure authentication is available on the IBM FTM product documentation page. More instructions on how to enable this authentication by using config drop-ins described in the security documentation (IBM_FTM_V4041_Security_Configuration.pdf) that is available to entitled users.
127768 – Simplify PV/Folder Structure to be more readable and meaningful
The folder structure on the persistent volumes (PV) for FTM was simplified. New PV names with their purpose are defined in the following list.
- pv-ftm-image-data: Dedicated PV that holds image file data.
- pv-ftm-application: Dedicated PV for all the FTM application storage requirements. For example, fix JAR files, shared libraries, custom task configuration files, and temporary transaction processing files.
- pv-ftm-debug-data: Dedicated PV for application core dumps and snapshots that are needed to debug problems.
128489 – Remove PV concepts for customer configurations (ConfigMaps only)
FTM simplified the customization of application configuration by introducing config maps and removing the use of persistent volumes (PVs) for any configuration customization.
For Java Platform, Enterprise Edition (J2EE) components, you can customize the Liberty configuration and JVM settings.
135814 Dynamic Provisioning
You have the following options to create the persistent volumes (PV) and persistent volume claims (PVC) that are needed for the application:
1. Dynamic provisioning: The operator creates the PVs, PVCs, and folder structure that is needed.
2. Static provisioning: You must create the PVs and PVCs that are needed. The names of the PVCs need to match what the operator is expecting. The operator creates the folder structure on the provided PVCs.
| Back to top |
4.0.4.0 release
|
Entitled Documentation
Entitled documentation can be downloaded from Fix Central at:
Database installation and migration documentation
High Availability
Additional resiliency is needed in some scenarios to improve the handling of error detection / auto-recovery. This issue will be addressed in the delivery of the interim fix.
Feature changes
121472 Improved efficiency and consistency with HTTP probes for the ACE containers
FTM comes with probes (readiness and liveness) and PreStop hooks for managing pod lifecycle events. In this release, the ACE probes are changed from scripted probes to HTTP probes.
The HTTP probes provide performance improvements and future integrations with external monitoring tools.
123986 Allow customization of jvm.options in Liberty containers
Users can provide additional JVM options to the JEE components. The JVM options for every JEE component can be configured separately. It can be done by providing the customized jvm.options file.
Overriding the default JVM settings is useful in many situations, like during the troubleshooting sessions, enabling memory dumps, identifying performance issues, enable profiling, and so on.
122332 DB2U: Incorporate the use of a standard DB2 container
The FTM offerings running on Red Hat OpenShift can be combined with Db2 on Red Hat OpenShift to get the convenience of the operator capabilities. Db2 can be deployed in a Red Hat OpenShift cluster as a containerized micro-service, or pod, managed by Kubernetes. This robust operator allows us to use the stateful behavior and provides features like HA to get maximum performance and reliability in production.
For more information, see the v4.0.4 Financial Transaction Manager for Red Hat OpenShift IBM Documentation.
126196 FTM Logging
FTM applications running on Red Hat OpenShift adhere to the basic principle of writing logs to the console (stdout and stderr) so that financial institutions can easily integrate these logs with the appropriate logging service supported by Red Hat OpenShift.
Upgrade Liberty to 21.0.0.6
The Liberty server was upgraded to 21.0.0.6.
Support usage metering for FTM for Check
FTM Metering was updated to store and report usage counts to the IBM License server for FTM for Check installations on Red Hat OpenShift. It includes two counts per day, Base count and Check count. Both counts are the same and Only Master Transactions are counted.
Back to topWas this topic helpful?
Document Information
Modified date:
30 June 2022
UID
ibm16488433