============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2016 All Rights Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ============================================================================== ============================================================================== README for IBM(R) WebSphere(R) Business Integration for Financial Networks for Multiplatforms V3.1.1 SUPPORT FOR SWIFTNET FIN AND FINANCIAL MESSAGE TRANSFER (3.1.1.13) PTF UI38427 for APAR PI53116 Driver level: 6240 Date 2016-06-30 ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Installation E APAR details F Other changes G Known issues A. About this document ---------------------- Only the online version of this readme document is current. Before you install the corresponding PTF, download the latest version from: http://www.ibm.com/software/integration/wbifn/support Download the latest version of the WebSphere BI for FN product documentation from: http://www-01.ibm.com/support/docview.wss?uid=swg27041133 The structure of WebSphere BI for FN readme documents is identical for all PTFs. Sections that are not applicable are left blank. If you install more than one PTF at a time, combine the readme documents by merging the contents of each section. During the installation phase of this PTF your system can not process messages. This readme document uses the following variables: The installation directory of WebSphere BI for FN. The directory /opt/IBM is used in examples. The name of the WebSphere BI for FN instance. The name INST1 is used in examples. The name of the organizational unit. Depending on the context, this might be SYSOU, DNFSYSOU, or the name of a business OU. The names of users, groups, files, and directories are the same as those used in WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PI53116 FIN TPS FINCOPY MESSAGES MAY BE SENT OUT WITH A WRONG FINCOPY1 DIGEST PI57756 FIN DNIE4497E AND FIN MESSAGE BACKED OUT WHEN FIELD 32A IS EMPTY AND MWH IS ENABLED PI58680 FIN ENSURE FMT HANDLES AND SENDS A MT671 TO SIPN Additional functional changes: - none Documentation updates: The following manuals have been changed: - none The following modules have been changed: /dnfv311/run/flows/DNF_PF_CMD.bar /dnfv311/run/flows/DNF_PF_IR.bar /dnfv311/run/flows/DNF_PF_IS.bar /dnfv311/run/flows/DNF_ILC_CMD.bar /dnfv311/run/flows/DNF_ILC_FIN.bar /dnfv311/run/flows/DNF_ILS_ACK.bar /dnfv311/run/flows/DNF_ILS_FIN.bar /dnfv311/run/jplugin/dnf.asp.acc.jar C. Planning ----------- C1. Checks to be done >>BEFORE<< installing a new PTF ----------------------------------------------------- 1. Check if you have any efixes (emergency fixes) applied in your WebSphere BI for FN installation. In case you have efixes installed after your previous WebSphere BI for FN PTF installation and migration contact your IBM support before installing and migrating this PTF. 2. Ensure that all previously prepared deployment instructions were carried out. 3. Ensure that all previous CDD changes were implemented using the CDP. To check this, log on to AIX on the customization system as a customizer (ucust1) and enter the following command on your customization system: /dniv311/admin/bin/dnicdpst -i -cdefs where The name of the WebSphere BI for FN instance The name of the customization definitions directory as specified in the CDP ini file, for example: /var/dni_03_01/cus/defs If the response to this command indicates that a customization operation is still pending and it was carried out in: - Customization mode (dnicdp), implement the pending operation before continuing. - Migration mode (dnicdpm): - Ensure that you have not yet shared the files contained in this or any other PTF as described in section D5 step 2. - Implement the pending operation before continuing. 4. Until the migration for this PTF has been completely finished, ensure that no changes are made to the currently implemented CDD. 5. Ensure that all configuration administration changes have been deployed. To check this, enter the following commands: dnicli -s DNI_SYSADM -ou SYSOU > list -ou % -qo amorz > list -cos % -qo amorz > list -ct % -qo amorz Each list command should result in 'No [OU/COS/CT] match search criteria'. 6. Ensure that all security administration changes have been approved. To check this, enter the following commands for each OU: dnicli -s DNI_SECADM -ou > list -ro % -qo mor [only for SYSOU] > list -rg % -qo mor [only for SYSOU] > list -user % -qo mor The list command should result in 'No roles/role groups/users found that match specified criteria'. C2. Prerequisite and supersede information ------------------------------------------ This PTF requires the following PTFs: - UI22234 for APAR PI24454 (CSN 3.1.1.12, SECURE WBIFN SEMAPHORES ON GROUP LEVEL TO AVOID ALTERATION BY OTHER APPLICATIONS) - UI29378 for APAR PI42892 (Base 3.1.1.25, SWIFT SR2015: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION) C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - WebSphere MB administrator (uwmba1) D. Installation --------------- D1. Stopping all sessions and services you use ---------------------------------------------- Stop all sessions and services, for example: - Stop all applications that send requests to WebSphere BI for FN. - Log out SIPN FIN LTs. - Close MSIF SnF input and output channels. - Release SWIFTNet SnF queues. - Stop the MSIF Message Transfer service. - Close all dnicli sessions. For further information, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration". D2. Stopping all application servers ------------------------------------ NOT APPLICABLE. D3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- Stop all WebSphere BI for FN message brokers. D4. Backing up your system -------------------------- We recommend to backup your AIX LPAR so that in case of migration issues you can revert to your previous system setup and continue to process workload. D5. Installing PTF by InstallAnywhere ------------------------------------- 1. Install this PTF using IAW based on the chapter "Installing WebSphere BI for FN" in WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization. Please be aware of the directory containing the installation data for this PTF has changed compared to the directory documented in this chapter, use the path Disk1/InstData/NoVM instead of Disk1/InstData/VM. 2. Ensure that the group ownership of the /dnfv311/admin directory and all of its subdirectories and files, is set to group dniadmin. To do this, enter the following command in AIX: chgrp -R dniadmin /dnfv311/admin 3. Set the group ownership of the runtime directories and its files to group dnilpp. To do this, enter the following command in AIX: chgrp -R dnilpp /dnfv311/run D6. Steps on a customization system ----------------------------------- NOT APPLICABLE. D7. Following the deployment instructions created in step D6 ------------------------------------------------------------ NOT APPLICABLE. D8. Additional activities ------------------------- NOT APPLICABLE. D9. Restarting all WebSphere BI for FN message brokers ------------------------------------------------------ Restart all WebSphere BI for FN message brokers. D10. Prepare BAR file deployment -------------------------------- D10.1. Backup the BTD repository - - - - - - - - - - - - - - - - 1. On the runtime system on which you use the BAP, log on to AIX as the WebSphere MB administrator (for example, uwmba1) and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a backup of your BTD repository. The location of this directory depends on the version of WebSphere Message Broker you are using: - for version 6.1: $DNI_BAP_PATH/bap/$DNI_QMGR_CFG - for version 7 or version 8: $DNI_BAP_PATH/bap/$DNI_I where the values of the environment variables DNI_BAP_PATH, DNI_QMGR_CFG and DNI_I correspond to the settings made in your dniprofile. For example, to create a backup of a Broker V7 or Broker V8 BTD repository by copying the corresponding directory, enter the following commands: mkdir -p $DNI_BAP_PATH/bap/UI38427/$DNI_I cp -R $DNI_BAP_PATH/bap/$DNI_I/ $DNI_BAP_PATH/bap/UI38427/$DNI_I D10.2. Customize BAR files when using mqsideploy or the Toolkit to deploy them - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Perform this step only if you use mqsideploy or the Toolkit to deploy broker archive (BAR) files manually. If you use the BAP (dniczbap) to automatically deploy the BAR files, skip this step and later deploy the BAR files directly as described in step D11.2.2. If you are unsure which method to use, use the same method that you used when you initially created your instance as described in WebSphere BI for FN Planning, Installation, and Customization. To customize the BAR files for manual deployment: 1. On the runtime system on which you use the BAP, log on to AIX as the WebSphere MB administrator (for example, uwmba1) and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a temporary directory to which you have read and write access and that has at least 35MB of free space. This is the directory in which dniczbap will store the customized BAR files. 3. The component to which the BAP deploys message flows depends on which version of WebSphere Message Broker is used: - For V6.1, the BAP deploys message flows to the configuration manager. - For V7 or V8, the BAP deploys message flows to the broker. Sometimes, the BAP cannot connect directly to this component, for example, when you use Broker V6.1 and the configuration manager is located on Windows. How you customize the BAR files depends on whether the BAP can connect to this component: a. If a connection is not possible, issue the following command to customize all BAR files: dniczbap -cmd prepare -all -dir where represents the output directory created in step 2. b. If a connection is possible, ensure that the configuration manager (if using Broker V6) and the brokers are running, and that no flows or execution groups are stopped. Issue the following command to cause the BAP to identify the BAR files that are to be updated: dniczbap -cmd prepare -update new -dir where represents the output directory created in step 2. Regardless of which method (a or b) you use, each of the customized BAR files in the output directory has a name of the form: ....bar where The name of your instance. The name of the broker to which the BAR file is to be deployed. The name of the execution group to which the BAR file is to be deployed. The name of the BAR file as provided by WebSphere BI for FN. 4. If you performed step 3.a, identify the BAR files that are listed in section "B. Summary of changes" and delete all other BAR files from the output directory. 5. Transfer, in binary mode, the customized BAR files in the output directory to the Toolkit or to the system on which you will later issue the mqsideploy command. 6. If you will use the Toolkit to deploy the message flows, import the customized BAR files. D11. Deploy updated BAR files ----------------------------- Deploying the WebSphere BI for FN BAR files that are delivered in this PTF updates the message flows that run in the broker. For a list of flows contained in each BAR file, refer to "Planning execution groups" section in WebSphere BI for FN Planning, Installation, and Customization. Each WebSphere BI for FN message flow has a suffix that represents its version. For example, the flow DNI_SYSADM_1141 has the version 1141. The version of a flow corresponds to the number of the PTF that most recently updated it. Refer to the header of this readme to determine the PTF number of this PTF. To deploy BAR files, you must have the access rights of the WebSphere MB administrator (uwmba1). D11.1. Deploy new message flows - - - - - - - - - - - - - - - - NOT APPLICABLE. D11.2. Update existing message flows - - - - - - - - - - - - - - - - - - If you already prepared the customized BAR files as described in step D10, proceed with step D11.2.1; otherwise, proceed with step D11.2.2 D11.2.1 Deploying the BAR files customized in step D10 - - - - - - - - - - - - - - - - - - - - - - - - - - - Note: If you have configured multiple broker servers you must deploy the BAR files to each broker server. Use the Toolkit or the mqsideploy command to manually deploy the BAR files. Remove the old versions of the message flows that have been updated by the BAR files you deployed. If you neglect to do this, two different versions of the flows will run simultaneously with unpredictable results. D11.2.2 Deploying BAR files when step D10 was not performed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Note: If you are using Broker V7 or V8 and you have configured multiple broker servers you must perform the following steps on each broker server. Use the BAP (dniczbap) to customize and automatically deploy the BAR files: 1. Ensure that: - The configuration manager is running (applies only for Broker V6.1) - The brokers are running - No flows or execution groups are stopped. Otherwise, old flow levels might not be deleted during the BAP update operation. 2. On the runtime systems where you use the BAP, log on to AIX as the WebSphere MB administrator (for example, uwmba1) and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 3. Ensure that you have at least 35 MB of free space in the current directory. 4. Issue the following command: dniczbap -cmd prepare -update new -deploy -broker The parameter -broker is only required if you use multiple broker servers. 5. Issue the following command to verify that all previous versions of the updated message flows were removed successfully: dniczbap -cmd check The result should be: DNIZ1314I: No problems detected. If you receive the message DNIZ1313E follow the instructions provided in the user response to correct the problem. D11.3. Activating WebSphere BI for FN accounting - - - - - - - - - - - - - - - - - - - - - - - - After all message flows have been deployed, activate the WebSphere BI for FN accounting: SIPN FIN and FMT FIN services: The following bar files are changed with this PTF and deployed: - DNF_ILS_FIN.bar - DNF_ILS_ACK.bar To activate the accounting, the WebSphere MB administrator, for example, UWMBA1, must enter the following commands: F ,CHANGEFLOWSTATS A=YES,E='',f='DNF_ILS_FIN_',C=ACTIVE,B=BASIC,O='XML' F ,CHANGEFLOWSTATS A=YES,E='',f='DNF_ILS_ACK_',C=ACTIVE,B=BASIC,O='XML' where: The name of the broker. The name of the execution group. The level of the message flow. To determine the levels of all deployed message flows, enter the following command: dniczbap -cmd list The output contains messages that indicate the level of each message flow, for example: DNIZ1466I Flow name: DNF_ILS_ACK_9213 If you deployed the above mentioned bar files to multiple execution groups, repeat the steps for each execution group in which the bar files are deployed. D12. Migrating configuration data --------------------------------- NOT APPLICABLE. D13. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ NOT APPLICABLE. D14. Restarting all sessions and services ----------------------------------------- Restart all of the sessions and services that you use. How to do this depends on which WebSphere BI for FN features you use. For example: - Log in SIPN FIN LTs. - Subscribe MSIF to SAGs to enable file transfer and session monitoring. - Start the MSIF Message Transfer service. - Acquire SWIFTNet SnF queues. - Open MSIF SnF input and output channels. - Start the applications that send requests to WebSphere BI for FN. For further information, see "Administering and operating components, sessions, and services" in WebSphere BI for FN System Administration. D15. Updating the Toolkit development environment ------------------------------------------------- NOT APPLICABLE. D16. Verifying your Installation -------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Installation * *------------------------------------------------------------------------------* E. APAR details --------------- Fixes for the following APARs are contained in this PTF: PI53116 FIN TPS FINCOPY MESSAGES MAY BE SENT OUT WITH A WRONG FINCOPY1 DIGEST Formerly, when a customer actively participates in a TPS FINCopy Service with a CLS member bank, the message must be signed with a FINCopy1 digest to authenticate the message against the CLS member bank. A change made with APAR PM87592 could cause, that a wrong CI could be taken to calculate this digest. This would then result in a digest verification error at the CLS member bank, which consequently rejected the message and didn't process it further. Now, the FINCopy1 digest to authenticate the message against the CLS member bank is calculated correctly. PI57756 FIN DNIE4497E AND FIN MESSAGE BACKED OUT WHEN FIELD 32A IS EMPTY AND AND MWH IS ENABLED Formerly, when message warehouse was enabled, and when a SWIFT ISN was processed in DNF_ILC_FIN, where the amount field was empty or contained invalid characters, the message was backed out to DNF_ERROR and the event DNIE4497E was issued. Now, this has been corrected. PI58680 FIN ENSURE FMT HANDLES AND SENDS A MT671 TO SIPN Formerly, MT671 messages were not handled by FMT FIN as described in the documentation. For example, see chapter "Sending and receiving FIN messages", section "Financial Message Transfer for FIN messages (FMT FIN)" in System Administration guide. Refer also to APAR PI58667. Now, MT671 messages are handled and sent to SIPN by FMT FIN. F. Other changes ---------------- NOT APPLICABLE. G. Known issues --------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++