V4.0.3 Release Information for Financial Transaction Manager for Digital Payments for Red Hat OpenShift

Known Issues

121368

Gateway Server has an SQL CODE: -302 error when the initiateCreditTransfer clearing_system_member_identification value has length of 32 to 35 characters.

High Availability

Additional resiliency is needed in some scenarios to improve the handling of error detection / auto recovery. This issue is addressed in the delivery of the interim fix.

120369

Interac Payments with backspace character in the payment payload are not supported and rejected immediately in the FTM Outbound (Channel) API. Interac Payments with tab, new line, and carriage return characters are posted to the Interac Network correctly, but render as \t, \n and \r in the Control Center and OAC user interfaces.

1119353
Interac solution can support only debtor names of 20 characters. If debtor name is longer than 20 characters, it is truncated to 20 characters and stored in database.

Feature changes

Enhanced UTF-8 support
Implemented UTF-8 character support for DSU, Distribution Manager, and Business Rules Server.
- DSU can be used to import and export configuration information with UTF-8 characters.
- Operator is able to activate release (build and validate TBL file)
- Business Rules Server successfully receives the activated descriptors/file and process the activated releases.
- Business Rules Server is able to process transmissions and transactions that include UTF-8 characters.

Enhanced software upgrade capabilities and process management

Improved reliability of the Business Rules Server rules activation
The Business Rules Server now uses a database polling mechanism to load business rules upon activation by utilizing the ENVIRONMENT database table settings.

Improved flexibility and scaling capabilities for the IBM App Connect Enterprise and IBM MQ containers
FTM split the combined containers into separate IBM App Connect Enterprise and IBM MQ containers.

The IBM MQ container is now a separate container that is running IBM MQ 9.2. IBM App Connect Enterprise 11.0.0.11 is running in separate IBM App Connect Enterprise containers.
Benefits of the split:
- Ability to deploy IBM App Connect Enterprise and IBM MQ separately
- Ability to have IBM App Connect Enterprise connect to a remote queue manager.
- Ability to customize the IBM App Connect Enterprise deployment topology as required.
- Ability to have multiple IBM App Connect Enterprise containers.
- Ability to set resources (CPU and Memory) for the IBM App Connect Enterprise and IBM MQ containers separately
- Provide features of both auto and manual scaling for IBM App Connect Enterprise containers

Additional error codes to better identify the source system in error scenarios
FTM is providing more error codes to help better identify the source system in which an error scenario occurs.
These error codes are provided with the FTM configuration sheets for the TCH and Interac references.
The following error codes were added and linked to categories for better clarity. The category linked to these error codes represents the source system (or process) that identified the issue.

Improved security of communication between FTM components
FTM communication between components is now more secure with TLS encryption.
IBM MQ and Db2 communications are running over TLS.
The J2EE, J2SE, and IBM App Connect Enterprise client applications connect over a TLS protocol.
The procedure to generate (if self-signed certificates) and configure TLS certificates used by all the FTM components is documented by FTM. The default CipherSuite/CipherSpec used by IBM MQ and all the clients is SSL_RSA_WITH_AES_128_CBC_SHA256/TLS_RSA_WITH_AES_128_CBC_SHA256. This default can be customized during deployment with the Operator Instance YAML.

LPTA Keys by default
No customization is required. LTPA keys are managed by the individual J2EE Liberty server instances. The default configuration is used and LTPA keys are created when the application pod starts.

Readiness and Liveness health check probes and prestop pod lifecycle event
FTM now comes with health check probes (readiness and liveness) and prestop pod lifecycle events implemented.
Readiness and liveness probes: During the rolling upgrades, the new version Pod gets created and when it becomes ready, then OpenShift deletes the old pod. OpenShift runs the Readiness probe to decide whether the pod is Ready or not. Unless the probe returns success, it does not mark the new Pod in ready state.
Liveness probes are run periodically, like the readiness probe. If liveness probe fails, OpenShift restarts the container.
Prestop pod lifecycle event: OpenShift allows adding the PreStop hook to be run inside the container before OpenShift deletes the container. This script is called by OpenShift before it deletes the container.

Allow customization of config files and server.xml files by using configMap
FTM operator now supports a ConfigMap-based approach to let user provide custom server.xml or other configuration files in addition to the persistent volume-based approach. Separate ConfigMaps are created for each FTM component, and the customer can place all the customized files in those ConfigMaps. This method is useful for the customers who do not use persistent volumes (PV) or do not have easy access to the PVs from outside. This method is supported for JSE and Java EE components.

Usage count metering differentiates between production and non-production environments
The FTM metering application, which is in the OAC pod, now differentiates between production and non-production usage counts. The differentiation is made based on the "Environment type" variable under "License" category of IBM FTM Base operator.
- Customers should set this variable to "Production" or "NonProduction" based on the type of environment they are building during the operator installation.
- Regardless of "Environment type" value, all usage counts are calculated and stored in the database.
- Only production mode usage counts are reported to the IBM License Server, which is in the "ibm-common-services" namespace and is shared across all projects.