IBM(R) Financial Transaction Manager for SWIFT Services (FTM SWIFT) for Multiplatforms Version 3.0.0.3 Readme Product/Component Release: 3.0.0 Update Name: Fix Pack 3 Fix ID: 3.0.0-FTM-SWS-MP-fp0003 Publication Date: December 30, 2016 =================================================================================================== Contents: 1. Download location 2. Prerequisites and co-requisites 3. What's new in FTM SWIFT 3.0.0.3 4. Installation information 4.1 Prior to installation 4.2 Installing 4.3 Uninstalling the update if necessary 5. Summary of changes 6. Copyright and trademark information 7. Document change history =================================================================================================== 1. Download location =================================================================================================== Download IBM(R) Financial Transaction Manager for SWIFT Services for Multiplatforms Version 3.0.0.3 from FixCentral at the following location: http://www.ibm.com/eserver/support/fixes/ Search for the Fix ID: 3.0.0-FTM-SWS-MP-fp0003 =================================================================================================== 2. Prerequisites and co-requisites =================================================================================================== Before installing FTM SWIFT 3.0.0.3, 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 SWIFT 3.0.0.3. - You need to have a file system with 500 MB 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 SWIFT product installed and have obtained special fixes, contact IBM 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. =================================================================================================== 3. What's new in FTM SWIFT 3.0.0.3 =================================================================================================== - Support for SWIFT Alliance Gateway (SAG) Version 7.0.50. - Fix list, see http://www.ibm.com/support/docview.wss?uid=swg21970097 =================================================================================================== 4. 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. ============================================================================== 4.1 Prior to installation ============================================================================== Before installing FTM SWIFT 3.0.0.3, perform the following steps: - Download the Fix Pack tar file. ============================================================================== 4.2 Installing ============================================================================== Note: This Fix Pack can be installed without having installed FTM SWIFT 3.0.0.0, FTM SWIFT 3.0.0.1 or FTM SWIFT 3.0.0.2 first. You can find further information about the installation steps in the "FTM for Multiplatforms Knowledge Center" on the following Web site: http://www.ibm.com/support/knowledgecenter/SSRH46_3.0.0_SWS ============================================================================ 4.2.1 Installing FTM SWIFT 3.0.0.3 - Create a new installation ============================================================================ Follow the instructions in the FTM for Multiplatforms Knowledge Center under 'Financial Transaction Manager for SWIFT Services > Planning, installation, and customization'. ============================================================================ 4.2.2 Installing FTM SWIFT 3.0.0.3 - Update an existing installation ============================================================================ Depending on how you share your product files there are two installation variants that differ in the downtime during which you cannot process workload. You can find more details regarding selected steps in the "FTM for Multiplatforms Knowledge Center" under 'Financial Transaction Manager for SWIFT Services > Appendixes > Maintenance for FTM SWIFT'. ========================================================================== 4.2.2.1 Update where installation system is separated from runtime and customization environment ========================================================================== Preparing: 1) Backup WebSphere Application Server profiles. 2) Ensure that no customization operation is pending. 3) Ensure that no configuration or security administration change is pending. 4) If your current installation is FTM SWIFT 3.0.0.0, use IBM Installation Manager to uninstall it. 5) Use IBM Installation Manager to install the FTM SWIFT 3.0.0.3. 6) Share your files from the installation system with the customization system. 7) Update customization definition data and create deployment instructions and vehicles. 8) Prepare the migration of configuration entities. 9) If you plan manual deployment of your BAR files, prepare them accordingly. Switching: 1) Stop all sessions and services you use. 2) Stop all FTM SWIFT enterprise applications. 3) Stop all FTM SWIFT related message flows. 4) Stop all FTM SWIFT message brokers. 5) Share your files from the installation system with the runtime system. 6) Back up your runtime database. 7) Open and follow the deployment instructions. 8) Verify the installed (updated) Java database routines. See section 'Financial Transaction Manager for SWIFT Services > Planning, installation, and customization > Verifying your customized installation > Verifying the installation of the Java database routines'. 9) If you deployed the SIPN FIN service, bind the FSM database package. 10) Restart all FTM SWIFT message brokers. 11) Deploy BAR files. 12) Restart all FTM SWIFT related message flows. 13) Migrate the configuration entities. 14) If you deployed the MER facility, deploy the updated enterprise application for MER. 15) If you deployed the RMA service, deploy the updated enterprise application for RMA. 16) Restart all FTM SWIFT enterprise applications. 17) Restart all sessions and services. 18) Update your IBM Integration Toolkit workstation if you utilized it for your own flow development. 19) If you use SAG Add-On, update the SAG Add-On. ========================================================================== 4.2.2.2 Update where installation, runtime and customization environment are on the same system ========================================================================== Preparing: 1) Backup WebSphere Application Server profiles. 2) Ensure that no customization operation is pending. 3) Ensure that no configuration or security administration change is pending. Switching: 1) Stop all sessions and services you use. 2) Stop all FTM SWIFT enterprise applications. 3) Stop all FTM SWIFT related message flows. 4) Stop all FTM SWIFT message brokers. 5) If your current installation is FTM SWIFT 3.0.0.0, use IBM Installation Manager to uninstall it. 6) Use IBM Installation Manager to install the FTM SWIFT 3.0.0.3. 7) Update customization definition data and create deployment instructions and vehicles. 8) Back up your runtime database. 9) Open and follow the deployment instructions. 10) Verify the installed (updated) Java database routines. See section 'Financial Transaction Manager for SWIFT Services > Planning, installation, and customization > Verifying your customized installation > Verifying the installation of the Java database routines'. 11) If you deployed the SIPN FIN service, bind the FSM database package. 12) Restart all FTM SWIFT message brokers. 13) If you plan manual deployment of your BAR files, prepare them accordingly. 14) Deploy BAR files. 15) Restart all FTM SWIFT related message flows. 16) Prepare the migration of configuration entities. 17) Migrate the configuration entities. 18) If you deployed the MER facility, deploy the updated enterprise application for MER. 19) If you deployed the RMA service, deploy the updated enterprise application for RMA. 20) Restart all FTM SWIFT enterprise applications. 21) Restart all sessions and services. 22) Update your IBM Integration Toolkit workstation if you utilized it for your own flow development. 23) If you use SAG Add-On, update the SAG Add-On. ============================================================================== 4.3 Uninstalling the update if necessary ============================================================================== 1) Stop all sessions and services you use. 2) Stop all FTM SWIFT application servers. 3) Stop all FTM SWIFT related message flows. 4) Stop all FTM SWIFT message brokers. 5) Use IBM Installation Manager to fall back to your previous level. 6) Share your files from the installation system with the customization and runtime system, if applicable. 7) Recover the customization system. 8) Restore your runtime database. 9) Restart all FTM SWIFT message brokers. 10) Deploy previous BAR files: dniczbap -cmd prepare -update old -deploy [-broker broker_name] 11) Restart all FTM SWIFT related message flows. 12) Restore the WebSphere Application Server profile backups. 13) Restart all FTM SWIFT application servers. 14) Restart all sessions and services you use. 15) Restore your IBM Integration Toolkit workstation if you utilized it for your own flow development: 15.1 Restore your Toolkit dropins directory. 15.2 Restore your Toolkit workspace. 15.3 Deploy your restored message flows. 16) If you updated SAG Add-On, roll back the SAG Add-On. =================================================================================================== 5. Summary of changes =================================================================================================== The fix packs include following changes: ================================================================================ 3.0.0.3 ================================================================================ - Resource classes DB and DBSP * Following tables are altered: DNI_COS, DNI_COS_CT_CON_REL, DNI_CT, DNI_CT_ATTR, DNI_OU, DNI_CT_ATTR_VALUE, DNI_ROLE, DNI_RO_CT_ATTR_REL, DNI_ROLEGROUP, DNI_RG_ROLE_REL, DNI_USER, DNI_USR_ROLE_REL, DNI_USR_RG_REL * Following audit views are altered: DNI_VW_COS, DNI_VW_CT, DNI_VW_OU_ou, DNI_VW_RG, DNI_VW_ROLE, DNI_VW_URG_ou, DNI_VW_URO_ou * Following table is updated: DNI_DBHISTORY * The Java stored procedures are updated - Following bar-files are changed: - SIPN FIN service: > DNF_ILC_CMD.bar, DNF_ILC_FIN.bar, DNF_ILS_ACK.bar, DNF_ILS_FIN.bar, DNF_PF_CMD.bar, DNF_PF_IR.bar, DNF_PF_IS.bar - Following configuration entities are changed: * MSIF service: > Attributes added to CT DnfEfaBouParameters: add -ct DnfEfaBouParameters -attr SnFSessionCloseMode > Attributes added to CO DnfEfaBouParameters of type DnfEfaBouParameters: add -ct DnfEfaBouParameters -ou DNIvOU -co DnfEfaBouParameters -attr SnFSessionCloseMode -val Auto - Following Toolkit resources are changed: * Message set: dni.schemas.swiftFin2016.zip ================================================================================ 3.0.0.2 ================================================================================ - Following bar-files are changed: - MER facility: > DNQ_K_FIN1.bar, DNQ_K_FIN2.bar, DNQ_K_MX1.bar, DNQ_K_UAR.bar - Following configuration entities are changed: * MER facility: > Attributes added to CT DnqERMessageRightsDNIMX: add -ct DnqERMessageRightsDNIMX -attr auth.012.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.013.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.014.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.015.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.018.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.019.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.020.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.021.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.022.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.023.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.024.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.025.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.026.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.027.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.028.001 -type P add -ct DnqERMessageRightsDNIMX -attr semt.041.001 -type P add -ct DnqERMessageRightsDNIMX -attr semt.042.001 -type P > Attributes added to CO ALL of type DnqERMessageRightsDNIMX: add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.012.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.013.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.014.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.015.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.018.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.019.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.020.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.021.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.022.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.023.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.024.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.025.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.026.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.027.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.028.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr semt.041.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr semt.042.001 * MSIF service: > Attributes added to CT DnfEfaMsgReceiveOptionSet: add -ct DnfEfaMsgReceiveOptionSet -attr PassSnFOutputInfo add -ct DnfEfaMsgReceiveOptionSet -attr AllowDuplicateTypes > Attributes added to CT DnfEfaFileReceiveOptionSet: add -ct DnfEfaFileReceiveOptionSet -attr PassSnFOutputInfo - Following Toolkit resources are changed: * Nodes: DniStandardsProcessing * Message set: dni.schemas.comibmdni.zip, dni.schemas.swiftFin2014.zip dni.schemas.swiftFin2015.zip, dni.schemas.swiftFin2016.zip * Message set projects: DNI_DniMsgSetMqrfh2 contained in dni.project.interchange.zip * MER facility: Sample message flows: DNQ_K_FIN1_4, DNQ_K_FIN2, DNQ_K_MX1_OUT, DNQ_K_UA contained in projects: DNI_DnqErCommon.zip, DNI_DnqErSwiftNetFin.zip DNI_DnqErSwiftNetMX.zip, dnq.project.interchange.zip ================================================================================ 3.0.0.1 ================================================================================ - Following bar-files are changed: All ================================================================================ 6. Copyright and trademark information ================================================================================ http://www.ibm.com/legal/copytrade.shtml ================================================================================ 7. Document change history ================================================================================ +--------------------+------------------------------------------------+ | Date | Description of change | +--------------------+------------------------------------------------+ | December 30, 2016 | Original publication date | +--------------------+------------------------------------------------+