======================================================================= = IBM WebSphere Business Integration for Financial Networks = 5724-D9621 for Multiplatforms Extending Features V2.2.0 = PTF UK34476 for APAR PK62545 ======================================================================== 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 problems addressed by this PTF A. How to use this document --------------------------- This PTF requires the WebSphere BI for FN SAG AddOn at fix level PK39172 or above. You can download SAG AddOn updates from the following FTP server: ftp://ftp.software.ibm.com/ps/products/wbifn/ptfs/WBIFN_SAGAddOn/V2R2/SAGAddOn_for_SAG6 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 has been changed: /dnf_02_02/admin/data/DNFCOMMON.xml /dnf_02_02/admin/data/DNFEIAS.xml /dnf_02_02/admin/data/DNFFILEACT.xml /dnf_02_02/admin/data/DNFFIN.xml /dnf_02_02/admin/data/dnfceccs.cli /dnf_02_02/admin/data/dnfcfcfc.cli /dnf_02_02/admin/data/dnfcfrfc.cli /dnf_02_02/admin/data/dnfczaar.cli /dnf_02_02/admin/data/dnfczc1y.cli /dnf_02_02/admin/data/dnfczcah.lst /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/dnfczcoy.cli /dnf_02_02/admin/data/dnfczdas.cli /dnf_02_02/admin/data/dnfczdat.cli /dnf_02_02/admin/data/dnfczeco.ddl /dnf_02_02/admin/data/dnfczf02.ddl /dnf_02_02/admin/data/dnfczf03.ddl /dnf_02_02/admin/data/dnfczf04.ddl /dnf_02_02/admin/data/dnfczf3g.ddl /dnf_02_02/admin/data/dnfczfco.ddl /dnf_02_02/admin/data/dnfczfct.ddl /dnf_02_02/admin/data/dnfczfus.ddl /dnf_02_02/admin/data/dnfcztco.ddl /dnf_02_02/admin/win/com.ibm.dnf.Core.zip /dnf_02_02/admin/win/com.ibm.dnf.EnhInterAct.zip /dnf_02_02/admin/win/com.ibm.dnf.FileAct.zip /dnf_02_02/admin/win/com.ibm.dnf.FinInterfaceLayer.zip /dnf_02_02/admin/win/com.ibm.dnf.RelationshipManagementRuntime.zip /dnf_02_02/admin/win/com.ibm.dnf.SagCfg.zip /dnf_02_02/run/bin/dnfcfsfd /dnf_02_02/run/bin/dnfcfsfs /dnf_02_02/run/bin/dnfczmlc.sh /dnf_02_02/run/bin/dnfczml1.awk /dnf_02_02/run/bin/dnfczml2.awk /dnf_02_02/run/classes/dnfcdrtn.jar /dnf_02_02/run/classes/dnfcecom.jar /dnf_02_02/run/classes/dnfceias.jar /dnf_02_02/run/data/dnfcwdbs.bnd /dnf_02_02/run/data/dnfczcah.lst /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/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/lib/libdnfmbapi.a /dnf_02_02/run/lil/dnfcfpin.lil /dnf_02_02/run/lil/dnfchchk.lil /dnf_02_02/run/lil/dnfcuaut.lil /dnf_02_02/run/lil/dnfdgst.lil /dnf_02_02/run/lil/dnfrmimi.lil /dnf_02_02/run/lil/dnfuhsls.lil /dnf_02_02/run/msg/dnfccmsg.cat /dnf_02_02/run/res/dnfceevt.xml /dnf_02_02/run/res/dnfcersp.xml /dnf_02_02/run/res/dnfcfevt.xml /dnf_02_02/run/res/dnfchevt.xml /dnf_02_02/run/res/dnfclrsp.xml /dnf_02_02/run/res/dnfcsevt.xml /dnf_02_02/run/res/dnfcsrsp.xml /dnf_02_02/run/res/dnfctevt.xml /dnf_02_02/run/res/dnfctrsp.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 ----------------------------------- Before you start the customization migration you should ensure that earlier migrations are completed using the implement command. Otherwise the CDP might generate migration statements again, which may cause the deployment vehicles to fail. To update your current definition directory: 1. Log on to AIX on the customization system as a customizer (ucust1). 2. Change to the customization directory by issuing the following command: cd /var/dni_02_02/cus 3. Run your customization profile by issuing the following command: . ./dnicus_ 4. Start the CDP in migration mode by issuing the following command: dnicdpm -i 5. 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". 6. Import your current CDD by issuing the following command: import cdd/.cdd 7. 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' and 'DBBND' 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'. 8. 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 9. Quit the CDP session by entering the following command: quit E. Steps on a run-time system ------------------------------ E1. Install the DB2 UDF - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1. Log on as DB2 administrator. 2. Enter the following command to extract UDF jar file dnfxdrtn [-jar ] [-t ] where: is the directory containing the file dnfcdrtn.jar. The default is /opt/IBM/dnf_02_02/run/classes. is the target directory which UDF java class files will be extracted to. For example,/var/dni_02_02/run/routines. This command extracts the class files from the jar file and stores it into directory /com/ibm/dnf/dbm/rtn. You can check log file dnfrundb.log and trace file dnfrundb.trc in the current directory. Make sure the routine classes have been updated. 3. Issue a DB2 command in DB2 command mode to force DB2 to load the new classes: CALL SQLJ.REFRESH_CLASSES() E2. Transferring the WebSphere BI for FN 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.EnhInterAct.zip /dnf_02_02/admin/win/com.ibm.dnf.FileAct.zip /dnf_02_02/admin/win/com.ibm.dnf.FinInterfaceLayer.zip /dnf_02_02/admin/win/com.ibm.dnf.RelationshipManagementRuntime.zip /dnf_02_02/admin/win/com.ibm.dnf.SagCfg.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.EnhInterAct.zip get com.ibm.dnf.FileAct.zip get com.ibm.dnf.FinInterfaceLayer.zip get com.ibm.dnf.RelationshipManagementRuntime.zip get com.ibm.dnf.SagCfg.zip cd /dni_02_02/admin/win mget dni* bye E3. 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 3. Preparing to create an instance", "Preparing the WebSphere MB Toolkit workstation", -> "Setting the Toolkit version and directories" E4. Backing up all WebSphere BI for FN 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 E2. 2. Enter the command: dninibak This stores the following data in a compressed backup file: 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 the directory \eclipse\workspace that have names that begin with "DNI_" 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. E5. Installing the changed WebSphere BI for FN plug-ins - - - - - - - - - - - - - - - - - - - - - - - - - - - - To install the changed WebSphere BI for FN plug-ins: In the Command Prompt window and from the temporary directory you used in step E2., enter dnininst If the dnininst program issues an error message, check the log file for more information about the reason for the error. 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'. c. Select all projects with names like "DNI_*", right-click and select 'Refresh', then right-click and select 'Rebuild Project' E6. 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. To prepare the broker archive files: a. Ensure the Message Brokers Toolkit is not running. b. 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. c. Check the log file dniupdbd.log to ensure that the files were successfully prepared. E7. Stop all sessions and services you use - - - - - - - - - - - - - - - - - - - - - Stop all sessions and services you use, e.g. log out SIPN FIN LTs, stop Enhanced InterAct and release InterAct SnF sessions. How to do this is described in the System Administration manual, chapter 18: 'Operating components, sessions, and services'. Then close all open CLI sessions. E8. Stop all WebSphere BI for FN message brokers - - - - - - - - - - - - - - - - - - - - - - - - Stop all WebSphere BI for FN message brokers. E9. 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. 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 DNFFIN service bundle - replace 1 indices for table DNF_OAMS - bind a new package for the SFD 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. 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: a. In the Command Prompt window and from the temporary directory you used in step E2. and E6., 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 E6. and contained in the current directory to the broker(s). b. Check the log file dniupdbd.log 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 AIX 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. Switch to the directory into which dnfczmlc is to place the files it generates and enter the following command: dnfczmlc -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 /opt/IBM/dnf_02_02, the default directory is /opt/IBM/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 -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 If dual authorization is on (-dual YES): - dnfczmlc_6_sa_cre_co_com.cli - dnfczmlc_6_sa_cre_co_dep.cli Check the file dnfczmlc.log to ensure that dnfczmlc ran correctly. 6. Remove the statements that modify the value of attribute 'MsgRuleSet' of CO 'DnfFinMsgVal' for all business OUs in the files dnfczmlc_2_sa_ent_all.cli -or- dnfczmlc_6_sa_cre_co_com.cli For instance, add a semicolon (;) as first character of these lines to deactivate the statements. These statements were created by accident as described by APAR PK64423. If the removed or deactivated statement was the only modification for a OU then you must deactivate the commit (com), approve (app) and deploy (dep) statements for this OU. Otherwise, when you execute the files, you will receive error messages that indicate that the OU cannot be committed, approved or deployed. 7. Execute the generated CLI command files by entering the following command: dnicli -i -s DNI_SYSADM -ou SYSOU -cft | tee -a PK62545cli.log where: The name of the instance. The CLI command file name, for example dnfczmlc_6_sa_cre_co_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 system configuration administrator If dual authorization is on (-dual YES): 1. dnfczmlc_6_sa_cre_co_com.cli by the first system configuration administrator (sa1) 2. dnfczmlc_6_sa_cre_co_dep.cli by the second system configuration administrator (sa1) E13. Update existing bootstrap authorization records - - - - - - - - - - - - - - - - - - - - - - - - - - This step must be only performed if you did not previously install a PTF that fixed APAR PK54765 so that you already performed the update. If and how you have to update existing bootstrap authorization records depends on your usage scenario: - If you are using 'AuthProviderLocal' for all your LTs you were not impacted by the problem of APAR PK54765. No update is required. - If you are using 'AuthProviderLocal' for none of your LTs, all existing bootstrap authorization records have a wrong setting which causes the validate command to fail. To update the records, your DB2 administrator (udb2adm1) needs to issue the following SQL statement: UPDATE DNIvSN.DNF_RMES SET MC='Y' - If you are using 'AuthProviderLocal' for some of your LTs, but not for all, then please contact your IBM support representative to get additional instructions. E14. Changing the attribute 'MaxLength2000' of CO 'DnfExceptMsgAttr' - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This step must be only performed if you did not previously install a PTF UK26588 so that you already performed the update. To set the attribute MaxLength2000 of the CO DnfExceptMsgAttr to the correct value: 1. On the runtime system, log on to AIX with the user ID of a WebSphere BI for FN system configuration administrator (for example, sa1 or sa2). Ensure that you also have read access to /dnf_02_02/admin/data/dnfczc1y.cli, e.g. by being member of the group dniadmin. Alternatively, you can ask the customizer (for example, ucust1) for a copy of the file. 2. Execute your profile for the runtime environment, for example: . /var/dnf_02_02/run/dnfprofile 3. Start the command line interface (CLI) in transactional command file mode and execute the commands in the file dnfczc1y.cli by entering the following command on a single line: dnicli -ou SYSOU -s DNI_SYSADM -cft /dnf_02_02/admin/data/dnfczc1y.cli -cp IBM-1047 This command file changes the value of the MaxLength2000 attribute and commits the SYSOU. 4. Log on to AIX with the user ID of another WebSphere BI for FN system configuration administrator. 5. Execute your profile for the runtime environment, for example: . /var/dnf_02_02/run/dnfprofile 6. Start the CLI: dnicli -ou SYSOU -s DNI_SYSADM 7. Enter the following commands in your CLI session to approve and deploy the changes: app -ou SYSOU dep -ou SYSOU E15. Changing the LT configuration data - - - - - - - - - - - - - - - - - - - - This step must be only performed if: - You are a Central Institution and send MT097 messages with PV03 in Y-Copy mode. and - You did not previously install PTF UK26588. 1. On the runtime system, log on to AIX with the user ID of WebSphere BI for FN system configuration administrator (sa1 or sa2). 2. Execute your profile for the runtime environment: . /var/dnf_02_02/run/dnfprofile 3. Start the command line interface (CLI): dnicli -ou SYSOU -s DNI_SYSADM 4. Change your LT setting and add the FIN Copy service connection by issuing the following commands: add -ou -ct DnfLT -co -attr CiFinCopyService -val add -ou -ct DnfFinCopyServiceConn -co -attr SignerDN -val com -ou where: Name of the OU The name of the logical terminal. The 3-character ID of the FIN Copy service followed by an underscore and either LIVE or TEST. Two-digit number of the FIN Copy service connection, for example 01 Distinguished name of the security endpoint that is to sign the MT097 message for the specified combination of LT and connection 5. Approve and deploy the changes app -ou dep -ou E16. Changing the FIN Copy service profile definition - - - - - - - - - - - - - - - - - - - - - - - - - - _ FIN Copy service profiles are configured with COs of CT DnfFinCopyService and follow the naming scheme: 3 digit FIN Copy service code +”_? usage code The naming scheme has been enhanced to contain an optional component for the service administrator: 3 digit FIN Copy service code +”_? service administrator BIC +”_? usage code For more information refer to System Administration (SH12-6883-03), Chapter 11. 'Configuring SIPN FIN services', section 'Specifying FIN Copy configuration data'. E17. Restart all sessions and services you use - - - - - - - - - - - - - - - - - - - - - - - Restart all sessions and services you use, e.g. login SIPN FIN LTs, start Enhanced InterAct and aquire InterAct SnF sessions. How to do this is described in the System Administration manual, chapter 18: 'Operating components, sessions, and services'. *------------------------------------------------------------------------* * End of Migration * *------------------------------------------------------------------------* F. APARs addressed by this PTF ------------------------------ PK62545 SUMMARY PTF FOR WEBSPHERE BI FOR FN EXTENDING FEATURES 2.2 There are many separate PTFs with dependencies to each other for WebSphere BI for FN Extending Features 2.2. Most available PTFs should be replaced (superseded) by a Summary PTF to easily bring an environment to the current maintenance level. PK51688 FIN FINCOPY DIGEST CALCULATION ERROR FOR PARTIAL COPY SERVICES If a FINCopy service does partial copy and the fields used for calculation contain multiline fields (e.g. field 72, 57D), WBI-FN digest calculation only uses the first line. If the sender BIC of the message as well as the Central Institution are both logged in with protocol version 3, the MT096 will be rejected by the Central Institution with a Digest Verification error. PK52543 EIAS Enhanced InterAct Service must support SignatureList Some applications that exploit features introduced with SWIFTNet Link 6.0, for example RMA, need to be able to sign InterAct messages using a signature list. Formerly, the WebSphere BI for FN Enhanced InterAct service did not support the SignatureList message element. This has been corrected. PK53242 FAILED TO READ MWH WITH USER DEFINDED FUNCTION (UDF)ON DB2V9 When using User Definded Function (UDF) to read message warehouse from a DB2V9 message warehouse table, WebSphere BI for FN gets the error SQLSTATE=38W03 - XML message' was not found"." PK53945 FIN SR2007: DNFH3763E INVALID CHARACTER FOUND IN MESSAGE. In SWIFT SR2007 the Z character set is extended with the character '_' (underscore). The FIN check plugin needs to be changed to allow this character to be used in the appropriate fields. PK54765 RM FIN VALIDATE COMMAND FAILS FOR MERVA CONNCETED LTS Formerly, when bootstrap authorization were recorded based on MERVA BKE data, the origin information (MERVA, WBI-FN) in table DNF_RMES was not written correctly for MERVA connected systems. Therefore a VALIDATE command issued in service DNF_L_ADM tried to verify the bootstrap authorization against WBI-FN instead of MERVA, which led to error messages and failing command processing. This has been corrected. New bootstrap authorizations are recorded with the correct origin. PK55201 RM RM IMPORT NEEDS TO FOLLOW RMA SPECS Currently, if a rejected RMA Authorisation is included in an RMA Import file, WebSphere BI for FN does not change the status of the authorisation. It remains enabled. According to the RMA vendor specification, the authorisation must be updated even if the 'Issued Datetime' (IssdDtTm) is the same as with the previous authorisation. The FIN vendor specification says that an import is only allowed when the 'Issued Datetime' (IssdDtTm) of the update is greater than the timestamp of the available authorisation. According to SWIFT the FIN vendor specification will be updatetd to match the RMA vendor specification. PK56044 FIN RP USER RESYNCH REQUIRED AFTER SWIFT ABORT SS100 FS012 Formerly, the user had to manually re-login the LT after system abort SS100 FS012. However, the reason for this abort is often of temporary nature so that the SFD will now automatically try to resynchronize. PK56943 RM DNF_L_ADM MESSAGEFLOW LOOPING DURING THE VALIDATE COMMAND Formerly, the validate command did process all records within a single transaction, which could lead to resource shortages, long execution times or even abends of the execution group depending on the number of records. Now, validate is performed in chunks of 10 bootstrap authorizations in a single transaction. The flow triggers itself to process the next chunk. A response to CLI is returned after having processed all bootstrap authorizations. G. Other problems addressed by this PTF --------------------------------------- - IMPLEMENT THE OFFICIAL T2 DATE ANNOUNCED AND CONFIRMED BY SWIFT: SEPTEMBER 28TH, 2008 Formerly, SWIFT only mentioned that T2 will start end of September 2008. SWIFT now announced and confirmed that T2 will begin on September 28th, 2008. The attribute value of attribute T2 of the configuration object DnfFinPhase2Migration reflects this date and will be adapted accordingly, if it still is at the default value 2008-09-30 as originally provided by WebSphere BI for FN. - PARTIAL IMPORT OF RM DATA INCLUDING PERMISSIONS DOES NOT WORK PROPERLY Formerly, if a RM import file containing service-specific permissions was imported in partial mode, the permissions were imported corrrectly, but the flag to actually use them was not set. Therefore the permissions did not become effective during authorization of messages. Now, the RM import command sets the flag to use permissions if an import is done in partial mode. To correct previously imported data repeat the import. - SUPPORT FOR SAG/SNL 6.1 FOR WEBSPHERE BI FOR FN ENHANCED INTERACT Formerly, changes introduced with SNL 6.1 caused the Enhanced InterAct service to fail with an error event DNIX2110E related to message audit. Now, Enhanced InterAct can work with SAG/SNL 6.1. - SUPPORT POLICY ID IN SetupUserForRecovery COMMAND The SetupUserForRecovery SAG configuration command now supports the parameter -policy to be able to move existing certificates into the HSM box. There is a corresponding update of the WebSphere BI for FN SAG AddOn that you have to install. - EIAS DNFE3400E DNF_EI_LRT THE EIA SERVICE HAS RECEIVED AN SAG CLIENT RESPONSE MESSAGE WITH AN INVALID PAYLOAD CONTENT. The Enhanced InterAct service does not validate the business message. When a message validation error response is received from the SIPN this can result in a parser error in Enhanced InterAct. The event DNFE3400E is thrown and the message is routed to a backout queue. This has been corrected. - SAG Cfg PROBLEMS WITH ADDMESSAGEPARTNERCOM COMMAND Formerly, When performing several addMessagePartnerCom commands using service DNFSAGCFG in DNFSYSOU, and the MessagePartnerCom were destined for different business OUs, the 'approve -sag ' command did only approve the business OU specified in the last addMessagePartnerCom command and the DNFSYSOU. All other Ous were not approved and cannot be deployed with a 'deploy -SAG ' command, if dual authorization is switched on. This has been fixed. - FIN SIGNERDN VERIFICATION FAILED FOR RECEIVED TANK FILES When using PV3, WebSphere BI for FN does not recognize that received tank file messages are T&T and therefore SignerDNs must not be checked. The behavior has been corrected. - SAG AddOn MESSAGE FILE CHANGES FOR SAG ADDON APAR PK45605 The fix for SAG AddOn APAR PK45605 requires an update of the message files in WebSphere BI for FN in order to display the SAG AddOn events correctly. - SAG Cfg MISSING MDT ATTRIBUTE DURING THE DEPLOY TO SAG IN DNFSAGCFG SERVICE Formerly, when addCert command was the first SAG Configuration command and no other SAG configuration object did exist, the created configuration object did not have the 'mdt' attribute required by the SAG Add-On. This did result in error DNFS1533E when deploying to the SAG. The SAG Configuration service now correctly adds the mdt attribute. - EIAS WRONG MESSAGE PARTNER DISPLAY IN EIAS QUERY Formerly, when using the query command for service DNF_EI_CMD sometimes the wrong message partner was displayed. This has been corrected. - FIN PERFORMANCE DEGRADATION IN ACCESSING DNF_OAMS WHEN LT GROUPING IS USED The CPU consumption of the SQL query used to access the DNF_OAMS table in LT grouping scenario was increased. A new query was designed to optimize the CPU consumption. - FIN IMPROVE TRACING FOR SITUATIONS WHERE MESSAGE DNFF4011E IS LOGGED WHEN LTS LOG OFF It sometimes happened that message DNFF4011E is logged when LT's are logged off. The current trace information was not sufficient to identify this problem. The tracing has been improved for this scenario. - SAG AddOn MESSAGE FILE CHANGES FOR SAG ADDON APAR PK50170 The fix for SAG AddOn APAR PK50170 requires an update of the message files in WebSphere BI for FN in order to display the SAG AddOn events correctly. - FIN PROBLEM WITH WHITE SPACE IN DNS WebSphere BI for FN must be able to process messages received from SWIFT. This applies also to messages that are not fully compliant to all the rules of the format of a DN as specified in the Naming and Addressing guide (e.g. messages with DNs which contain white spaces or uppercase). Formerly these messages caused error DNFH3861E (signature verification error). Now, the signature of the SWIFT OSN is successfully verified even if the signer DN contains whitespaces or uppercase characters. - FIN MWH_AMOUNT SOMETIMES EMPTY Formerly the field MWH_AMOUNT was not filled, if a message field prior to field 32A or 32B contained a value of :32. This has been corrected. Formerly, after receiving an ISN ACK message, the RFH2 was contained twice in the message warehouse record for the original ISN message. This has been corrected. - FIN NO BOOTSTRAP RECORDS CREATED FOR TORCV Formerly, no bootstrap records were created when receiving messages from SWIFT, if the messages are received in 'PV2 format' (no digests, but MAC/PAC). Now, bootstrap records are always created, when the LT is logged in with PV3. - FIN EXECUTIONGROUP FNFIN THOWS EXCEPTIONS WHILE UPDATING IN MWH Formerly, when messages with parameter Resend=True are rejected by WebSphere BI for FN, the message warehouse update throws an exception. This has been corrected. - FIN DNFH3901E WEBSPHERE MB ERROR DURING CONFIGURATION-DATA PROVIDER PROVIDER NODE PROCESSING; REASON CODE: '22'.: DNFCHDGT(255) Formerly, messages containing invlid characters, which used the flag MessageValid=Yes to omit the message validation could cause an error in the digest calculation. Now WebSphere BI for FN checks the characters used in a message in each case before calculating a digest. An error is returned to the sending application if an invalid character is contained in the message. - FIN FINCOPY FAILS WHEN AUTHENTICATION IS DONE IN WBI-FN AND MESSAGE HAS NOT TO BE AUTHENTICATED Formerly the following scenario failed: - A message was passed to WBI-FN which was not already authenticated - The message type itself does not need authentication - A FIN Copy service was specified in field 103 of the message which needs double authentication If the FIN Copy service requires authorisation, the message was rejected by WBI-FN with DNFL9430E. If the FIN Copy service does not require authorisation, the message was rejected by SWIFT or the central institution because of a missing PAC. This has been corrected. - FIN STORING DATA IN MWH DOES NOT WORK CORRECT ANYMORE: ISN AND OSN IS 0 FOR ALL MESSAGES After the fix for PK48348 was applied, the following message warehouse problems could have been observed: - ISN and OSN were always 0 - for acknowledgments, sender BIC and sender LT were empty - application name and user contained 'SWIFTNETFIN' This has been corrected. - FIN PROBLEM INCREASING THE COMMIT COUNT ON A MESSAGE FLOW THAT HAS BEEN DEPLOYED TO A BROKER MORE THAN ONCE Formerly, when DNF_ILC_FIN and DNF_ILS_FIN have been deployed more than once, deadlocks may have occured when accessing table DNF_RMDS. This has been corrected. - FIN MISSING 'EXPLANATION' PARAMETER IN DNFH3720E FOR MERVA CONNECTED LTS AND UNIMPORTANT ERROR DISPLAYED IN MERVA Formerly, the explanation parameter for message DNFH3720E was not filled. In addition the order of error reasons reported to MERVA did not ensure that the most important reason was displayed in MERVA. This has been corrected. - FIN OUTPUT MESSAGE IN DNF_ILC_FIN QUEUE LEADS TO WRONG BEHAVIOUR Formerly, when a SWIFT OSN was sent to DNF_ILC_FIN by accident, and exception queue handling was configured, the message was passed back twice. One copy was passed back to the application with error code DNFH3790E, a second copy was put to the configured exception queue with error code DNFH3799E. This has been corrected. - RM DNFL9542E THE IMPORT NODE DETECTED AN INVALID TRIGGER MESSAGE Formerly, the import command did not handle invalid import files properly. No response or event was provided and the service stopped processing. After restart it failed again with the same input message, which was still on the queue. Now, an invalid import file is recognized and an appropriate response is generated. APAR PK56787 addresses a subsequent problem in this scenario, which prevented an error event to be written by DNF_L_IMP. Therefore you should also install the PTF for APAR PK56787. - RM WRONG OUTPUT OF THE QUERY COMMAND IN SERVICE DNF_L_ADM Formerly, the query command displayed the date for issued status twice. Now, the output contains the date only once. - RM INFORMATIONAL EVENTS FROM DNF_L_ADM SHOULD NOT CAUSE BROKER EXCEPTIONS Formerly, informational responses caused the WebSphere message broker to write exceptions in the console log. Now, informational responses are processed without causing message broker exceptions. - RM AUDIT LOG RECORDS FOR RMDS CHANGES WRITTEN IN WRONG OU IF IMPORT FILE CONTAINS DATA FOR OTHER OUS THAN THE CURRENT Formerly, the import command wrote all audit information in the audit table of the current OU, even if the import file contained data for other OUs. Now audit records regarding changes in Relationship Management Data Store (RMDS) are always written to the message audit table of the OU that is actually affected by the changes. However, command audit records are always written to the message audit table of the OU in which the import command is issued. - RM SQL ERROR HY093 WHEN EXECUTING VALIDATE COMMAND Formerly, the validate command failed with SQL error HY093 if more than 10 bootstrap authorizations had to be updated. Now, validate can also handle more than 10 updates. - RM IF WBI-FN MQ HLQ CONTAINS A DOT, THE LOCAL QUEUE .DNF_L_IMP WILL NOT FOUND. Formerly, when the customization placeholder DNIvQPFX contained a dot, the RM import service did not find the queue .DNF_L_IMP. This has been corrected. - RM FAILED TO UPDATE RM RECORDS WITH PARTIAL IMPORT MODE Formerly, when import was done in partial mode, no records were updated in the table when column REC_ISSUED_GMT_TS contained the NULL value for an existing record. This has been corrected. - RM DNF_L_IMP FAILS TO WRITE EVENT MESSAGE ON PROCESSING ERRORS Formerly, DNF_L_IMP failed to write event messages with WebSphere MQ reason code 2097. Now events are successfully written into the WebSphere BI for FN event log. - FIN AFTER RESENDING A MESSAGE AFTER DNFH3799E THE MERVA REF STRING MAY NOT FOUND Formerly, if a message was passed back to an application other than MERVA with error indication DNFH3799E and this message was sent to WBI-FN again after the problem was solved, a MERVA connect error could occur, because the MERVA reference string was not found. In this case the message was passed back to the application again with DNFH3799E Reason DSL884I NIC4000. Now, resended messages from applications other than MERVA are processed correctly. - FIN BOOTSTRAP RECORD WRITTEN EVEN WITHOUT VALID BKE Formerly, when a message was received WebSphere BI for FN created a bootstrap authorization without a valid BKE record on certain environments. Now WebSphere BI for FN only creates bootstrap authorizations if valid BKE records exist. A subsequent problem occured after the validate command of service DNF_L_ADM set such erroneous bootstrap authorizations to status 'Invalid'. These 'Invalid' bootstrap authorizations caused the error DNFL9430E (reason NOTFOUND") when FINCopy messages were received which do not require authorization e.g. for the TARGET2 service. Now FIN Copy messages which do not need authorization do not cause authorization failures in WebSphere BI for FN even if 'Invalid' bootstrap authorizations exist. +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++