============================================================================== ============================================================================== 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 UK58142 for APAR PM07599 = Date 2010-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 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 "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: PM07599 Base SWIFT SR2010: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION. Functional changes: - S.W.I.F.T. Standard Release 2010 (SR2010) changes This PTF contains the message definition set 'fin2010' for S.W.I.F.T. Standard Release 2010 (SR2010) changes. The S.W.I.F.T. SR2010 live date is currently planned for 20 November 2010. You can install this PTF before this date and continue to process messages according to the SR2009 message definition set. The SR2010 message definition set is automatically activated on the planned live date. How to activate the message definition set 'fin2010' before its live date in a test environment is described in this readme in section E7.2. WebSphere MB related activities, Activation of the SR2010 message definition set. - The schema of the messages in the definition set 'fin2010' differs from the schema of messages in 'fin2009' to increase compatibility with SWIFTs MT/XML Schema Library. For details regarding the MT message formats refer to Concepts and Components guide. As a result of this change you may have to change XPath statements used in your routing flows when you start to process messages using the 'fin2010' message definition set. - A new possibility is provided to activate a message definition set for test purposes even before its official activation date. Refer to the System Administration guide, chapter Administering and operating components, sessions, and services, Testing a new message definition set, and in this readme to section E7.2. WebSphere MB related activities, Activation of the SR2010 message definition set. - Support for SWIFTNet Exceptions and Investigations 1.1 (Bank-to-Bank) was added in the 'eni12' message definition set. Support for SWIFTNet Exceptions and Investigations 1.2 (Bank-to-Corporate) is still available in the same message definition set. Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Concepts and Components - Messages and Codes - System Administration - Application Programming - Information Center The following modules have been changed: /dni_03_01/admin/data/DNFCOMMON.xml /dni_03_01/admin/data/dnfczcat.cli /dni_03_01/admin/data/dnfczdat.cli /dni_03_01/admin/data/dniczbdt.txt /dni_03_01/admin/data/dniczcly.txt /dni_03_01/admin/data/dniczcla.txt /dni_03_01/admin/toolkit/com.ibm.dni.api.jar /dni_03_01/run/classes/com.ibm.dni.msgstds.defset.fin2009.xml /dni_03_01/run/classes/com.ibm.dni.msgstds.defset.eni12.xml /dni_03_01/run/classes/com.ibm.dni.msgstds.ibmapi.CommonMessageDomainService.xml /dni_03_01/run/classes/dni.msgstds.api.jar /dni_03_01/run/classes/dni.msgstds.impl.jar /dni_03_01/run/classes/dnicvcks.jar /dni_03_01/run/classes/dnicvcks_sfmtxml09.jar /dni_03_01/run/classes/dnicvrls_sfmtxml09.jar /dni_03_01/run/classes/dnicvcks_sfunds4.jar /dni_03_01/run/classes/dnicvrls_sfunds4.jar /dni_03_01/run/classes/dnicvcks_sfunds41.jar /dni_03_01/run/classes/dnicvrls_sfunds41.jar /dni_03_01/run/classes/dnicvcks_sfunds42.jar /dni_03_01/run/classes/dnicvrls_sfunds42.jar /dni_03_01/run/classes/dnicvcks_ssys63.jar /dni_03_01/run/classes/dnicvrls_ssys63.jar /dni_03_01/run/classes/dnprdu.jar /dni_03_01/run/bin/dnicli /dni_03_01/run/data/dnfczcat.cli /dni_03_01/run/doc/dni.msgstds.api.doc.zip /dni_03_01/run/jplugin/dni.msg.stds.node.jar /dni_03_01/run/lil/dnicpn.lil /dni_03_01/run/lil/dnicin.lil /dni_03_01/run/msg/dnicymsg.cat /dni_03_01/run/res/dnicymsg.xml The following are new modules: /dni_03_01/run/classes/com.ibm.dni.msgstds.defset.fin2010.xml /dni_03_01/run/classes/dnicvrls_sfmtxml10.jar /dni_03_01/run/classes/dnicvcks_sfmtxml10.jar /dni_03_01/run/classes/dnicvcks_seni1.jar /dni_03_01/run/classes/dnicvrls_seni1.jar The following modules are removed: /dni_03_01/run/classes/dnicvcks_seni12.jar /dni_03_01/run/classes/dnicvrls_seni12.jar /dni_03_01/run/classes/com.ibm.dni.msgstds.defset.fin2008.xml /dni_03_01/run/classes/dnicvcks_sfmtxml08.jar /dni_03_01/run/classes/dnicvrls_sfmtxml08.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: - UK54898 for APAR PM08215 (UPDATES ON MESSAGE STANDARDS COMPONENT) This PTF should be installed together with: - UK58149 for APAR PK13495 (MESSAGE MANAGEMENT UPDATES FOR SWIFT SR2010 CHANGES) Roles involved: The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - WebSphere MB application developer (uwmbad1) - 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 you use. 2. Stop all WebSphere BI for FN message brokers. 2. Install this PTF using IAW. 3. Share the files in the /dni_03_01/admin directory with your customization system. 4. Ensure that the group ownership of the /dni_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: chgrp -R dniadmin /dni_03_01/admin 5. Share the files in the following directories with your runtime systems: /dni_03_01/run/bin /dni_03_01/run/data These files are already needed during the preparation phase and do not influence normal operation. 6. 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/bin chgrp -R dnilpp /dni_03_01/run/data 7. Restart all WebSphere BI for FN message brokers. D2. 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: . ./dnicus_ 4. Start the CDP in migration mode and use the following commands to migrate customization data: dnicdpm -i > export cdd/_PM07599.cdd > import cdd/_PM07599.cdd 5. Implement the customization definition data and quit the CDP session: > implement When the message "DNIZ9013I: Current Definition file already exists." is displayed enter 'y' to continue. > quit D3. Generating configuration data migration scripts --------------------------------------------------- To prepare the migration of configuration entities: 1. On the runtime system on which the message broker runs, log on to AIX as the system configuration administrator, for example, sa1, and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Check if you have enabled wildcard escaping for the 'list -ro' command and disable it temporarily. To check if you have configured an escape character enter the following commands: dnicli -s DNI_SYSADM -ou SYSOU > list -ou SYSOU -co DniSecAdm.list -attr DniEscapeCharacter -lo osv If the response is 'No OUs match search criteria.' no escape character is defined. Otherwise note the value displayed and enter the following command in the CLI session to temporarily disable the escape character: > rem -ou SYSOU -ct DniSecAdm.list -co DniSecAdm.list -attr DniEscapeCharacter Commit, approve and deploy the OU SYSOU. Close the CLI session: > .quit 3. Create a temporary directory where dnfczmlc stores the CLI command files which will contain the configuration migration statements. 4. Switch to this directory and enter the following command: dnfczmlc -i [-dual YES|NO] [-to timeout] where: -i The name of the instance. -dual YES|NO Specifies whether files are to be created for a system that uses dual authorization for SYSOU. The default is -dual YES. Specify -dual NO only if dual authorization is to be turned off for both DNI_SYSADM and DNI_SECADM in SYSOU at the time when the created files are executed. Whether dual authorization is switched on or off for other OUs is irrelevant. -to timeout The number of milliseconds that the CLI waits for a response to this command before it issues an error message. The default is 100000 (100 seconds). It must be a whole number between 20000 and 9999999. Note: This command starts a long-running task that might take several minutes to complete. Check the file dnfczmlc.log to ensure that it completed successfully. The program dnfczmlc creates the following CLI command files: If dual authorization is not used (-dual NO): 1. dnfczmlc_2_sa_ent_all.cli If dual authorization is used (-dual YES): 1. dnfczmlc_5_sa_cre_ct_com.cli 2. dnfczmlc_5_sa_cre_ct_dep.cli 5. Enable the escape character for the 'list -ro' command if you have temporarily disabled it in step 2: dnicli -s DNI_SYSADM -ou SYSOU > add -ou SYSOU -co DniSecAdm.list -ct DniSecAdm.list -attr DniEscapeCharacter -val where is the value that was displayed in response to the list command in step 2. This PTF changes the following configuration entities: - adds new CT 'DniMsgDomain' with attribute 'TestMsgDefSet' 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. - Release SWIFTNet SnF queues. - Stop the MSIF Transfer service. - Stop the Enhanced InterAct services. - 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 /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 -------------------------------------------------------------- Follow the deployment instructions that were created in step D2.4. This will update the run-time system resources. 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: dni_03_01/run/classes/dnicvrls_sfmtxml10.jar dni_03_01/run/classes/dnicvcks_sfmtxml10.jar and the new configuration file: dni_03_01/run/classes/com.ibm.dni.msgstds.defset.fin2010.xml are automatically recognized as soon as you restart the message broker. Activation of the SR2010 message definition set: Note for production environment: The S.W.I.F.T. SR2010 live date is currently planned for 20 November 2010. 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 SR2010 is set in file: dni_03_01/run/classes/com.ibm.dni.msgstds.defset.fin2010.xml The activation date in this file is set to the planned S.W.I.F.T. SR2010 live date, 20 November 2010. You should not change this file in a production environment. Note for test environment: To activate the message definition set for SR2010 in a business OU for the test environment refer to section E10. 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 --------------------------------- Execute the CLI command files generated in step D4 in the following sequence and using the following user authorization: If dual authorization was not used (-dual NO): - dnfczmlc_2_sa_ent_all.cli by any SA If dual authorization was on (-dual YES): - dnfczmlc_5_sa_cre_ct_com.cli by the first SA (sa1) - dnfczmlc_5_sa_cre_ct_dep.cli by the second SA (sa2) 1. On the runtime system, log on to AIX as the indicated user and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Switch to the temporary directory you created in step D4.2 and execute the generated CLI command files by entering the following command: dnicli -s DNI_SYSADM -ou SYSOU -cft | tee -a PM07599cli.log where: The CLI command file name, for example dnfczmlc_6_sa_cre_co_com.cli. Note for test environment: To activate the message definition set for SR2010 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 SR2010 message definition set attribute value and commit the change: add -ou -ct DniMsgDomain -co DNIFIN -attr TestMsgDefSet -val fin2010 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 SR2010 message definition set. 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 ------------------------------------------------- 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 been changed in this PTF: -> API nodes: - DniStandardsProcessing To update your Toolkit environment: - If you modified samples that were provided by WebSphere BI for FN and want to keep your modifications, rename the projects. However, these saved projects will not be updated. - Delete the old WebSphere BI for FN provided projects in your workspace. - To reinstall the new versions of the Toolkit resources, follow the instructions provided in the section of 'Application Programming' that describe how to prepare the WebSphere Message Broker Toolkit workstation. - Clean all projects and redeploy the message flows that you built using nodes that were provided by WebSphere BI for FN. *------------------------------------------------------------------------------* * End of Activating * *------------------------------------------------------------------------------* F. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM07599 Base SWIFT SR2010: 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 2010. PM16878 Base CHANGE OF THE TRACE FILES NAMES GENERATED BY THE DNPRDU TOOL WITH -TRACE OPTION Formerly, when the DNPRDU generated trace and log files, the names of the trace and log files were misleading. The formats for trace file names were RDU_yyyyMMdd_HHmmssSSS_trc.log, and for log file names were RDU__yyyyMMdd_HHmmssSSS.txt (e.g. RDU_CT_yyyyMMdd_HHmmssSSS.txt). Now, the formats of the trace file names have been changed to RDU_yyyyMMdd_HHmmssSSS.trc. The formats of the log file names have been changed to RDU__yyyyMMdd_HHmmssSSS.log. G. Other changes ---------------- - MTXML New header schemas based on SWIFT MTXML GA version Formerly, the representation of FIN messages in WebSphere BI for FN V3.1.0 based on a pre-version of the SWIFT Standards Developer Kit. Now, with SR2010 the implementation of WebSphere BI for FN is changed to follow the header structure of SWIFT's GA version of the SWIFT Standards Developer Kit. - Message definition set activation Formerly, WebSphere BI for FN V3.1.0 requested to change the activation date for the message definition set for SWIFT validation rules by editing the source file in the installation directory directly. This contradicts the defined role concept from WebSphere BI for FN and is not feasible in a customer environment. Now, WebSphere BI for FN adds in CT: DniMsgDomain, CO: , e.g. 'DNIFIN' for SR2010 changes, attr: TestMsgDefSet, val: , e.g. 'fin2010' for SR2010 changes. This can be used to activate the new message definition set, e.g. for SR2010 changes, for test purposes. Example for activating the message definition set for SR2010 changes: add -ou BOU -ct DniMsgDomain -co DNIFIN -attr TestMsgDefSet -val fin2010 The message definition set will otherwise be activated automatically on S.W.I.F.T. SR2010 live date currently planned for 20 November 2010. On your production you can install this PTF before before S.W.I.F.T. SR2010 live date, but you must not change the activation date for the message definition set for SR2010. - ENI 1.1 Formerly, ENI 1.2 have been supported with WebSphere BI for FN V3.1.0 Message Management for Corporate to Bank interaction. Now, ENI 1.1 is supported to allow banks to be able to implement Exceptions and Investigations between my bank and correspondent banks. - Updated instruction text Formerly, the stored procedure verification section was missed in instruction.txt. The stored procedure verification needs to be checked before the FNCON was run. Now, the FNCON related text contains following expansion: Before carrying out these deployment instructions, ensure that your DB2 administrator has followed the procedure described in the 'Verifying the installation of the database routines' section of 'Planning, Installation, and Customization'. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++