============================================================================== ============================================================================== 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 UI16878 for APAR PI13399 Driver level: 4203 Date 2014-05-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 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 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: PI13399 MSIF FILE TRANSFER ENDED IN DELIVFILEINERROR, INDICATING A NETWORK TRANSMISSION ERROR PI11249 MSIF INERRORACTION APP IS NOT CONSIDERED FOR DNFO3654E PI13982 MSIF MSIF: ADAPTING WEBSPHERE BI FOR FN BASE APAR PI07234 AUTHORITIZATION CHANGES IN MSIF PI14721 MSIF DNFO1253E SHOULD SHOW THE SCENARIO STATE BY THE TIME WHEN AN ERROR OCCURRED, NOT THE STATE WHICH IS SET DUE TO THE ERROR PI15467 MSIF FULL SUPPORT OF PAYLOAD ATTRIBUTES AND SIGNATURE REFERENCES IN MSIF PI15567 MSIF EXCEPTIONS IN BROKER JOBLOG, WHEN MSIF IS CUSTOMIZED BUT NOT CONFIGURED Additional functional changes: - MSIF removes service check for delivery notifications - MSIF adds the logical file name to the AckInfo SNL parameter Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Messages and Codes - Application Programming - System Administration The following modules have been changed: /dnfv311/admin/data/DNFEFAS.xml /dnfv311/admin/data/dnfxzoco.def /dnfv311/run/jplugin/dnfco.jar /dnfv311/run/msg/dnfcomsg.cat /dnfv311/run/msg/DNFO_Msg.properties /dnfv311/run/res/dnfcomsg.xml The following are new modules: /dnfv311/admin/data/dnfxzo1o.def 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: - UI13192 for APAR PM99720 (MSIF 3.1.1.10, INTRODUCING BATCHING FOR DETECTION OF TIMED OUT AND EXPIRED TRANSFERS) - UI15322 for APAR PI07294 (Base 3.1.1.17, CHANGE AO FACILITY TO USE RES-AUTH CONTAINER AND SPECIFY ALL REQUIRED RESOURCES IN THE WEB.XML) C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - WebSphere MQ administrator (uwmqadm1) - 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 following: 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 ----------------------------------- To update your current definition directory and the customized administrative scripts, and to create deployment instructions and vehicles: 1. Log on to AIX on the customization system as a customizer (ucust1). 2. Change to the customization directory: cd 3. Run your customization profile: 3.1. Verify your customization profile: Ensure that the setting of the DNI_JAVA environment variable is set to the Java 6 64-bit home directory, for example: DNI_JAVA=/usr/java6_64 3.2. Run your customization profile: . ./dnicus_ 4. Start the CDP in migration mode and use the following commands to migrate customization data: dnicdpm -i > export cdd/_UI16878.cdd > import cdd/_UI16878.cdd > prepare This step updates the customized administrative scripts in the directory '//admin' and generates deployment data for migration of the run-time system for the following resource classes: - MQAUT * update permission on queue DNIvINST.DNIvOU.DNF_O_CMD for group DNIvSGRP Deployment instructions are generated in the file '///instructions.txt'. You will need this later in the step D7. 5. Implement the customization definition data and quit the CDP session: > implement When the message "DNIZ9013I: If you continue, the current CDD will be overwritten by a new CDD." is displayed enter 'y' to continue. > quit D7. Following the deployment instructions created in step D6 ------------------------------------------------------------ Follow the deployment instructions that were created in step D6. 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. 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: PI13399 MSIF FILE TRANSFER ENDED IN DELIVFILEINERROR, INDICATING A NETWORK TRANSMISSION ERROR If MSIF receives a file where a delivery notification is requested by the sender, then, as soon as the file is received, it sends back to SWIFT an acknowledgement request. Then SWIFT returns an acknowledgement response indicating whether the request was processed successfully. Beside this acknowledegment processing MSIF performs some file operation like copying or unzipping the file, before it finally sends a FileReceived notification message to the application. If there are multiple MSIF threads running, then the acknowledgement handling and the file operations are performed in parallel. In this case it is possible that either the acknowledgement processing completes before the file operations, or vice versa. Formerly, if the acknowledgement processing completed before the file operations, and the acknowledgement response contained errors, then the file was delivered to the application with completion code Failed, and the transfer ended in state DelivFileInError. If the file operations completed before the acknowledgement processing, that means the file was delivered to the application before the acknowledgement response was received, then the file was delivered to the application with completion code Ok, and the transfer ended in state DelivComplete. Now, the completion code and the transfer state is independent on the acknowledgement processing, that means that errors in the acknowledgement response are issued as events and are regarded for the notification state, but are not regarded anymore for the completion code and the transfer state. PI11249 MSIF INERRORACTION APP IS NOT CONSIDERED FOR DNFO3654E Formerly, when an application sent a SendFile request to MSIF that referred to a file that did not exist or could not be accessed, then MSIF did not use the option InErrorAction of CT DnfEfaBouParameters, but always issued an error event, for example DNFO3654E. Now, in such an error scenario, MSIF checks the option InErrorAction, and if it is set to App, then it notifies the application about the file access problem instead of raising an event. PI13982 MSIF MSIF: ADAPTING WEBSPHERE BI FOR FN BASE APAR PI07234 AUTHORITIZATION CHANGES IN MSIF With WebSphere BI for FN Base PTF UI16369 for APAR PI07234 the WAS security in WebSphere BI for FN web applications was changed. This WebSphere BI for FN MSIF PTF provides the necessary adaptions for MSIF. See also to WebSphere BI for FN Base APAR PI07234. PI14721 MSIF DNFO1253E SHOULD SHOW THE SCENARIO STATE BY THE TIME WHEN AN ERROR OCCURRED, NOT THE STATE WHICH IS SET DUE TO THE ERROR The error events DNFO1249E and DNFO1253E contain the original state in which a transfer received an error. Formerly, the events did not contain the original state, but the state in which the transfer went after handling the error. Now, the events contain the original state before handling the error. PI15467 MSIF FULL SUPPORT OF PAYLOAD ATTRIBUTES AND SIGNATURE REFERENCES IN MSIF To support a solution for the CLS service, an extended support of payload attributes and signature references was required. Formerly MSIF provided a full support of the payload type attribute, but only a limited support of payload attributes in general. Now MSIF provides a full support of payload attributes. Payload attributes can now be specified by an application in a SendMsg request, and are forwarded in a MsgReceived notification to an application. For more information see the Application Programming manual. Formerly MSIF supports a maximum of 8 signature references. This restriction is derived from a limitation in the central system at SWIFT. SWIFT has announced a plan to increase this limit later this year. Please note that at the time this PTF is published, the limit is still 8 due to the limitation in the central system at SWIFT. Now MSIF provides a support of an unlimited number of signature references in SendMsg requests. For more information see the Application Programming manual. PI15567 MSIF EXCEPTIONS IN BROKER JOBLOG, WHEN MSIF IS CUSTOMIZED BUT NOT CONFIGURED Formerly if in the WBIFN configuration no configuration object DnfEfaParameters was configured, then MSIF failed to determine the batch size and initiate the internal timeout processing due to a NullPointerException. Now this was corrected, and MSIF initiates the timeout processing without errors. F. Other changes ---------------- - Message updates: * Event messages changed: DNFO0461E, DNFO3251E, DNFO3600E, DNFO9501E * Response messages changed: DNFO0557E, DNFO9500E - MSIF removes service check for delivery notifications MSIF can process InterAct and FileAct traffic in different MSIF services DNF_O_FTx. Formerly, MSIF verified that on the sending side a delivery notification is received in the same service than the corresponding send transfer was processed. In case the delivery notification was received in a different service, MSIF rejected the message. Now, this condition is not verified anymore, and delivery notification received in other MSIF services are accepted. This change can simplify the message routing conditions specified on an SAG. - MSIF adds the logical file name to the AckInfo SNL parameter Due to a SWIFT vendor letter MSIF adds now the logical file name to the AckInfo SNL parameter so SWIFT can forward this information in delivery notification messages to the sender of a file. G. Known issues --------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++