================================================================================ ================================================================================ Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2009 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 Message Management PTF UK51830 for APAR PK97166 = Date 2009-12-21 = ================================================================================ ================================================================================ ================================================================================ Table of contents ----------------- A About this document B Summary of changes C Planning D Preparation E Activating F Cleaning up G Falling back to the previous PTF level H Re-migrating after a previous fallback I APAR details J 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 home directory of the application server profile. /usr/IBM/WebSphere/AppServer/profiles/AppSrv01 is used in examples. 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: PK97166 MM UPDATES FOR MESSAGE MANAGEMENT PM01882 MM WAS DEPLOY DOES NOT WORK IN A CLUSTERED APPLICATION SERVER ENVIRONMENT Functional changes: - The Message management components now support the following new message domains provided by WebSphere BI for FN Base: - DNIENI (SWIFTNet Exceptions and Investigations) - DNISNSYS (SWIFTNet System messages) - The Message management components now support the following new message definition sets provided by WebSphere BI for FN Base: - SWIFTNet Funds 4.1 and 4.2 - SWIFTNet Exceptions and Investigations 1.2 - SWIFTNet System messages 6.3 - The MER routing sample project DNI_DnqErSwiftNetFunds has been renamed to DNI_DnqErSwiftNetMX to indicate that the message flows are designed to handle message from the various MX domains. - The DnqEr(Fin/Msif)Output nodes now support a configurable ReplyToQueue. - The MER Facility context view now provides an explanation for SWIFTNet FIN NAK codes. - The MER FIN routing samples are enhanced to demonstrate handling of OSN messages. - SDF is now able to handle only messages of a certain OU subset of an export queue. - The DnqErFinOutput node is now able to send messages to the FMT service. - The message sets DNI_DnqMsgSetEnv and DNI_DnqMsgSetMqrfh2 have been enhanced to reflect the latest WebSphere BI for FN APIs. - Schema definitions for the SWIFT Standards Release 2009 are provided. Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Concepts and Components - Messages and Codes - System Administration - Application Programming - User's Guide - Information Center The following modules have been changed: /dnq_03_01/admin/data/DNQCOMMON.xml /dnq_03_01/admin/data/DNQER.xml /dnq_03_01/admin/data/DNQERBS.xml /dnq_03_01/admin/data/dnqccins.properties /dnq_03_01/admin/data/dnqccmqc.properties /dnq_03_01/admin/data/dnqcecro.cli /dnq_03_01/admin/data/dnqczaer.cli /dnq_03_01/admin/data/dnqczcah.lst /dnq_03_01/admin/data/dnqczcar.cli /dnq_03_01/admin/data/dnqczcat.cli /dnq_03_01/admin/data/dnqczceh.lst /dnq_03_01/admin/data/dnqczcer.cli /dnq_03_01/admin/data/dnqczcey.cli /dnq_03_01/admin/data/dnqczcob.cli /dnq_03_01/admin/data/dnqczcoy.cli /dnq_03_01/admin/data/dnqczdat.cli /dnq_03_01/admin/data/dnqczect.ddl /dnq_03_01/admin/data/dnqczegt.ddl /dnq_03_01/admin/data/dnqczeob.cli /dnq_03_01/admin/data/dnqczert.ddl /dnq_03_01/admin/data/dnqczwcf.txt /dnq_03_01/admin/toolkit/com.ibm.dnq.api.jar /dnq_03_01/admin/toolkit/dnq.project.interchange.zip /dnq_03_01/admin/toolkit/dnq.schemas.comibmdni.zip /dnq_03_01/run/appsrv/dnq.app.main.ear /dnq_03_01/run/appsrv/dnqccins.py /dnq_03_01/run/appsrv/dnqccrem.py /dnq_03_01/run/bin/dnqczmce /dnq_03_01/run/classes/com.ibm.dnq.attex.jar /dnq_03_01/run/classes/dnq.header.jar /dnq_03_01/run/classes/dnq.maxhf.api.jar /dnq_03_01/run/classes/dnq.print.jar /dnq_03_01/run/classes/dnqcbsdf.jar /dnq_03_01/run/config/com.ibm.dnq.maxhf.domain.DNIFIN.xml /dnq_03_01/run/config/com.ibm.dnq.maxhf.domain.DNIFUNDS.xml /dnq_03_01/run/data/dnqczcah.lst /dnq_03_01/run/data/dnqczcar.cli /dnq_03_01/run/data/dnqczcat.cli /dnq_03_01/run/data/dnqczceh.lst /dnq_03_01/run/data/dnqczcer.cli /dnq_03_01/run/data/dnqczcey.cli /dnq_03_01/run/data/dnqczcob.cli /dnq_03_01/run/data/dnqczcoy.cli /dnq_03_01/run/flows/DNQ_K_FIN1.bar /dnq_03_01/run/flows/DNQ_K_FIN2.bar /dnq_03_01/run/flows/DNQ_K_MX1.bar /dnq_03_01/run/flows/DNQ_K_UAR.bar /dnq_03_01/run/flows/DNQ_O_SFI.bar /dnq_03_01/run/flows/DNQ_O_SFO.bar /dnq_03_01/run/flows/DNQ_O_SMX.bar /dnq_03_01/run/flows/DNQ_P_CMD.bar /dnq_03_01/run/flows/DNQ_P_DSP.bar /dnq_03_01/run/flows/DNQ_P_PRT.bar /dnq_03_01/run/msg/dnqcbmsg.cat /dnq_03_01/run/msg/dnqccmsg.cat /dnq_03_01/run/msg/dnqcdmsg.cat /dnq_03_01/run/msg/dnqcemsg.cat /dnq_03_01/run/msg/dnqckmsg.cat /dnq_03_01/run/msg/dnqcomsg.cat /dnq_03_01/run/msg/dnqcpmsg.cat /dnq_03_01/run/msg/dnqcrmsg.cat /dnq_03_01/run/msg/dnqcwmsg.cat /dnq_03_01/run/res/dnqcbevt.xml /dnq_03_01/run/res/dnqccevt.xml /dnq_03_01/run/res/dnqccidf.xml /dnq_03_01/run/res/dnqcdevt.xml /dnq_03_01/run/res/dnqceevt.xml /dnq_03_01/run/res/dnqckevt.xml /dnq_03_01/run/res/dnqcoevt.xml /dnq_03_01/run/res/dnqcpevt.xml /dnq_03_01/run/res/dnqcpsdf.xml /dnq_03_01/run/res/dnqcrevt.xml /dnq_03_01/run/res/dnqcwevt.xml /dnq_03_01/run/samples/dnqcbsdf.sh The following modules are new: /dnq_03_01/admin/data/dnqczemt1.ddl /dnq_03_01/admin/data/dnqczemt2.ddl /dnq_03_01/admin/toolkit/dnq.schemas.swiftFin2009.zip /dnq_03_01/run/config/com.ibm.dnq.maxhf.domain.DNIENI.xml /dnq_03_01/run/config/com.ibm.dnq.maxhf.domain.DNISNSYS.xml /dnq_03_01/run/data/dnqczeob.cli The following modules are removed: /dnq_03_01/admin/toolkit/DNI_DnqErCommon.zip /dnq_03_01/admin/toolkit/DNI_DnqErSwiftNetFin.zip /dnq_03_01/admin/toolkit/DNI_DnqErSwiftNetFunds.zip C. Planning ----------- Install this PTF together with the product code of WebSphere BI for FN V3.1 Base, PTF UK49806, and PTF UK51812 and the product code of WebSphere BI for FN V3.1 MM and PTF UK49768 and either follow the instructions in "WebSphere BI for FN: Planning, Installation, and Customization" to do a new customization of your WBI-FN V3.1 environment or customize follow the instructions in "WebSphere BI for FN: Planning, Installation, and Customization" after current WebSphere BI for FN V2.2 Instance has been migrated to Version 3.1 Depending on which product services you use, you should install this PTF together with the product code of WebSphere BI for FN V3.1 MESSAGING SERVICES FOR SWIFTNET INTERACT AND FILEACT and WebSphere BI for FN V3.1 SUPPORT FOR SWIFTNET FIN, SUPPORT FOR SWIFTNET INTERACT, FINANCIAL MESSAGE TRANSFER. Please check the Readme's for UK51523 and UK51823 for more detailed information. Prerequisite and supersede information: This PTF requires the following PTFs: - UK49768 for APAR PK91869 (UPDATES FOR MESSAGE MANAGEMENT). - UK51812 for APAR PK97165 (WEBSPHERE BI FOR FN BASE UPDATES). This PTF should be installed together with: - UK51523 for APAR PK97164 (UPDATE FOR MESSAGING SERVICES FOR SWIFTNET INTERACT AND FILEACT). - UK51823 for APAR PK97167 (UPDATES FOR WEBSPHERE BI FOR FN SUPPORT FOR SWIFTNET FIN,SWIFTNET INTERACT,AND FMT). The MER enterprise application for use on a WebSphere Application Server running on AIX can be in conjunction with WebSphere BI for FN Message Management on z/OS. For Message Management on z/OS, please check the Readme for UK52940 for more detailed information. The Activating of MER enterprise application for use on a WebSphere Application Server running on AIX has to be done in the timeframe where you would have done step E11 in this readme document. Roles involved: The activities in this PTF involve the following roles: - Installer (root) D. Preparation -------------- D1. Installation ---------------- 1. Install this PTF using as described in the "Installing WebSphere BI for FN" section of "Planning, Installation, and Customization". 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 ---------------------------------------------- NOT APPLICABLE. E2. Stopping all application servers ------------------------------------ NOT APPLICABLE. E3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- NOT APPLICABLE. E4. Sharing the runtime directory structure ------------------------------------------- NOT APPLICABLE. E5. Backing up runtime database ------------------------------- 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 ------------------------------------------------------ NOT APPLICABLE. E9. Redeploy updated BAR files ------------------------------ NOT APPLICABLE. E10. Migrating configuration data --------------------------------- NOT APPLICABLE. E11. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ E11.1. Backing up the WebSphere Application Server configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. E11.2. Update the WebSphere Application Server environment - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Update the Java 2 security permissions. In a clustered application server environment you have to do this on each node that is to run the MER enterprise application. To add Java2 security permissions to the server.policy property file of a node do the following: 1. Open the server.policy file on the node by entering the following command: vi /properties/server.policy 2. Locate the section that already grants permissions to access the WebSphere BI for FN files: grant { permission java.io.FilePermission "/dni_03_01/run/classes/-", "read"; permission java.io.FilePermission "/dnq_03_01/run/classes/-", "read"; permission java.io.FilePermission "/dnq_03_01/run/config/-", "read"; permission java.util.PropertyPermission "*", "read"; }; 3. Append the following lines to the end of the section, but before the closing curly brace: permission com.ibm.websphere.security.WebSphereRuntimePermission "WSSecureMap"; permission com.ibm.websphere.security.WebSphereRuntimePermission "accessLTPAServerObject"; permission java.lang.RuntimePermission "accessDeclaredMembers"; permission java.lang.RuntimePermission "modifyThreadGroup"; permission java.lang.RuntimePermission "modifyThread"; permission java.net.SocketPermission "*", "resolve,connect"; permission org.osgi.framework.ServicePermission "*", "get"; 4. Save and close the file. E11.3. Migrating the enterprise application - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. E12. Restarting all sessions and services ----------------------------------------- NOT APPLICABLE. E13. Updating the Toolkit development environment ------------------------------------------------- NOT APPLICABLE. *----------------------------------------------------------------------------* * End of Activating * *----------------------------------------------------------------------------* F. Cleaning up -------------- NOT APPLICABLE. G. Falling back to the previous PTF level ----------------------------------------- NOT APPLICABLE. *----------------------------------------------------------------------------* * End of Fallback * *----------------------------------------------------------------------------* H. Re-migrating after a previous fallback ----------------------------------------- NOT APPLICABLE. *----------------------------------------------------------------------------* * End of Re-migration * *----------------------------------------------------------------------------* I. APAR details --------------- Fixes for the following APARs are contained in this PTF: PK97166 MM UPDATES FOR MESSAGE MANAGEMENT WebSphere BI for FN Message Management was updated: - The new message domains DNIENI and DNISNSYS are supported. - The DnqEr(Fin/Msif)Output nodes now support a configurable ReplyToQueue. - The MER Facility context view now provides an explanation for SWIFTNet FIN NAK codes. - The MER FIN routing samples are enhanced to demonstrate handling of OSN messages. - The DnqErFinOutput node is now able to send messages to the FMT service. - New schema definitions for the SWIFT Standards Release 2009 are provided. PM01882 MM WAS DEPLOY DOES NOT WORK IN A CLUSTERED APPLICATION SERVER ENVIRONMENT The deployment instructions tell you to deploy the MER enterprise application in two steps: - use dnqccins.py to deploy the resources required only once - use dnqccins.py to deploy the resources required once per server Formerly, the dnqccins.py failed in this scenario. Only if you copied the property files created for both cases in a single directory and run dnqccins.py the installation was successful. Now you can use installation script dnqccins.py as described in the deployment instructions. J. Other changes ---------------- MER Facility: - The uninstallation script for the MER enterprise application did not correctly remove it. - Detection for situations where server and browser are out of synch was added: - if more than one message is opened in one browser session by a user at a time - if a message is used from the local browser cache which does not correspond to the actual version of this message on the server A warning message is issued in such situations. - The MER facility tries to unlock the current message in error situations. - Double-byte and Unicode characters in the comment field of templates were not handled correctly. MER and general purpose routing: - No user ID was recorded in Message History for backed out MER messages. - Repaired NAK message could not be sent successfully from the MER facility to the DNF_ILC_FIN service. - Header fields for routing and MWH of a FUNDS message are tried to extract even if the message is unparsable. - In some cases MWH records could not be written for SWIFTNet FIN messages in the MM routing adapter nodes. SDF: - SDF events were missing for some warning and error conditions. - The SDF import command failed when only command line parameters were used and no environment variables were set. Printing: - Three attributes of COs of CT DnqPrintQueue are not mandatory any more since default values have been implemented as follows: PrintFormatHeader = 3 Include message history and other RFH2 entries PrintFormatMessage = 1 Format output, but print only fields with data OrderSize = 1 Each message will be a separate order. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++