============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2013 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 Message Management PTF UK90472 for APAR PM84606 Driver level: 3220 Date 2013-06-24 ============================================================================== ============================================================================== 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. If you install more than one PTF at a time, combine the readme documents by merging the contents of each section. 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 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: PM84606 MM SCROLL BAR IN WRONG POSITION WHEN COPYING OR MOVING MESSAGES FROM THE QUEUE LIST PM83508 MM IMPROVE MWH INSERTS/UPDATES IN MER FOR FIN PM82236 MM MER MSG ROUTING IS NOT AS EXPECTED PM86975 MM CHANGES NECESSARY TO SUPPORT WEBSPHERE BI FOR FN BASE CDP APAR PM78252 PM75655 MM MER PRINT PROBLEM WHEN ENTER COMPLEX CHARACTER (E.G. CHINESE) OR SIMPLE BUT SPECIAL CHARACTERS IN THE COMMENT. PM86067 MM GPA SYSTEM MESSAGE (E.G. GPA072) ACKNOWLEDGED BY SWIFT ARE NOT VISIBLE IN MER MESSAGE LISTS PM85704 MM DNIY0120E OCCURRED WHEN RECEIVED MT598 WITH EMPTY FIELDS FROM SWIFT PM84140 MM A DB2 -913 ERROR (DEADLOCK) OCCURRED WHILE USER PROCESS MESSAGES IN MER PM82591 MM NO SUPPORT FOR SINGLE SIGN-OFF VIA AUTHENTICATION PROXY IN MER/A&O/RMA GUI PM86803 MM AFTER APPLY OF MM PTF UK90053, ACKNOWLEDGED FIN SYSTEM MESSAGES CAN NO LONGER BE OPENED FROM THE MER MESSAGE LIST PM87626 MM CAN NOT KEY IN LOWERCASE 'P' IN FIELD 79 WHEN CREATE FIN799 MESSAGE PM86968 MM DNQE6800I, DNQE6801E ARE NOT IN MESSAGE CATALOGUE IN PTF UK90053, THIS LEADS TO DNIK2560E MESSAGE TEXT NOT AVAILABLE PM88543 MM THE MESSAGE TEMPLATE CREATED ON MER IS WRONGLY STORED AS AN ENTRY IN MWH Additional functional changes: - Requirement MR0228135337 "FIN reference extraction" implemented - Requirement MR1023123838 "Display branch information" implemented - Import of MX templates implemented - API Extract nested message out of MT021 implemented - Cleanup utility to manage and delete messages in MER queues implemented - Monitoring of MER queues according to a threshold implemented - Custom defined Retype-fields for FIN messages implemented Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Concepts and Components - Messages and Codes - System Administration - Application Programming - User's Guide - Information Center The following modules have been changed: /dnqv311/admin/appsrv/res/dnq.app.main.ear /dnqv311/admin/data/dnq.xml /dnqv311/admin/data/dnqcecoo.cli /dnqv311/admin/data/DNQCOMMON.xml /dnqv311/admin/data/dnqczcah.lst /dnqv311/admin/data/dnqczcat.cli /dnqv311/admin/data/dnqczcob.cli /dnqv311/admin/data/dnqczect.ddl /dnqv311/admin/data/dnqczpct.ddl /dnqv311/admin/data/DNQER.xml /dnqv311/admin/data/DNQERBS.xml /dnqv311/admin/data/DnqMer_upd.py /dnqv311/admin/data/DnqMer.py /dnqv311/admin/data/DNQPRINT.xml /dnqv311/admin/data/DNQROUTS.xml /dnqv311/admin/toolkit/com.ibm.dnq.api.jar /dnqv311/admin/toolkit/DNI_DnqErCommon.zip /dnqv311/admin/toolkit/DNI_DnqErSwiftNetFin.zip /dnqv311/admin/toolkit/DNI_DnqErSwiftNetMX.zip /dnqv311/admin/toolkit/dnq.project.interchange.zip /dnqv311/run/classes/com.ibm.dnq.attex.jar /dnqv311/run/classes/dnq.print.jar /dnqv311/run/classes/dnq.common.jar /dnqv311/run/config/com.ibm.dnq.maxhf.domain.DNIFIN.xml /dnqv311/run/data/dnqczcah.lst /dnqv311/run/data/dnqczcat.cli /dnqv311/run/data/dnqczcob.cli /dnqv311/run/flows/DNQ_K_FIN1.bar /dnqv311/run/flows/DNQ_K_FIN2.bar /dnqv311/run/flows/DNQ_K_MX1.bar /dnqv311/run/flows/DNQ_K_TPL.bar /dnqv311/run/flows/DNQ_K_UAR.bar /dnqv311/run/flows/DNQ_P_CMD.bar /dnqv311/run/flows/DNQ_P_DSP.bar /dnqv311/run/flows/DNQ_P_PRT.bar /dnqv311/run/jplugin/dnq.broker.runtime.nodes.jar /dnqv311/run/msg/dnqcemsg.cat /dnqv311/run/msg/dnqckmsg.cat /dnqv311/run/msg/dnqcpmsg.cat /dnqv311/run/msg/DNQE_Msg.properties /dnqv311/run/msg/DNQK_Msg.properties /dnqv311/run/msg/DNQP_Msg.properties /dnqv311/run/msg/DNQR_Msg.properties /dnqv311/run/res/dnqceevt.xml /dnqv311/run/res/dnqckevt.xml /dnqv311/run/res/dnqcpevt.xml The following modules are new: /dnqv311/admin/data/dnqcze03.ddl /dnqv311/admin/data/dnqczp02.ddl /dnqv311/admin/data/dnqczpm2.ddl /dnqv311/admin/data/DNQMON.xml /dnqv311/admin/data/DNQMON.properties /dnqv311/run/bin/dnpadm.sh /dnqv311/run/classes/dnqcaadm.jar /dnqv311/run/flows/DNQ_K_MON.bar /dnqv311/run/msg/DNQA_Msg.properties /dnqv311/run/msg/dnpctmsg.cat /dnqv311/run/msg/dnqcamsg.cat /dnqv311/run/res/dnpctevt.xml /dnqv311/run/res/dnqcaevt.xml 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. To check this, log on to AIX on the customization system as a customizer (ucust1) and enter the following command on your customization system: /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 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 the migration for this PTF has been completely finished, ensure that no changes are made to the currently implemented CDD. 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 ------------------------------------------ - UK92427 for APAR PM79562 (MM 3.1.1.8, SEVERAL DNQERQUEUEINPUT NODES IN THE SAME FLOW MIX UP PROPERTIES). - UK94069 for APAR PM84617 (Base 3.1.1.12, IMPROVE ADMINISTRATION AND OPERATION FACILITY SECURITY) C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - DB2 administrator (udb2adm1) - 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) 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 /dnqv311/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 /dnqv311/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 /dnqv311/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 to AIX on the customization system as a customizer (ucust1). 2. Change to the customization directory: cd 3. Run your customization profile: . ./dnicus_ 4. Start the CDP in migration mode and use the following commands to migrate customization data: dnicdpm -i > export cdd/_UK90472_temp.cdd > supplement cdd/_UK90472_temp.cdd cdd/_UK90472.cdd Edit the supplemented CDD. Search for each occurrence of the new placeholder DNIvLOGOUTURL. Make sure that the value of the placeholder is empty. After you have successfully completed the installation and migration process for this PTF you can do customization for the new placeholder. > import cdd/_UK90472.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 * Index DNIvSN.DNQX4EMS added * Index DNIvSN.DNQU1EMD added * Table DNQP_MESSAGE changed, Column ROW_CREATION_UTS added * Index DNIvSN.DNQX1PQU added * Index DNIvSN.DNQX1POR added * Index DNIvSN.DNQZ1PMS added * Index DNIvSN.DNQY2PMS added * Index DNIvSN.DNQY5PMS added * Index DNIvSN.DNQX1PCN added * Index DNIvSN.DNQY1PMS dropped * Index DNIvSN.DNQX2PMS dropped * Index DNIvSN.DNQX5PMS dropped - CFGPF * 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: - do not execute the instructions provided for resource class CFGPF now; you will use them in step D13.3. D8. Additional activities ------------------------- D8.1. DB2 related activities ---------------------------- NOT APPLICABLE. D8.2. WebSphere MB related activities ------------------------------------- NOT APPLICABLE. D8.3. WebSphere MQ related activities ------------------------------------- NOT APPLICABLE. 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 ------------------------- NOT APPLICABLE. 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 - - - - - - - - - - - - - - - NOT APPLICABLE. 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 ----------------------------------------------------- To prepare the migration of configuration entities: 1. On the runtime system on which the message broker runs, log on to AIX as the system configuration administrator, for example, sa1, and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a temporary directory where dnfczmlc stores the CLI command files which will contain the configuration migration statements. 3. Switch to this directory and enter the following command: dnfczmlc.sh -i [-dual YES|NO] [-to timeout] where: -i The name of the instance. -dual YES|NO Specifies whether files are to be created for a system that uses dual authorization for SYSOU. The default is -dual YES. Specify -dual NO only if dual authorization is to be turned off for both DNI_SYSADM and DNI_SECADM in SYSOU at the time when the created files are executed. Whether dual authorization is switched on or off for other OUs is irrelevant. -to timeout The number of milliseconds that the CLI waits for a response to this command before it issues an error message. The default is 100000 (100 seconds). It must be a whole number between 20000 and 9999999. Note: This command starts a long-running task that might take several minutes to complete. Check the file dnfczmlc.log to ensure that it completed successfully. The program dnfczmlc creates the following CLI command files: If dual authorization is not used (-dual NO): 1. dnfczmlc_2_sa_ent_all.cli If dual authorization is used (-dual YES): 1. dnfczmlc_5_sa_cre_ct_com.cli 2. dnfczmlc_5_sa_cre_ct_dep.cli 3. dnfczmlc_6_sa_cre_co_com.cli 4. dnfczmlc_6_sa_cre_co_dep.cli This PTF changes the following configuration entities: - New attributes added to CT DnqEROUOptions add -ct DnqEROUOptions -attr FINReferenceExtraction add -ct DnqEROUOptions -attr MonitorThresholdUser add -ct DnqEROUOptions -attr MonitorThresholdRouting add -ct DnqEROUOptions -attr RetypeFieldDefinitionsFile - New attributes added to CT DnQERQueue add -ct DnQERQueue -attr MonitorThresholdUser add -ct DnQERQueue -attr MonitorThresholdRouting - New attribute for CO DnqEROUOptions of type DnqEROUOptions addded add -ou -ct DnqEROUOptions -co DnqEROUOptions -attr FINReferenceExtraction -val '108,20' D12.2 Executing the migration scripts ------------------------------------- Execute the CLI command files generated in step D12.1 in the following sequence and using the following user authorization: If dual authorization was not used (-dual NO): - dnfczmlc_2_sa_ent_all.cli by any SA If dual authorization was on (-dual YES): - dnfczmlc_5_sa_cre_ct_com.cli by the first SA (sa1) - dnfczmlc_5_sa_cre_ct_dep.cli by the second SA (sa2) - dnfczmlc_6_sa_cre_co_com.cli by the first SA (sa1) - dnfczmlc_6_sa_cre_co_dep.cli by the second SA (sa2) 1. On the runtime system, log on to AIX as the indicated user and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Switch to the temporary directory you created in step D12.1 and execute the generated CLI command files by entering the following command: dnicli -s -ou SYSOU -cft | tee -a UK90472cli.log where: DNI_SYSADM for files executed by the system configuration administrators, abbreviated as SA The CLI command file name, for example dnfczmlc_5_sa_cre_ct_com.cli. 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: DnqErFinInput DnqErFinOutput DnqErMsifInput DnqErMsifOutput DnqErQueueInput DnqErQueueOutput DnqFinInput DnqFinExtractFromMT021 DnqPrintInputAdapter -> sample message flows in these projects: - DNI_DnqErCommon - DNI_DnqErSwiftNetFin - DNI_DnqErSwiftNetMX - DNI_DnqErRouting 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. *------------------------------------------------------------------------------* * End of Installation * *------------------------------------------------------------------------------* E. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM84606 MM SCROLL BAR IN WRONG POSITION WHEN COPYING OR MOVING MESSAGES FROM THE QUEUE LIST Now, when selecting from a long list of target queues for a move or copy operation in the message list, the scrollbar appears in the drop-down list rather than at the side of the browser window. PM83508 MM IMPROVE MWH INSERTS/UPDATES IN MER FOR FIN When FIN messages are created in MER, the MWH field MWH_MSG_TYPE must show ACK for ACK's and NAKs, and not the MT of the original ISN. For NAK'ed messages, the NAK and the corrected message must be treated seperately, and lead to 2 entries in MWH. The MWH_EXT_IDENTIFIER field should not show ComIbmDnfFIN, as this relates to DNF_IL*. Formerly, the MWH fields MWH_MSG_TYPE and MWH_EXT_IDENTIFIER did not show the expected information. Now, this has been changed. The MWH_EXT_IDENTIFIER in this case is ComIbmDnqMM. PM82236 MM MER MSG ROUTING IS NOT AS EXPECTED Formerly, a code error caused some messages to be routed incorrectly. This error has been fixed and the messages are now routed correctly. PM86975 MM CHANGES NECESSARY TO SUPPORT WEBSPHERE BI FOR FN BASE CDP APAR PM78252 This PTF provides the changes required for WebShpere BI for FN Base (CDP) APARs PM80628, PM82134, and PM78252. Descriptions of problems refer to APARs PM80628, PM82134, and PM78252. PM75655 MM MER PRINT PROBLEM WHEN ENTER COMPLEX CHARACTER (E.G. CHINESE) OR SIMPLE BUT SPECIAL CHARACTERS IN THE COMMENT. Formerly, when a user in MER entered a complex character (e.g. Chinese) in the comment and such a message was printed out, strange control characters were printed for the whole comment which was unreadable. The print output after the comment was also corrupted. A similar problem might occur when simple, but special characters were used (e.g. danish or german umlaut). In that case not the whole comment was unreadable, but only the single special character. Now, all characters that can not be displayed in the default charset of the hosting Java virtual machine used by the message broker are replaced with the default substitute character (usually, the question mark "?"), and the print output is no longer disarranged by unexpected control characters. PM86067 MM GPA SYSTEM MESSAGE (E.G. GPA072) ACKNOWLEDGED BY SWIFT ARE NOT VISIBLE IN MER MESSAGE LISTS Formerly, GPA System Message (e.g. GPA072) acknowledged by SWIFT were not visible in MER message lists. Affected were acknowledged ISN messages and received OSN messages. Now, this has been corrected. PM85704 MM DNIY0120E OCCURRED WHEN RECEIVED MT598 WITH EMPTY FIELDS FROM SWIFT Formerly, when receiving MT598 message from SWIFT and the message contains empty field 77E, MER could not display the message properly and error DNIY0120E appeared. Now, this has been corrected. PM84140 MM A DB2 -913 ERROR (DEADLOCK) OCCURRED WHILE USER PROCESS MESSAGES IN MER Formerly, there was a chance that running several MER routing flows could cause a deadlock on DNQE_MESSAGES table. Now, an automatic retry for MER routing flows has been implemented which can circumvent temporary failures like this. PM82591 MM NO SUPPORT FOR SINGLE SIGN-OFF VIA AUTHENTICATION PROXY IN MER/A&O/RMA GUI With this change it is possible to configure a logout URL for single sign-off with an authentication proxy. PM86803 MM AFTER APPLY OF MM PTF UK90053, ACKNOWLEDGED FIN SYSTEM MESSAGES CAN NO LONGER BE OPENED FROM THE MER MESSAGE LIST Formerly, after MM PTF UK90053 had been applied, acknowledged FIN system messages could no longer be opened from the MER message list. The error message "no permission to open" occured, if user tried to open the message, and the Message Warehouse entry for the message didn't include the type any more. Now, this has been corrected. PM87626 MM CAN NOT KEY IN LOWERCASE 'P' IN FIELD 79 WHEN CREATE FIN799 MESSAGE Formerly, when using IE, it was not possible to type a lowercase p in field 79 or other multi-line input fields. Now, this has been corrected. PM86968 MM DNQE6800I, DNQE6801E ARE NOT IN MESSAGE CATALOGUE IN PTF UK90053, THIS LEADS TO DNIK2560E MESSAGE TEXT NOT AVAILABLE This behavior has been corrected. PM88543 MM THE MESSAGE TEMPLATE CREATED ON MER IS WRONGLY STORED AS AN ENTRY IN MWH Formerly, when creating a message template in MER, the template was stored as an entry in MWH. As the template is not a message it should not be stored in MWH. Now, this has been corrected. F. Other changes ---------------- - Message updates: * Event messages changed: DNQR0004E * Event messages new: DNQK2014E, DNQK1130I, DNQK1131I, DNQK1132E, DNQK1133E, DNQE5077E, DNPT0024I, DNQA0017I - DNQA0022I, DNQA0023E, DNQA0025E, DNQA0026I * Response messages changed: DNQE9990I, DNQE9991E, DNQE9992E, DNQE9993E, DNQE9994E, DNQE9997E, DNQE9998E, DNQE9999E * Response messages new: DNQK1050E, DNPT0002I-DNPT0022I, DNQA0003I-DNQA0013I, DNQA0015I, DNQA0024E, DNPT0023E * Messages depricated: DNQE6800I, DNQE6801E - Message Printing: * Formerly, if the data displayed in section "Message History" did not fit into a line, then it was cut off. Now, message history data is rearranged and no longer cut off. * Formerly, it was not apparent at which point of time a print output was generated. Now, a timestamp is provided in the header for each message. This timestamp specifies the UTC date and UTC time when the message printing service generated the output for this message. - Requirement MR0228135337 implemented: Now, in the message list the column reference can be customized for newly created FIN messages or FIN messages sent to MER. The value of the FINReferenceExtraction attribute of the CO DnqEROUOptions of type DnqEROUOptions determines from which FIN message field the message reference of the corresponding WebSphere BI for FN message is to be extracted. Only the following values are valid: 108,20 The fields of the FIN message are checked in the following order: - Field 108 (ApplicationReference) - Field 20 (TransactionReference) - Field 20C with qualifier SEME (TransactionReference) This is the default. 20 The fields of the FIN message are checked in the following order: - Field 20 (TransactionReference) - Field 20C with qualifier SEME (TransactionReference) The message reference is set to the first non-null value that is detected. If all field values are null, the message reference is not set. - MER has been changed to provide the following information in the request message that is passed to FIN or MSIF: * ApplicationInformation.User is set to the MER User that created the message * ApplicationInformation.Application is set to a string that indicates the MER component (DNQMER) - Requirement MR1023123838 "Display branch information" Information about individual branches is now displayed to users of the MER Facility. This information is shown in the list of BICs that is displayed during message creation, and in the BIC information field that is displayed after a BIC is selected. - Cleanup utility The MER Facility provides an administrative command-line utility for removing oudated messages from MER queues and updating the message warehouse. - Monitor queue depth of MER queues The new MER queue-depth notification service generates event messages that notify users when either: * The number of messages that are waiting to be routed reaches or exceeds a specified threshold. * The number of messages that are awaiting user action reaches or exceeds a specified threshold. - Custom defined retype fields The MER Facility uses default definitions to determine which fields of a FIN message in a retype queue must be retyped (and are therefore not displayed). For each message type, the default definitions can be replaced with custom definitions. - Import of MX message templates The template import service, which imports message templates into the MER Facility, can now process MX message templates, too. - API extract nested message out of MT021 A new node (DnqFinExtractFromMT021) can be used to extract a nested APDU from a FIN MT 021 Retrieved Message (Text and History). G. Known issues --------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++