=============================================================================== = 5724D-9621 IBM WebSphere Business Integration for Financial Networks = = for Multiplatforms Extending Features V2.2.0 = = PTF UK36059 for APAR PK65298 = =============================================================================== Table of contents ----------------- A. How to use this document B. Changes to your current system C. Post-Installation D. Steps on a customization system E. Steps on a run-time system F. APARs addressed by this PTF G. Other changes implemented by this PTF A. How to use this document --------------------------- Only the online version of this document is up to date. We strongly recommend that you download the latest version from http://www.ibm.com/software/integration/wbifn/support before you install this PTF. This PTF requires PTF UK36062 for APAR PK65304 for WebSphere BI for FN Base. Install that PTF and follow the description in UK36062.220.readme.txt before you install the current PTF. This PTF requires PTF UK34476 for APAR PK62545. Install that PTF and follow the description in PK62545.220.readme.txt before you install the current PTF. This PTF requires the SAG AddOn PTF 2.2.0.2 for APAR PK65346 to ensure the SAG configuration commands 'readGlobalParameters' and 'updateGlobalParameters' work correctly. The installation of this PTF is done in two phases: 1. Preparation phase During this timeframe your system can continue to process the workload as usual. This phase contains the steps up to and including 'E5 Preparing BAR files with the updated WebSphere BI for FN flows'. 2. Migration phase During this timeframe your system cannot process workload. This phase begins with step 'E6 Stop all sessions and services you use' and continues until you finished the migration. We recommend that you download the latest version of the documentation from the following web site: www.ibm.com/software/integration/wbifn/library This document assumes the following: 1. The installation directory of WebSphere BI for FN is /opt/IBM/ 2. The names of users, groups, files, directories, etc. are the same as those used in the "Planning, Installation and Customization" manual. If you use different names, use those names instead of the names shown here. B. Changes to your current system --------------------------------- The following modules have been changed: /dnf_02_02/admin/data/dnfczaar.cli /dnf_02_02/admin/data/dnfczcar.cli /dnf_02_02/admin/data/dnfczcas.cli /dnf_02_02/admin/data/dnfczcat.cli /dnf_02_02/admin/data/dnfczcob.cli /dnf_02_02/admin/data/dnfczcoy.cli /dnf_02_02/admin/data/dnfczdas.cli /dnf_02_02/admin/data/dnfczdat.cli /dnf_02_02/admin/data/dnfcpcac.cli /dnf_02_02/admin/data/dnfcpcde.cli /dnf_02_02/admin/data/dnfczfrt.ddl /dnf_02_02/admin/data/dnfczfco.ddl /dnf_02_02/admin/data/dnfczlct.ddl /dnf_02_02/admin/data/dnfczuct.ddl /dnf_02_02/admin/data/dnfczpco.mq /dnf_02_02/admin/data/dnfczpro.mq /dnf_02_02/admin/data/dnfczpcs.mq /dnf_02_02/admin/data/dnfczprs.mq /dnf_02_02/admin/data/dnfczctp.txt /dnf_02_02/admin/data/dnfczdtp.txt /dnf_02_02/admin/data/dnfxzpco.def /dnf_02_02/admin/data/dnfxzpcs.def /dnf_02_02/admin/data/dnfxzpro.def /dnf_02_02/admin/data/dnfxzprs.def /dnf_02_02/admin/data/DNF_ILS_FIN.msgflow /dnf_02_02/admin/data/DNF_PF_CMD.msgflow /dnf_02_02/admin/data/dnf.properties /dnf_02_02/admin/data/DNFRMR.properties /dnf_02_02/admin/data/dnfczccf.txt /dnf_02_02/admin/data/dnf.xml /dnf_02_02/admin/data/DNFAUTH.xml /dnf_02_02/admin/data/DNFCOMMON.xml /dnf_02_02/admin/data/dnfczcdd.xml /dnf_02_02/admin/data/DNFFIN.xml /dnf_02_02/admin/data/DNFRMR.xml /dnf_02_02/admin/data/DNFFMTFIN.xml /dnf_02_02/admin/win/com.ibm.dnf.Core.zip /dnf_02_02/admin/win/com.ibm.dnf.FinInterfaceLayer.zip /dnf_02_02/admin/win/com.ibm.dnf.SagCfg.zip /dnf_02_02/admin/win/com.ibm.dnf.SagOp.zip /dnf_02_02/admin/win/com.ibm.dnf.PrivateFinancialMessageTransferFin.zip /dnf_02_02/admin/win/com.ibm.dnf.RelationshipManagementRuntime.zip /dnf_02_02/run/bin/dnfcfsfd /dnf_02_02/run/bin/dnfcfsfs /dnf_02_02/run/bin/dnfczml2.awk /dnf_02_02/run/bin/dnfxzrmr /dnf_02_02/run/bin/dnfxzrmc /dnf_02_02/run/bin/dnfxzrmo /dnf_02_02/run/data/dnfczcar.cli /dnf_02_02/run/data/dnfczcas.cli /dnf_02_02/run/data/dnfczcat.cli /dnf_02_02/run/data/dnfcwdbs.dbrm /dnf_02_02/run/lib/libdnfcf.a /dnf_02_02/run/lib/libdnfcwbas.a /dnf_02_02/run/lib/libdnfcwdbs.a /dnf_02_02/run/lib/libdnfcwetc.a /dnf_02_02/run/lib/libdnfcwqio.a /dnf_02_02/run/lil/dnfcfpin.lil /dnf_02_02/run/lil/dnfrmini.lil /dnf_02_02/run/lil/dnfrmexp.lil /dnf_02_02/run/lil/dnfrmrpt.lil /dnf_02_02/run/msg/dnfccmsg.cat /dnf_02_02/run/res/dnfcfevt.xml /dnf_02_02/run/res/dnfchevt.xml /dnf_02_02/run/res/dnfchrsp.xml /dnf_02_02/run/res/dnfcrevt.xml /dnf_02_02/run/res/dnfcsevt.xml /dnf_02_02/run/res/dnfcpevt.xml /dnf_02_02/run/res/dnfcprsp.xml /dnf_02_02/run/res/dnfclrsp.xml The following modules are new: /dnf_02_02/admin/data/dnfcvcsc.cli /dnf_02_02/admin/data/dnfcvcsv.cli /dnf_02_02/admin/data/dnfcvrsc.cli /dnf_02_02/admin/data/dnfcvrsv.cli /dnf_02_02/admin/data/dnfcpcdr.cli /dnf_02_02/admin/data/dnfczfo3.ddl /dnf_02_02/admin/data/dnfczl02.ddl /dnf_02_02/admin/data/dnfczlco.ddl /dnf_02_02/admin/data/dnfczlro.ddl /dnf_02_02/admin/data/dnfczuo2.ddl /dnf_02_02/admin/data/dnfczvcg.ddl /dnf_02_02/admin/data/dnfczvct.ddl /dnf_02_02/admin/data/dnfczvrt.ddl /dnf_02_02/admin/data/dnfczpcg.ddl /dnf_02_02/admin/data/dnfczpct.ddl /dnf_02_02/admin/data/dnfczprt.ddl /dnf_02_02/admin/data/dnfxzvco.def /dnf_02_02/admin/data/dnfxzvcs.def /dnf_02_02/admin/data/dnfxzvro.def /dnf_02_02/admin/data/dnfxzvrs.def /dnf_02_02/admin/data/dnfxzps1.def /dnf_02_02/admin/data/dnfxzp01.def /dnf_02_02/admin/data/dnfczp01.mq /dnf_02_02/admin/data/dnfczps1.mq /dnf_02_02/admin/data/dnfczvco.mq /dnf_02_02/admin/data/dnfczvcs.mq /dnf_02_02/admin/data/dnfczvro.mq /dnf_02_02/admin/data/dnfczvrs.mq /dnf_02_02/admin/data/DNF_PF_IR.msgflow /dnf_02_02/admin/data/DNF_R_EXP.msgflow /dnf_02_02/admin/data/DNF_V_ADM.msgflow /dnf_02_02/admin/data/DNF_V_REQ.msgflow /dnf_02_02/admin/data/DNF_V_RSP.msgflow /dnf_02_02/admin/data/DNFVERIF.properties /dnf_02_02/admin/data/dnfczcvf.txt /dnf_02_02/admin/data/DNFVERIF.xml /dnf_02_02/admin/win/com.ibm.dnf.DnfLauProcessor.zip /dnf_02_02/admin/win/com.ibm.dnf.Verification.zip /dnf_02_02/run/classes/dnfclau.jar /dnf_02_02/run/jplugin/dnfclaup.jar /dnf_02_02/run/res/dnfccevt.xml /dnf_02_02/run/res/dnfcvevt.xml /dnf_02_02/run/res/dnfcvrsp.xml where represents the installation directory C. Post-Installation -------------------- After you have installed this PTF using ISMP: 1. Share the files with your customization and run-time systems. 2. Ensure that the group ownership of the /dnf_02_02/admin directory and all subdirectories and files therein is set to group dniadmin. To do this, enter the following command in AIX shell: chgrp -R dniadmin /opt/IBM/dnf_02_02/admin 3. Ensure that the group ownership of the /dnf_02_02/run directory and all subdirectories and files therein is set to group dnilpp. To do this, enter the following command in AIX shell: chgrp -R dnilpp /opt/IBM/dnf_02_02/run D. Steps on a customization system ---------------------------------- Note: This PTF introduces the new service bundle DNFVERIF for the new signature reverification service. Do not assign this service bundle as part of this migration process. You can do this after the migration has been finished as part of the usual recustomization process. Before you start the customization migration you should ensure that earlier migrations are completed using the CDP 'implement' command. Otherwise the CDP might generate migration statements again, which may cause the deployment vehicles to fail. To update your current definition directory and the customized administrative scripts, and to create deployment instructions and vehicles: D1. Log on to AIX on the customization - - - - - - - - - - - - - - - - - - - - - - Log on to AIX UNIX on the customization system as a customizer (ucust1). D2. Change to the customization directory - - - - - - - - - - - - - - - - - - - - - Change to the customization directory by issuing the following command: cd /var/dni_02_02/cus D3. Run your customization profile - - - - - - - - - - - - - - - - - Run your customization profile by issuing the following command: . ./dnicus_ D4. Start the CDP in migration mode - - - - - - - - - - - - - - - - - - Start the CDP in migration mode by issuing the following command: dnicdpm -i D5. Identify your current CDD - - - - - - - - - - - - - - - If you are not sure whether your .cdd reflects your current WebSphere BI for FN instance layout, generate a CDD using the CDP export command. How to this is described in "Planning, Installation, and Customization", Appendix E "CDP command reference". D6. Import your current CDD as the target CDD - - - - - - - - - - - - - - - - - - - - - - - Import your current CDD as the target CDD by issuing the following command: import cdd/.cdd D7. Prepare customization data - - - - - - - - - - - - - - - Update the customized administrative scripts for FIN in the directory '//admin' and generate deployment data for the run-time system migration by entering the following command: prepare Depending on the service bundles you have assigned and the superseded PTFs you already have applied this command may generate deployment vehicles for the following resource classes: 'DB', 'DBBND', 'DBGNT', 'MQ', 'MQAUT' and 'MBRK' and deployment instructions in the file /var/dni_02_02/cus/depdata///instructions.txt. You will need this later in step 'E8 Updating the run-time system resources'. D8. Implement the customization changes - - - - - - - - - - - - - - - - - - - - After you have successfully deployed the changes in step E8, implement this CDD as your current CDD to update your 'current definition directory' by entering the following command: implement When the message "DNIZ9013I: Current Definition file already exists." is displayed enter 'y' to continue. D9. Quit the CDP session - - - - - - - - - - - - Quit the CDP session by entering the following command: quit E. Steps on a run-time system ----------------------------- E1. Transferring resources to the WebSphere MB Toolkit workstation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To prepare the WebSphere BI for FN resources located on the WebSphere MB Toolkit workstation in the following steps, you must have the authority of the WebSphere MB domain administrator (UWBIMBD1). The access rights of this user are described in the "Planning, Installation, and Customization" manual in Chapter 1. Planning, in the section "Roles, users, and user groups". To transfer the WebSphere BI for FN resources to a WebSphere MB Toolkit workstation: 1. Log on to the Toolkit workstation. 2. Create a temporary directory to store the files to be transferred from the installation system. 3. Open a Command Prompt window and change to this directory. 4. Transfer, in binary mode, from the installation system to this temporary directory following files: /dnf_02_02/admin/win/com.ibm.dnf.Core.zip /dnf_02_02/admin/win/com.ibm.dnf.FinInterfaceLayer.zip /dnf_02_02/admin/win/com.ibm.dnf.DnfLauProcessor.zip /dnf_02_02/admin/win/com.ibm.dnf.SagCfg.zip /dnf_02_02/admin/win/com.ibm.dnf.SagOp.zip /dnf_02_02/admin/win/com.ibm.dnf.Verification.zip /dnf_02_02/admin/win/com.ibm.dnf.PrivateFinancialMessageTransferFin.zip /dnf_02_02/admin/win/com.ibm.dnf.RelationshipManagementRuntime.zip /dni_02_02/admin/win/dni* For example, you can use the following File Transfer Program (FTP) commands to transfer the files: ftp bin prompt cd /dnf_02_02/admin/win get com.ibm.dnf.Core.zip get com.ibm.dnf.FinInterfaceLayer.zip get com.ibm.dnf.DnfLauProcessor.zip get com.ibm.dnf.SagCfg.zip get com.ibm.dnf.SagOp.zip get com.ibm.dnf.Verification.zip get com.ibm.dnf.PrivateFinancialMessageTransferFin.zip get com.ibm.dnf.RelationshipManagementRuntime.zip cd /dni_02_02/admin/win mget dni* bye 5. Transfer, in binary mode, from the customization system to this temporary directory the message flows customized in step D7: /DNF_R_EXP.msgflow /DNF_ILS_FIN.msgflow /DNF_PF_CMD.msgflow /DNF_PF_IR.msgflow where: The resource file directory created for resource class MBRK during step D7, which has a name of the form .../com.ibm.dni.MBRK For example, you can use the following File Transfer Program (FTP) commands to transfer the files: ftp bin prompt cd get DNF_R_EXP.msgflow get DNF_ILS_FIN.msgflow get DNF_PF_CMD.msgflow get DNF_PF_IR.msgflow bye E2. Setting the Toolkit version and directories - - - - - - - - - - - - - - - - - - - - - - - - To set the correct environment for the tools used in the subsequent steps follow the instructions in the "Planning, Installation, and Customization" manual in chapter "Preparing to create an instance", "Preparing the WebSphere MB Toolkit workstation", -> "Setting the Toolkit version and directories" E3. Backing up all resources installed in a WebSphere MB Toolkit workstation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To save the current level of all WebSphere BI for FN resources installed on a WebSphere MB Toolkit: 1. Open a Command Prompt window and change to the temporary directory you used in step E1. 2. Enter the command: dninibak This command creates backup files with names of the form: _dn.zip where represents a letter or letters that indicate to which product feature or features the backup file applies: i The Base feature f All extending features except Enhanced Support for SWIFTNet FileAct fo The Enhanced Support for SWIFTNet FileAct feature Each backup file contains: Links All files in the directory \eclipse\links that have names of the form "com.ibm.dn.link" WebSphere BI for FN eclipse plugins All subdirectories of with names of the form "com.ibm.dn" WebSphere BI for FN project directories All subdirectories of your workspace directory that have names that begin with "DNI_Dn" Note: The dninibak command issues messages to inform you of directories it was unable to find. For example: - If the Enhanced Support for SWIFTNet FileAct feature is not installed, dninibak issues a message to inform you that it was unable to find directories or projects for the feature "dnfo". - If none of the other extending features are installed, dninibak issues a message to inform you that it was unable to find directories or projects for the feature "dnf". If you do not use the corresponding features, you can safely ignore such messages. E4. Installing the updated WebSphere BI for FN Eclipse plug-ins and flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To install the updated WebSphere BI for FN Eclipse plug-ins and message flows: 1. Open a Command Prompt window and change to the temporary directory you used in step E1. 2. Enter the command: dnininst This command will install the updated Eclipse plugins. A warning message is displayed for each installed file that did already exist. If the dnininst program issues an error message, check the log file for more information about the reason for the error. 3. Enter the command: dninimcp This command will install the updated message flows. A warning message is displayed for each installed file that did already exist. To refresh the meta data in the Message Brokers Toolkit: a. Start the Toolkit with the -clean parameter. b. In the Message Brokers Toolkit, open the 'Broker Application Development Perspective'. To re-build the WebSphere BI for FN projects: - For Message Broker Toolkit V5: a) Select all projects with names of the form DNI_DnMainflows. b) Right-click and select "Refresh" from the pop-up menu. c) Right-click and select "Rebuild" from the pop-up menu. - For Message Broker Toolkit V6: a) Disable the "Build Automatically" feature. To do this, deselect the "Projects"->"Build Automatically" item in the pull-down menu. b) For all 'DNI_DnMainflows' projects: 1) In the "Resource navigator" window, select the projects. 2) From the main menu, select "Projects->Clean..." 3) In the popup window, select "Clean selected project" and ensure "Start a build immediately" is selected. 4) Press "OK". E5. Preparing BAR files with the updated WebSphere BI for FN flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To activate the changes within the WebSphere BI for FN eclipse plugins all affected message flows need to be deployed to all execution groups on all brokers where they are running. Furthermore, BAR files for new WebSphere BI for FN message flow DNF_R_EXP.msgflow have to be prepared. If you have assigned the DNFFMTFIN service bundle, new WebSphere BI for FN message flow DNF_PF_IR.msgflow have to be also prepared. To prepare the broker archive files for the new message flows: a. In the Message Brokers Toolkit, open the 'Broker Administration Perspective'. b. Create one or two new BAR file depends on if you have assigned the DNFFMTFIN service bundle. c. In these BAR file, click the 'add' icon in the 'Content' window. d. Select the flow DNF_R_EXP and press 'OK', if you have flow DNF_PF_IR, also select DNF_PF_IR into another BAR file. e. A 'Progress Information' pops up. Check the result and press 'OK'. f. In the BAR file editor, select the 'Configure' tab. g. Select the DNF_R_EXP entry and DNF_PF_IR if necessary, check the coordinated transaction checkbox and ensure Commit Count is set to 1. h. Close the 'Content' window. i. Confirm 'Save Resource'. To prepare the broker archive files for the existing message flows: a. Ensure that the WebSphere MB configuration manager is running. b. Stop the Message Brokers Toolkit. c. In the Command Prompt window and from the temporary directory you used in step E1, enter dniupdbd -prepare -d . -q [-p ] [-h ] where The name of the queue manager to which the WebSphere MB configuration manager (CM) is connected. The port required to connect to the queue manager. The default is 1414. The host address of the machine running the CM. The default is 127.0.0.1 (localhost). This step creates broker archive files containing all WebSphere BI for FN message flows affected by the changes contained in this PTF, which are: - DNF_BACKOUT - DNF_FSM_QRY - DNF_FSM_STA - DNF_ILC_CMD - DNF_ILC_FIN - DNF_ILC_SLS - DNF_ILS_ACK - DNF_ILS_FIN - DNF_L_ADM - DNF_L_IMP - DNF_SAGCFG - DNF_SAGCFGR - DNF_SAGOP - DNF_SAGOPRE - DNF_UB_IN - DNF_UB_OUT - DNF_PF_CMD - DNF_PF_IS d. Check the log file dniupdbd.log to ensure that the files were successfully prepared. E6. Stop all sessions and services you use - - - - - - - - - - - - - - - - - - - - - Stop all sessions and services you use. How to do this depends on the features of WebSphere BI for FN that you are using. For instance: - Stop all applications that send requests to WebSphere BI for FN. - Log out SIPN FIN LTs. - Release SWIFTNet SnF queues. - Stop Enhanced FileAct File Transfer service. - Stop Enhanced InterAct service. - Close all dnicli sessions. For further information refer to the System Administration manual, chapter: 'Operating components, sessions, and services'. E7. Stop all WebSphere BI for FN message brokers - - - - - - - - - - - - - - - - - - - - - - - - Stop all WebSphere BI for FN message brokers. E8. Updating the run-time system resources - - - - - - - - - - - - - - - - - - - - - Follow the deployment instructions created in step D7 to update the run-time system resources such as database tables and queues. Ignore the instructions for resource class MBRK here; the steps to update the message flows are integrated in this readme. Depending on the WebSphere BI for FN maintenance level you already have applied the deployment may bring the following changes to your system: -> if you have assigned the DNFAUTH service bundle DB2 related changes: - Create a new index for the tables DNF_BKE_DNIvOU. -> if you have assigned the DNFFIN service bundle DB2 related changes: - New package DNFvCOLLID.DNFCWDBS.(WBIFN_CSN_V2R2_PK62842) for the SFD. - Create a new index for the tables DNF_BKMRV_DNIvOU. -> if you have assigned the DNFRMR service bundle DB2 related changes: - New views DNIvSN.DNF_RMAUT_DNIvOU, DNIvSN.DNF_RMPRM_DNIvOU. - Create a new index for table DNF_RMDS. -> if you have assigned the DNFFMTFIN service bundle DB2 related changes: - new database table DNFP_FRSS including tablespace, index and permissions MQ related changes: - new alias queue DNIvINST.DNIvOU.DNF_PF_IR - new local queue DNIvQPFX.DNF_PF_IR with MQ security definition After you have successfully deployed the resources you have to implement the customization changes as described in step D8 in order to ensure that future migrations do not prepare the current deployment data again. If you have already closed the CDP session you have to repeat step D1 to D6, but not D7, before you continue with step D8. E9. Update the WebSphere MB environment - - - - - - - - - - - - - - - - - - - - To make the new file dnfclau.jar available to WebSphere BI for FN, ensure that the CLASSPATH environment variables of all message brokers includes: /dnf_02_02/run/classes/dnfclau.jar How to update the message broker configuration depends on the version you use. Refer to 'Planning, Installation and Customization', chapter 'Preparing a message broker' for further details. E10. Restart all WebSphere BI for FN message brokers - - - - - - - - - - - - - - - - - - - - - - - - - - Restart all WebSphere BI for FN message brokers. E11. Deploying all affected WebSphere BI for FN message flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To deploy the broker archive files for the existing message flows: a. Ensure that the WebSphere MB configuration manager is running. b. Ensure that the Message Brokers Toolkit is stopped. c. In the Command Prompt window and from the temporary directory you used in step E1 and E5, enter dniupdbd -deploy -q [-p ] [-h ] [-t ] where The name of the queue manager to which the WebSphere MB configuration manager (CM) is connected. The port required to connect to the queue manager. The default is 1414. The host address of the machine running the CM. The default is 127.0.0.1 (localhost). The wait interval for configuration manager and broker response. The default is 600 seconds (10min). This step deploys the broker archive files prepared in step E5 and contained in the current directory to the broker(s). d. Check the log file dniupdbd.log to ensure that the files were successfully deployed. To deploy the broker archive files for the new message flows: a. Start the Message Brokers Toolkit. b. Open the 'Broker Administration Perspective'. c. Right click the BAR files you created in step E5 for the new flows, and select 'Deploy File' from the pop-up menu. d. Select the execution group from the list and press 'OK'. A status dialog pops up and indicates the result. e. Select 'OK'. f. After the system responds, check the event log of the broker to ensure that the files were successfully deployed. E12. Migrate configuration data - - - - - - - - - - - - - - - - Migrate WebSphere BI for FN Extending Features configuration entities: 1. Ensure that all CTs, COSs and OUs in your current instance are committed, approved, and deployed. 2. On the runtime system on which the message broker runs, log on to z/OS UNIX as the system configuration administrator, for example, SA1. 3. Run the profile for your runtime environment by entering: . /var/dnf_02_02/run/dnfprofile 4. To verify that all necessary components are operational, open a CLI session and issue the list command: dnicli -ou SYSOU -s DNI_SYSADM -c "list -ou %" The CLI displays a list of all OUs. 5. Create a temporary directory where the configuration migration script dnfczmlc can store the CLI command files it will generate and that contain the migration statements. 6. Switch to this directory and enter the following command: dnfczmlc.sh -i [-dir ] [-dual YES|NO] where: The name of the instance. -dir The directory on the runtime system in which the resource files dnfczcat.cli, dnfczcas.cli and dnfczcar.cli are located. The default is the /run/data subdirectory of the directory specified in your runtime profile (dnfprofile) by the DNF_PATH variable. For example, if the value of DNF_PATH is /usr/lpp/dnf_02_02, the default directory is /usr/lpp/dnf_02_02/run/data. -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 will 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. Note: This is a long-running task, and might take several minutes to complete. For example, if the name of your instance is INST1 and your system does not use dual authorization, enter: dnfczmlc.sh -i INST1 -dual NO Depending on which of the superseded PTFs you already have applied the program dnfczmlc may create the following CLI command files in the current directory: If dual authorization is not used (-dual NO): - dnfczmlc_2_sa_ent_all.cli - dnfczmlc_3_ua_cre_ro_all.cli If dual authorization is on (-dual YES): - dnfczmlc_2_sa_rem_cos_com.cli - dnfczmlc_2_sa_rem_cos_dep.cli - dnfczmlc_5_sa_cre_ct_com.cli - dnfczmlc_5_sa_cre_ct_dep.cli - dnfczmlc_6_sa_cre_co_com.cli - dnfczmlc_6_sa_cre_co_dep.cli - dnfczmlc_7_sa_cre_cos_com.cli - dnfczmlc_7_sa_cre_cos_dep.cli - dnfczmlc_8_ua_cre_ro_com.cli - dnfczmlc_8_ua_cre_ro_app.cli Check the file dnfczmlc.log to ensure that dnfczmlc ran correctly. 7. Execute the generated CLI command files by entering the following command: dnicli -i -s -ou SYSOU -cft | tee -a PK65304cli.log where: The name of the instance. 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. The generated CLI command files must be executed in the following sequence and using the following user authorization: If dual authorization is not used (-dual NO): 1. dnfczmlc_2_sa_ent_all.cli by any SA 2. dnfczmlc_3_ua_cre_ro_all.cli by any UA If dual authorization is on (-dual YES): 1. dnfczmlc_2_sa_rem_cos_com.cli by the first SA (SA1) 2. dnfczmlc_2_sa_rem_cos_dep.cli by the second SA (SA2) 3. dnfczmlc_5_sa_cre_ct_com.cli by the first SA (SA1) 4. dnfczmlc_5_sa_cre_ct_dep.cli by the second SA (SA2) 5. dnfczmlc_6_sa_cre_co_com.cli by the first SA (SA1) 6. dnfczmlc_6_sa_cre_co_dep.cli by the second SA (SA2) 7. dnfczmlc_7_sa_cre_cos_com.cli by the first SA (SA1) 8. dnfczmlc_7_sa_cre_cos_dep.cli by the second SA (SA2) 9. dnfczmlc_8_ua_cre_ro_com.cli by the first UA (UA1) 10.dnfczmlc_8_ua_cre_ro_app.cli by the second UA (UA2) E13. Restart all sessions and services you use - - - - - - - - - - - - - - - - - - - - - - - Restart all sessions and services you use. How to do this depends on the features of WebSphere BI for FN that you are using. For instance: - Log in SIPN FIN LTs. - Start Enhanced FileAct File Transfer service. - Start Enhanced InterAct service. - Acquire SWIFTNet SnF queues. - Start the applications that send requests to WebSphere BI for FN. For further information refer to the System Administration manual, chapter: 'Operating components, sessions, and services'. *----------------------------------------------------------------------------* * End of Migration * *----------------------------------------------------------------------------* F. APARs addressed by this PTF ------------------------------ PK65298 FIN ENHANCEMENTS TO WEBSPHERE BI FOR FN VERSION 2 RELEASE 2 Signature reverification: WebSphere BI for FN now provides a service that regularly reattempts to verify the signatures of FIN messages for which a previous attempt failed due to a recoverable error. Message administrators can also reattempt signature verification manually. MT398 messages now processed in accordance with SWIFT CLS TPS: When WebSphere BI for FN receives a SWIFT MT398 message, it now extracts and verifies the signature of the imbedded message, as required by the SWIFT Continuous Link Settlement (CLS) Third Party Service (TPS) specification. Notification of impending LAU key expiration: When a LAU key is about to expire, or has already expired, WebSphere BI for FN now issues a warning message. More detailed status for FIN messages in message warehouse: FIN messages in the Message Warehouse now provide more detailed information about their status. PK65313 FIN MWH FIELD MWH_TRAN_REFERENCE NEEDS ALWAYS TO BE FILLED WITH THE LAST 16 CHARS Formerly, for messages containing field 20C the transaction reference was incorrectly written into the message warehouse column MWH_TRAN_REFERENCE. 16 characters were extracted left- aligned so that the colon, the qualifier and the separation characters '//' were written together with at most 9 out of the 16 possible characters of the transaction reference. Now, the colon, the qualifier and the separation characters are skipped in field 20C and all possible 16 characters of the transaction reference are written to the message warehouse. PK65231 FIN PERFORMANCE DEGRADATION IN QUERY -LT COMMAND WITH WBI-FN 2.2 Formerly, when a large number of logical terminals (LTs) was defined for an OU the query command of service DNF_ILC_CMD had a performance degradation. Now, the query command performance has been improved for scenarios where a large number of LTs is defined. PK65236 FIN FSM SHOULD RETRY TO WRITE AUDIT DATA Formerly, the SFD did abort the session immediately when a message audit request could not be written to the remote audit queue. However, WMQ errors are often of temporary nature so that the SFD should retry. Now, the SFD tries to put the audit request 10 times after waiting 2 seconds in each iteration, before giving up. PK65237 RM SQL -905 WHEN GENERATING RM REPORTS Formerly, the RM command 'report' caused very high CPU load in DB2. Now, new indices reduce the CPU consumption of certain SQL statements. PK58413 FMT SUPPORT FOR INTER INSTANCE FMT This PTF introduces support for inter-instance FMT. PK65215 FMT To avoid dependencies for non-FMT customers the common files that will be changed for the inter-instance FMT PTF are shipped in a separate PTF. PK65306 RM SEQUENCE ORDER DURING THE IMPORT OF THE AUTHORIZATIONS ¡V FINISHED EVENTS ARE DISPLAYED BEFORE ACCEPTED Formerly, events written by the DNF_L_ADM commands import and export contained only a timestamp with seconds. Therefore the order of the events may be reversed in a listing. Now, events from these commands have a milli-second precision to ensure correct ordering. PK65300 RM EMPTY RMA IMPORT FILE CAUSES 0C4 ABEND Formerly, empty RM import files might have caused an abend. Now, empty RM import files are handled correctly and an appropriate response is returned. PK65309 RM The SWIFTNet FIN Vendor specification indicated that an empty FINSvcPermssn or Permssn elements in an RM import file is not allowed. However, the RMA Vendor specification was clarifed with vendor letter VL15007 and the defined semantic is that NO permissions are present. SWIFT will update the SWIFTNet FIN Vendor specification to follow the RMA Vendor specification and WebSphere BI for FN has implemented the required changes with this APAR. Formerly, as side effect of these previously non-conform RM import files containing empty (FINSvc)Permssn elements WebSphere BI for FN did loop when processing such a file. Now these files are imported as specified by SWIFT. PK65310 FIN PROBLEM DURING THE IMPORT COMMAND IF THE LOG FILE PATH IS INVALID Formerly, if you did specify an invalid or non-accessible log file path for the DNF_L_ADM import command the DNF_L_IMP service did stop and the event DNFL9543E was written. You had to remove the trigger message from the DNF_L_IMP queue and then restart the DNF_L_IMP service using the start command. Now, DNF_L_ADM immediately replies with error message DNFL9543E in case of an invalid or non-accessible log file path and does not trigger the DNF_L_IMP service. PK65311 RM OUTPUT OF DNF_L_ADM REPORT COMMAND INFLUENCED BY OTHER OU¡¦S Formerly, the output of the DNF_L_ADM report command may have been influenced by data of another organizational unit within the same instance. Now, the report command segregates data from different OUs correctly. PK65294 TRC IMPROVE WBI-FN TRACE ERROR MESSAGE Formerly, if WebSphere BI for FN was not able to write traces into the trace directory, it wrote an unspecific error message in the file /var/tmp/dnigtrace. Now, if WebSphere BI for FN is not able to write traces into the trace directory, it writes an error message indicating the reason in the file /var/tmp/dnigtrace. PK65430 RM RM IMPORT: DNFL9461E THOUGH CONFIGURATION OF SYNONYM LT IS OK Formerly, if a distribution file contained the BIC8 of a synonym LT as issuer or correspondent, then the RM command 'import' always failed with following error message: DNFL9461E OU mapping not possible for the following destinations: ''. Now, distribution files containing synonym LTs are processed correctly. PK57423 RM RM RECORDS ARE WRITTEN INTO RMDS WITH WRONG OU IF THE IMPORT COMMAND IS ISSUED IN AN OU OTHER THAN DNFSYSOU. Formerly, when the RM command 'import' was issued in a business OU other than DNFSYSOU the RM records were written for the wrong OU. Now, RM records are always imported for the correct OU. G. Other changes implemented by this PTF ---------------------------------------- - WebSphere BI for FN will report events when the following SWIFT System messages are received: DNFF4261I - S009 (request to logout) DNFF4262I - S008 (request to quit) - Notification of impending LAU key expiration When a LAU key is about to expire, or has already expired, WebSphere BI for FN now issues a warning message. For more information refer to System Administration, chapter 'Configuring LAU key expiration'. - Signature reverification WebSphere BI for FN now provides a service that regularly reattempts to verify the signatures of FIN messages for which a previous attempt failed due to a recoverable error. Message administrators can also reattempt signature verification manually. For more information refer to Concepts and Components, chapter 'Signature verification' and to System Administration, chapter 'Configuring signature verification'. - MT398 messages now processed in accordance with SWIFT CLS TPS When WebSphere BI for FN receives a SWIFT MT398 message, it now extracts and verifies the signature of the imbedded message, as required by the SWIFT Continuous Link Settlement (CLS) Third Party Service (TPS) specification. For more information refer to Concepts and Components, chapter 'Signature verification'. - More detailed status for FIN messages FIN messages in the Message Warehouse now provide more detailed information about their status. For more information refer to System Administration, chapter 'Message Warehouse Fields for FIN Messages', section 'Possible values in the MWH_MSG_STATUS field'. - WebSphere BI for FN is enhanced to retrieve (readGlobalParameters) and update (updateGlobalParameters) the following configuration values of an SAG: - GetFileQueue - FileDirectory - FileExpiration - MaxLFTMessageSize For more information refer to System Administration, chapter 'SAG configuration commands'. - WebSphere BI for FN is enhanced to allow read-only access to relationship management (RM) data via two new DB2 views. For more information refer to System Administration, chapter 'Managing WebSphere BI for FN data', section 'Retrieving RM data from the RM DS'. - the informational message DNFP9402I has been reclassified to an error message (DNFP9402E) - DNFCZMLC CREATES WRONG ADD STATEMENT Formerly, the configuration migration script dnfczmlc did create statements to reset the value of attribute 'MsgRuleSet' of CO 'DnfFinMsgVal' to 'swift2006' if you did change it to 'swift2007' when the SWIFT SR 2007 went live. Now, the script dnfczmlc does no longer create statements to change the attribute value for 'MsgRuleSet'. Note: If you are validating your FIN messages in WebSphere BI for FN the attribute must currently be set to 'swift2007' and you must have applied PTF UK27434. If you are validating your FIN messages outside of WebSphere BI for FN, e.g. in MERVA, then the value should remain 'swift2006' as you do not have PTF UK27434 applied that delivers the checking rules for SR 2007. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++