============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2016 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 Base (3.1.1.28) PTF UI41571 for APAR PI69993 Driver level: 6411 Date 2016-10-27 ============================================================================== ============================================================================== 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 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: PI69993 Base TAG 111 SHOULD ONLY ALLOW NUMERIC CHARACTER NO LETTERS PI69994 Base SR2016 22L SHOULD BE A MANDATORY WITH MT304 PI69992 Base ALL SPACING OR BLANKS IN TAG 121 SHOULD BE AN INVALID INPUT Documentation updates: The following manuals have been changed: - none The following modules have been changed: /dniv311/admin/toolkit/dni.schemas.swiftFin2016.zip /dniv311/run/classes/dnicvcks_sfmtxml16.jar /dniv311/run/classes/dnicvrls_sfmtxml16.jar 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: - UI39783 for APAR PI59038 (Base 3.1.1.27, SQLCODE: '-4461', SQLSTATE: '42815', 'CREATE NEW DNI_OU ENTRY' WHILE THE OU_LEVEL HIT THE COLUMN LIMITATION) If you are using the Message Management feature of WebSphere BI for FN, then this PTF must be installed together with: - UI41572 for APAR PI70043 (MM 3.1.1.21, MESSAGE MANAGEMENT UPDATES FOR BASE APARS PI69520, PI68767, AND PI69595) C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - WebSphere MB administrator (uwmba1) - WebSphere MB application developer (uwmbad1) 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. Ensure that the group ownership of the /dniv311/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 /dniv311/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 /dniv311/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 ------------------------------------------------- You must update your Toolkit environment if you use at least one of the following components: - WebSphere BI for FN sample message flows as foundation for your own flow development - WebSphere BI for FN nodes in your own message flows - WebSphere BI for FN message set projects containing XML schema definitions, that, for example, are utilized by the XPath wizard Furthermore, you have to rebuild and redeploy your message flows if they are based on the WebSphere BI for FN API. The following resources are changed by this PTF: - WebSphere BI for FN nodes: - none - WebSphere BI for FN message sets: - dni.schemas.swiftFin2016.zip - WebSphere BI for FN message set projects: - none To install the new versions of the Toolkit resources, follow the instructions of the listed sections provided in "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN Application Programming: - Transferring the WebSphere BI for FN resources - Installing the WebSphere BI for FN Eclipse plug-ins If you use WebSphere BI for FN sample message flows as foundation for your own flow development follow the instructions provided in "Using the sample routing flows" in WebSphere BI for FN Application Programming. Otherwise, continue with the instructions provided in "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN Application Programming: - Importing WebSphere BI for FN Base sample projects - Importing the message sets and sample routing flows Additionally, if you use WebSphere BI for FN message set projects containing XML schema definitions for your own flow development follow the instructions provided in section "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN Application Programming: - Importing the message sets and sample routing flows - Importing XSD files for SWIFT message payloads D16. Verifying your Installation -------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Installation * *------------------------------------------------------------------------------* E. APAR details --------------- Fixes for the following APARs are contained in this PTF: PI69993 Base TAG 111 SHOULD ONLY ALLOW NUMERIC CHARACTER NO LETTERS Formerly, when loading an MT103 message with Tag111 as 'ABC', the WebSphere BI for FN did not validate this as an invalid field. SWIFTNet rejects messages with letters in Tag111. Now, this has been corrected. PI69994 Base SR2016 22L SHOULD BE A MANDATORY WITH MT304 Formerly, when a MT304 message with optional sequence C1 where 22L was not mandatory and 22M and 22N were populated, WebSphere BI for FN did not validate this as invalid. According to SWIFT message standard, user expects WebSphere BI for FN to validate this as an error since SWIFTNet rejects this message without 22L. Now, this has been changed. PI69992 Base ALL SPACING OR BLANKS IN TAG 121 SHOULD BE AN INVALID INPUT In field 121 of MT199, SWIFT eliminates leading blanks, which leads to an empty field if only blanks are specified. SWIFT returns then a NAK for this message. Formerly, WebSphere BI for FN did not validate this as invalid. Now, this has been corrected. F. Other changes ---------------- NOT APPLICABLE. G. Known issues --------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++