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-gwy-runtime-processing: Dedicated PV for all Gateway Server file processing (inbound, outbound, and DTA)
• 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 the Java Platform, Standard Edition (J2SE) components such as Gateway Server, Transaction Server, Business Rules Server, and Distribution Manager, you can customize all the application configuration files.

For Java 2 Platform, Enterprise Edition (J2EE) components, you can customize the Liberty configuration and JVM settings.

135957 - New createNewRelease property in Business Rules Properties

Enhancements to the Business Rules import capabilities were added. These enhancements provide more release ID capabilities without the customer needing to know the release ID ahead of time.

A new flag was added to the DSU load of Business Rules. It causes the import to not create a new release, but to look for the latest viable or editable release.

#  

# Release Identification Parameters 

# ================================= 

# 

# createNewRelease = false   <-- new property

# releaseId        = 1  

New 'buildtables' command was added to Business Rules Manager 'Control' page

A new command was made available for customers to run a 'buildtables' command for a specific Distribution Manager component.

128139 Get ValidationVersionNum set correctly for Check

When the payment level update occurs, the version number of the existing validation record is incremented. In other words, the version of each payment has the corresponding validation records version so that the history of the validation process is maintained.

 The following components increment the version numbers after each payment record update.

1. Suspect Image Review

2. Payment Repair

3. Duplicate Detect

4. Amount Keying (when updated with Business Rules validation)

5. TCR (when updated with Business Rules validation)

6. Revalidation of the payment level is done.

 Suspect Image Review, Payment Repair, and Duplicate Detect increment the version numbers of the payment only when the payment is accepted.

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.