============================================================================== ============================================================================== 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 UK77970 for APAR PM55951 = Date 2012-04-30 = ============================================================================== ============================================================================== ============================================================================== 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 ---------------------- If you install this PTF as part of the migration from WebSphere BI for FN Version 3.1.0 to Version 3.1.1 then do not follow the steps in this readme, but those described in the Migration Information 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 /usr/lpp is used in examples. The customization directory. The directory /var/dniv311/cus is used in examples. The deployment directory. The directory /var/dniv311/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 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: PM55951 Base DNICZBAP THROWS NULLPOINTEREXCEPTION DURING RECUSTOMIZATION PM56109 Base RMA WEB-APPLICATION LOGOUT LEEDS INTO UNAUTHORIZED SESSIONREQUESTEXCEPTION PM53395 Base RESTRICT AUTHORISATIONS OF USER URUNDA1 (USER TO ACCESS RUNTIME DATA) PM56106 Base RESPONSE WITH MULTIPLE FOLDER NOT PROCESSED IN RMA PM55962 Base IMPROVE TRACING IN DNICIN.LIL PM60225 Base LINE PARSER IMPORT FAILS. ERROR MESSAGES INDICATED THE POSITION ONLY PM57890 Base NO RESPONSE DURING WRONG .QUIT CMD FROM DNICLI PM58267 Base DNPRDU CREATES EMPTY TRACEFILE Additional functional changes: - dnfczmlc considers setting of DniEscapeCharacter Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Messages and Codes - System Administration The following modules have been changed: /dniv311/admin/appsrv/res/dnf.rma.web.ear /dniv311/admin/appsrv/res/dni.home.ear /dniv311/admin/data/DNFRMA.xml /dniv311/admin/data/DNIWEBHOME.xml /dniv311/admin/data/dni.properties /dniv311/admin/data/dni.xml /dniv311/admin/data/DNICOMMON.xml /dniv311/admin/data/DNFRMR.xml /dniv311/admin/data/dnicdcig.ddl /dniv311/admin/data/dnfczacg.ddl /dniv311/admin/data/dnfczlcg.ddl /dniv311/run/bin/dnicli /dniv311/run/bin/dniczbap /dniv311/run/bin/dnfczmlc.sh /dniv311/run/bin/dnfczml2.awk /dniv311/run/classes/dniczbap.jar /dniv311/run/classes/dnprdu.jar /dniv311/run/classes/dnicvcks_seni1.jar /dniv311/run/classes/dnicvrls_seni1.jar /dniv311/run/classes/dnicvcks_sfmtxml09.jar /dniv311/run/classes/dnicvrls_sfmtxml09.jar /dniv311/run/classes/dnicvcks_sfmtxml10.jar /dniv311/run/classes/dnicvrls_sfmtxml10.jar /dniv311/run/classes/dnicvrls_sfmtxml11.jar /dniv311/run/classes/dnicvcks_sfmtxml11.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/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 /dniv311/run/classes/dnicvcks.jar /dniv311/run/jplugin/dnf.rma.tr.jar /dniv311/run/lil/dnicin.lil /dniv311/run/msg/dnfclmsg.cat /dniv311/run/msg/dniccmsg.cat /dniv311/run/msg/dnicymsg.cat /dniv311/run/res/dnfclmsg.xml /dniv311/run/res/dnicomsg.xml /dniv311/run/res/dnicymsg.xml The following modules are new: /dniv311/admin/data/dnicdm3g.ddl /dniv311/admin/data/dnfcza1g.ddl /dniv311/admin/data/dnfczl1g.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 PTF: - PTF UK74550 for APAR PM47966 (Base 3.1.1.4) This PTF supersedes the following PTF: - none Roles involved: The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - DB2 administrator (udb2adm1) - WebSphere MB administrator (uwmba1) - WebSphere Application Server administrator (uwasa1) - WebSphere Application Server operator (uwaso1) 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 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 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/_UK77970_temp.cdd > supplement cdd/_UK77970_temp.cdd cdd/_UK77970.cdd Open the supplemented CDD and search for each occurrence of the new placeholder DNIvUGRP and specify the appropriate placeholder values. > import cdd/_UK77970.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: - DBGNT * new group DNIvUGRP introduced for user URUNDA1 This group receives the following privileges on DB2 objects: + Service Bundle DNICOMMON: - INSERT,SELECT,UPDATE,DELETE priveleges on DNIvSN.DNI_EVENT, and DNIvSN.DNI_UPREF + Service Bundle DNFRMA: - INSERT,SELECT,UPDATE,DELETE priveleges on DNIvSN.DNF_RMAH, DNIvSN.DNF_RMQH, DNIvSN.DNF_RMQS, and DNIvSN.DNF_RMSS + Service Bundle DNFRMR: - INSERT,SELECT,UPDATE,DELETE priveleges on DNIvSN.DNF_RMRL, DNIvSN.DNF_RMAD, DNIvSN.DNF_RMAL, DNIvSN.DNF_RMAP, DNIvSN.DNF_ASP, DNIvSN.DNF_ASP_TPL, and DNIvSN.DNF_ASP_TPL_RMAF - EXECUTE privilege on procedure DNIvSN.DNFCHECKRMAUTH * new placeholder DNIvUGRP - CFGPF (if SVB DNFRMA is assigned) * instructions and files required to update the WebSphere BI for FN enterprise applications running in the application server 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. - 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, sessons, and services" in "WebSphere BI for FN for Multiplatforms: System Administration", SH12-6943. E2. Stopping all application servers ------------------------------------ NOT APPLICABLE. E3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- NOT APPLICABLE. 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 -------------------------------------------------------------- Follow the deployment instructions that were created in step D2.4 with the following exception: - do not execute the instructions provided for resource class CFGPF now; you will use them in step E11.3. E7. Additional activities ------------------------- E7.1. DB2 related activities ---------------------------- NOT APPLICABLE. E7.2. WebSphere MB related activities ------------------------------------- NOT APPLICABLE. E7.3. WebSphere MQ related activities ------------------------------------- NOT APPLICABLE. E7.4. External security manager related activities -------------------------------------------------------- On the runtime system of the broker server, log on to AIX as root. Create new group for placeholder DNIvUGRP. Remove user URUNDA1 from group DNIvSGRP and add to group DNIvUGRP. 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 ------------------------------------------------------------ E11.1. Backing up the WebSphere Application Server configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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: On Windows: \bin\manageprofiles.bat -backupProfile -profileName -backupFile On other platforms: /bin/manageprofiles.sh -backupProfile -profileName -backupFile where represents the installation directory of the application server and 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 - - - - - - - - - - - - - - - - - - - - - - If the instructions created in step D2.4 contain the resource class CFGPF, follow this section now to update the enterprise applications. Before starting to update the enterprise applications, start the application server on which the enterprise application runs. If you use a clustered application server environment, start the deployment manager, node agent, and all members of the application server cluster. E12. Restarting all sessions and services ----------------------------------------- 1. 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, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration", SH12-6943. 2. A subscription to receive FileAct events is needed for each SAG that the MSIF Transfer Service uses to conduct file transfers. Because one of the previous steps erased all subscriptions from the WebSphere BI for FN database, for each SAG that the MSIF Transfer Service is to use to conduct file transfers, resubscribe manually by issuing the "subscribe" command. E13. Updating the Toolkit development environment ------------------------------------------------- NOT APPLICABLE. *-----------------------------------------------------------------------------* * End of Activating * *-----------------------------------------------------------------------------* F. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM55951 Base DNICZBAP THROWS NULLPOINTEREXCEPTION DURING RECUSTOMIZATION Formerly, when during re-customization the CDP did generate a BTDD.xml that did not specify the 'action' attribute for each broker the DNICZBAP terminated with a NullPointerException. Now, DNICZBAP can parse such BTDD documents. PM56109 BASE RMA WEB-APPLICATION LOGOUT LEEDS INTO UNAUTHORIZED SESSIONREQUESTEXCEPTION Formerly, when a user logged out of the WebSphere BI for FN RMA web application when the LTPA token was already expired, the error "SRVE0232E: Internal Server Error" occured, caused by an UnauthorizedSessionRequestException. Now, the logout handles this exception internally. PM53395 Base RESTRICT AUTHORISATIONS OF USER URUNDA1 (USER TO ACCESS RUNTIME DATA) In an application-server authentication alias for JDBC data sources, the runtime data accessor user ID is used to authenticate the connection between an WebSphere BI for FN enterprise application (MER, RMA) and the runtime database. The recommended user ID is URUNDA1. Formerly this user ID has been a member of group DNIvSGRP. DNIvSGRP is vested with authority regarding queues, channels and database resources. This group comprises more privileges than required. Now, a new group DNIvUGRP has been specifically designed for URUNDA1 to restrict access rights to those resources that this user needs. PM56106 Base MSIF Response with multiple folder not processed in RMA Formerly, when a negative response with multiple reason codes was received, all but the first reason codes have been ignored. Now, when a negative response with multiple reason codes is received, for each reason code, except for the first one, RMA creates event DNFL2183E. Please refer also to WebSphere BI for FN MSIF PTF UK75563 and APAR PM54677. PM55962 Base IMPROVE TRACING IN DNICIN.LIL Formerly, when the CIN encountered an internal error, the trace did not provide sufficient information to investigate the problem. Now, tracing has been improved to provide more information in case of internal error. PM57890 Base NO RESPONSE DURING WRONG .QUIT CMD FROM DNICLI Formerly, when dnicli command '.quit' was issued with parameters dnicli did not issue an error message and did not end. Now, when dnicli command '.quit' is issued with parameters dnicli responds with error message DNIK2508E. PM58267 Base DNPRDU CREATES EMPTY TRACEFILE Formerly, when a trace level was set to SEVERE or WARNING, dnprdu created an empty trace file, even when no SEVERE or WARNING messages occured. Now, when one of the trace levels is set and no SEVERE or WARNING messages occure dnprdu deletes the trace file. G. Other changes ---------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++