Fix Readme
Abstract
This document contains the Release Information for Financial Transaction Manager (FTM) Nacha for Red Hat OpenShift 4.0.7.
Content
This release information has the following sections.
- FTM 4.0.7 Release Information
- Support
- Entitled documentation fix pack
- Important FTM 4.0.7 document links
- Migrating from FTM 3.2.13 to 4.0.7.0
- Data Setup Utility (DSU) migration
- Transaction Server Scheduler XML
- FTM 4.0.7 Information to be aware of
- Java 17 support
- Introducing phase 1 of the modernized Control Center (UI)
- 4.0.7.0 Known Issues
Release information
| Release | Channel | Operator | Operand | Supported Operands | Case |
| 4060_iFix5 | v4.4 | 4.4.5 | 4.0.6.0_iFix5 | 4.0.6.0, 4.0.6.0_iFix1, 4.0.6.0_iFix2, 4.0.6.0_iFix3, 4.0.6.0_iFix4 & 4.0.6.0_iFix5 | V4.4.5 |
| 4.0.7.0 | stable-v4.6 | 4.6.0 | 4.0.7.0 | 4.0.6.0_iFix5 & 4.0.7.0 | V4.6 |
Support
FTM 4.0.7 supports the following Red Hat OpenShift versions:
- Red Hat OpenShift 4.16.x
- Red Hat OpenShift 4.18.x
on architectures:
- amd64
- ppc64le
Running on OpenShift allows you to deploy on Azure, AWS, IBM Cloud, Google, and on bare metal servers. This is aligned with IBM’s hybrid multi-cloud strategy.
Notes:
- Consistent with IBM’s hybrid multi-cloud strategy, testing is performed on standard OpenShift reference configurations and is not independently run in the lab for every native cloud deployment pattern.
- 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 Check for Red Hat OpenShift is available for IBM Power Systems. This support extends the available hardware platform options, allowing organizations to leverage the numerous benefits of Power Systems.
Power Systems help organizations respond faster to business demands, protect from core to cloud, and streamline insights and automation while maximizing reliability in a sustainable way.
Power Systems can modernize applications and infrastructure with a seamless hybrid cloud experience, providing the agility organizations need.
Entitled documentation fix pack
Entitled documentation can be downloaded from Fix Central at: Entitled documentation fix pack for FTM 4.0.7
The entitled documentation fix pack contains the documents that are shown in the following table
| Document | Description |
| FTM_DB_Design_Doc_v407.html | The database design document describes the FTM BASE data dictionary, table entities, and view entities. It also includes an appendix with the table and view index and column index. |
| FTM_Check_DB_Design_Doc_v4070.html | The database design document describes the FTM Check data dictionary, table entities, and view entities. It also includes an appendix with the table and view index and column index. |
| FTM_DUP_DETECT_DB_Design_Doc_v4070.html | The database design document describes the FTM Check data dictionary, table entities, and view entities. It also includes an appendix with the table, view, and column index for the Duplicate Detection database. |
| FTM Check Migration from 3.0.5 to 4.0.7.doc | This document aids in migrating Financial Transaction Manager (FTM) for Check 3.0.5 on a traditional WebSphere Application Server environment to FTM Check 4.0.7 on Red Hat OpenShift |
| DSUMigrationBR_v4.0.7.docx | This document describes the changes to the rules between releases used by the Business Rules Server (BR). |
| DSUmigration_v4.0.7.docx | This document describes the changes to the Import/Export workbooks between releases used by the Data Setup Utility (DSU). |
| TransactionServerSchedulerChanges_v4.0.7.doc | This document outlines the changes to Transaction Server Scheduler events between releases. These changes can be specific to scheduler events or to the SchedulerReference.xml file. |
| Using_Database_for_Problem_Resolution.pdf | This document contains solutions for various product issues that can only be resolved by updating the database. A database administrator needs to run the database scripts. |
| logging-dashboard.json | Sample Grafana dashboard |
| folder: yaml | OpenAPI documentation for FTM web services provided in YAML format. |
| folder: swagger | |
| folder: FTM3054-Fix |
Clients migrating from FTM 3.0.5.4 must apply this fix. |
| FTM for NACHA Migration 3.2.13 to 4.0.7 |
This document aids in migrating Nacha 3.2.13 on a traditional WebSphere Application Server environment to FTM Nacha 4.0.7 on Red Hat OpenShift |
Important FTM 4.0.7 document links
- The IBM FTM 4.0.7 documentation (IBM Docs)
- The Download document
- The Resources document
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.7.pdf
- DSUMigrationBR_v4.0.7.pdf
These documents are provided in the Entitled documentation fix pack (see above).
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). Download the appropriate JRE for IBM Semeru 17 from IBM Semeru Runtimes Downloads
Transaction Server Scheduler XML
The following documentation describes the changes to the scheduler XML for the Transaction Server component:
- TransactionServerSchedulerChanges_v4.0.7.pdf
This document is provided in the Entitled documentation fix pack (see above).
| Back to contents | FTM 4.0.7 Information to be aware of |
Caution: The FTM Operator is set to auto-deploy by default (by OpenShift). 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.
12680 FTM Operator has been split into two operators.
FTM Operator has been split into two operators. The API operator installs the FTM CRD, which can be installed once per cluster. The controller operator installs the FTM controller, which must be installed in each namespace where an FTM instance is to be deployed. Refer to the FTM documentation for more information.
13564 FTM now enforces SSL hostname verification
Ensure that the SSL Certificate used by FTM contains the correct domains in the list of Subject Alternative Names. Refer to the FTM documentation for more information.
8440 IBM App Connect integration-runtimes migration
The Integration Server custom resource (or operand) is deprecated in IBM® App Connect Operator 11.5.0 and will be removed in a future release of the Operator. It is suggested to switch to using the Integration Runtime custom resource (or operand) by creating integration runtimes as described in IBM App Connect integration-runtime(https://www.ibm.com/docs/en/app-connect/13.0.x?topic=resources-integration-runtime-reference)
Since the IBM App Connect operator has deprecated the integration-server instances, the IBM FTM operator does not create the IBM App Connect integration-server instances by default but instead creates IBM App Connect integration-runtimes instances from version FTM 4.0.7.0
FTM standard bar files and the associated configuration instances are now deployed on the IBM App Connect integration runtime instances.
What has changed:
- All default ACE pods in FTM deployment will have “ir” appended in the name instead of “is”. For example ftm-inst-core-flows-ir
- The IBM App Connect dashboard instance will be deployed with displayMode:IntegrationRuntimes
19974 The MQ cipher used in FTM 407
The default cipher spec used with MQ is now TLS_AES_128_GCM_SHA256
Communications between FTM application components
All direct RMI/IIOP communications between FTM application components are performed over SSL/mTLS connections. Insecure connections are not supported.
config:
instance:
referenceImplementations:
simualtors:
enabled: true
include:
- vetting
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:
| Back to contents | Java 17 support |
FTM 4.0.7.0 introduces support for Java 17, a significant upgrade from the Java 8 support of prior releases. All FTM container images where Java is executed now use IBM Semeru Certified Edition 17.
FTM components are no longer compatible with Java 8 Java Runtime Environments (JREs), with the exception of the following:
- User-defined functions (UDFs) registered with Db2 (run on the Db2 server). These are isolated to FTM's base_udf_utilities.jar.
- FTM Base custom plug-ins running in Rational Software Architect Designer (RSAD) 9.7.
Customer Action: Customers running FTM utility programs outside the OpenShift environment will need to download IBM Semeru Certified Edition 17, except for Windows environments, which will require IBM Semeru Open Edition 17. Public download site: https://developer.ibm.com/languages/java/semeru-runtimes/downloads/.
Additionally, all user exits called by FTM and all utilities that invoke FTM Application Programming Interfaces (APIs) must be recompiled using one of the aforementioned IBM Semeru 17 downloads. Be sure to compile against the FTM API and dependent JAR files provided on the FTM 4.0.7.0 artifacts pod.
The following links to Java migration information are provided for your convenience:
- Semeru Runtimes migration guide for users who are migrating from IBM® SDK, Java™ Technology Edition, Version 8 to version 11 of the IBM Semeru Runtime: https://www.ibm.com/support/pages/semeru-runtimes-migration-guide.
- Oracle JDK Migration Guide: https://docs.oracle.com/en/java/javase/17/migrate/index.html.
Gateway Server Email Properties
The Gateway Server now sends emails directly by interfacing with a Simple Mail Transfer Protocol (SMTP) server, rather than relying on the Services Framework Engine to send them on its behalf. As such, the Gateway Server property mailServiceProviderURL is now obsolete and has been replaced with three new properties for interacting with an SMTP server: smtpHost, smtpPort, and smtpMaxRetries. As such, the Websphere Mail Session JNDI name on the Outbound Channel Definition detail page for mail routing types is no longer needed and has been removed.
Gateway Server gatewayEngineUrl Property
The Gateway Server now performs NACHA and CPA returns processing internally, eliminating the need for remote processing calls to the Gateway Engine. Also, Control Total Validation for NACHA no longer utilizes remote processing calls to the Gateway Engine. Instead, an MQ message is issued to the Gateway Engine input queue for this purpose. This queue is configured using the new mqGatewayEngineQueue property, making the gatewayEngineUrl obsolete.
| Back to contents | Introducing phase 1 of the modernized Control Center (UI) |
FTM 407 Introduces phase 1 of the new React/Carbon-based Control Center (also known as the User Interface or "UI"); the remaining work will be delivered in future releases.
A significant upgrade to Control Center is being released with FTM 4.0.7, bringing a modern, fresh, and easy-to-use look to the platform. This new interface has been crafted using React and the Carbon Design System, cutting-edge technologies that form the foundation of its superior performance and user experience. Why such a change is being delivered? The previous Control Center was built on older technology. This resulted in an outdated feel and presented certain security concerns. Client security and an optimal experience are always our top priorities.
Therefore, this new design has been developed, and it offers substantial benefits:
-
increased ease of use: The Control Center has been made more intuitive, allowing information to be found faster and tasks to be completed with less effort
-
simplified navigation: movement within the system has been smoothed. Less time will be spent searching, and more time will be spent accomplishing tasks
-
strengthened security: the latest technology has been utilized to keep data secure within the new system
-
improved experience: a clean, modern design has been implemented, which will make using the Control Center a much more pleasant experience
With FTM 4.0.7, it is expected that this new look will make work smoother, more enjoyable, and more productive.
It's important to note that pages within the UI will be replaced incrementally. While modernized pages will showcase the new design, all unmodernized pages will remain available and will appear as they did in previous versions, framed within the new Control Center in 4.0.7.
UI Changes for FTM 407
Naming convention used to identify OpenShift resource types (Pods, Containers, Deployments, Services, ConfigMaps and Routes) for the new React/Carbon-based Control Center and the legacy Control Center.
-
control-center-core-api - used to identify the API component of the new React/Carbon-based Control Center
-
control-center - used to identify the UI part of the new React/Carbon-based Control Center
-
control-center-frame - used to identify the legacy Control Center
Control Center help links now link to external IBM Documentation
System Overview and linked pages date range differences
The date/time range filter used on the System Overview page is translated to a full-day date range when navigating to the "Outbound Transmission" page via the "Outbound > Transmission in Error" link.
Separate OIDC logout required
By design, users are required to log out of their OIDC provider independently after logging out of the application.
TCR advice view requires a PDF viewer in the Chrome engine.
If the user's Advice is not visible in the Chrome browser, it means the PDF viewer must be installed before viewing.
A PDF viewer extension can be downloaded at https://chromewebstore.google.com/detail/pdf-viewer/oemmndcbldboiebfnladdacbdfmadadm?hl=en.
Refer to the FTM publication for Transaction Correction and Reconciliation User's Guide > Customer Advice page for details.
Control Center (UI) known issues
We're sorry!
Content not found
- name: control-center
containers:
control-center:
env:
- name: DOCUMENTATION_URL
value: https://www.ibm.com/docs/SSRH46_4.0.7/
9781 The Inbound Batches “show columns” dialog check-box may not respond in Firefox.
The “show columns” dialog box to add or remove columns on the inbound batches screen occasionally does not respond when selecting multiple columns on the Firefox browser. If it occurs, please reopen the dialog box.
13585 Firefox: Truncated navigation labels.
For some Firefox screen resolutions, navigation labels may appear truncated. Although resolution adjustments can help, the truncated labels are still usable.
16689 The Scroll bar is missing on the inbound transactions screen.
Occasionally the scroll bar is missing on the inbound transaction screen. If it occurs, please click the refresh button.
17877 Occasional login prompt on logout
Occasionally, users might encounter a login prompt when attempting to log out. If this occurs, please log in again and then proceed with the logout.
19357 "Download Advice" presents a loading warning
Upon clicking "Download Advice" on the Transmission Hierarchy screen, a warning message may appear, indicating that loading the page is taking longer than expected, along with the loaded PDF. In this case, the user may safely ignore and close the warning message.
19648 Cache Monitor Polling Interval appears in Component Properties
The Cache Monitor Polling Interval is displayed on the Payment Feature Services component properties. This property has no effect and can be ignored.
| Back to contents | FTM 4.0.7 Known Issues |
13279 The newly upgraded MQ version 9.4.2 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.2:
-
Change the cipher on the client end to TLS_AES_128_GCM_SHA256 or other ciphers that are supported by MQ 9.4.2 (MQ operator 3.5.0)
-
Enable deprecated cipher as described in MQ documentation here.
Additionally, if any scripts are used to connect to the IBM MQ instance using MQ Client, the client libs may need to be upgraded to the latest version.
19685 The "Alert Email" task has a known issue that requires it to be rerun before it can be successfully used
Mitigation: Invoke another instance of the "Alert Email" task to send any emails. You should only need to do one repeat run. Note that this is not a task restart, but a new run. The run will pick up any alerts not sent.
15897 Scheduled tasks in the Transaction scheduler.xml that are scheduled based on days or business days may not fire at the proper time after a time change.
After switching from standard time to daylight savings time and vice versa, verify that tasks are running at the proper time. This can be determined by running the Transaction server diagnostic command "list schedule" from the Components UI. If it is off, alter the starting time or date to get it back in sync.
18235 Processing high Nacha volumes could result in a DB2 transaction log full (-964 error) condition
When processing high volumes of Nacha payments through FTM a DB2 transaction log full (-964 error) condition may occur if the configured DB2 maximum transaction log size is inadequate.
The config-dropins.xml value in the ConfigMap control-center-frame-dropins is improperly formatted. The XML appears as a single line with "\n" and "\t" control characters. There is no functional impact. However, it is difficult to read at a glance, and users seeking to modify the XML may inadvertently introduce syntax errors.
The formatting will be corrected in a future release. Until then, users should take care of editing the config-dropins.xml.
Was this topic helpful?
Document Information
Modified date:
05 June 2025
UID
ibm17234215