============================================================================== ============================================================================== 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.0 Messaging Services for SWIFTNet InterAct and FileAct PTF UK69511 for APAR PM39486 Date 2011-07-31 ============================================================================== ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Preparation E Activating F APAR details G Other changes H 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. 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/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 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: PM36668 MSIF MSIF ACCOUNTING DATA MISSING PM37358 MSIF EFA RECEIVE REQUESTS ARE REJECTED WHILE THE SUBSCRIBE REQUEST IS RUNNING PM39486 MSIF THE MSIF API INTERFACE STRUCTURES FOR INTERACT SCENARIOS MISS SOME ESSENTIAL TIMESTAMPS RELATED TO SWIFTNET PROCESSING. Documentation updates: The following manuals have been changed: - Application Programming The following modules have been changed: /dnf_03_01/run/jplugin/dnfco.jar /dnf_03_01/run/msg/dnfcomsg.cat /dnf_03_01/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 return a message of the form: '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 return a message of the form: '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: - UK67874 for APAR PM42536 (Base 3.1.0.7, USE THE @ TO MARK A GROUP WITH ACCESS AUTHORITY IN CDD) - UK66459 for APAR PM33433 (MSIF 3.1.0.4, DELIVERYNOTIFICATION RECEIVED PRIOR TO THE EXPECTED ACK RESULTS IN REJECT) This PTF supersedes the following PTFs: - none 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. 4. Share the files in the /dnf_03_01/admin directory with your customization system. 5. Ensure that the group ownership of the /dnf_03_01/admin directory and all of its subdirectories and files, is set to group dniadmin. To do this, enter the following command in AIX shell: chgrp -R dniadmin /dnf_03_01/admin 6. Share the files in the following directories with your runtime systems: /dnf_03_01/run These files are already needed during the preparation phase and do not influence normal operation. 7. 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 /dnf_03_01/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. - Release SWIFTNet SnF queues. - Stop the MSIF Transfer service. - Stop the Enhanced InterAct service. - Close all dnicli sessions. For further information, refer to the section of "System Administration" that describes how to operate components, sessions, and services. 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 /dnf_03_01/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 shell: chgrp -R dnilpp /dnf_03_01/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 ----------------------------------------- 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. - Start the MSIF Transfer service. - Start the Enhanced InterAct service. - Acquire SWIFTNet SnF queues. - Start the applications that send requests to WebSphere BI for FN. For further information, refer to the section of "System Administration" that describes how to operate components, sessions, and services. E13. Updating the Toolkit development environment ------------------------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Activating * *------------------------------------------------------------------------------* F. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM36668 MSIF MSIF ACCOUNTING DATA MISSING Formerly, MSIF collected accounting data only with InterAct receive mode for SnF and with automatic response mode for RT scenarios. This accounting went wrong if the customer uses the flexible response mode. Now, accounting data are collected in both modes (flexible and automatic). PM37358 MSIF EFA RECEIVE REQUESTS ARE REJECTED WHILE THE SUBSCRIBE REQUEST IS RUNNING Formerly, when a subscribe command was issued while a SAG had been subscribed before, receive requests were rejected with the reject info='Reason=NoSubscription'. EFAS and MSIF changed the subscription status from "subscribed" to "subscribe in progress" whenever a subscribe command was issued. During the "subscribe in progress" timeframe, EFAS and MSIF behaved as if there was no subscription available. Now, this behaviour has been changed: when a subscription is already available and the subscribe command is issued. receive requests are accepted. PM39486 MSIF THE MSIF API INTERFACE STRUCTURES FOR INTERACT SCENARIOS MISS SOME ESSENTIAL TIMESTAMPS RELATED TO SWIFTNET PROCESSING. Formerly, the MSIF API interface structures for InterAct scenarios missed some essential timestamps related to SWIFTNet processing. Now, the MSIF API interface structures for InterAct scenarios have been enhanced to provide the SNF Input Time and the DeliveryTime for InterAct store and foreward message transfers. G. Other changes ---------------- NOT APPLICABLE. H. Known issues --------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++