============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2010 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 Base PTF UK54898 for APAR PM08215 = Date 2010-04-19 = ============================================================================== ============================================================================== ============================================================================== 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 ---------------------- 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 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 the "Planning, Installation, and Customization" maunal. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PM08215 Base UPDATES ON MESSAGE STANDARDS COMPONENT PM09456 Base DNIY3303E IN MESSAGE VALIDATION, IF FIELD 61 IN MT940 CONTAINS SUBFIELD SUPPLEMENTARY INFORMATION PM09323 Base BAP DOES NOT RECOGNIZE BAR FILES FROM 2010 AS BEING NEWER THAN THOSE FROM 2009 PM10381 Base HARDCODE OF 'WBIFNV210' WITHIN DNICMBEL.CPP, IT SHOULD BE SHOWN WITH 3.1 VERSION OF WBIFN Functional changes: NOT APPLICABLE. Documentation updates: NOT APPLICABLE. The following modules have been changed: /dni_03_01/run/classes/dnicvcks_sfmtxml09.jar /dni_03_01/run/classes/dnicvcks_sfunds4.jar /dni_03_01/run/classes/dnicvcks_sfunds41.jar /dni_03_01/run/classes/dnicvcks.jar /dni_03_01/run/classes/dnicvrls_sfmtxml09.jar /dni_03_01/run/classes/dnicvrls_sfunds4.jar /dni_03_01/run/classes/dnicvrls_sfunds41.jar /dni_03_01/run/classes/dniczbap.jar /dni_03_01/run/jplugin/dni.msg.stds.node.jar /dni_03_01/run/lil/dnicnp.lil 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: - UK51812 for APAR PK97165. This PTF supersedes the following PTFs: not applicable Roles involved: The activities in this PTF involve the following roles: - Installer (root) - WebSphere MB administrator (uwmba1) D. Preparation -------------- D1. Installation ---------------- 1. This PTF requires the Base for Multiplatforms PTF V3.1.0.2 (UK51812 for APAR PK97165), please install the Base PTF V3.1.0.2 first. This PTF will overwrite partial installed files. After installation, the V.R.M.F will upgrade to V3.1.0.3. The detail steps of installation could be found in "Installing WebSphere BI for FN", in the "Planning, Installation and Customization" manual. D2. Steps on a customization system ----------------------------------- NOT APPLICABLE. D3. Copy DB2 modules to data sets --------------------------------- NOT APPLICABLE. D4. Generating configuration data migration scripts --------------------------------------------------- NOT APPLICABLE. D5. Customize updated BAR files when not using the BAP (dniczbap) to deploy them -------------------------------------------------------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Preparation * *------------------------------------------------------------------------------* E. Activating ------------- E1. Stopping all sessions and services you use ---------------------------------------------- Stop all sessions and services. How to do this depends on which WebSphere BI for FN features you use. 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 Message Transfer service. - Stop the Enhanced InterAct services. - Close all dnicli sessions. For further information, refer to the section of the 'System Administration' manual 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 /dni_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: chgrp -R dnilpp /dni_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 ------------------------- 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 Message Transfer service. - Start the Enhanced InterAct services. - Acquire SWIFTNet SnF queues. - Start the applications that send requests to WebSphere BI for FN. For further information, refer to the section of the 'System Administration' manual 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: PM08215 Base UPDATES ON MESSAGE STANDARDS COMPONENT The message standards component of WebSphere BI for FN is updated as described in this document. PM09456 Base DNIY3303E IN MESSAGE VALIDATION, IF FIELD 61 IN MT940 CONTAINS SUBFIELD SUPPLEMENTARY INFORMATION Formerly, when trying to send a MT940 containing the subfield supplementary information in field 61, WebSphere BI for FN V3.1 message validation got an exception that resulted in error event DNIY3303E. Now, WebSphere BI for FN V3.1 message validation handles MT940 containing the supplementary information subfield in field 61 correctly. PM09323 Base BAP DOES NOT RECOGNIZE BAR FILES FROM 2010 AS BEING NEWER THAN THOSE FROM 2009 Formerly, the DNICZBAP Program did not recognize BAR Files created in year 2010 (sequence numbers are 0xxx) as being newer than BAR Files created in year 2009 (sequence numbers are 9xxx). Now, the DNICZBAP Program is modified to recognize and handle the BAR files in the correct yearly sequence PM10381 Base HARDCODE OF 'WBIFNV210' WITHIN DNICMBEL.CPP, IT SHOULD BE SHOWN WITH 3.1 VERSION OF WBIFN The WBIFN version is updated from WBIFNv210 to WBIFNv310. G. Other changes ---------------- - The DniStandardsProcessing node did transform messages even if they already had been transformed before. This has been corrected. - The SWIFT Funds standard specification was unclear in the area of validation rules for various identifiers. This was clarified with a SWIFT knowledgebase entry: https://www2.swift.com/search/kb/fetchTip.faces?tip=2233831 The message validation for Funds messages was enhanced to conform to these additional rules. - Some versions of MT021 OSN messages caused 'DNIY0018E: Invalid element reference' error messages in MER. This has been corrected. - Field 115 in FIN is only used in an Output Message, therefore it is no longer displayed when creating a message in MER. It will be displayed when you open a message where field 115 contains data. - Field 119 in FIN determines the variant of some message types. In message types with fixed variants, e.g. 102.STP, 103.REMIT, 103.STP, 202.COV, 205.COV, 574.IRSLST or 574.W8BENO it is displayed, but cannot be changed. In messages types 502, 503, 504, 505, 506, 507, 509 and 515 it is visible and can be changed. In all other message types it is not visible unless it contains data. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++