Release Notes
Abstract
Release Notes for IBM Financial Transaction Manager for Immediate Payments 3.2.6.1
Content
- Accessing the latest version of the release notes
- Prior to installation
- Product documentation
- Support
- Feature updates
- Known issues
Accessing the latest version of the release notes
Always use the latest version of this release notes file, which is available at:
www.ibm.com/support/pages/node/6409506
Prior to installation
System requirements
Check the IBM Financial Transaction Manager system requirements to ensure that your installation platform is supported for the product edition that you plan to install. For information about the system requirements for all of the different versions of the product, see the IBM Financial Transaction Manager system requirements website.
Downloading the product:
Obtain the fix pack from Fix Central.
Product documentation
The online product documentation is in IBM Knowledge Center.
IBM Financial Transaction Manager for Multiplatforms documentation.
Defects:
Technotes:
For more information about available fixes, see the IBM support web page. To find the information, click the Fix Central link in the Download section of the page. Then, enter the product name. This web page provides links to the latest available maintenance for the in-service IBM Financial Transaction Manager family of products.- Retry functionality
A new optional capability has been added to the Outgoing Payments to TCH RTP workflow to support the automatic retry of payments that are rejected by RTP or the receiving FI. This may be especially useful when the reason for the rejection is due to a timeout or technical error at the receiving FI.
The decision on whether to retry uses Digital Payments Business Rules which determine, based on the reason code, whether to retry, how many times to retry, and how long to delay before attempting to retry.
As shipped, the retry function is disabled. If the retry function is enabled (see below on configuring the retry function), when a reject response is received from RTP the Digital Payments Business Rules are invoked to determine whether an automatic retry should be performed. If no retry is to be performed, the outgoing payment process continues as normal, performing an accounting debit reversal operation before terminating with a failed status. If a retry is to be performed, the outgoing payment process performs the accounting debit reversal operation to tidy up the failed payment, then after pausing for the specified period, the process resumes from the beginning of the Pre-Checks steps, repeating all the Pre-Check services, etc. and submits a new payment (new IDs) to RTP.
Configuring/ Enabling Retry Function for outgoing payments
The retry specific configuration is located under category PFS_RETRY_WORKFLOW:Key Default value Description INVOKE_QUEUE FXR.IP.INVOKE.PFS.WS queue name of (internal) messageflow which invokes business rules web service; this value should not have to be edited IP_ACC_DEBITREVERSAL_REQUEST NO_OUT_TXN_TYPE to enable retry, change this value to OUT_TXN_TYPE IP_FROM_CDTR_ACWPRET NO_RETRY_TXN_TYPE to enable retry, change this value to RETRY_TXN_TYPE IP_FROM_CDTR_RET NO_RETRY_TXN_TYPE to enable retry, change this value to RETRY_TXN_TYPE IP_FROM_DBTR_INSTR NO_RETRY_TXN_TYPE to enable retry, change this value to RETRY_TXN_TYPE IP_FROM_DBTR_INSTR_FI NO_RETRY_TXN_TYPE to enable retry, change this value to RETRY_TXN_TYPE WS_TIMEOUT 60 timeout to wait for a response from Business Rules web service WS_URL http://localhost:7080/businessrules/workflow/retryconfig URL of Business Rules web serviceNotes:The bar file FtmIpDpIntegration.bar, found in <install_dir>/ip/v326/multiplatform/TCH/FTM_IP_TCH_WMB_PI.zip!/FTM IP TCH Bars/ is configured to use a security profile "ftmWsSecurityProfile" to invoke the web service.
This security profile has to created before deploying the bar file, using mqsicreateconfigurableservice command. Refer to Integration Bus documentation about details of this command.
Example:
mqsisetdbparms <integration node> -n WsIdentity -u <user> -p <password>
mqsicreateconfigurableservice <integration node> -c SecurityProfiles -o ftmWsSecurityProfile -n 'propagation,idToPropagateToTransport,transportPropagationConfig' -v 'TRUE,STATIC ID,WsIdentity'
where <user> and <password> are the credentials used to authenticate to the web service.For the Business Rules workflow configuration of the retry refer to V3.2.6 Release Information for Digital Payments, feature 115787.
The category used by Immediate Payments is "IP_RETRY_CSM".
Known issues
This section outlines the known issues and their workarounds (if any).
Issue 1
Users affected: Customers that use IBM Integration Bus toolkit 10.0.0 Fix Pack 11
Summary:
BAR build fails with java.lang.ArrayIndexOutOfBoundsException in the details.
Resolution:
The fix for this issue (APAR IT23841) is available in IBM Integration Bus 10.0.0 Fix Pack 12
Other workarounds include
- Building BAR files in IBM Integration Bus 9.0 or IBM Integration Bus 10.0, up to and including V10.0.0 Fix Pack 10
- Building BAR files by using mqsipackagebar on the command line.
Issue 2
Users affected: Customers that use IBM Integration Bus toolkit 10.0.0 Fix Pack 12
Summary:
BAR build fails with java.lang.IllegalStateException in the details.
Resolution:
Request fixes for IBM Integration Bus APAR IT24755 from IBM Support.
Other workarounds include
- Building BAR files in IBM Integration Bus 9.0 or IBM Integration Bus 10.0, up to and including V10.0.0 Fix Pack 10
- Building BAR files by using mqsipackagebar on the command line.
Was this topic helpful?
Document Information
Modified date:
01 February 2021
UID
ibm16409506