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.

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

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.

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.