============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2009 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.0 Messaging Services for SWIFTNet InterAct and FileAct PTF UK51523 for APAR PK97164 Date 2009-12-21 ============================================================================== ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Preparation E Activating F Cleaning up G Falling back to the previous PTF level H Re-migrating after a previous fallback I APAR details J Other changes 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. The installation of this PTF is done in two phases: 1. Preparation - During this phase your system can continue to process messages as usual. 2. Activation - During this phase 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 names of users, groups, files, and directories are the same as those used in "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: PK97164 MSIF WEBSPHERE BI FOR FN MSIF UPDATES PK90061 MSIF INITIAL PDMS ARE REJECTED AS DUPLICATE PM01881 MSIF RCV STATUS FAILS WITHOUT AN ERROR INDICATION PM01876 MSIF COUNTERPART REJECTS FILE TRANSFER REQUEST WITH REASON=FILETRANSFERONGOING APARs of WebSphere BI for FN V2.2: PK96759 EFA FILE TRANSFER PROBLEM DUE TO THE SAG TIMOUT SITUATION AND AUTOMATIC RECOVERY PROCESSING OF THE FILE TRANSFER PM00018 EFA WRONG ORDER OF EVENTS IN LIST COMMAND PK99493 EFA PD FLAG IN MWH WAS NOT SET DURING FILE TRANSFER WITH "DELIVFILEINERROR" PM01767 EFA SAG KEEP WAITING UNTIL TIMEOUT ONCE EFA COULD NOT CORRELATE THE DELIVERY NOTIFICATION TO ANY FILE TRANSFER Functional changes: - Automatic recovery for SendFile scenario added - Automatic recovery for FileReceived scenario changed - Product information fields added to ComIbmDni folder - More InterAct application header fields added to ComIbmDni folder - Received InterAct messages can be enriched with message domain information - Non-delivery warnings can be requested in FileAct scenarios - With SAG 6.3, the SAG restart signal is used to indicate which SAG was restarted - Behavior changed for received files in SnF mode from SWIFT that are flagged as PDM - MSIF can be configured so that SWIFT can distribute traffic to different SAGs. Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Concepts and Components - Messages and Codes - System Administration - Application Programming - Information Center The following modules have been changed: /dnf_03_01/admin/data/DNFEFAS.xml /dnf_03_01/admin/data/dnfczoct.ddl /dnf_03_01/admin/data/dnfczogt.ddl /dnf_03_01/admin/data/dnfczort.ddl /dnf_03_01/admin/data/dnfczoct.cli /dnf_03_01/admin/data/dnfczoch.lst /dnf_03_01/admin/data/dnfczocb.cli /dnf_03_01/admin/data/dnfczocy.cli /dnf_03_01/admin/data/dnfczocs.cli /dnf_03_01/admin/data/dnfczodt.cli /dnf_03_01/admin/data/dnfcocmr.cli /dnf_03_01/admin/data/dnfcocms.cli /dnf_03_01/admin/data/dnfcocno.cli /dnf_03_01/admin/data/dnfcocpo.cli /dnf_03_01/admin/data/dnfcocso.cli /dnf_03_01/admin/data/dnfcocsy.cli /dnf_03_01/run/jplugin/dnfco.jar /dnf_03_01/run/msg/dnfcomsg.cat /dnf_03_01/run/res/dnfcomsg.xml /dnf_03_01/run/data/dnfczoct.cli /dnf_03_01/run/data/dnfczocs.cli /dnf_03_01/run/data/dnfczocb.cli /dnf_03_01/run/data/dnfczocy.cli /dnf_03_01/run/data/dnfczoch.lst The following modules are new: /dnf_03_01/admin/data/dnfcocpi.cli /dnf_03_01/admin/data/dnfczo01.ddl /dnf_03_01/admin/data/dnfczo1g.ddl /dnf_03_01/admin/data/dnfczom4.ddl /dnf_03_01/admin/data/dnfczom5.ddl /dnf_03_01/admin/data/dnfczom6.ddl C. Planning ----------- Install this PTF together with the product code of WebSphere BI for FN V3.1 Base, PTF UK49806, and PTF UK51812 and the product code of WebSphere BI for FN V3.1 MSIF, and PTF UK49772 and either follow the instructions in "WebSphere BI for FN: Planning, Installation, and Customization" to do a new customization of your WBI-FN V3.1 environment or follow the instructions in "WebSphere Business Integration for Financial Networks for Multiplatforms: Migrating an instance within its current environment" to migrate your existing WebSphere BI for FN V2.2 Instance to Version 3.1. Prerequisite and supersede information: This PTF requires the following PTFs: - UK49772 for APAR PK91868 WEBSPHERE BI FOR FN MSIF UPDATES - UK51812 for APAR PK97165 WEBSPHERE BI FOR FN BASE UPDATES This PTF supersedes the following PTFs: - APAR PM01592 (SVB CHANGES FOR INPLACE MIGRATION) - APAR PK96255 (CIN STOPS ON RECEIVING A FILE WITH A BLANK IN FILEINFO TAG) - APAR PM03032 (ENCOUNTER DNFO1204E ERROR WHILE USING XPATH WITH BACHUS-NAUR VALUE IN TRANSFERINFO AND FILEINFO) Roles involved: The activities in this PTF involve the following roles: - Installer (root) D. Preparation -------------- D1. Installation ---------------- 1. Install this PTF using as described in the "Installing WebSphere BI for FN" section of "Planning, Installation, and Customization". D2. Steps on a customization system ----------------------------------- NOT APPLICABLE. D3. Generating configuration data migration scripts --------------------------------------------------- NOT APPLICABLE. D4. Customize updated BAR files when not using the BAP (dniczbap) to deploy them -------------------------------------------------------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Preparation * *------------------------------------------------------------------------------* E. Activating ------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Activating * *------------------------------------------------------------------------------* F. Cleaning up -------------- NOT APPLICABLE. G. Falling back to the previous PTF level ----------------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Fallback * *------------------------------------------------------------------------------* H. Re-migrating after a previous fallback ----------------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Re-migration * *------------------------------------------------------------------------------* I. APAR details --------------- Fixes for the following APARs are contained in this PTF: PK97164 MSIF WEBSPHERE BI FOR FN MSIF UPDATES See section J. PK90061 MSIF INITIAL PDMS ARE REJECTED AS DUPLICATE In store-and-forward (Snf) mode, if a delivery attempt from the SnF queue to the receiver fails, SWIFT resends the corresponding FileAct primitive with a PDMHistory indicator. Formerly, the MSIF Transfer Service rejected such a primitive as a duplicate. Now, if the MSIF Transfer Service already received the file, it sends a response to SWIFT to keep the SnF session open for further transfers; otherwise, it accepts the file and sets a possible duplicate indicator in the notification that it sends to the receiving application. PK90061 MSIF RCV STATUS FAILS WITHOUT AN ERROR INDICATION When a counterparty initiates a file transfer, the transfer is accepted, but the SNL indicates that the file transfer over the SIPN failed, the MSIF Transfer Service changes the transfer status of the corresponding scenario to 'Failed' and its transfer condition to 'finished'. Formerly, the MSIF Transfer Service did not issue an event. Now: - For a FileReceived scenario in real-time mode, it issues event DNFO1253E - For a FileReceived scenario in store-and-forward (SnF) mode, if auto-recovery is activated, it issues event DNFO1213I, and automatically issues another Sw:FetchFileRequest primitive. - For a FileAct receive scenario in SnF mode, if auto-recovery is not configured or is switched off, or if all auto-recovery attempts have failed it issues event DNFO1249E. PM01876 MSIF COUNTERPART REJECTS FILE TRANSFER REQUEST WITH REASON=FILETRANSFERONGOING Formerly, during a SendFile scenario, when a counterparty rejected the file transfer, the explanation contained in the SendFile response stated that an SAG rejected an ExchangeFileRequest primitive. This explanation was misleading, because it did not specify whether it was the sending or the receiving SAG that rejected the primitive. This explanation has been changed to make it clearer that the receiving SAG rejected the primitive. Fixes for the following WebSphere BI for FN V2.2 APARs are now added to WebSphere BI for FN V3.1: PK96759 EFA FILE TRANSFER PROBLEM DUE TO THE SAG TIMOUT SITUATION AND AUTOMATIC RECOVERY PROCESSING OF THE FILE TRANSFER Formerly, when automatic recovery was enabled and the SAG reported a timeout, the timeout was not treated as being recoverable; instead, a response was sent to the application and the transfer state was set to 'Error_Notif'. Now, when automatic recovery is enabled and the SAG reports a timeout, the timeout is treated as being recoverable and automatic recovery is started. PM00018 EFA WRONG ORDER OF EVENTS IN LIST COMMAND Formerly, the sort order of events in a list output was descending instead of ascending. This has been corrected. PK99493 EFA PD FLAG IN MWH WAS NOT SET DURING FILE TRANSFER WITH "DELIVFILEINERROR" When a FileAct primitive with a possible duplicate indicator is received but the corresponding file has not yet been successfully received, the file is accepted, a notification with code DNFO1219I is sent to the receiving application, and the transfer state of the scenario is set to "DelivFileInError". Formerly, the PDIndicator flag of the corresponding entry in the message warehouse was set to "N"; it was set to "Y" only if the file had previously been successfully received. Now, the PDIndicator flag of the corresponding entry in the message warehouse is set to "Y". PM01767 EFA SAG KEEPS WAITING UNTIL TIMEOUT ONCE EFA COULD NOT CORRELATE THE DELIVERY NOTIFICATION TO ANY FILE TRANSFER Formerly, when a delivery notification could not be correlated with a file transfer, EFA did not answer the delivery notification. When this happened, the SAG waited for an answer until its timeout was reached. This wasted the resource on SAG and kept the network busy. Now, EFA replies with an SAG Status message that indicates a server application error, and issues a corresponding error event. Fixes for the following APARs from superseded PTFs are also contained in this PTF: PK96255 MSIF CIN STOPS ON RECEIVING A FILE WITH A BLANK IN FILEINFO TAG Formerly, when WebSphere BI for FN MSIF received a FileAct primitive that contained a blank in its FileInfo field, error events DNFO1057E and DNFO9501E were raised. Processing of the file transfer could continue only after the corresponding request message was deleted from its queue. This required that the receiver contact the sender and to ask that FileInfo be specified as defined by SWIFT. This behaviour has been changed. Blank values are now ignored. PM03032 MSIF ENCOUNTER DNFO1204E ERROR WHILE USING XPATH WITH BACHUS-NAUR VALUE IN TRANSFERINFO AND FILEINFO In a FileReceived scenario, the FileInfo and TransferInfo fields of the SNL primitive are specified in Backus-Naur Form (BNF). The MSIF Transfer Service transforms these values from BNF to XML before comparing them to the XPath values specified for the FileInfo and TransferInfo file receive options. Formerly, due to a transformation error, some of the resulting XPath queries failed. This has been fixed. J. Other changes ---------------- New/changed functions: - Automatic recovery for SendFile scenario added: An SNL request primitive that is issued during a SendFile scenario (real-time or store-and-forward) is not answered by SWIFT until the end of the timeout period, or until the corresponding SNL response primitive indicates a recoverable error in its SwGbl:Status field. If SagComm option MaxAutoRecoverCount is greater than 0, then the MSIF Transfer Service attempts to automatically recover this scenario. For further information, see 'Concepts and Components'. - Automatic recovery for FileReceived scenario changed: States and conditions associated with the sending of delivery notifications and handling the responses to delivery notifications has been removed from the transfer life cycle and moved to the notification life cycle. - An application program can specify, in a request, information on up to three products. For further information, see 'Application Programming'. - An application program can specify in a request that SWIFT sends a non-delivery warning when the file was not received by the receiver after a certain period of time has elapsed, or a certain point of time is reached. For further information, see 'Application Programming'. - An application program can specify in a request more application header (AppHdr) elements than before. These are passed unaltered to the receiving application. The supported elements are described in 'Application Programming'. - Enrich received InterAct messages with the message standard domain: When MSIF creates an MsgReceived request or MsgReceived notification, it sets element MQRFH2.ComIbmDni.MsgStandardInfo.Domain to the value that is specified by attribute MsgStandardDomain of the corresponding message receive option set. - Use SAG restart signal to indicate which SAG was restarted: Formerly, when transferring files, the MSIF Transfer Service (DNF_O_FT) used SAG events to control certain aspects of its processing. Consequently, the MSIF Transfer Service had to subscribe to each of the SAGs that it used to conduct file transfers. If an SAG to which DNF_O_FT was subscribed was stopped and restarted, the subscription was cancelled and had to be re-established manually. Now, with SNL 6.3, the restart signal indicates which SAG was restarted and DNF_O_FT issues a Websphere BI for FN event message that indicates which SAG. was restarted - Formerly, each incoming SAG message in a MsgReceived, FileReceived, or RespondDownload scenario specified a certain combination of LocalDN, RemoteDN, Service, and RequestType (G4), and that G4 determined which SAG MP option set was used. Each SAG MP option set specifies: o One SNL ID. The MSIF Transfer Service checks whether this SNL ID is the same as the SNL ID of the SAG that provided the SAG message, and rejects the SAG message if it is not. Consequently, the MSIF Transfer Service is currently unable to process SAG messages with the same G4 that do not all come from the same SAG. o One message partner (MP). Consequently, the MSIF Transfer Service is currently unable to process SAG messages with the same G4 that do not all have the same MP. o One SignerDN, AuthoriserDN, and EncryptDN. Consequently, the MSIF Transfer Service is currently unable to process SAG messages with the same G4 that do not all use the same SignerDN, AuthoriserDN, and EncryptDN. Now, you can configure MSIF so that SWIFT can distribute traffic to different SAGs. To realize this, each G4 is no longer tied to a particular SNL ID or MP. Instead, the SAG MP option set that is associated with a specific G4 is able to vary depending on which SNL ID and message partner (MP) are specified in the SAG message. - Performance for SendMsg and MsgReceived scenarios has been improved. Problems fixed: - Formerly, a file transfer was rejected with SNL AcceptStatus 'Rejected' if each of the following is true: o a file transfer request was received with a PDE indication o the file was already received, and the state of that original transfer is 'Accepted', 'Responded', 'FileReceived' o the file receive option AllowDuplicates is set to True. SNL AcceptStatus 'Rejected' indicates to the sender that the file was not received, and the receiver does not want to receive the file. The ongoing original transfer however could still fail or succeed. Now, PDE flagged transfers in these states are always accepted, and the file is delivered to the local application with a possible duplicate indication DNFO1210I. - Formerly, if many files were downloaded and files were provided to be downloaded, and if several instances of the MSIF service were running a DB2 deadlock or timeout occurred. This no longer occurs. - Formerly, if a business message containing an XML declaration was sent to the SAG, a parsing error occurred. Now, such business messages are processed correctly. - The maximum size that a transferred file can have depends on the values of the SAG communication options CommType and LftChunking: o If CommType=MQHA and file chunking is not used (that is, the LftChunking option is not specified), the maximum size is 100 MB. o If CommType=MQHA and file chunking is used (that is, the LftChunking option is specified), or if CommType=LOCAL, the maximum size is 250 MB. Formerly, the default value of the MaxFileSize option of an SAG communication option set was 250 MB regardless of the values of CommType and LftChunking. When CommType was set to MQHA and LftChunking was not specified, this resulted in validation error DNFO3119E or DNFO3120E, because the 250 MB default value of MaxFileSize exceeded the 100 MB maximum. Now, the default value of MaxFileSize depends on the values of CommType and LftChunking: o If CommType=MQHA and LftChunking is not specified, the default is 100 MB. o If CommType=MQHA and LftChunking is specified, or if CommType=LOCAL, the default is 250 MB. - Formerly, when a counterparty downloaded a file, and the SNL indicated that the file transfer did not succeed (SNL indicates status "Failed"), or it is unsure whether the counterparty received the file (SNL indicates status "Unknown"), MSIF did not notify the application or issue an event. Now: o For SNL status "Failed", the MSIF Transfer Service issues event DNFO1400E o For SNL status "Unknown", the MSIF Transfer Service issues event DNFO1400E and a FileDownloaded notification that specifies completion code "PartialOk", indicating that a counterparty attempted to download a file but it is unsure whether the file was received. o For SNL status "Completed", the MSIF Transfer Service issues a FileDownloaded notification that specifies completion code "Ok", indicating that the counterparty successfully downloaded the file. - Formerly, the migration from WebSphere BI for FN Enhanced FileAct V2.2 including PTF UK38256 to WebSphere BI for FN Messaging Services for SWIFTNet InterAct and FileAct did not perform a required DB2 step. Now, it does. - Formerly, if a SendFile scenario was canceled, sometimes event DNFO1020E was issued, indicating that an invalid SAG/MQHA message was received. This has been corrected. - Formerly, the SNL error code Sw.Gbl.HSMContextLost was considered to be a recoverable error. Now, it is considered to be an unrecoverable error. - Formerly, if you issued the command "list -me 0" to list events, you received an empty list. Now you get following error message: DNFO0098E The value of '0' is invalid for the 'me' parameter; allowed minimum = '1'. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++