============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2012 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 PTF UK80421 for APAR PM61747 Driver level: 2340 = Date 2012-08-31 = ============================================================================== ============================================================================== ============================================================================== 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 WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization, SH12-6942. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PM61747 Base SWIFT SR2012: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION. Functional changes: - S.W.I.F.T. Standard Release 2012 (SR2012) changes This PTF contains the message definition set 'fin2012' for S.W.I.F.T. Standard Release 2012 (SR2012) changes. The S.W.I.F.T. SR2012 live date is currently planned for 17 November 2012. You can install this PTF before this date and continue to process messages according to the SR2011 message definition set. The SR2012 message definition set is automatically activated on the planned live date. How to activate the message definition set 'fin2012' before its live date in a test environment is described in this readme in section E7.2. WebSphere MB related activities, Activation of the SR2012 message definition set. - S.W.I.F.T. Standard Release 2012 (SR2012) MaxLength2000 changes This PTF contains an update to the message length check required by the S.W.I.F.T. Standard Release 2012 (SR2012) changes. You have to implement this change in WebSphere BI for FN even if you validate your messages before you send them to WebSphere BI for FN (e.g. in MERVA). Since the S.W.I.F.T. SR2012 live date is currently planned for 17 November 2012, it must not be activated in a production environment prior that date (see E10.2. Activate the changed length check for SR2012). However, installing this PTF does not automatically activate the changed length check for SR2012 so that you can apply the PTF before the live date. With SR2012 the length restriction of max. 2000 characters is lifted for the following message types: 021, 029, 066, 082, 083, and 097 This requires the WebSphere BI for FN configuration value for attribute MaxLength2000 of type/object DnfExceptMsgAttr to change when the SR2012 goes live on 17 November 2012. - S.W.I.F.T. Funds 4.3 support added Documentation updates: - Concepts and Components guide - System Administration The following modules have been changed: /dniv311/admin/toolkit/dni.schemas.comibmdni.zip /dniv311/run/classes/com.ibm.dni.msgstds.ibmapi.CommonMessageDomainService.xml /dniv311/run/classes/dnicvcks.jar /dniv311/run/msg/dnicymsg.cat /dniv311/run/res/dnicymsg.xml /dniv311/admin/toolkit/dni.schemas.swiftFin2010.zip /dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2010.xml /dniv311/run/classes/dnicvrls_sfmtxml10.jar /dniv311/run/classes/dnicvcks_sfmtxml10.jar /dniv311/admin/toolkit/dni.schemas.swiftFin2011.zip /dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2011.xml /dniv311/run/classes/dnicvrls_sfmtxml11.jar /dniv311/run/classes/dnicvcks_sfmtxml11.jar /dniv311/run/classes/dnicvcks_seni1.jar /dniv311/run/classes/dnicvrls_seni1.jar /dniv311/run/classes/dnicvcks_sfunds40.jar /dniv311/run/classes/dnicvrls_sfunds40.jar /dniv311/run/classes/dnicvcks_sfunds41.jar /dniv311/run/classes/dnicvrls_sfunds41.jar /dniv311/run/classes/com.ibm.dni.msgstds.defset.funds42.xml /dniv311/run/classes/dnicvcks_sfunds42.jar /dniv311/run/classes/dnicvrls_sfunds42.jar /dniv311/run/classes/dnicvcks_ssys63.jar /dniv311/run/classes/dnicvrls_ssys63.jar /dniv311/run/classes/dnicvcks_ssys70.jar /dniv311/run/classes/dnicvrls_ssys70.jar The following are new modules: /dniv311/admin/toolkit/dni.schemas.swiftFin2012.zip /dniv311/run/data/dnfczc12.cli /dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2012.xml /dniv311/run/classes/dnicvrls_sfmtxml12.jar /dniv311/run/classes/dnicvcks_sfmtxml12.jar /dniv311/run/classes/com.ibm.dni.msgstds.defset.funds43.xml /dniv311/run/classes/dnicvcks_sfunds43.jar /dniv311/run/classes/dnicvrls_sfunds43.jar The following modules are removed: /dniv311/admin/toolkit/dni.schemas.swiftFin2009.zip /dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2009.xml /dniv311/run/classes/dnicvcks_sfmtxml09.jar /dniv311/run/classes/dnicvrls_sfmtxml09.jar 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 PTF: - UK79973 for APAR PM37343 (Base 3.1.1.6, MANDATORY BASE PTF FOR BROKER 7 SUPPORT) This PTF should be installed together with: - UK80422 for APAR PM61749 (MM 3.1.1.5, SWIFT SR2012: MESSAGE MANAGEMENT UPDATES FOR SWIFT SR2012 CHANGES) Roles involved: The activities in this PTF involve the following roles: - Installer (root) - WebSphere MB administrator (uwmba1) - First WebSphere BI for FN system configuration administrator (sa1) - Second WebSphere BI for FN system configuration administrator (sa2) 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, SH12-6942. 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. 4. Share the files in the /dniv311/admin directory with your customization system. 5. 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 6. Share the files in the following directories with your runtime systems: /dniv311/run/classes 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: chgrp -R dnilpp /dniv311/run/classes 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 (dniczbap) 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. - 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. For further information, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration". 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 /dniv311/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 /dniv311/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 - - - - - - - - - - - - - - - - - - - Update the WebSphere MB environment: If you have configured the CLASSPATH environment variable in the broker configuration as described in "Planning, Installation and Customization" the new message definition set libraries: dniv311/run/classes/dnicvrls_sfmtxml12.jar dniv311/run/classes/dnicvcks_sfmtxml12.jar and the new configuration file: dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2012.xml are automatically recognized as soon as you restart the message broker. Activation of the SR2012 message definition set: Note for production environment: The S.W.I.F.T. SR2012 live date is currently planned for 17 November 2012. Before this date the new message definition set should not be activated on a production environment. The activation date for the message definition set for SR2012 is set in file: dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2012.xml The activation date in this file is set to the planned S.W.I.F.T. SR2012 live date, 17 November 2012. You should not change this file in a production environment. Note for test environment: To activate the message definition set for SR2012 in a business OU for the test environment refer to section E10.1 in this readme. 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 --------------------------------- E10.1. Activate the message definition set for SR2012 - - - - - - - - - - - - - - - - - - - - - - - - - - - Activate the message definition set for SR2012 in a business OU for the test environment: Note for test environment: To activate the message definition set for SR2012 in a business OU for the test environment: 1. On the runtime system, log on to AIX with the user ID of WebSphere BI for FN system configuration administrator (sa1 or sa2). 2. Execute your profile for the runtime environment, e.g.: . /var/dni_03_01/run/dniprofile 3. Start the command line interface (CLI): dnicli -ou SYSOU -s DNI_SYSADM 4. Enter the following commands in your CLI session to set the SR2012 message definition set attribute value and commit the change: add -ou -ct DniMsgDomain -co DNIFIN -attr TestMsgDefSet -val fin2012 com -ou 5. Log on to AIX with the user ID of another WebSphere BI for FN system configuration administrator. 6. Execute your profile for the runtime environment, e.g.: . /var/dni_03_01/run/dniprofile 7. Start the command line interface (CLI): dnicli -ou SYSOU -s DNI_SYSADM 8. Enter the following commands in your CLI session to approve and deploy the changes: app -ou dep -ou Note: In the previous steps, replace with the business OU for which you want to activate the SR2012 message definition set. E10.2. Activate the changed length check for SR2012 - - - - - - - - - - - - - - - - - - - - - - - - - - Activate the changed length check for SR2012 in a business OU for the production environment and the test environment: Note: The S.W.I.F.T. SR2012 live date is currently planned for 17 November 2012. Before this date the new message length check must not be activated on a production environment. To activate the changed length check for SR2012: 1. On the runtime system, log on to AIX with the user ID of a WebSphere BI for FN system configuration administrator (for example, sa1 or sa2). 2. Execute your profile for the runtime environment, for example: . /var/dni_03_01/run/dniprofile 3. Start the command line interface (CLI) in transactional command file mode and execute the commands in the file dnfczc12.cli by entering the following command on a single line: dnicli -ou SYSOU -s DNI_SYSADM -cft /dniv311/run/data/dnfczc12.cli This command file changes the value of the MaxLength2000 attribute and commits the SYSOU. 4. Log on to AIX with the user ID of another WebSphere BI for FN system configuration administrator. 5. Execute your profile for the runtime environment, for example: . /var/dni_03_01/run/dniprofile 6. Start the CLI: dnicli -ou SYSOU -s DNI_SYSADM 7. Enter the following commands in your CLI session to approve and deploy the changes: app -ou SYSOU dep -ou SYSOU 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. - Subscribe MSIF to SAGs to enable file transfer and session monitoring. - Start the MSIF Message Transfer service. - Start the Enhanced InterAct 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". E13. Updating the Toolkit development environment ------------------------------------------------- If you use WebSphere BI for FN nodes or message sets in your own message flows, or if you modified WebSphere BI for FN sample message flows, you must update your Toolkit environment and redeploy your message flows. The following resources have changed in this PTF: -> schema definitions: - /dniv311/admin/toolkit/dni.schemas.comibmdni.zip - /dniv311/admin/toolkit/dni.schemas.swiftFin2010.zip - /dniv311/admin/toolkit/dni.schemas.swiftFin2011.zip - /dniv311/admin/toolkit/dni.schemas.swiftFin2012.zip To update your Toolkit environment: - Delete the old WebSphere BI for FN provided message set projects in your workspace. - To reinstall the new versions of the Toolkit resources, follow the instructions provided in the section of 'Application Programming' that describes how to prepare the WebSphere Message Broker Toolkit workstation. *-----------------------------------------------------------------------------* * End of Activating * *-----------------------------------------------------------------------------* F. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM61747 Base SWIFT SR2012: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION. This PTF deliveres support for checking FIN messages according to the S.W.I.F.T. Standard Release 2012. G. Other changes ---------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++