============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2014 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 Messaging Services for SWIFTNet InterAct and FileAct PTF UI13192 for APAR PM99720 Driver level: 4030 Date 2014-01-28 ============================================================================== ============================================================================== 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.ibm.com/software/integration/wbifn/library 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 cannot 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 customization directory. The directory /var/dni_03_01/cus 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: PM99720 MSIF INTRODUCING BATCHING FOR DETECTION OF TIMED OUT AND EXPIRED TRANSFERS PM99525 MSIF ADAPT MSIF TO IMPLEMENT VL/122013 WHICH DEFINED CHANGES IN DIGITAL SIGNATURES FOR INTERACT AND FILEACT MESSAGING PI06310 MSIF ENHANCED MSIF TRACING IN CONTEXT OF THE DNFO9501E AND DNFO9505E PI07557 MSIF CHANGE CLEANUP TO USE "WITH UR" TO AVOID SQL -913 (TIMEOUT) PI08269 MSIF TRY AUTORECOVERY WHEN UNKNOWN SAG STATUS EVENTS ARE RECEIVED PI09424 MSIF DNFO3463E DURING SENDMSG SCENARIO VIA INPUT CHANNEL Additional functional changes: - none Documentation updates: The following manuals have been changed: - Concepts and Components - System Administration - Application Programming Note: Documentation will be published on IBM library site two weeks after PTF availability. In case you need a draft before contact IBM support. The following modules have been changed: /dnfv311/run/jplugin/dnfco.jar C. Planning ----------- C1. Checks to be done >>BEFORE<< installing a new PTF ----------------------------------------------------- 1. Ensure that all previously prepared deployment instructions were carried out. 2. 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. 3. Until the migration for this PTF has been completely finished, ensure that no changes are made to the currently implemented CDD. 4. 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'. 5. 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 -user % -qo mor Each list command should result in 'No roles found that match specified criteria'. C2. Prerequisite and supersede information ------------------------------------------ This PTF requires the following PTFs: - UI12328 for APAR PM98191 (Base 3.1.1.16, AO FACILITY: ADD MESSAGE PRINTING SUPPORT) - UK97480 for APAR PM92781 (MSIF 3.1.1.9, PROCESSING OF BIG FILES IN MSIF LEADS TO TIMEOUTS FOR OTHER TRANSFERS) C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - 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. Customize BAR files when using mqsideploy or the Toolkit to deploy them ---------------------------------------------------------------------------- NOT APPLICABLE. D11. Redeploy updated BAR files ------------------------------- NOT APPLICABLE. 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 for Multiplatforms: 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: PM99720 MSIF INTRODUCING BATCHING FOR DETECTION OF TIMED OUT AND EXPIRED TRANSFERS The MSIF DNF_O_CMD service periodically looks for transfers that, for example, timed out or expired from a business perspective. For each of these transfers the DNF_O_CMD service sends an internal MQ message to the DNF_O_FTx service to further process the transfer. The maximum number of transfers that the DNF_O_CMD service handles in a single broker transaction can be configured with parameter BatchSize of configuration object DnfEfaParameters. Formerly, this parameter specified the maximum number of transfers that the DNF_O_CMD service could handle in a period of three minutes. If this number was too large, this could end up in abends because the execution group ran out of resources. Now, when the DNF_O_CMD service determines that there are more transfers than configured as BatchSize, it immediately continues a new batch in another broker transaction. Batching is now used in the following situations: - cleanup - timed-out transfers - transfers that expired from a business perspective - monitoring the replication status of SnF transfers - transfers affected by SnF system recovery - monitoring the file transfer window for an SAG - stopped transfers that can be restarted when the service gets started The default value for BatchSize in all situations is 100. PM99525 MSIF ADAPT MSIF TO IMPLEMENT VL/122013 WHICH DEFINED CHANGES IN DIGITAL SIGNATURES FOR INTERACT AND FILEACT MESSAGING Formerly the usage of digest references in SNL primitives sent to an SAG have been unclear for some InterAct and FileAct scenarios. With vendor letter VL/122013 SWIFT provided a clarification for all InterAct and FileAct scenarios. Now, MSIF fully applies to this vendor letter and for all supported InterAct and FileAct scenarios MSIF adds the required digest references to the SNL primitives sent to an SAG. PI06310 MSIF ENHANCED MSIF TRACING IN CONTEXT OF THE DNFO9501E AND DNFO9505E Formerly, when running MSIF flows with additional flow instances, it was possible that in rare cases an event DNFO9501E was issued that indicated an internal error. The root cause of this internal error was, that two MSIF threads tried to initialize the same internal object at the same time. For a correct object initialization it was required that at most one thread executes the object initialization. Now, this problem is fixed and the MSIF code guarantees that only one thread executes the object initialization. PI07557 MSIF CHANGE CLEANUP TO USE "WITH UR" TO AVOID SQL -913 (TIMEOUT) MSIF processes business transfers and in parallel can issue a cleanup process to delete finished transfers. The processing of business transfers and the cleanup process, both access the DB2 table DNFO_FSM_STATE as part of their transaction. Formerly, this could cause DB2 timeouts in the cleanup processing, especially when long file operations were executed and the DB2 table DNFO_FSM_STATE was locked longer than the timeout specified in DB2. The reason for this scenario was that the cleanup processing tried to get a list of transfers that are eligible for cleanup in a transactional way. Now, this behavior has been changed, and the cleanup processing gets the list of transfers that are eligible for cleanup with uncommitted read DB2 access. PI08269 MSIF TRY AUTORECOVERY WHEN UNKNOWN SAG STATUS EVENTS ARE RECEIVED MSIF supports automatic recovery of failed transfers by specifying the attribute MaxAutoRecoverCount of CO DnfEfaSagCommOptionSet. In case of errors reported by an SAG, MSIF analyzes the error codes Sag:System.xxx.xxx and initiates the recovery of a transfer only for selected codes. Formerly, in case an SAG reported an error code that is undocumented in the SWIFT error guide manual, then MSIF treated such an unknown error as non-recoverable. Now, this behavior has been changed and the failed transfer is automatically recovered. PI09424 MSIF DNFO3463E DURING SENDMSG SCENARIO VIA INPUT CHANNEL An application passes an MSIF SendMsg transfer to MSIF that is to be transferred to SWIFT using an input channel. In case a severe error like a DB2 error occurs before the transfer is initially sent out on the input channel, it is possible the transfer remains in the state Requested and condition inError. Formerly, when issuing a recover command on such a transfer the recovery failed with an exception as no message partner was assigned to the transfer. Now, the recovery succeeds and the transfer is sent out on the input channel successfully. F. Other changes ---------------- - Refuse Start command and Stop command for DNFSYSOU Formerly, it was possible to issue a start and a stop command for the DNFSYSOU. As these commands have no effects, and the behavior was inconsistent to the query command, the implementation was changed, and issuing a start or a stop command for the DNFSYSOU now results in the error message DNFO0096. G. Known issues --------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++