============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2015 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 (3.1.1.16) PTF UI30300 for APAR PI41363 Driver level: 5340 Date 2015-09-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 customization directory. The directory /var/dni_03_01/cus is used in examples. The deployment directory. The directory /var/dni_03_01/cus/depdata 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: PI41363 FILEACT FILES "IN ERROR" MARKED AS RECOVERABLE COULD NOT BE RECOVERED PI41934 SENDFILE TRANSFER SHOULD'T GO INTO ERROR_NOTIF, IF NO SAG SUBSCRIPTION, AND DELIVERY NOTIFICATION RECEIVED SUCCESSFULLY PI46203 FILES ARE ALWAYS SENT UNZIPPED, WHEN A PROBLEM OCCURS DURING RM CHECK IN MSIF FILEACT Additional functional changes: - none Documentation updates: The following manuals have been changed: - Messages and Codes - System Administration The following modules have been changed: /dnfv311/run/dnfxzora /dnfv311/run/dnfxzoro /dnfv311/run/dnfxzort /dnfv311/run/jplugin/dnfco.jar /dnfv311/run/msg/dnfcomsg.cat /dnfv311/run/msg/DNFO_Msg.properties /dnfv311/run/res/dnfcomsg.xml 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: - UI27536 for APAR PI40043 (MSIF 3.1.1.15, MSIF SHOULDN'T END IN A CIN STOP, WHEN A PREVIOUSLY PROCESSED RECEIVE NOTIFICATION IS ACCIDENTLY SENT BACK TO DNF_O_FT) - 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. 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 -------------------------------- NOT APPLICABLE. D11. Deploy 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 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: PI41363 MSIF FILEACT FILES "IN ERROR" MARKED AS RECOVERABLE COULD NOT BE RECOVERED In the WebSphere BI for FN configuration it can be specified that a compressed file that is received from a counterpart should be uncompressed by MSIF before it is delivered to an application. If a counterpart sends an uncompressed file and the uncompression operation fails, then the FileReceived scenario goes into condition 'InError'. The root cause for such an error scenario can be that, for example, the counterpart accidently sends the file uncompressed, or that the file should be uncompressed but it was accidently configured in the WebSphere BI for FN configuration that it is compressed. Formerly, the only option to resolve such an error scenario was to cancel the FileReceived transfer, correct the root cause, and ask the counterpart to resend the file in the expected format. Now, a new argument 'mode' has been introduced to the recover command. The recover command can be issued on a FileAct scenario in state 'FileReceived' to skip any uncompression or conversion operations and deliver the file 'as is' to the application. The file is delivered with completion code PartialOk and message DNFO1256I. PI41934 MSIF SENDFILE TRANSFER SHOULD'T GO INTO ERROR_NOTIF, IF NO SAG SUBSCRIPTION, AND DELIVERY NOTIFICATION RECEIVED SUCCESSFULLY After MSIF initiates a SendFile transfer it expects to receive status events from the SAG that indicate the progress of the file transfer to the receiver. If subscriptions to receive SAG status events have been lost on the SAG, then the SAG does not send such events and MSIF is not informed of the successful completion of a transfer. If for a SendFile transfer MSIF requested from the receiver a delivery notification, then there might be a scenario where no SAG status events are received but a successful delivery notification of the file is received. Formerly, MSIF treated this scenario as an error because no SAG status event is received that indicated a successful transfer of the file. Now, MSIF treats this scenario as success because the delivery notification indicates that the receiver received the file successfully. PI46203 MSIF FILES ARE ALWAYS SENT UNZIPPED, WHEN A PROBLEM OCCURS DURING RM CHECK IN MSIF FILEACT If compression options are specified, then MSIF zips a file before it sends it out to the SAG. In the transaction where a file is zipped, MSIF also checks whether the file can be send out according to ASP and RM settings. If the ASP and RM check fails due to a DB problem, then the transaction is rolled back. When MSIF executes the same transaction again, then it detects that the file is already zipped successfully, so it does not zip it again. Formerly, in such a scenario there was a possibility that MSIF continued to work with the original unzipped file, because the file name was set back to its original value during the DB2 rollback. Now, in such an error scenario the zipped file is always used and sent out to the SAG. F. Other changes ---------------- - Message updates: * Changed Messages: DNFO1230E, DNFO1231E * New messages: DNFO0324I, DNFO1256I, DNFO2062E G. Known issues --------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++