============================================================================== ============================================================================== 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 UK62356 for APAR PM26603 Date 2010-12-23 ============================================================================== ============================================================================== ============================================================================== 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 name of the runtime database. The name DNIDBRUN is used in examples. The names of users, groups, files, and directories are the same as those used in the '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: PM18765 Base DNICZBAP SHOWS THE INCORRECT DEPLOY INFORMATION WITH 'PREPARE' PARAMETER PM18763 Base DNIZ9361E : THE PLACEHOLDER 'COM.IBM.DNF.DNFVMWX' WITH SCOPE 'OU' NOT SPECIFIED. PM19975 Base CHANGE CDP FOR USING ITS OWN /DEFS DIRECTORY PM20374 Base LIST COMMAND INCLUDES THE RESPONSE TO THE PREVIOUS COMMAND IF PRECEEDED BY A SYNTAX ERROR IN DNICLI PM23689 Base WEBSPHERE BI FOR FN MESSAGE REPORTING ENHANCEMENTS USING IBM COGNOS - FRAMEMANAGER DATA MODEL PM23323 Base IMPROVE TRACING IN MESSAGE VALIDATION, ESPECIALLY FOR "LOADOBJECT" FAILURES. PM20904 Base DNFCZMLC MAY CREATE TOO MUCH OUTPUT PM23375 Base DNFCZMLC DID NOT CHECK THE DB WITH THE CT DNIMSGDOMAIN TO GENERATE THE CLI OUTPUT PM24366 Base CHANGE SR2010 ACTIVATIONDATE/TIME FROM 0:00 20NOV GMT TO 16:00 20NOV GMT TIME PM26603 Base DATABASE CHANGES REQUIERED FOR PTF FOR APAR PM24367 (AMOUNT NOT ALWAYS STORED IN FIN MWH) Functional changes: - Reporting enhancements using IBM Cognos Documentation updates: - Messages and Codes - Refer to WebSphere Business Integartion for Financial Networks download document titled "WebSphere BI for FN V3.1 Reporting enhancements using IBM Cognos - Framemanager" on the web site Support & Downloads. The following modules have been changed: /dni_03_01/admin/bin/dnicdp.jar /dni_03_01/run/classes/dni.msgstds.impl.jar /dni_03_01/run/classes/dnicvcks.jar /dni_03_01/run/classes/dniczbap.jar /dni_03_01/run/samples/DniReconCBI.zip /dni_03_01/admin/data/DNICOMMON.xml /dni_03_01/admin/data/DNIOU.xml /dni_03_01/admin/data/dnicdcwt.ddl /dni_03_01/run/bin/dnfczmcf /dni_03_01/run/bin/dnfczml2.awk /dni_03_01/run/bin/dnfczmlc.sh /dni_03_01/run/bin/dnicli /dni_03_01/run/classes/dnicvcks_sfunds41.jar /dni_03_01/run/classes/dnicvrls_sfmtxml10.jar /dni_03_01/run/doc/dni.msgstds.api.doc.zip The following are new modules: /dni_03_01/admin/data/dnicdo01.ddl 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: - UK58142 for APAR PM07599 (SWIFT SR2010: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION.) This PTF supersedes the following PTFs: - UK61132 for APAR PM23689 - UK59975 for APAR PM20904 - UK60826 for APAR PM24366 Roles involved: The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - DB2 administrator (udb2adm1) - WebSphere MB administrator (uwbimba1) 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. - 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. 2. Stop all WebSphere BI for FN message brokers. 3. Install this PTF using as described in the 'Installing WebSphere BI for FN' in 'Planning, Installation and Customization' manual. 4. Share the files in the /dni_03_01/admin directory with your customization system. 5. 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 4. 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 5. 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/_PM26603.cdd > import cdd/_PM26603.cdd > prepare This step updates the customized administrative scripts in the directory '//admin' and generates deployment data for migration of the run-time system for the following resource classes: - DB * Message Warehouse table DNIMWH_PT_DNIvOU changed (Column MWH_AMOUNT changed) Deployment instructions are generated in the file '///instructions.txt'. You will need this later in the 'E. Activating' section. 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 --------------------------------------------------- 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. - Release SWIFTNet SnF queues. - Stop the MSIF Message Transfer service. - Stop the Enhanced InterAct service. - 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 -------------------------------------------------------------- Back up the WebSphere BI for FN runtime database: 1. On the system where the DB2 subsystem resides, log on to AIX as a DB2 administrator (udb2adm1). 2. Issue the following command: db2 backup db E6. Following the deployment instructions created in step D2 -------------------------------------------------------------- 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 - - - - - - - - - - - - - - - - - - - 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 service. - Acquire SWIFTNet SnF queues. - Start the applications that send requests to WebSphere BI for FN. For further information, see "Administering and operating components, sessions, and services" in "WebSphere Business Integration for Financial Networks for Multiplatforms - System Administration" E13. Updating the Toolkit development environment ------------------------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Activating * *------------------------------------------------------------------------------* F. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM18765 Base DNICZBAP SHOWS THE INCORRECT DEPLOY INFORMATION WITH 'PREPARE' PARAMETER Formerly, the bap tool showed incorrect message (DNIZ1460E - Deploying the bar file 'DNI_TIMER.bar' to the execution group 'default' at broker 'WFNBRK' failed.) to user, only when a prepare command was executed, and not any deploy flow action to broker. When the error message was issued the returncode was 0, and the bap tool did not define any return code after encountering errors. Now, this has been changed. PM18763 Base DNIZ9361E : THE PLACEHOLDER 'COM.IBM.DNF.DNFVMWX' WITH SCOPE 'OU' NOT SPECIFIED. Formerly, some CDP messages indicated problems with a place holder as "E" messages, although the CDP continued processing. Now, the following messages have been changed to "I" messages: DNIZ9096I, DNIZ9097I, DNIZ9099I, DNIZ9100I, DNIZ9101I, DNIZ9102I, DNIZ9105I, DNIZ9106I. Another message is following that explains how the CDP is handling the cause for these messages, and is flagged as an "E" message, in case the CDP stops processing. PM19975 Base CHANGE CDP FOR USING ITS OWN /DEFS DIRECTORY Formerly, the CDP, running in migration mode, was using the WebSphere BI for FN installation directory to store temporary files. It failed because the CDP must not have write permissions for those directories. Now, the CDP is using its own customization definition directory to store temporary files. PM20374 Base LIST COMMAND INCLUDES THE RESPONSE TO THE PREVIOUS COMMAND IF PRECEEDED BY A SYNTAX ERROR IN DNICLI Formerly, when a syntax error occured in dnicli before a list command was issued, the response to the list command included the response to the previous command, too. Now, this behavior is corrected and only the response to the list command is shown. PM23689 Base WEBSPHERE BI FOR FN MESSAGE REPORTING ENHANCEMENTS USING IBM COGNOS - FRAMEMANAGER DATA MODEL This APAR has been opened to provide a PTF, which delivers a datalayer that allows to access WebSphere BI for FN tables (Message Warehouse and Audit). Refer to WebSphere Business Integartion for Financial Networks download document titled "WebSphere BI for FN V3.1 Reporting enhancements using IBM Cognos - Framemanager" on the web site Support & Downloads. Refer also to Message Management PTF UK61192 for APAR PM22470. PM23323 Base IMPROVE TRACING IN MESSAGE VALIDATION, ESPECIALLY FOR "LOADOBJECT" FAILURES. Formerly, when problems to load the classes for the validation rules in message validation occured return and reason codes were mostly not available. Now, more detail information of the exceptions is shown. PM20904 Base DNFCZMLC MAY CREATE TOO MUCH OUTPUT Formerly, when more than one business OU was configured, and service bundles assigned to this various OUs were not the same, dnfczmlc nevertheless creates configuration objects (COs) for all service bundles in all business OUs. For example, if business OU OUA was configured for FIN (service bundles DNFFIN and DNFRMR) and business OU OUB was configured for MSIF (DNFEFAS), dnfczmlc created scripts to add MSIF configuration objects in OUA, and FIN and RM configuration objects in OUB. Now, dnfczmlc only creates scripts to add COs in OUs when the corresponding service bundle is assigned to this OU. PM23375 Base DNFCZMLC DID NOT CHECK THE DB WITH THE CT DNIMSGDOMAIN TO GENERATE THE CLI OUTPUT Formerly, when PTF UK58117 was installed, then dnfczmlc output cli > cre -ct DniMsgDomain -desc 'Message domain specific configuration' > add -ct DniMsgDomain -attr TestMsgDefSet -type R was performed, and after that dnfczmlc was executed again, the ct DniMsgDomain and attr TestMsgDefSet were generated twice. Now, this has been corrected. The ct DniMsgDomain and attr TestMsgDefSet are not generated twice. PM24366 Base CHANGE SR2010 ACTIVATIONDATE/TIME FROM 0:00 20NOV GMT TO 16:00 20NOV GMT TIME The activation date/time for the Standard Release 2010 changes has been changed from 20 November 2010, 00:00 hours to 20 November 2010, 16:00 hours. PM26603 Base DATABASE CHANGES REQUIERED FOR PTF FOR APAR PM24367 (AMOUNT NOT ALWAYS STORED IN FIN MWH) Apar PM24367 describes the problem that huge amounts using the full 15 digits allowed per SWIFT field specification are not extracted from the FIN message and the corresponding fields in the Message Warehouse are not filled. The fix for Apar PM24367 within the WebSphere BI for FN FIN component requires a corresponding database change within the WebSphere BI for FN Base component (Base Apar PM26603), too. The fix for Base Apar PM26603 will provide the necessary change for the Message Warehouse table. The amount field is expanded to support the full 15 digits allowed per SWIFT field specification. H. Other changes ---------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++