IBM(R) Financial Transaction Manager for SWIFT Services (FTM SWIFT) for Multiplatforms Version 3.0.0.5 Readme Product/Component Release: 3.0.0 Update Name: Fix Pack 5 Fix ID: 3.0.0-FTM-SWS-MP-fp0005 Publication Date: October 31, 2017 Before starting with the installation process, view the online version of this readme file to check if information has changed since the readme file was downloaded. ================================================================================ Contents: 1. Download location 2. Prerequisites and co-requisites 3. What's new in FTM SWIFT 3.0.0.5 4. Installation information 4.1 Installing 4.2 Uninstalling the update if necessary 5. Summary of changes 6. Copyright and trademark information 7. Document change history ================================================================================ 1. Download location ================================================================================ You can download IBM Financial Transaction Manager for SWIFT Services for Multiplatforms Version 3.0.0.5 from FixCentral at the following location: http://www.ibm.com/eserver/support/fixes/ Search for the Fix ID: 3.0.0-FTM-SWS-MP-fp0005 ================================================================================ 2. Prerequisites and co-requisites ================================================================================ Before installing FTM SWIFT 3.0.0.5, 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 on the Financial Transaction Manager product support Web site: https://www.ibm.com/support/home - 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. - If you already have an FTM SWIFT product installed, you need to have at least Fix Pack 3.0.0.3 installed and executed the post-installation steps. ================================================================================ 3. What's new in FTM SWIFT 3.0.0.5 ================================================================================ - Support for SWIFTNet 7.2 added FIN message transfer services and MSIF transfer services can now use SWIFT Alliance Gateway (SAG) 7.2 and SWIFTNet Link (SNL) 7.2 to send and receive messages or files. - SAG Add-On for SWIFT Alliance Gateway (SAG) Version 7.2 provided An SAG Add-On based on a 64-bit architecture to operate, configure, or monitor an SAG 7.2 is provided. You need to install SAG 7.2 to activate SWIFTNet 7.2 - and if SAG Add-On is used, you need to install the SAG Add-On 7.2 repository too. See section 'Financial Transaction Manager for SWIFT Services > Planning, installation, and customization > Preparing to create an instance > Installing the SAG Add-On' - Fix list, see http://www.ibm.com/support/docview.wss?uid=swg21970097 ================================================================================ 4. Installation information ================================================================================ ============================================================================== 4.1 Installing ============================================================================== You can find 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.1.1 Installing FTM SWIFT 3.0.0.5 - Create a new installation ============================================================================ 1. Install Fix Pack 3.0.0.5. 2. Follow the instructions in the FTM for Multiplatforms Knowledge Center under 'Financial Transaction Manager for SWIFT Services > Planning, installation, and customization'. ============================================================================ 4.1.2 Installing FTM SWIFT 3.0.0.5 - 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.1.2.1 Update where installation system is separated from runtime and customization environment ========================================================================== Preparing: If your FTM SWIFT Fix Pack level is 3.0.0.4 you can skip step 1 and 2: 1) Identify outdated messages and templates using the MER message administration utility. Perform a migration action on the detected templates. 2) Back up WebSphere Application Server profiles. 3) Ensure that no customization operation is pending. 4) Ensure that no configuration or security administration change is pending. 5) Use IBM Installation Manager to install the FTM SWIFT 3.0.0.5. 6) Share the files in the /admin directory with your customization system. 7) Update customization definition data and create deployment instructions and vehicles. 8) If you plan manual deployment of your BAR files, prepare them accordingly. If your FTM SWIFT Fix Pack level is 3.0.0.4 you can skip step 9: 9) Prepare the migration of configuration entities. 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 the files in the /run directory with your runtime system. 6) Back up your runtime database. 7) Open and follow the deployment instructions. 8) If you deployed the SIPN FIN service, bind the FSM database package. 9) Restart all FTM SWIFT message brokers. 10) Deploy BAR files 11) Restart all FTM SWIFT related message flows. If your FTM SWIFT Fix Pack level is 3.0.0.4 you can skip step 12 and 13: 12) Migrate the configuration entities. 13) If you deployed the MER facility, deploy the updated enterprise application for MER. 14) Restart all FTM SWIFT enterprise applications. 15) Restart all sessions and services. If your FTM SWIFT Fix Pack level is 3.0.0.4 you can skip step 16: 16) Update your IBM Integration Toolkit workstation if you utilized it for your own flow development. ========================================================================== 4.1.2.2 Update where installation, runtime and customization environment are on the same system ========================================================================== Preparing: 1) Ensure that no customization operation is pending. 2) Ensure that no configuration or security administration change is pending. If your FTM SWIFT Fix Pack level is 3.0.0.4 you can skip step 3 and 4: 3) Identify outdated messages and templates using the MER message administration utility. Perform a migration action on the detected templates. 4) Backup WebSphere Application Server profiles. 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.5. 6) Update customization definition data and create deployment instructions and vehicles. 7) Back up your runtime database. 8) Open and follow the deployment instructions. 9) If you deployed the SIPN FIN service, bind the FSM database package. 10) Restart all FTM SWIFT message brokers. 11) If you plan manual deployment of your BAR files, prepare them accordingly. 12) Deploy BAR files. 13) Restart all FTM SWIFT related message flows. If your FTM SWIFT Fix Pack level is 3.0.0.4 you can skip step 14, 15, and 16: 14) Prepare the migration of configuration entities. 15) Migrate the configuration entities. 16) If you deployed the MER facility, deploy the updated enterprise application for MER. 17) Restart all FTM SWIFT enterprise applications. 18) Restart all sessions and services. If your FTM SWIFT Fix Pack level is 3.0.0.4 you can skip step 19: 19) 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 roll 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. ....If your FTM SWIFT Fix Pack level is 3.0.0.4 you can skip step 12: 12) Restore the WebSphere Application Server profile backups. 13) Restart all FTM SWIFT application servers. 14) Restart all sessions and services you use. If your FTM SWIFT Fix Pack level is 3.0.0.4 you can skip step 15: 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.5 ================================================================================ - Resource class DB * Following table is altered: DNF_ASP * Following table is updated: DNI_DBHISTORY - Following bar-files are changed: * SAG configuration and operation services: > DNF_SAGCFG.bar, DNF_SAGOP.bar - Message updates: * Messages new: DNFO3612E ================================================================================ 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 | +-----------------------+------------------------------------------------------+ | October 31, 2017 | Original publication date | +-----------------------+------------------------------------------------------+