============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2011 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 UK69903 for APAR PM35865 Date 2011-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 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: PM35865 MM MESSAGE MANAGEMENT UPDATES FOR SWIFT SR2011 CHANGES Functional changes: - Adaptions for S.W.I.F.T. Standard Release 2011 (SR2011) changes Documentation updates: The following manuals have been changed: - none The following modules have been changed: /dnq_03_01/admin/data/dnqczcat.cli /dnq_03_01/admin/data/dnqczcob.cli /dnq_03_01/admin/toolkit/dnq.schemas.comibmdni.zip /dnq_03_01/run/bin/dnqczmcq /dnq_03_01/run/bin/dnqczmce /dnq_03_01/run/config/com.ibm.dnq.maxhf.domain.DNIFIN.xml /dnq_03_01/run/appsrv/dnq.app.main.ear /dnq_03_01/run/data/dnqczcat.cli /dnq_03_01/run/data/dnqczcob.cli /dnq_03_01/run/classes/dnqcbsdf.jar The following are new modules: /dnq_03_01/admin/toolkit/dnq.schemas.swiftFin2011.zip /dnq_03_01/run/config/com.ibm.dnq.maxhf.defset.fin2009.xml The following modules are removed: /dnq_03_01/run/config/com.ibm.dnq.maxhf.defset.fin2010.xml 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: - UK58149 for APAR PM13945 (MM 3.1.0.4, SR2010: MESSAGE MANAGEMENT UPDATES FOR SWIFT SR2010 CHANGES) - UK69902 for APAR PM35864 (Base 3.1.0.8, SWIFT SR2011: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION) This PTF should be installed together with: - UK69437 for APAR PM38599 (CSN 3.1.0.7, SR2011: FIN/FMT UPDATES TO SUPPORT NEW SSI MESSAGES) This PTF supersedes the following PTFs: - UK59976 for APAR PM23170 (WBIFN MESSAGE MANAGEMENT PART FOR BASE APAR PM20904) - UK61129 for APAR PM22475 (NAK CODES FOR SR2010 CHANGES). - UK69512 for APAR PM37384 (IMPORT PROBLEMS WHEN SOURCE MESSAGE INCLUDES CRLF CODES). Update your MER enterprise application as described in step E11 of this readme document. Roles involved: The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - WebSphere MB application developer (uwmbad1) - WebSphere MB administrator (uwmba1) - WebSphere Application Server operator (uwaso1) - WebSphere Application Server administrator (uwas1) - First WebSphere BI for FN system configuration administrator (sa1) - Second WebSphere BI for FN system configuration administrator (sa2) D. Preparation -------------- D1. Installation ---------------- 1. This PTF requires the Base PTF V3.1.0.8 (UK69902 for APAR PM35864) and the previous Message Management for Multiplatforms V3.1.0.4 (UK58149 for APAR PM13945), please install the Base PTF V3.1.0.8 first. This PTF will overwrite partial installed files. After installation, the V.R.M.F will upgrade to V3.1.0.5. The detail steps of installation could be found in "Installing WebSphere BI for FN", in the "Planning, Installation and Customization" manual. 2. Share the files in the /dnq_03_01/admin directory with your customization system. 3. Ensure that the group ownership of the /dnq_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 /dnq_03_01/admin 4. Share the files in the following directories with your runtime systems: /dnq_03_01/run These files are already needed during the preparation phase and do not influence normal operation. 5. Set the group ownership of these directories and files to group dnilpp. To do this, enter the following command in AIX: chgrp -R dnilpp /dnq_03_01/run D2. Steps on a customization system ----------------------------------- NOT APPLICABLE. 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.sh stores the CLI command files which will contain the configuration migration statements. 4. Switch to this directory and enter the following command: dnfczmlc.sh -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.sh 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 3. dnfczmlc_6_sa_cre_co_com.cli 4. dnfczmlc_6_sa_cre_co_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. Commit, approve and deploy the OU SYSOU. Close the CLI session: > .quit This PTF changes the following configuration entities: - adds attributes for the new Messages Types of SWIFT Standard Release 2011 changes (FIN670, FIN671, FIN070, FIN071) to CT DnqERMessageRightsDNIFIN - adds these new attributes also to the COs named 'ALL' of CT DnqERMessageRightsDNIFIN 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 ------------------------------------ Stop all application servers. 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 /dnq_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 shell: chgrp -R dnilpp /dnq_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 --------------------------------- Execute the CLI command files generated in step D3 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) - dnfczmlc_6_sa_cre_co_com.cli by the first sa (sa1) - dnfczmlc_6_sa_cre_co_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 D3.2 and execute the generated CLI command files by entering the following command: dnicli -s -ou SYSOU -cft | tee -a PM35865cli.log where: DNI_SYSADM for files executed by the system configuration administrators, abbreviated as sa DNI_SECADM for files executed by the security administrators, abbreviated as ua The CLI command file name, for example dnfczmlc_5_sa_cre_ct_com.cli. E11. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ E11.1. Backing up the WebSphere Application Server configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Which resources you need to back up depends on whether you use a clustered application server environment or a single server: - If you have a clustered application server environment, back up your deployment manager profile and all other profiles on all nodes that belong to the cluster. - If you have a single application server environment, back up the application server profile. As the WebSphere Application Server operator (uwaso1), issue the following command for each profile that is to be backed up: /bin/backupConfig.sh where represents the file name under which the backup should be stored. E11.2. Update the WebSphere Application Server environment - - - - - - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. E11.3. Migrating the enterprise application - - - - - - - - - - - - - - - - - - - - - - Start the application server on which the enterprise application runs. If you use a clustered application server environment, start the deployment manager, node agents, and all members of the application server cluster. Issue the following command with the user ID of the WebSphere Application Server operator (uwaso1): /bin/wsadmin.sh -user -password -lang jython -f /dnqccupd.py where: The user ID of the WebSphere Application Server administrator (uwas1). The password of the user. The path to the migration script: /dnq_03_01/run/appsrv. Path to the MER ear file: /dnq_03_01/run/appsrv/. 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, refer to the section of 'System Administration' 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: PM35865 MM MESSAGE MANAGEMENT UPDATES FOR SWIFT SR2011 CHANGES SR2011: Message Management updates for SWIFT SR2011 changes Fixes for the following APARs from superseded PTFs are also contained in this PTF: PM22475 MM NAK CODES FOR SR2010 CHANGES THE SWIFT NAK CODES HAVE BEEN CHANGED TO REFLECT THE CHANGES WITH SWIFT NOVEMBER 2010 CHANGES (SR2010). NAK codes changed for SR2010: B01, C01, C02, C03, C05, C28, C29, C32, C34, C35, C38, C39, C41, C42, C50, C58, C59, C62, C65, C71, C80, C87, C89, D07, D19, D25, D29, D36, D56, D57, D92, E03, E24, E37, E41, E57, E58, E59, E76, E77, E78, E80, E82, E84, E87, E99, G05, G08, G17, G24, H55, Knn, M75, S72, T03, T04, T14, T27, T39, T45, T47, T61, T85, T86, U00, V21, V62 NAK codes new for SR2010: S76, V69, V70, V71, V72, V73, V74 PM23170 MM WBIFN MESSAGE MANAGEMENT PART FOR BASE APAR PM20804 This PTF for APAR PM23170 provides the Message Management parts for the Base PTF for the APAR PM20904 PM37384 MM IMPORT PROBLEMS WHEN SOURCE MESSAGE INCLUDES CRLF CODES Formerly, when message contains CRLF codes the SDF import received error message DNIY0089E. Now, the CRLF codes are handled correctly. G. Other changes ---------------- - Extraction rules for 'fin2009' are now handled as exceptional case. Extraction rules for 'fin2010' and 'fin2011' are handled as default. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++