IBM(R) Financial Transaction Manager for Multiplatform Version 3.0.0.1 Readme Readme file for IBM(R) Financial Transaction Manager for Multiplatform Version 3.0.0.1 Product/Component Release: 3.0.0 Update Name:Fix Pack 1 Fix ID: 3.0.0-FTM-MP-fp0001 Publication Date: 27 March 2015 Last modified date: ====================================================================== Contents: Download location Prerequisites and co-requisites 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.1 from Fix Central at the following location: http://www.ibm.com/eserver/support/fixes/ Search for the Fix ID: 3.0.0-FTM-MP-fp0001 ====================================================================== Prerequisites and co-requisites ====================================================================== Before downloading FTM v3.0.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 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.1. - Read the "Known issues" section of this readme. - You need to have a file system with 200MB 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 FTM v3.0.0.1. This helps to ensure that your system is in a consistent state and that no special fixes are lost. ====================================================================== Known issues ====================================================================== Issue 1 : 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 : Please raise a Service Request with the WTX product to request a fix for APAR PI31636. Issue 2 : IBM Integration Bus(IIB) version 9.0.0.x 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 : Please raise a Service Request with the IIB product to request a fix for APAR IT06286. ====================================================================== 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.1, perform the following steps: - Download the fix pack tar file to an appropriate location. - Uncompress the tar file. ====================================================================== Installing ====================================================================== ==================================================================== Installing FTM v3.0.0.1 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 "Installing" section of the "FTM for Multiplatforms Knowledge Center" available on the FTM Product website at http://www.ibm.com/software/industry/financial-transaction-manager/ ==================================================================== Installing FTM v3.0.0.1 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 Update. - 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. - Database Migration: The following database changes will be made using the procedures below: - Added CACHE_LEARN column to the H_APP_VERSION table. - Added RENDER_MSG_OVERRIDE column to the H_APP_VERSION table. - Added LOG_EVENT_OVERRIDE column to the H_APP_VERSION table. - Changed the data type of the COMPONENT_NAME column on the ERROR table to VARCHAR(100). - TXN_SEC_V_INS view updated to change ISF_DATA supported data length from 20k to 30k on inserts. - For DB2 only: Changed GENERATED attribute of the ID column on the OUT_REQ_CORREL table to BY DEFAULT. - For Oracle only: Changed SWT_OUT_REQ_CORREL_ID trigger to allow the ID column on the OUT_REQ_CORREL table to be set or generated. - For Oracle only: T_CALENDAR_ENTRY_U trigger updated to resolve CAL_DATE issue. - For Oracle only: TRANSMISSION_V_INS trigger changed to update additional columns. - For Oracle only: CONVERT_UTC_TO_DB_TZ function refreshed to resolve timezone issue. Migration procedures: - Backup the database so that it may be rolled back should there be a problem during or after the migration process - On AIX/Linux for DB2 run the /admin/scripts/db2/migration/3.0.0.1_from_3.0.0.0/Migrate-Unix.sh script. - On AIX/Linux for Oracle run the /admin/scripts/oracle/migration/3.0.0.1_from_3.0.0.0/Migrate-Unix.sh script. - Application Migration: The following steps must be followed to migrate FTM applications and their runtime environment. - Ensure that the broker is correctly configured to use the JPLUGIN and CLASSES resources in \run - Make a backup of your current WebSphere Message Broker Toolkit workspace. - FTM applications in WebSphere Message Broker Toolkit workspaces must be migrated as follows: - Re-import the following resources, then rebuild and redeploy the applications bar file(s). - Re-import the FTM Core Flows (found in the /multiplatform/FXH_Core_Projects_WMB.zip file) into the workspace. - Re-import the FTM Generic Model Actions(found in /multiplatform/FXH_GenericModel.zip) into the workspace. - Re-import the FTM SWIFT MT Flows(found in /multiplatform/FXH_Core_Projects_WMB.zip) into the workspace. - OAC Migration: The OAC ear file must be re-deployed to the Websphere Application Server from \multiplatform\FXH_Console.zip - RSA Model Tooling Migration: The following steps must be followed to migrate the FTM Model Tooling and existing FTM Models: - Follow the Installing > Installing the FTM Model Tools package > Installation instructions section in the FTM Knowledge Center to install the new Model Tooling from /multiplatform/FXH_FSM_Model_Tools.zip - To migrate an existing FTM FSM Model, open the model in RSA. If any migration issues are encountered, a report file in HTML format will be created in the RSA workspace. - Tools Migration: The Usage Reporting Tool, which can be found at /tools/, has been updated. ====================================================================== 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. ====================================================================== Additional information ====================================================================== This section contains updated documentation. Usage Reporting Tool(URT): The usage report tool has been modified slightly with regards to encryption support. It is now possible to provide an encrypted properties file along with a plaintext properties file, retrieving properties from each. (An encrypted properties file can be created using the encryption.jar as discussed below.) The Usage Reporting Tool no longer takes parameters from the command line specifying which properties file to use. The URT requires that a non encrypted properties file named 'usageReport.properties' is provided, however this file can optionally specify an additional encrypted properties file using the property encrypted.properties= This second, encrypted properties file can then contain some or all of the properties required by the application. If a property is defined in both files, the version from the encrypted properties file will be given priority over the non encrypted properties file. Usage example: The database user/password credentials may be considered sensitive, so a plaintext properties file containing just these two properties is created, and then encrypted using the encryption utility. The plaintext properties file can then be deleted, and the newly encrypted file distributed. The encyrpted properties file should then be named in the non-encrypted properties file using the 'encrypted.properties' property. At runtime, the URT retrieves the username and password from the encrypted file, and all remaining properties from the non encrypted file. If the non-encrypted file should happen to have a property defining the username or password, they will be ignored in this case. Purge utility Purge utility now supports encrypted properties files via a new optional property. (An encrypted properties file can be created using the encryption.jar as discussed below.) The purge utility requires that a non encrypted properties file named 'purgeDB.properties' is provided, however this file can optionally specify an additional encrypted properties file using the property encrypted.properties= This second, encrypted properties file can then contain some or all of the properties required by the application. If a property is defined in both files, the version from the encrypted properties file will be given priority over the non encrypted properties file. Usage example: The database user/password credentials may be considered sensitive, so a plaintext properties file containing just these two properties is created, and then encrypted using the encryption utility. The plaintext properties file can then be deleted, and the newly encrypted file distributed. The encyrpted properties file should then be named in the non-encrypted properties file using the 'encrypted.properties' property. At runtime, the purge tool retrieves the username and password from the encrypted file, and all remaining properties from the non encrypted file. If the non-encrypted file should happen to have a property defining the username or password, they will be ignored in this case. Initial purgable states optional property: purgable.states= Use format 'state1','state2','state3' e.g. 'S_InPTComplete','S_InPTFailed' If this property is omitted, the default value of 'S_InPTComplete','S_InPTFailed' will be used. Encryption utility A utility for creating encrypted properties files is newly available in \tools\encryption To run the encryption jar, place the file to be encrypted into the same directory as the jar, then invoke the jar from the command line, passing the name of the file to be encrypted as a parameter eg: 'java -jar encryption.jar file.properties' will generate an encrypted version of 'file.properties', named 'file.properties.en3' ====================================================================== List of fixes ====================================================================== Fixes included in FTM for Multiplatform v3.0.0.1 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 | +--------------------+------------------------------------------------+ | 27 March 2015 | Original publication date | +--------------------+------------------------------------------------+