============================================================================== ============================================================================== 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 UK90052 for APAR PM74136 Driver level: 2502 = Date 2012-12-21 = ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Installation E APAR details F Other changes G Known issues 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. During the installation phase of this PTF 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 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 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: PM74136 BASE UPDATES FOR ADMINISTRATION AND OPERATION PM76700 BASE WSADMIN COULD NOT UPDATE CFGPH000.APPLIST PROPERLY (DNPW1109E: APPLICATION LIST IS EMPTY) PM77821 BASE MODIFY THE CONTENT OF THE ERROR MESSAGE "DNFL9430E" TO BE CLEARLY DISPLAYED ON MERVA SCREEN PM77819 BASE DNICPD/DNICDPM IMPROVEMENTS NECESSARY TO DETERMINE THE STATE OF A PREVIOUS ACTION AND AVOID PROBLEMS DURING APPLYING MAINTENANCE PM76975 BASE REMOVE CHECK FOR CHARACTER 8 IN RECEIVERS BIC, NOW ALLOW "1" PM73199 BASE DNICONFIGSVB WAS NOT REMOVED WHILE USER REMOVE A DNFEFAS SVB PM74802 BASE UPDATE CIN FOR MSIF APAR PM72542 PM76092 BASE JAVA OUTOFMEMORY ERROR WHILE RUNNING INSTALLER IN GUI MODE TO INSTALL WBIFN PTF Functional changes: - a new role group concept is introduced in DNI_SECADM - new message domains are introduced: DNIMX, DNIBULKPMT, DNICASHREP, DNICLEARING, DNICOLLMGMT, DNICORPACT, DNIEINVOICING, DNIPROXYVOTING, DNISWIFTREMIT, DNITRANSREP - WebSphere MQ 7.1 is now supported if you use WebSphere Message Broker V7 FP5 - a new web-based UI for administration and operation 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 manual is new: - Administration and Operation Facility User's Guide The following modules have been changed: /dniv311/admin/appsrv/dniapplication.py /dniv311/admin/appsrv/dnicommon.py /dniv311/admin/appsrv/dnidatasource.py /dniv311/admin/appsrv/dniinstapi.py /dniv311/admin/appsrv/dnimain.py /dniv311/admin/appsrv/dnisetup.py /dniv311/admin/appsrv/res/dnf.rma.web.ear /dniv311/admin/appsrv/res/dni.home.ear /dniv311/admin/bin/dnicdp.jar /dniv311/admin/data/DNFRMA.xml /dniv311/admin/data/DNFRMR.xml /dniv311/admin/data/DNICOMMON.xml /dniv311/admin/data/DNIOU.xml /dniv311/admin/data/DNIWEBHOME.xml /dniv311/admin/data/DnfRma.py /dniv311/admin/data/DnfRma_upd.py /dniv311/admin/data/DniWas.py /dniv311/admin/data/DniWebHome.py /dniv311/admin/data/DniWebHomePy.properties /dniv311/admin/data/DniWebHome_upd.py /dniv311/admin/data/dnf.properties /dniv311/admin/data/dnf.xml /dniv311/admin/data/dnfclaph.applist /dniv311/admin/data/dnfczl02.ddl /dniv311/admin/data/dnfczlcr.ddl /dniv311/admin/data/dnfmzl8m.ddl /dniv311/admin/data/dnicdcat.ddl /dniv311/admin/data/dnicdccp.ddl /dniv311/admin/data/dnicdcct.ddl /dniv311/admin/data/dnicdcet.ddl /dniv311/admin/data/dnicdcig.ddl /dniv311/admin/data/dnicdcog.ddl /dniv311/admin/data/dnicdcts.ddl /dniv311/admin/data/dnicdcup.ddl /dniv311/admin/data/dnicdcwt.ddl /dniv311/admin/data/dnicddat.ddl /dniv311/admin/data/dnicddco.ddl /dniv311/admin/data/dnicddct.ddl /dniv311/admin/data/dnicddts.ddl /dniv311/admin/data/dnicddup.ddl /dniv311/admin/data/dnicdhit.ddl /dniv311/admin/data/dnicdico.ddl /dniv311/admin/data/dnicdict.ddl /dniv311/admin/data/dniczbdt.txt /dniv311/admin/data/dniczcdd.xml /dniv311/admin/data/dniczdlq.mq /dniv311/admin/data/dniczrlq.mq /dniv311/admin/data/dniczrra.txt /dniv311/admin/data/dniczrtf.txt /dniv311/admin/data/dniczwcf.txt /dniv311/admin/data/dnixzr02.def /dniv311/admin/data/dnixzs02.def /dniv311/admin/samples/dniczcdp.ini /dniv311/admin/toolkit/com.ibm.dni.api.jar /dniv311/admin/toolkit/dni.schemas.comibmdni.zip /dniv311/admin/toolkit/dni.schemas.swiftFin2010.zip /dniv311/admin/toolkit/dni.schemas.swiftFin2011.zip /dniv311/admin/toolkit/dni.schemas.swiftFin2012.zip /dniv311/run/bin/dnfczml2.awk /dniv311/run/bin/dnfczmlc.sh /dniv311/run/bin/dnfczrma /dniv311/run/bin/dnfczrmc /dniv311/run/bin/dnfczrmo /dniv311/run/bin/dnfczrmr /dniv311/run/bin/dnicli /dniv311/run/bin/dnixdcsp /dniv311/run/bin/dnprdu /dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2010.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2011.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2012.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.funds40.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.funds42.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.funds43.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.funds44.xml /dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIFIN.xml /dniv311/run/classes/com.ibm.dni.msgstds.ibmapi.CommonMessageDomainService.xml /dniv311/run/classes/dni.msgstds.api.jar /dniv311/run/classes/dni.msgstds.impl.jar /dniv311/run/classes/dnicdcfg.jar /dniv311/run/classes/dnicdusr.jar /dniv311/run/classes/dnicgtrc.jar /dniv311/run/classes/dnicvcks.jar /dniv311/run/classes/dnicvcks_seni1.jar /dniv311/run/classes/dnicvcks_sfmtxml10.jar /dniv311/run/classes/dnicvcks_sfmtxml11.jar /dniv311/run/classes/dnicvcks_sfmtxml12.jar /dniv311/run/classes/dnicvcks_sfunds40.jar /dniv311/run/classes/dnicvcks_sfunds41.jar /dniv311/run/classes/dnicvcks_sfunds42.jar /dniv311/run/classes/dnicvcks_sfunds43.jar /dniv311/run/classes/dnicvcks_sfunds44.jar /dniv311/run/classes/dnicvcks_ssys63.jar /dniv311/run/classes/dnicvcks_ssys70.jar /dniv311/run/classes/dnicvrls_seni1.jar /dniv311/run/classes/dnicvrls_sfmtxml10.jar /dniv311/run/classes/dnicvrls_sfmtxml11.jar /dniv311/run/classes/dnicvrls_sfmtxml12.jar /dniv311/run/classes/dnicvrls_sfunds40.jar /dniv311/run/classes/dnicvrls_sfunds41.jar /dniv311/run/classes/dnicvrls_sfunds42.jar /dniv311/run/classes/dnicvrls_sfunds43.jar /dniv311/run/classes/dnicvrls_sfunds44.jar /dniv311/run/classes/dnicvrls_ssys63.jar /dniv311/run/classes/dnicvrls_ssys70.jar /dniv311/run/classes/dnp.aspal.api.jar /dniv311/run/classes/dnp.aspal.impl.jar /dniv311/run/classes/dnp.jab.jar /dniv311/run/classes/dnp.nls.util.jar /dniv311/run/classes/dnp.util.model.jar /dniv311/run/classes/dnp.util.services.jar /dniv311/run/classes/dnprdu.jar /dniv311/run/data/dnfczc12.cli /dniv311/run/doc/dni.msgstds.api.doc.zip /dniv311/run/flows/DNF_BACKOUT.bar /dniv311/run/flows/DNF_RM.bar /dniv311/run/flows/DNF_RMA.bar /dniv311/run/flows/DNF_R_EXP.bar /dniv311/run/flows/DNF_SAGCFG.bar /dniv311/run/flows/DNF_SAGOP.bar /dniv311/run/flows/DNF_V_ADM.bar /dniv311/run/flows/DNI_ACCADM.bar /dniv311/run/flows/DNI_AGATHER.bar /dniv311/run/flows/DNI_A_EVENT.bar /dniv311/run/flows/DNI_DEPLOY.bar /dniv311/run/flows/DNI_MONITOR.bar /dniv311/run/flows/DNI_N_EVENT.bar /dniv311/run/flows/DNI_RCP.bar /dniv311/run/flows/DNI_RSP.bar /dniv311/run/flows/DNI_R_AUDIT.bar /dniv311/run/flows/DNI_R_EVENT.bar /dniv311/run/flows/DNI_R_FMT.bar /dniv311/run/flows/DNI_R_MWH.bar /dniv311/run/flows/DNI_SAMPLE.bar /dniv311/run/flows/DNI_SECADM.bar /dniv311/run/flows/DNI_SYSADM.bar /dniv311/run/flows/DNI_SYSOP.bar /dniv311/run/flows/DNI_TIMER.bar /dniv311/run/jplugin/dnf.asp.imp.jar /dniv311/run/jplugin/dnf.rma.tr.jar /dniv311/run/jplugin/dni.msg.stds.node.jar /dniv311/run/lib/libdnicpcac.a /dniv311/run/lib/libdnicpcac64.a /dniv311/run/lib/libdnicpcom.a /dniv311/run/lib/libdnicpcom64.a /dniv311/run/lib/libdnicq.a /dniv311/run/lib/libdnicq64.a /dniv311/run/lil/dniacp.lil /dniv311/run/lil/dnicin.lil /dniv311/run/lil/dnicpn.lil /dniv311/run/lil/dnictp.lil /dniv311/run/lil64/dniacp64.lil /dniv311/run/lil64/dnicin64.lil /dniv311/run/lil64/dnicpn64.lil /dniv311/run/lil64/dnictp64.lil /dniv311/run/msg/dnfccmsg.cat /dniv311/run/msg/dnfclmsg.cat /dniv311/run/msg/dniccmsg.cat /dniv311/run/msg/dnicymsg.cat /dniv311/run/msg/dnpcjmsg.cat /dniv311/run/msg/dnpcumsg.cat /dniv311/run/res/dnfclevt.xml /dniv311/run/res/dnfclmsg.xml /dniv311/run/res/dnfclrsp.xml /dniv311/run/res/dniceevt.xml /dniv311/run/res/dnicersp.xml /dniv311/run/res/dnichevt.xml /dniv311/run/res/dnichrsp.xml /dniv311/run/res/dnicmevt.xml /dniv311/run/res/dnicmrsp.xml /dniv311/run/res/dnicomsg.xml /dniv311/run/res/dnicuevt.xml /dniv311/run/res/dnicursp.xml /dniv311/run/res/dnicymsg.xml /dniv311/run/res/dnpcjmsg.xml /dniv311/run/res/dnpcumsg.xml The following modules are new: /dniv311/admin/appsrv/res/dnp.ado.web.ear /dniv311/admin/bin/dnicdpst /dniv311/admin/data/DNPAO.properties /dniv311/admin/data/DNPAO.xml /dniv311/admin/data/DnpAo.py /dniv311/admin/data/DnpAoPy.properties /dniv311/admin/data/dnicdi04.ddl /dniv311/admin/data/dnicdj01.ddl /dniv311/admin/data/dnicdm03.ddl /dniv311/admin/data/dnicdm4g.ddl /dniv311/admin/data/dnicdmm1.ddl /dniv311/admin/data/dnicdmn1.ddl /dniv311/admin/data/dnicdo01.ddl /dniv311/admin/data/dnicdo0g.ddl /dniv311/admin/data/dnicdp01.ddl /dniv311/admin/data/dnicdurc.ddl /dniv311/admin/data/dnicdurd.ddl /dniv311/admin/data/dnicdurr.ddl /dniv311/admin/data/dniczm09.mq /dniv311/admin/data/dnixzm09.def /dniv311/admin/data/dnp.properties /dniv311/admin/data/dnp.xml /dniv311/admin/data/dnpclaph.applist /dniv311/admin/data/dnpczcoy.cli /dniv311/admin/data/dnpczcvf.txt /dniv311/admin/data/dnpczoar.cli /dniv311/admin/data/dnpczocg.ddl /dniv311/admin/data/dnpczocr.cli /dniv311/admin/data/dnpczocs.mq /dniv311/admin/data/dnpczoct.ddl /dniv311/admin/data/dnpczors.mq /dniv311/admin/data/dnpczort.ddl /dniv311/admin/data/dnpxzocs.def /dniv311/admin/data/dnpxzors.def /dniv311/run/classes/com.ibm.dni.msgstds.defset.bulkpmt21.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.cashrep50.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.clearing20.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.collmgmt20.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.corpact10.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.corpact12.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.einvoice10.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.mx2012.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.proxyvote11.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.proxyvote12.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.swiftrem20.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.transrep10.xml /dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIBULKPMT.xml /dniv311/run/classes/com.ibm.dni.msgstds.domain.DNICASHREP.xml /dniv311/run/classes/com.ibm.dni.msgstds.domain.DNICLEARING.xml /dniv311/run/classes/com.ibm.dni.msgstds.domain.DNICOLLMGMT.xml /dniv311/run/classes/com.ibm.dni.msgstds.domain.DNICORPACT.xml /dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIEINVOICING.xml /dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIMX.xml /dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIPROXYVOTING.xml /dniv311/run/classes/com.ibm.dni.msgstds.domain.DNISWIFTREMIT.xml /dniv311/run/classes/com.ibm.dni.msgstds.domain.DNITRANSREP.xml /dniv311/run/classes/dni.sec.jar /dniv311/run/classes/dnicvcks_swiftmx.jar /dniv311/run/classes/dnicvrls_mx_all2012.jar /dniv311/run/classes/dnicvrls_mx_bulkpmt21.jar /dniv311/run/classes/dnicvrls_mx_cashrep50.jar /dniv311/run/classes/dnicvrls_mx_clearing20.jar /dniv311/run/classes/dnicvrls_mx_collmgmt20.jar /dniv311/run/classes/dnicvrls_mx_corpact10.jar /dniv311/run/classes/dnicvrls_mx_corpact12.jar /dniv311/run/classes/dnicvrls_mx_einvoice10.jar /dniv311/run/classes/dnicvrls_mx_proxyvote11.jar /dniv311/run/classes/dnicvrls_mx_proxyvote12.jar /dniv311/run/classes/dnicvrls_mx_swiftrem20.jar /dniv311/run/classes/dnicvrls_mx_transrep10.jar /dniv311/run/data/dnpczcoy.cli /dniv311/run/data/dnpczocr.cli /dniv311/run/flows/DNP_F_FH.bar /dniv311/run/flows/DNP_O_EVT.bar /dniv311/run/jplugin/dnp.fh.jar /dniv311/run/msg/DNFC_Msg.properties /dniv311/run/msg/DNFG_Msg.properties /dniv311/run/msg/DNFL_Msg.properties /dniv311/run/msg/DNFM_Msg.properties /dniv311/run/msg/DNFN_Msg.properties /dniv311/run/msg/DNFR_Msg.properties /dniv311/run/msg/DNFS_Msg.properties /dniv311/run/msg/DNFV_Msg.properties /dniv311/run/msg/DNIC_Msg.properties /dniv311/run/msg/DNIE_Msg.properties /dniv311/run/msg/DNIF_Msg.properties /dniv311/run/msg/DNIH_Msg.properties /dniv311/run/msg/DNII_Msg.properties /dniv311/run/msg/DNIJ_Msg.properties /dniv311/run/msg/DNIK_Msg.properties /dniv311/run/msg/DNIL_Msg.properties /dniv311/run/msg/DNIM_Msg.properties /dniv311/run/msg/DNIO_Msg.properties /dniv311/run/msg/DNIP_Msg.properties /dniv311/run/msg/DNIS_Msg.properties /dniv311/run/msg/DNIT_Msg.properties /dniv311/run/msg/DNIU_Msg.properties /dniv311/run/msg/DNIW_Msg.properties /dniv311/run/msg/DNIX_Msg.properties /dniv311/run/msg/DNIY_Msg.properties /dniv311/run/msg/DNIZ_Msg.properties /dniv311/run/msg/DNPA_Msg.properties /dniv311/run/msg/DNPF_Msg.properties /dniv311/run/msg/DNPJ_Msg.properties /dniv311/run/msg/DNPO_Msg.properties /dniv311/run/msg/DNPR_Msg.properties /dniv311/run/msg/DNPU_Msg.properties /dniv311/run/msg/DNPW_Msg.properties /dniv311/run/msg/dnpcfmsg.cat /dniv311/run/msg/dnpcomsg.cat /dniv311/run/res/dnpcfmsg.xml /dniv311/run/res/dnpcomsg.xml /dniv311/run/samples/dni_custom_bdr.war C. Planning ----------- C1. Checks to be done >>BEFORE<< installing a new PTF ----------------------------------------------------- 1. Ensure that all previously prepared deployment instructions were carried out. 2. Ensure that all previous CDD changes were implemented using the CDP. If a customization operation is still pending and it was carried out in: - Customization mode (dnicdp), implement the pending operation before continuing. - Migration mode (dnicdpm): - Ensure that you have not yet shared the files contained in this or any other PTF as described in section D5 step 2. - Implement the pending operation before continuing. 3. Until this PTF has been fully installed, ensure that no changes are made to the currently implemented CDD except for the changes described in this PTF readme document. 4. Ensure that 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'. 5. Ensure that 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'. C2. Prerequisite and supersede information ------------------------------------------ This PTF requires the following PTFs: - UK82437 for APAR PM73208 (Base 3.1.1.9, ASP PROCESSING THREAD HANDLING WITH 2 DIFFERENT SYMPTOMS 'DNPA1153E: MISSING ELEMENT' AND NULLPOINTER EXCEPTION) This PTF should be installed together with: - UK90053 for APAR PM74138 (MM 3.1.1.7, MESSAGE MANAGEMENT UPDATES), if you are using the Message Management extending feature of WebSphere BI for FN. This PTF supersedes the following PTFs: - none C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - DB2 administrator (udb2adm1) - ESM administrator (uesm1) - WebSphere MQ administrator (uwmqadm1) - WebSphere MB application developer (uwmbad1) - WebSphere MB administrator (uwmba1) - WebSphere Application Server operator (uwaso1) - WebSphere Application Server administrator (uwasa1) - First WebSphere BI for FN system configuration administrator (sa1) - Second WebSphere BI for FN system configuration administrator (sa2) - First WebSphere BI for FN security configuration administrator (ua1) - Second WebSphere BI for FN security configuration administrator (ua2) D. Installation --------------- D1. 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, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration". D2. Stopping all application servers ------------------------------------ Stop all application servers. D3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- Stop all WebSphere BI for FN message brokers. D4. Backing up your system -------------------------- We recommend to backup your AIX LPAR so that in case of migration issues you can revert to your previous system setup and continue to process workload. D5. Installing PTF by InstallAnywhere ------------------------------------- 1. 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. 2. 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 3. Set the group ownership of the runtime directories and its files to group dnilpp. To do this, enter the following command in AIX: chgrp -R dnilpp /dniv311/run D6. 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 AIX on the customization system as a customizer (ucust1). To verify again that all previous CDD changes were implemented, enter the following command: /dniv311/admin/bin/dnicdpst -i -cdefs where The name of the WebSphere BI for FN instance The name of the customization definitions directory as specified in the CDP ini file, for example: /var/dni_03_01/cus/defs If the response to this command indicates that a customization operation is still pending, refer to section C1 step 2 for further instructions. 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/_UK90052_temp.cdd > supplement cdd/_UK90052_temp.cdd cdd/_UK90052.cdd Edit the supplemented CDD to specify a value for the new placeholder DNIvPATH. Search for each occurrence of the string value=" and specify the appropriate placeholder values. > import cdd/_UK90052.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 * create new table spaces DNIRG, DNIRGR, DNIURG and DNIURV * create new tables DNI_ROLEGROUP, DNI_RG_ROLE_REL, DNI_USR_RG_REL and DNI_USER_RESOLVED * create new views DNI_VW_CT, DNI_VW_ROLE, DNI_VW_RG and DNI_VW_COS * alter tables DNI_COS, DNI_CT, DNI_OU, DNI_ROLE, DNI_STATUS_COMMENT, DNI_USER * alter table DNI_EVENT, add new column * create new index DNIX1EVT on table DNI_EVENT * rename table DNI_UPREF to DNI1UPREF for migration * create new table DNI_UPREF, copy existing data from DNI1UPREF * create new index DNIU1UPR * drop views DNI_V_CT, DNI_V_COS, DNI_V_ROLE * re-create views DNI_V_CT, DNI_V_COS, DNI_V_ROLE * alter table DNI_A_MSG_DNIvOU, DNI_A_USR_DNIvOU, DNIMWH_PT_DNIvOU for each OU * drop views DNIV_A_OU_DNIvOU, DNIV_A_US_DNIvOU and DNI_MWH_DNIvOU for each OU * re-create views DNIV_A_OU_DNIvOU, DNIV_A_US_DNIvOU and DNI_MWH_DNIvOU for each OU * create new views DNI_VW_OU_DNIvOU, DNI_VW_URO_DNIvOU, DNI_VW_URG_DNIvOU and DNIV_MWH_DNIvOU for each OU * update DNI_DBHISTORY - DBCNT * insert new configuration data: CT: DniFileDir CO: DniMessageFiles -ct DniFileDir -ou SYSOU -attr path -val DNIvPATH/run/msg CO: DniMessageFiles -ct DniFileDir -ou SYSOU -attr read CO: DniSecAdm.cre -ct DniSecAdm.cre -ou SYSOU -attr rg CO: DniSecAdm.del -ct DniSecAdm.del -ou SYSOU -attr rg CO: DniSecAdm.add -ct DniSecAdm.add -ou SYSOU -attr rg CO: DniSecAdm.rem -ct DniSecAdm.rem -ou SYSOU -attr rg CO: DniSecAdm.list -ct DniSecAdm.list -ou SYSOU -attr rg CO: DniSecAdm.com -ct DniSecAdm.com -ou SYSOU -attr rg CO: DniSecAdm.app -ct DniSecAdm.app -ou SYSOU -attr rg * update security data: Role DniUA, add role-group related commands: -co DniSecAdm.cre -ct DniSecAdm.cre -attr rg -co DniSecAdm.del -ct DniSecAdm.del -attr rg -co DniSecAdm.add -ct DniSecAdm.add -attr rg -co DniSecAdm.rem -ct DniSecAdm.rem -attr rg -co DniSecAdm.list -ct DniSecAdm.list -attr rg -co DniSecAdm.com -ct DniSecAdm.com -attr rg -co DniSecAdm.app -ct DniSecAdm.app -attr rg * strip trailing blanks in columns extended from CHAR to VARCHAR in tables DNI_COS, DNI_CT, DNI_OU, DNI_ROLE, DNI_STATUS_COMMENT, DNI_USER * pre-fill table DNI_USER_RESOLVED * strip trailing blanks in columns extended from CHAR to VARCHAR in tables DNI_A_MSG_DNIvOU, DNI_A_USR_DNIvOU, DNIMWH_PT_DNIvOU for each OU - DBSP * migrate Java stored procedures - new procedures DNI9CREATE9RG, DNI9COMMIT9RG, DNI9APPROVE9RG, DNI9MODIFY9RG, DNI9REJECT9RG, DNI9RG9ADD9ROLE, DNI9RG9REM9ROLE, DNI9DELETE9RG, DNI9USER9ADD9RG DNI9USER9REM9RG - drop and recreate procedures DNI9CREATE9CT, DNI9CREATE9COS, DNI9COMMIT9CT, DNI9COMMIT9OU, DNI9COMMIT9COS, DNI9APPROVE9CT, DNI9APPROVE9OU, DNI9APPROVE9COS, DNI9DEPLOY9CT, DNI9DEPLOY9OU, DNI9DEPLOY9COS, DNI9REJECT9CT, DNI9REJECT9OU, DNI9REJECT9COS, DNI9REJAPPROVE9CT, DNI9REJAPPROVE9OU, DNI9REJAPPROVE9COS, DNI9MODIFY9CT, DNI9MODIFY9OU, DNI9MODIFY9COS, DNI9DELETE9CT, DNI9DELETE9COS, DNI9ADDCO2COS, DNI9ADDCO2OU, DNI9ADDATTR2CT, DNI9REMCOFROMCOS, DNI9REMCOFROMOU, DNI9REMATTRFROMCT, DNI9REGISTER9COS, DNI9RESET9CT, DNI9RESET9OU, DNI9RESET9COS, DNI9CREATE9ROLE, DNI9COMMIT9ROLE, DNI9APPROVE9ROLE, DNI9MODIFY9ROLE, DNI9REJECT9ROLE, DNI9ROLE9ADD9RES, DNI9ROLE9REM9RES, DNI9DELETE9ROLE, DNI9COMMIT9USER, DNI9APPROVE9USER, DNI9REJECT9USER, DNI9USER9ADD9ROLE, DNI9USER9REM9ROLE, DNI9REVOKE9USER, DNI9REACTIVAT9USER, DNI9AUTHORIZE9USER, DNI9REJECT9USERAUT - DBGNT * grant insert, select, update and delete permission for re-created table DNI_UPREF to group DNIvSGRP * grant select permission for the new tables DNI_ROLEGROUP, DNI_RG_ROLE_REL, DNI_USR_RG_REL and DNI_USER_RESOLVED to group DNIvSGRP * grant execute permission for all Java stored procedures to group DNIvSGRP * grant insert, select, update and delete permission for re-created table DNI_UPREF to group DNIvUGRP * grant select permission to for re-created view DNI_MWH_DNIvOU to group DNIvSGRP * grant insert, update and select permission for new view DNIV_MWH_DNIvOU to group DNIvSGRP - MQ * create new local queue DNIvQPFX.DNP_F_FH * create new alias queue DNIvINST.SYSOU.DNP_F_FH - MQAUT * update permission on new queue DNIvQPFX.DNP_F_FH for group DNIvSGRP * update permission on new queue DNIvINST.SYSOU.DNP_F_FH for group DNIvYGRP - MBRK * create new message flow DNP_F_FH - CFGPF (if SVB DNQER or DNFRMA is assigned) * create 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 step D7. 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 D7. Following the deployment instructions created in step D6 -------------------------------------------------------------- Follow the deployment instructions that were created in step D6 with the following exceptions: - in resource class DBSP, follow the instructions of modifying flag in Vehicle #2 to migrate the WBI-FN system. - do not execute the instructions provided for resource class CFGPF now; you will use them in step D13.3. - ignore the deployment instructions for resource class MBRK. The updated BAR files will be deployed in step D11.1 D8. Additional activities ------------------------- D8.1. DB2 related activities - - - - - - - - - - - - - - Updating RUNSTATS data of Configuration and Security administration tables - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To run RUNSTATS, use the following ddl module after you have added an additional RUNSTATS statement for table DNI_USER_RESOLVED: deployment_dir/instance/admin/dnixzrst.ddl D9. Restarting all WebSphere BI for FN message brokers ------------------------------------------------------ Restart all WebSphere BI for FN message brokers. D10. Customize BAR files when using mqsideploy or the Toolkit to deploy them ---------------------------------------------------------------------------- Backup the BTD repository ------------------------- 1. On the runtime system on which you use the BAP, log on to AIX as the WebSphere MB administrator (for example, uwmba1) and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a backup of your BTD repository. The location of this directory depends on the version of WebSphere Message Broker you are using: - for version 6.1: $DNI_BAP_PATH/bap/$DNI_QMGR_CFG - for version 7: $DNI_BAP_PATH/bap/$DNI_I where the values of the environment variables DNI_BAP_PATH, DNI_QMGR_CFG and DNI_I correspond to the settings made in your dniprofile. For example, to create a backup of a Broker 7 BTD repository by copying the directory, enter the following commands: mkdir -p $DNI_BAP_PATH/bap/PM74136/$DNI_I cp -R $DNI_BAP_PATH/bap/$DNI_I/ $DNI_BAP_PATH/bap/PM74136/$DNI_I Customize BAR files ------------------- Perform this step only if you use mqsideploy or the Toolkit to deploy broker archive (BAR) files manually. If you use the BAP (dniczbap) to automatically deploy the BAR files, skip this step and later deploy the BAR files directly as described in step D11.2.2. If you are unsure which method to use, use the same method that you used when you initially created your instance as described in "Planning, Installation, and Customization". To customize the BAR files for manual deployment: 1. On the runtime system on which you use the BAP, log on to AIX as the WebSphere MB administrator (for example, uwmba1) and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a temporary directory to which you have read and write access and that has at least 35MB of free space. This is the directory in which dniczbap will store the customized BAR files. 3. The component to which the BAP deploys message flows depends on which version of WebSphere Message Broker is used: - For V6.1, the BAP deploys message flows to the configuration manager. - For V7, the BAP deploys message flows to the broker. Sometimes, the BAP cannot connect directly to this component, for example, when you use Broker V6.1 and the configuration manager is located on Windows. How you customize the BAR files depends on whether the BAP can connect to this component: a. If a connection is not possible, issue the following command to customize all BAR files: dniczbap -cmd prepare -all -dir where represents the output directory created in step 2. b. If a connection is possible, ensure that the configuration manager (if using Broker V6) and the brokers are running, and that no flows or execution groups are stopped. Issue the following command to cause the BAP to identify the BAR files that are to be updated: dniczbap -cmd prepare -update new -dir where represents the output directory created in step 2. Regardless of which method (a or b) you use, each of the customized BAR files in the output directory has a name of the form: ....bar where The name of your instance. The name of the broker to which the BAR file is to be deployed. The name of the execution group to which the BAR file is to be deployed. The name of the BAR file as provided by WebSphere BI for FN. 4. If you performed step 3.a, identify the BAR files that are listed in section "B. Summary of changes" and delete all other BAR files from the output directory. 5. Transfer, in binary mode, the customized BAR files in the output directory to the Toolkit or to the system on which you will later issue the mqsideploy command. 6. If you will use the Toolkit to deploy the message flows, import the customized BAR files. D11. Redeploy updated BAR files ------------------------------ Deploying the WebSphere BI for FN BAR files that are delivered in this PTF updates the message flows that run in the broker. For a list of flows contained in each BAR file, refer to "Planning execution groups" section of "Planning, Installation, and Customization". Each WebSphere BI for FN message flow has a suffix that represents its version. For example, the flow DNI_SYSADM_1141 has the version 1141. The version of a flow corresponds to the number of the PTF that most recently updated it. Refer to the header of this readme to determine the PTF number of this PTF. To deploy BAR files, you must have the access rights of the WebSphere MB administrator (uwmba1). D11.1 Deploy new message flows - - - - - - - - - - - - - - - Follow the deployment instructions for resource class MBRK that were created in step D6. D11.2. Update existing message flows - - - - - - - - - - - - - - - - - - If you already prepared the customized BAR files as described in step D10, proceed with step D11.2.1; otherwise, proceed with step D11.2.2 D11.2.1 Deploying the BAR files customized in step D10 Use the Toolkit or the mqsideploy command to manually deploy the BAR files. Remove the old versions of the message flows that have been updated by the BAR files you deployed. If you neglect to do this, two different versions of the flows will run simultaneously with unpredictable results. D11.2.2 Deploying BAR files when step D10 was not performed Use the BAP (dniczbap) to customize and automatically deploy the BAR files: 1. Ensure that: - The configuration manager is running (applies only for Broker V6.1) - The brokers are running - No flows or execution groups are stopped. Otherwise, old flow levels might not be deleted during the BAP update operation. 2. On the runtime system where you use the BAP, log on to AIX as the WebSphere MB administrator (for example, uwmba1) and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 3. Ensure that you have at least 35 MB of free space in the current directory. 4. Issue the following command: dniczbap -cmd prepare -update new -deploy 5. Issue the following command to verify that all previous versions of the updated message flows were removed successfully: dniczbap -cmd check The result should be: DNIZ1314I: No problems detected. If you receive the message DNIZ1313E follow the instructions provided in the user response to correct the problem. D11.3. Activating WebSphere BI for FN accounting - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D12. Migrating configuration data --------------------------------- D12.1 Generating configuration data migration scripts - - - - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D12.2 Executing the migration scripts - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D13. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ D13.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. D13.2. Update the WebSphere Application Server environment - - - - - - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE D13.3. Migrating the enterprise application - - - - - - - - - - - - - - - - - - - - - - If the instructions created in step D6 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. D14.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. - Subscribe MSIF to SAGs to enable file transfer and session monitoring. - Start the MSIF Message Transfer service. - Start the Enhanced InterAct service. - Acquire SWIFTNet SnF queues. - Open MSIF SnF input and output channels. - 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". D15. 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 changed in this PTF: -> API nodes: - DniMessageAudit - DniMwhInsert - DniMwhUpdate -> message sets: - DNI_DnqMsgSetEnv - DNI_DnqMsgSetMqrfh2 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 describes 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. D16. Verifying your Installation --------------------------------- To verify the installation of the Java database routines follow the steps described in Planning, Installation, and Customization guide, chapter 5. "Verifying your Installation", section "Verifying the installation of the Java database routines". *------------------------------------------------------------------------------* * End of Installation * *------------------------------------------------------------------------------* E.APAR details --------------- Fixes for the following APARs are contained in this PTF: PM74136 Base UPDATES FOR ADMINISTRATION AND OPERATION A new Administration and Operation Facility is introduced. You can install it after the migration has finished by assigning the new service bundle DNPAO. For further information refer to the Administration and Operation Facility Users Guide. PM76700 Base WSADMIN COULD NOT UPDATE CFGPH000.APPLIST PROPERLY (DNPW1109E: APPLICATION LIST IS EMPTY) After customer perform customization step to generated a CFGPH000.applist, user implement the wsadmin.sh script. However, the CFGPH000.applist was not updated on the WAS server after the wsadmin.sh script. Now, the Jython scripts deploy the CFGPH000.applist file when required. PM77821 Base MODIFY THE CONTENT OF THE ERROR MESSAGE "DNFL9430E" TO BE CLEARLY DISPLAYED ON MERVA SCREEN The message text for message DNFL9430E was changed from "The local RM data store does not contain an authorisation that authorizes the request; direction='direction', ASP name='aspName' ,ASP version='aspVersion', reason='reason'." to "Request is not authorized; direction='direction', reason='reason' ,ASP name='aspName', ASP Version='aspVersion'." PM77819 Base DNICPD/DNICDPM IMPROVEMENTS NECESSARY TO DETERMINE THE STATE OF A PREVIOUS ACTION AND AVOID PROBLEMS DURING APPLYING MAINTENANCE Formerly, there were poor indications to determine whether the last re-customization or migration has been implemented. Now, the preparation status information is enhanced with the mode (customization or migration) for which deployment data has been generated and are not yet implemented. A script 'dnicdpst' is introduced to show whether a deployment is ongoing and in which mode it has been initiated. PM76975 Base REMOVE CHECK FOR CHARACTER 8 IN RECEIVERS BIC, NOW ALLOW "1" The check for character 8 in receivers BIC has been removed. Now, "1" is allowed. PM73199 Base DNICONFIGSVB WAS NOT REMOVED WHILE USER REMOVE A DNFEFAS SVB Formerly, after completing a recustomization with the remove of the DNFEFAS SVB the DNFEFAS was still existing on the system. The dnfczmlc generated the EFAS configuration even the DNFEFAS SVB was removed. Now, dnfczmlc removes DNFEFAS SVB correctly. PM74802 Base UPDATE CIN FOR MSIF APAR PM72542 The changes required for MSIF Apar PM72542 make an update of Base components CIN, RMA, and RM necessary. This Base PTF for APAR PM74802 provides the required changes. Formerly, if a user attempted to start the CIN for the DNF_L_TR or DNF_L_IMP and the CIN was already active, the error event DNFL9037E was issued. Now, the informational event DNFL9041I is issued instead. PM76092 Base JAVA OUTOFMEMORY ERROR WHILE RUNNING INSTALLER IN GUI MODE TO INSTALL WBIFN PTF The WBI-FN installation utility InstallAnyWhere keeps record of installed modules for uninstalling purpose. When the number of changes increases to certain size the out of memory exception will occur. Now, the problem is fixed by improving the registry categorization. F.Other changes ---------------- - A role group concept was introduced in the security administration service. You can use role groups to define a set of roles so that you can assign the same roles to several users easily. Several of the DNI_SECADM commands have been extended to support role groups. For details refer to 'System Administration'. - WebSphere BI for FN now provides message definitions for the following new message domains: DNIMX, DNIBULKPMT, DNICASHREP, DNICLEARING, DNICOLLMGMT, DNICORPACT, DNIEINVOICING, DNIPROXYVOTING, DNISWIFTREMIT, DNITRANSREP The Standards Processing node can be used to validate messages from these domains. - All WebSphere BI for FN Base services were enhanced to be able to process requests submitted by users with a user id longer than 12 characters. Now up to 100 characters are allowed for user ids. - DNFvRMACONTROOT placeholder value was not used in the application list of the WebHome enterprise application so that the link did not work if you used a custom context root for RMA G. Known issues --------------- - You cannot use a userid with more than 12 characters in the Administration and Operation Facility to operate FIN and FMT services unless you have installed a PTF for APAR PM76872 (FIN AND FMT SUPPORT FOR ADMINISTRATION AND OPERATION WITH LONG USERIDS). - You cannot use a userid with more than 12 characters in the Administration and Operation Facility to operate MSIF services unless you have installed a PTF for APAR PM76870 (MSIF SUPPORT FOR ADMINISTRATION AND OPERATION WITH LONG USERIDS). ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++