IBM(R) Financial Transaction Manager for Multiplatform Version 3.0.0.9 Readme Readme file for IBM(R) Financial Transaction Manager for Multiplatform Version 3.0.0.9 Product/Component Release: 3.0.0 Update Name:Fix Pack 9 Fix ID: 3.0.0-FTM-MP-fp0009 Publication Date: 28 February 2018 ====================================================================== Contents: Download location Prerequisites and co-requisites What's new in FTM 3.0.0.9 Known Issues Installation information Prior to installation Installing Performing the necessary tasks after installation Uninstalling if necessary List of fixes Copyright and trademark information Document change history ====================================================================== Download location ====================================================================== Download IBM(R) Financial Transaction Manager for Multiplatform Version 3.0.0.9 from Fix Central at the following location: http://www.ibm.com/eserver/support/fixes/ Search for the Fix ID: 3.0.0-FTM-MP-fp0009 ====================================================================== Prerequisites and co-requisites ====================================================================== Before downloading FTM v3.0.0.9, 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 pack. - 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 pack, and they might contain workarounds that will impact your use of FTM v3.0.0.9. - Read the "Known issues" section of this readme. - You need to have a file system with 400MB of free space to contain the uncompressed installation image. Ensure that you have the free space required to install the fix pack. - 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 this fix pack. This helps to ensure that your system is in a consistent state and that no special fixes are lost. ====================================================================== What's new in FTM 3.0.0.9 ====================================================================== - Support application generated ID for correlation records that support ID range partitioning To support partitioning by range and distributed ID management techniques to reduce database contention thus improving performance the FTM Core code is change to support distributed ID generation for the 2 correlation tables OUT_RE_CORREL and IN_REQ_CORREL. A new configuration entry is supported to enable this: APP_VERSION_ID = NULL CATEGORY = CORE KEY = MRI_SET_CORREL_ID VALUE = Y | N When set to Y, the ID in the table will be set as follows: OUT_RE_CORREL.ID = OUT_RE_CORREL.REQ_TXN_ID IN_REQ_CORREL.ID = IN_REQ_CORREL.MASTER_ID - Improve efficiency of Event Filter evaluation Evaluation of Event Filter results & Event Filter values read from the Common Base Event during event evaluation are now cached to reduce the overhead of re-evaluation. Minor performance improvement. - [RFE 111814] In the Shutdown Node the current JDBC Provider name "FTMJDBCProvider" is fixed - should allow multiple options. A datasource can now be configured based on the Application name or the Execution Group Name. To maintain backward compatibility the hard-coded name can also be used. The code will search for a datasource by name in the following order: 1) FTMJDBCProvider_ 2) FTMJDBCProvider_ 3) FTMJDBCProvider - Reduce chances of double PT transmission in the event of IIB rollback after PT sent via Fileoutput node File output is now broken into 2 steps to prevent actual transmission of the file until the transmission unit of work commits via MQ/Database. The File data is written in the 1st unit of work, E_OutPTSent is raised The file is retained in the mqsitransit folder. E_OutPTSent is processed in a 2nd unit of work and triggers finalization of the file where it is only moved into the correct folder. E_OutPTSendConfirmed is then raised. The affect of this is that file transmission becomes more transactional and more resilient in the event of transaction rollbacks during the mapping stages. - Add optional reverse engineering support for Command Line Model Extractor A Command Line version of the existing Importer function is now available. More information is available in the following section of the Knowledge Center : Appendixes -> FTM Model Tools -> Command Line Utilities -> Importer See the following section in the FTM Knowledge Center for additional information: Financial Transaction Manager overview->What's new in FTM->What's new in FTM version 3.0.0.9 ====================================================================== Known issues ====================================================================== Issue 1 : User 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 : User Affected: Customers using IBM Integration Bus(IIB) version 9.0.0.x may experience the following BIP2930E error when deploying or restarting the broker. Summary of issue : RecoverableException BIP2930E: A function or procedure was called but the value supplied for the ''cAppVer'' parameter was of type ''BOOLEAN'' but the function/procedure expects value of type ''CHARACTER'' Functions and procedures require an exact matching between the data type of values supplied as parameters and the data type in its definition. Resolution : The fix for this issue(IIB APAR IT06286) is available in IIB Maintenance Level 9.0.0.4. Issue 3 : User Affected: Customers using IBM Integration Bus(IIB) version 9.0.0.3 Summary : Customers using IBM Integration Bus(IIB) version 9.0.0.3 may experience the following BIP2503E when executing customer flows if propagating from a node after exiting a FOR loop acting on a shared variable. RecoverableException BIP2503E: Propagate with a SHARED variable lock held by FOR statement. Resolution : The fix for this issue(IIB APAR IT07974) is available in IIB Maintenance Level 9.0.0.4. Issue 4 User Affected: Customers using IBM Integration Bus(IIB) version 9.0.0.5 Summary : Customers using IBM Integration Bus(IIB) version 9.0.0.5 may experience the following issue: If a user has a REFERENCE variable declared at the module or schema level which points at either OutputRoot, OutputLocalEnvironment or OutputExceptionList and performs a PROPAGATE without specifying DELETE NONE in a compute node then it is not defined what the REFERENCE variable will be left pointing at. After the PROPAGATE the Output trees are deleted and the REFERENCE variables should be reset to point at the root of the newly created trees. The module and schema level reference variables are not being reset and are thus left to point at the original syntax element which they were pointing at which will now have been reset leading to unexpected results. Resolution : The fix for this issue(IIB APAR IT14426) is available in IIB Maintenance Level 9.0.0.6. Issue 5 User 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 : IIB APAR IT14075 has been raised for this issue. Issue 6 User 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 https://www.ibm.com/support/knowledgecenter/SSRH46_3.0.0/fxhprogactionsdbpersistapicfg.html Issue 7 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. Therefore using multiple Pack for SWIFT versions at the same time in a specific instance of a program is not supported. Issue 8 User Affected: FTM v3.0.0.9 Multiplatform only Summary : The database sequence EVENT_ID_SEQ is incrementing by 1. This default value should be set to 1000 to reduce the calls to the database to retrieve the next sequence value. Resolution : Apply the following SQL statements: ALTER SEQUENCE .EVENT_ID_SEQ INCREMENT BY 1000; UPDATE VALUE SET value = '1000' where KEY = 'EVENT_ID_SEQ_INCREMENT'; ====================================================================== Installation information ====================================================================== 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. ==================================================================== Prior to installation ==================================================================== Before installing FTM v3.0.0.9, perform the following steps: - Download the fix pack tar file to an appropriate location. - Uncompress the tar file. ====================================================================== Installing ====================================================================== ==================================================================== Installing FTM v3.0.0.9 to create a new installation ==================================================================== - Start IBM Installation Manager. Add the location of the repository containing the FTM installation package: - Select File->Preferences. - Click Add Repository. - Browse to the directory containing the repository and select the file repository.config (if you are using a directory) or diskTag.inf (if you are using the installation CD) - Click Test Connections and click OK. - Click OK. - Transfer the FTM installation files to your installation directory: - On the main pane, click Install. - Select IBM Financial Transaction Manager for Multiplatforms and click Next. - Review the license agreements and click Next if appropriate. - On the first Install Packages pane, specify the shared resources directory of the Installation Manager and click Next. - On the second Install Packages pane, specify the installation directory (you must have write access to the directory) and click Next. - On the third Install Packages pane, do not change the selected features and click Next. - On the Install package summary information pane, click Install. - After installation is complete, click Finish. Follow the instructions in the "Financial Transaction Manager -> Installing" section of the "IBM FTM for Multiplatforms v3.0.0 documentation" available at https://www.ibm.com/support/knowledgecenter/SSRH46_3.0.0/SSRH46_3.0.0welcome.html ==================================================================== Installing FTM v3.0.0.9 to update an existing installation ==================================================================== - Start IBM Installation Manager. Add the location of the repository containing the FTM installation package: - Select File->Preferences. - Click Add Repository. - Browse to the directory containing the repository and select the file repository.config (if you are using a directory) or diskTag.inf (if you are using the installation CD) - Click Test Connections and click OK. - Click OK. - Transfer the FTM installation files to your installation directory: - On the main pane, click Install. - Select IBM Financial Transaction Manager for Multiplatforms and click Next. - Review the license agreements and click Next if appropriate. - On the first Install Packages pane, specify the shared resources directory of the Installation Manager and click Next. - On the second Install Packages pane, specify the installation directory (you must have write access to the directory) and click Next. - On the third Install Packages pane, do not change the selected features and click Next. - On the Install package summary information pane, click Install. - After installation is complete, click Finish. Follow the instructions in the "Financial Transaction Manager -> Planning -> Migration" section of the "IBM FTM for Multiplatforms v3.0.0 documentation" available at https://www.ibm.com/support/knowledgecenter/SSRH46_3.0.0/SSRH46_3.0.0welcome.html ====================================================================== 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. ====================================================================== List of fixes ====================================================================== Fixes included in FTM for Multiplatform v3.0.0.9 http://www-01.ibm.com/support/docview.wss?uid=swg21700249 ====================================================================== Copyright and trademark information ====================================================================== http://www.ibm.com/legal/copytrade.shtml Notices INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others. THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version. Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions: - the Excluded Components are provided on an "AS IS" basis - IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE - IBM will not be liable to you or indemnify you for any claims related to the Excluded Components - IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components. ====================================================================== Document change history ====================================================================== +---------------------+------------------------------------------------+ | Date | Description of change | +---------------------+------------------------------------------------+ | 28th February 2018 | Original publication date | +---------------------+------------------------------------------------+