============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2011 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 UK68724 for APAR PM45244 = Date 2011-09-17 = ============================================================================== ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Preparation E Activating F APAR details G Other changes A. About this document ---------------------- If you install this PTF as part of the migration from WebSphere BI for FN Version 3.1.0 to Version 3.1.1 then do not follow the steps in this readme, but those described in the Migration Information 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 customization directory. The directory /var/dniv311/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 Multiplatform 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: PM45244 MSIF HANDLING OF DELIVERY NOTIFICATIONS RECEIVED OUT OF SEQUENCE Please note: This is the sysrouted WebSphere BI for FN V3.1.1 APAR of the original WebSphere BI for FN V3.1.0 APAR PM33997. PM44901 MSIF INTERACT: APPHDR HANDLING WRONG, WHEN APPHDR CONTAINS BLANKS IN THE NAMESPACE DECLARATION PM45279 MSIF INTERACT: APPHDR HANDLING MAY FAIL, WHEN APPHDR CONTAINS TWO NAMESPACE DECLARATIONS Please note: This is the sysrouted WebSphere BI for FN V3.1.1 APAR of the original WebSphere BI for FN V3.1.0 APAR PM45066. PM44902 MSIF DNFO1027E WHEN A MSIF SNDFILE REQUEST EXPIRES PM38196 MSIF DUMP OF MSIF EG WHEN CLEANUP -ME 5000 IS PERFORMED PM42446 MSIF DNFO1034E DURING THE MSIF SEND FILE REASON LIST PARAMETERS LONGER THAN 1000 BYTES Functional changes: - Now, MSIF processes a SWIFTNet notification as an individual scenario with an individual MSIF reference 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: /dnfv311/run/jplugin/dnfco.jar /dnfv311/run/msg/dnfcomsg.cat /dnfv311/run/res/dnfcomsg.xml C. Planning ----------- Before installing a new PTF, ensure that: - All previously prepared deployment instructions have been carried out. - All previous CDD changes have been implemented using the CDP. - 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'. - 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'. Customization changes other than those described in a PTF readme document are not allowed during PTF installation. Prerequisite and supersede information: This PTF requires the following PTFs: - UK69904 for APAR PM38484 (SWIFT SR2011: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION.) - UK68443 for APAR PM40419 (UPDATES FOR V311 WEBSPHERE BI FOR FN MSIF) Roles involved: The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - WebSphere MB administrator (uwmba1) D. Preparation -------------- D1. Installation ---------------- 1. 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. - Stop the Enhanced InterAct service. - Close all dnicli sessions. 2. Stop all WebSphere BI for FN message brokers. 3. 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, SH12-6942. 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. 4. Share the files in the following directories with your runtime systems: /dnfv311/run/jplugin /dnfv311/run/msg /dnfv311/run/res These files are already needed during the preparation phase and do not influence normal operation. 5. Set the group ownership of these directories and files to group dnilpp. To do this, enter the following command in AIX shell: chgrp -R dnilpp /dnfv311/run 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 to deploy them --------------------------------------------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Preparation * *------------------------------------------------------------------------------* E. Activating ------------- E1. 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. - Stop the Enhanced InterAct service. - Close all dnicli sessions. For further information, see "Administering and operating components, sessons, and services" in "WebSphere BI for FN for Multiplatforms: System Administration", SH12-6943. E2. Stopping all application servers ------------------------------------ NOT APPLICABLE. E3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- Stop all WebSphere BI for FN message brokers. E4. Sharing the runtime directory structure ------------------------------------------- 1. Share the files in the /dnfv311/run directory with the runtime systems. 2. Set the group ownership of these directories and files to group dnilpp. To do this, enter the following command in AIX: chgrp -R dnilpp /dnfv311/run E5. Backing up configuration and security data in image copies -------------------------------------------------------------- NOT APPLICABLE. E6. Following the deployment instructions created in step D2.4 -------------------------------------------------------------- NOT APPLICABLE E7. Additional activities ------------------------- E7.1. DB2 related activities - - - - - - - - - - - - - - NOT APPLICABLE. E7.2. WebSphere MB related activities - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. E8. Restarting all WebSphere BI for FN message brokers ------------------------------------------------------ Restart all WebSphere BI for FN message brokers. E9. Redeploy updated BAR files ------------------------------ NOT APPLICABLE. E10. Migrating configuration data --------------------------------- NOT APPLICABLE. E11. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ NOT APPLICABLE. E12. Restarting all sessions and services ----------------------------------------- 1. 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. - Start the Enhanced InterAct 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", SH12-6943. 2. A subscription to receive FileAct events is needed for each SAG that the MSIF Transfer Service uses to conduct file transfers. Because one of the previous steps erased all subscriptions from the WebSphere BI for FN database, for each SAG that the MSIF Transfer Service is to use to conduct file transfers, resubscribe manually by issuing the "subscribe" command. E13. Updating the Toolkit development environment ------------------------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Activating * *------------------------------------------------------------------------------* F. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM45244 MSIF HANDLING OF DELIVERY NOTIFICATIONS RECEIVED OUT OF SEQUENCE Please note: This is the sysrouted WebSphere BI for FN V3.1.1 APAR of the original WebSphere BI for FN V3.1.0 APAR PM33997. Formerly, when a delivery notification of a send transfer was received before the response for the send request was received from SWIFT, the delivery notification could not be correlated and was discarded. Event DNFO1019I was issued. This was true for MSIF InterAct SnF, MSIF FileAct RT and SnF. The transfer itself completed successfully, but applications which requested delivery notifications could receive none. Thus, the notification state reflected "None", if the counterpart missed to resend the delivery notification (Receiver in case of RT, SWIFT in case of SnF). Now, delivery notification handling in MSIF has been improved to be able to handle a delivery notification even if it is received before the response. In detail: - Formerly, when the MSIF transfer service processed a SWIFTNet notification, it updated only the corresponding transfer scenario. Now, for each SWIFTNet notification, it creates a separate NotifReceived scenario. Each NotifReceived scenario has its own MSIF reference. A NotifReceived scenario can be correlated to its corresponding transfer scenario by means of: - The NotifReference field of the DeliveryAck notification that was created when the SWIFTNet notification was received (this contains the MSIF reference of the NotifReceived scenario) - The external reference of the NotifReceiced scenario (this contains the MSIF reference of the corresponding transfer scenario) If an error occurs during the processing of a SWIFTNet notification (for example, if a DeliveryAck msg cannot be put to the target queue), an MSIF administrator or operator must manage the NotifReceived scenario rather than the corresponding transfer scenario. - A new optional element NotifReference has been added to the DeliveryAck.Notification folder. For details, see "WebSphere BI for FN: Application Programming". - The following messages are new: DNFO2040E, DNFO2041E, DNFO2042E, DNFO2055E, DNFO2056E, DNFO2057E, DNFO2058E, DNFO2059E - The following messages are obsolete and have been removed: DNFO2037E, DNFO2038E, DNFO3167E, DNFO3913E - For messages that are processed by the MSIF transfer service, the AM_NODE column of an audit log can now contain the following additional values: DnfSagInReqNoCorrelEfa For an inbound SNL request that contains a SWIFTNet notification that cannot be correlated to a scenario. DnfSagOutRspNoCorrelEfa For an outbound SNL response to a SWIFTNet notification that could not be correlated to a scenario. PM44901 MSIF INTERACT: APPHDR HANDLING WRONG, WHEN APPHDR CONTAINS BLANKS IN THE NAMESPACE DECLARATION Formerly, when the MSIF transfer service received an InterAct request primitive from an SAG, if the primitive contained blanks in the XML namespace declaration of the application header (for example, ), when the MSIF transfer service created the corresponding MsgReceived notification, it did not provide the application header in the ComIbmDni folder, but only in the message body, together with the payload. Applications experienced problems when they tried to process such MsgReceived notifications. Now, this has been corrected, not only for blanks, but also for line feeds, carriage returns, form feeds, and tabulators. PM45279 MSIF INTERACT: APPHDR HANDLING MAY FAIL, WHEN APPHDR CONTAINS TWO NAMESPACE DECLARATIONS Formerly, when the MSIF transfer service received an InterAct request primitive from an SAG that contained more than one XML namespace declaration in the application header (for example, ), when the MSIF transfer service created the corresponding MsgReceived notification, it did not provide the application header in the ComIbmDni folder, but only in the message body, together with the payload. Applications or reporting tools such as Cognos experienced problems when trying to process or display such MsgReceived notifications. For example, some experienced XML parsing errors, because the message contained two XML root elements. Now, this has been corrected. The new implementation removes all types of application headers from the payload of a received InterAct request primitive, that is, all XML folders with name AppHdr independent of their XML namespaces. However, the AppHdr folder must be at the very beginning of the payload of the InterAct primitive; otherwise, it is handled as part of the payload and is not removed from the payload. All application headers that are removed from the payload of an InterAct primitive are now provided in the MsgReceived.Notification.ReceiveDetails.AppHdr.Hdr folder of the MsgReceived notification. This applies also to the InterAct application header, which has the XML name space urn:swift:xsd:$ahV10. PM44902 MSIF DNFO1027E WHEN A MSIF SNDFILE REQUEST EXPIRES Formerly, when a MSIF SendFile Request expired, event DNFO1027E (Received FSM event could not be associated with a scenario) occurred directly after event DNFO1002E. Now, the behavior has been changed. The event DNFO1027E is no longer issued here. PM38196 MSIF DUMP OF MSIF EG WHEN CLEANUP -ME 5000 IS PERFORMED Formerly, the MSIF execution group could dump, when a cleanup command was issued to cleanup more than 5000 transfers. The dump indication "Failed to allocate memory" showed up. Now, the MSIF cleanup command has been corrected to allow cleanup of more than 5000 transfers. PM42446 MSIF DNFO1034E DURING THE MSIF SEND FILE REASON LIST PARAMETERS LONGER THAN 1000 BYTES Formerly, during the MSIF send file error DNFO1034E occurred, caused by a length of parameter reasonList.Reason.Parameter2 that is greater 1000 bytes. Now, this has been corrected. Fixes for the following WebSphere BI for FN V3.1.0 APARs are now added to WebSphere BI for FN V3.1.1: PM33997 MSIF HANDLING OF DELIVERY NOTIFICATIONS RECEIVED OUT OF SEQUENCE Description refer to APAR PM45244 listed above. PM45066 MSIF INTERACT: APPHDR HANDLING MAY FAIL, WHEN APPHDR CONTAINS TWO NAMESPACE DECLARATIONS Description refer to APAR PM45279 listed above. G. Other changes ---------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++