Readme file for IBM Financial Transaction Manager for Multiplatforms v3.2.0.1
Product/Component Release: 3.2.0
Fixpack number: v3.2.0.1
Fix ID: 3.2.0-FTM-MP-fp0001
Download IBM(R) Financial Transaction Manager for Multiplatforms Version 3.2.0.1
from
Fix Central
Search for the Fix ID: 3.2.0-FTM-MP-fp0001
Note: the downloaded zip file(3.2.0-FTM-MP-fp0001.zip) contains the following two FTM Installation Manager repository files:
- Financial Transaction Manager for Multiplatforms v3.2.0.1.zip
- Financial Transaction Manager for zOS Developer Edition v3.2.0.1.zip
See the "Installation information" section below for information on installing the fixpack for your offering.
Before downloading FTM v3.2.0.1, perform the following steps:
- Ensure that your system meets all of the system requirements:
http://www.ibm.com/software/industry/financial-transaction-manager/requirements
This action prevents technical problems that might occur after the installation and configuration of the fix.
- Review the Flashes and open Authorized Problem Analysis Reports (APARs) on the Financial Transaction Manager product support Web site:
http://www.ibm.com/software/industry/financial-transaction-manager/support
Open APARs describe defects that are not yet addressed in a fix, and they might contain workarounds that will impact your use of FTM v3.2.0.1.
- Read the "Known issues" section of this readme.
- You need to have a file system with 400MB of free space to contain the fix files.
Ensure that you have the free space required to install the fix.
- If you already have an FTM product installed and have obtained special fixes, contact IBM(R) support to determine whether you need an updated version of the fixes before you install FTM v3.2.0.1.
This helps to ensure that your system is in a consistent state and that no special fixes are lost.
- Support for SWIFT Standards Release 2018. (Ref:82594)
- Added a Restore option in the OAC for Configuration history data. (Ref:82537)
In the History tab for the Configuration Data, a history entry can now be selected and restored as the current data.
- Support for display of JSON messages in the OAC. (Ref:82519)
In the OAC Raw Data tab, JSON formatted messages can now be displayed in a tree viewer.
See the "Financial Transaction Manager -> Financial Transaction Manager overview -> What's new in FTM" section of the "FTM for z/OS v3.2.0 Knowledge Center"
available at
IBM Financial Transaction Manager for z/OS V3.2.0 documentation
Issue 1
Users Affected : Customers using IBM WebSphere Transformation Extender(WTX) version 8.4.1.2.
Summary :
Customers using IBM WebSphere Transformation Extender(WTX) version 8.4.1.2
who use native schema and choice sequence iterations are
unable to access iterations of a particular sequence group.
Resolution :
The fix for this issue(APAR PI31636) is available in WTX v8.4.1.3.
Issue 2
Users Affected : Customers using any Broker level from v7.x.
Summary :
Customers using any Broker level from v7.x may experience inconsistent validation results when using FTM Channel based validation and/or IIB in ESQL parser validation.
Resolution :
The fix for this issue(IIB APAR IT14075) is available in IIB Maintenance Level 10.0.0.5.
Issue 3
Users Affected : Customers using Oracle Database v11.x and above.
Summary :
FTM(with Oracle) users may experience the following issues when using the Multi Row Insert(MRI) function :
"ORA-00932 inconsistent datatypes: expected NUMBER got TIMESTAMP"
"ORA-01400 cannot insert NULL into ()"
This issue is a known Oracle issue - reference Oracle bug # 9648430.
Resolution :
Apply the Oracle fix.
If an Oracle fix is not available for your version of Oracle then a workaround is to disable MRI in FTM as follows:
Category Key Value
CORE MRI_EM2_ENABLED N
For additional details about the Database Persistence API configuration, see the following section in the Knowledge Center for Financial Transaction Manager, Version 3.0.0 :
Financial Transaction Manager -> Application programming -> Actions -> Database Persistence -> API configuration
Issue 4
Users Affected : Customers using FTM SWIFT WTX maps.
Summary :
FTM SWIFT SR2016 WTX maps will not work with FTM SWIFT SR2015 WTX maps at a single broker instance together at the same time.
The reason is that IBM Transformation Extender has changed the JVCWrapper code with the new Financial Payments Pack for
SWIFT 9.0.1 release and it is not compatible with the earlier Pack for SWIFT releases.
Resolution :
Therefore using multiple Pack for SWIFT versions at the same time in a specific instance of a program is not supported.
Issue 5
Users Affected : Customers using IBM Integration Bus V10.0.
Summary :
Payments not completing correctly due to incorrect MQ rollback processing.
Resolution :
The fix for this issue(APAR IT25600) is targeted for delivery in the following PTFs:
| Version | Maintenance Level |
| v10.0 | 10.0.0.14 |
Note: If the maintenance level is not yet available,
information on its planned availability can be found
here.
Issue 6
Users Affected : Customers using IBM Integration Bus V10.0.
Summary :
BIP2329E: An unexpected NULL value was encountered.
Resolution :
Patches for this issue are available on request from IBM support.
Please quote the APAR number(IT25754) in the request and provide full details of the IIB 10 levels in use.
Before proceeding with the installation process, view the online version of this readme file to check if information has changed since the
readme file was downloaded.
FTM for Multiplatforms
Follow the instructions in the "Financial Transaction Manager -> Installing" section of the "FTM for Multiplatforms v3.2.0 Knowledge Center"
available at
IBM Financial Transaction Manager for Multiplatforms V3.2.0 documentation
To update an existing v3.2.0.x runtime installation
Follow the instructions in the "Financial Transaction Manager -> Planning -> Migration" section of the "FTM for Multiplatforms v3.2.0 Knowledge Center"
available at
IBM Financial Transaction Manager for Multiplatforms V3.2.0 documentation
FTM for zOS Developer Edition
Follow the instructions in the "Financial Transaction Manager -> Installing" section of the "FTM for zOS v3.2.0 Knowledge Center"
available at
IBM Financial Transaction Manager for zOS V3.2.0 documentation
To update an existing v3.2.0.x runtime installation
Follow the instructions in the "Financial Transaction Manager -> Planning -> Migration" section of the "FTM for zOS v3.2.0 Knowledge Center"
available at
IBM Financial Transaction Manager for zOS V3.2.0 documentation
Uninstalling if necessary
To rollback to the previous version of FTM:
- Start Installation manager
- Click Roll Back.
- Select the Package Group name where FTM is installed.
Database:
Restore the backup taken during the Database migration step.
Application Migration:
Revert to the WebSphere Message Broker Toolkit workspace taken during the installation steps.
Re-deploy the application bar files.
OAC Migration:
Re-deploy the OAC ear from the previous version.
RSA Model Tooling:
Use Installation manager to re-install the previous version of the 'FTM Model Tools'.
Fixes included in FTM for v3.2.0.1
http://www.ibm.com/support/docview.wss?uid=ibm10729307