IBM(R) Financial Transaction Manager for SWIFT Services (FTM SWIFT) for Multiplatforms Version 3.0.0.4 Readme Product/Component Release: 3.0.0 Update Name: Fix Pack 4 Fix ID: 3.0.0-FTM-SWS-MP-fp0004 Publication Date: August 31, 2017 ================================================================================ Contents: 1. Download location 2. Prerequisites and co-requisites 3. What's new in FTM SWIFT 3.0.0.4 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 Financial Transaction Manager for SWIFT Services for Multiplatforms Version 3.0.0.4 from FixCentral at the following location: http://www.ibm.com/eserver/support/fixes/ Search for the Fix ID: 3.0.0-FTM-SWS-MP-fp0004 ================================================================================ 2. Prerequisites and co-requisites ================================================================================ Before installing FTM SWIFT 3.0.0.4, 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.4. - 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.4 ================================================================================ - Reference Data Utility (RDU) supports BICDirectory2018 The Reference Data Utility can now load data from a SWIFT BICDirectory2018. Further information about the Reference Data Utility can be found in the FTM for Multiplatforms Knowledge Center, topic: 'Financial Transaction Manager for SWIFT Services > System administration > Command Reference > Reference Data Utility commands' - SWIFT Standards Release 2017 (SR2017) changes for FIN and MX added The FTM SWIFT activation date and time for SR2017 changes is 18 November 2017, 16:10:00 GMT. The SR2017 message definition sets are automatically activated at this date. However, you can install this Fix Pack before this date and time and continue to process messages according to the SR2016 message definition sets. 'Testing a new message definition set' is described in "FTM for Multiplatforms Knowledge Center". - SWIFT Standards Release 2014 (SR2014) and older versions removed Three versions of message definition sets will be provided at maximum for each message domain. These are the current one and if existent two back-level versions. If you are using outdated message definition sets with the Message Standards Service (Node or Java API) you must change your application to a current message definition set. - 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.4, perform the following steps: - Download the Fix Pack tar file. ============================================================================== 4.2 Installing ============================================================================== Note: This Fix Pack can be installed without having an existing installation. 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.4 - 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.4 - 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) Verify if your current installation is FTM SWIFT 3.0.0.3. If not, install this fix pack first. 2) Identify outdated messages and templates using the MER message administration utility. Perform a migration action on the detected templates. 3) Backup WebSphere Application Server profiles. 4) Ensure that no customization operation is pending. 5) Ensure that no configuration or security administration change is pending. 6) Use IBM Installation Manager to install the FTM SWIFT 3.0.0.4. 7) Share your files from the installation system with the customization system. 8) Update customization definition data and create deployment instructions and vehicles. 9) Prepare the migration of configuration entities. 10) 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) If you deployed the SIPN FIN service, bind the FSM database package. 8) Restart all FTM SWIFT message brokers. 9) Deploy BAR files 10) Restart all FTM SWIFT related message flows. 11) Migrate the configuration entities. 12) If you deployed the MER facility, deploy the updated enterprise application for MER. 13) Restart all FTM SWIFT enterprise applications. 14) Restart all sessions and services. 15) Update your IBM Integration Toolkit workstation if you utilized it for your own flow development. ========================================================================== 4.2.2.2 Update where installation, runtime and customization environment are on the same system ========================================================================== Preparing: 1) Verify if your current installation is FTM SWIFT 3.0.0.3. If not, install this fix pack first. 2) Identify outdated messages and templates using the MER message administration utility. Perform a migration action on the detected templates. 3) Backup WebSphere Application Server profiles. 4) Ensure that no customization operation is pending. 5) 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) Use IBM Installation Manager to install the FTM SWIFT 3.0.0.4. 6) Update customization definition data and create deployment instructions and vehicles. 7) Back up your runtime database. 8) If you deployed the SIPN FIN service, bind the FSM database package. 9) Restart all FTM SWIFT message brokers. 10) If you plan manual deployment of your BAR files, prepare them accordingly. 11) Deploy BAR files. 12) Restart all FTM SWIFT related message flows. 13) Prepare the migration of configuration entities. 14) Migrate the configuration entities. 15) If you deployed the MER facility, deploy the updated enterprise application for MER. 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. ============================================================================== 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. ================================================================================ 5. Summary of changes ================================================================================ The fix packs include following changes: ================================================================================ 3.0.0.4 ================================================================================ - Following configuration entities are changed: * MER facility: > Attributes added to CT DnqERMessageRightsDNIMX: add -ct DnqERMessageRightsDNIMX -attr auth.034.001 -type P add -ct DnqERMessageRightsDNIMX -attr auth.038.001 -type P add -ct DnqERMessageRightsDNIMX -attr caam.001.001 -type P add -ct DnqERMessageRightsDNIMX -attr caam.002.001 -type P add -ct DnqERMessageRightsDNIMX -attr caam.003.001 -type P add -ct DnqERMessageRightsDNIMX -attr caam.004.001 -type P add -ct DnqERMessageRightsDNIMX -attr caam.005.001 -type P add -ct DnqERMessageRightsDNIMX -attr caam.006.001 -type P add -ct DnqERMessageRightsDNIMX -attr caam.007.001 -type P add -ct DnqERMessageRightsDNIMX -attr caam.008.001 -type P add -ct DnqERMessageRightsDNIMX -attr caam.009.001 -type P add -ct DnqERMessageRightsDNIMX -attr caam.010.001 -type P add -ct DnqERMessageRightsDNIMX -attr caam.011.001 -type P add -ct DnqERMessageRightsDNIMX -attr caam.012.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.001.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.002.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.003.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.004.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.005.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.006.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.007.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.008.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.009.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.010.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.011.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.012.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.013.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.014.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.015.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.016.001 -type P add -ct DnqERMessageRightsDNIMX -attr catp.017.001 -type P add -ct DnqERMessageRightsDNIMX -attr pacs.028.001 -type P add -ct DnqERMessageRightsDNIMX -attr pain.017.001 -type P add -ct DnqERMessageRightsDNIMX -attr pain.018.001 -type P add -ct DnqERMessageRightsDNIMX -attr reda.056.001 -type P add -ct DnqERMessageRightsDNIMX -attr reda.057.001 -type P add -ct DnqERMessageRightsDNIMX -attr reda.058.001 -type P add -ct DnqERMessageRightsDNIMX -attr reda.059.001 -type P add -ct DnqERMessageRightsDNIMX -attr supl.030.001 -type P add -ct DnqERMessageRightsDNIMX -attr supl.031.001 -type P > Attributes removed from CT DnqERMessageRightsDNIMX: rem -ct DnqERMessageRightsDNIMX -attr fxtr.007.001 rem -ct DnqERMessageRightsDNIMX -attr fxtr.008.001 rem -ct DnqERMessageRightsDNIMX -attr fxtr.012.001 rem -ct DnqERMessageRightsDNIMX -attr fxtr.013.001 rem -ct DnqERMessageRightsDNIMX -attr fxtr.014.001 rem -ct DnqERMessageRightsDNIMX -attr fxtr.015.001 rem -ct DnqERMessageRightsDNIMX -attr fxtr.016.001 rem -ct DnqERMessageRightsDNIMX -attr fxtr.017.001 rem -ct DnqERMessageRightsDNIMX -attr fxtr.030.001 > Attributes added to CO ALL of type DnqERMessageRightsDNIMX: add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.034.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr auth.038.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caam.001.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caam.002.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caam.003.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caam.004.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caam.005.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caam.006.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caam.007.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caam.008.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caam.009.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caam.010.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caam.011.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caam.012.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.001.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.002.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.003.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.004.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.005.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.006.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.007.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.008.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.009.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.010.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.011.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.012.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.013.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.014.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.015.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.016.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr catp.017.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pacs.028.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pain.017.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pain.018.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr reda.056.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr reda.057.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr reda.058.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr reda.059.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr supl.030.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr supl.031.001 > Attributes removed from CO ALL of type DnqERMessageRightsDNIMX: rem -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr fxtr.007.001 rem -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr fxtr.008.001 rem -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr fxtr.012.001 rem -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr fxtr.013.001 rem -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr fxtr.014.001 rem -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr fxtr.015.001 rem -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr fxtr.016.001 rem -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr fxtr.017.001 rem -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr fxtr.030.001 > All attributes removed from CO ALL of type DnqERMessageRightsDNITRANSREP: (CO ALL removed) rem -ct DnqERMessageRightsDNITRANSREP -ou DNIvOU -co ALL -attr DNIUNPARSABLE rem -ct DnqERMessageRightsDNITRANSREP -ou DNIvOU -co ALL -attr DNIEMPTY rem -ct DnqERMessageRightsDNITRANSREP -ou DNIvOU -co ALL -attr semt.011.001 rem -ct DnqERMessageRightsDNITRANSREP -ou DNIvOU -co ALL -attr semt.010.001 rem -ct DnqERMessageRightsDNITRANSREP -ou DNIvOU -co ALL -attr semt.009.001 rem -ct DnqERMessageRightsDNITRANSREP -ou DNIvOU -co ALL -attr semt.008.001 rem -ct DnqERMessageRightsDNITRANSREP -ou DNIvOU -co ALL -attr auth.011.001 rem -ct DnqERMessageRightsDNITRANSREP -ou DNIvOU -co ALL -attr auth.010.001 rem -ct DnqERMessageRightsDNITRANSREP -ou DNIvOU -co ALL -attr auth.009.001 rem -ct DnqERMessageRightsDNITRANSREP -ou DNIvOU -co ALL -attr auth.008.001 > Attributes removed from CT DnqERMessageRightsDNITRANSREP: rem -ct DnqERMessageRightsDNITRANSREP -attr DNIUNPARSABLE rem -ct DnqERMessageRightsDNITRANSREP -attr DNIEMPTY rem -ct DnqERMessageRightsDNITRANSREP -attr semt.011.001 rem -ct DnqERMessageRightsDNITRANSREP -attr semt.010.001 rem -ct DnqERMessageRightsDNITRANSREP -attr semt.009.001 rem -ct DnqERMessageRightsDNITRANSREP -attr semt.008.001 rem -ct DnqERMessageRightsDNITRANSREP -attr auth.011.001 rem -ct DnqERMessageRightsDNITRANSREP -attr auth.010.001 rem -ct DnqERMessageRightsDNITRANSREP -attr auth.009.001 rem -ct DnqERMessageRightsDNITRANSREP -attr auth.008.001 > CT removed: del -ct DnqERMessageRightsDNITRANSREP > CO ALL removed from following MX roles: rem -ro DnqERMsgEditorMX1Create -ct DnqERMessageRightsDNITRANSREP -co ALL -attr * rem -ro DnqERMsgEditor -ct DnqERMessageRightsDNITRANSREP -co ALL -attr * rem -ro DnqERMsgEditorMX1AuthorizeSecond -ct DnqERMessageRightsDNITRANSREP -co ALL -attr * rem -ro DnqERMsgEditorMX1AuthorizeFirst -ct DnqERMessageRightsDNITRANSREP -co ALL -attr * rem -ro DnqERMsgEditorMX1Edit -ct DnqERMessageRightsDNITRANSREP -co ALL -attr * - Following bar-files are changed: * FMT FIN service: > DNF_PF_CMD.bar, DNF_PF_IR.bar, DNF_PF_IS.bar - Following WAS applications are changed: * MER facility: dnq.app.main.ear - Following Toolkit resources are changed: * Message set: dni.schemas.comibmdni.zip, dni.schemas.swiftFin2015.zip dni.schemas.swiftFin2016.zip, dni.schemas.swiftFin2017.zip - Message updates: * Messages new: DNIY5013E, DNIY5103E, DNIY6027E, DNIY6028E * Messages changed: DNIY0113E, DNIY0115E, DNIY0116E, DNIY6025E ================================================================================ 6. Copyright and trademark information ================================================================================ http://www.ibm.com/legal/copytrade.shtml ================================================================================ 7. Document change history ================================================================================ +-----------------------+------------------------------------------------------+ | Date | Description of change | +-----------------------+------------------------------------------------------+ | August 31, 2017 | Original publication date | +-----------------------+------------------------------------------------------+