============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2014 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 (3.1.1.15) PTF UI19671 for APAR PI17975 Driver level: 4320 Date 2014-08-22 ============================================================================== ============================================================================== 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-01.ibm.com/support/docview.wss?uid=swg27041133 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 name of the organizational unit. Depending on the context, this might be SYSOU, DNFSYSOU, or the name of a business OU. 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 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. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PI17975 MM SWIFT SR2014: MESSAGE MANAGEMENT UPDATES FOR SWIFT SR2014 CHANGES PI19785 MM AMOUNT VALUE COULD NOT SHOW PROPERLY WHEN RECEIVE MT N92 IN MER PI18586 MM LOCALE SETTING IS NOT RECOGNIZED WHEN FILTERING THE MER MESSAGE LIST FOR AMOUNT PI17952 MM MISMATCH BETWEEN DNQ_K_UA.BAR AND THE CORRESPONDING PI (DNQ.PROJECT.INTERCHANGE.ZIP) PI20173 MM LEAVE THIS FIELD EMPTY SHOULD NOT BE SHOWN ON MANDATORY FIELDS IN MER PI14736 MM BAD PERFORMANCE ON CREATE QUEUE WHEN ASSOCIATED TEMPLATE QUEUE CONTAINS HIGH NUMBER OF TEMPLATES Additional functional changes: - none Documentation updates: The following manuals have been changed: - Message Entry and Repair Facility User's Guide The following modules have been changed: /dnqv311/admin/appsrv/res/dnq.app.main.ear /dnqv311/admin/data/DNQER.xml /dnqv311/admin/data/dnqczcat.cli /dnqv311/admin/data/dnqczcob.cli /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/dnq.maxhf.api.jar /dnqv311/run/config/com.ibm.dnq.maxhf.domain.DNIFIN.xml /dnqv311/run/data/dnqczcat.cli /dnqv311/run/data/dnqczcob.cli C. Planning ----------- C1. Checks to be done >>BEFORE<< installing a new PTF ----------------------------------------------------- 1. Check if you have any efixes (emergency fixes) applied in your WebSphere BI for FN installation. In case you have efixes installed after your previous WebSphere BI for FN PTF installation and migration contact your IBM support before installing and migrating this PTF. 2. Ensure that all previously prepared deployment instructions were carried out. 3. 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. 4. Until the migration for this PTF has been completely finished, ensure that no changes are made to the currently implemented CDD. 5. 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'. 6. 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 -rg % -qo mor [only for SYSOU] > list -user % -qo mor The list command should result in 'No roles/role groups/users found that match specified criteria'. C2. Prerequisite and supersede information ------------------------------------------ This PTF requires the following PTFs: - UI18302 for APAR PI18228 (MM 3.1.1.14, SUPPORT OF MICROSOFT INTERNET EXPLORER 11) - UI19670 for APAR PI17958 (Base 3.1.1.20, SWIFT SR2014: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION) 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) - First WebSphere BI for FN security administrator (ua1) - Second WebSphere BI for FN security administrator (ua2) D. Installation --------------- D1. Stopping all sessions and services you use ---------------------------------------------- Stop all sessions and services, for example: - Stop all applications that send requests to WebSphere BI for FN. - Log out SIPN FIN LTs. - Close MSIF SnF input and output channels. - Release SWIFTNet SnF queues. - Stop the MSIF Message Transfer service. - Stop the Enhanced InterAct service. - Close all dnicli sessions. For further information, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration". D2. Stopping all application servers ------------------------------------ Stop all application servers. D3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- Stop all WebSphere BI for FN message brokers. D4. Backing up your system -------------------------- We recommend to backup your AIX LPAR so that in case of migration issues you can revert to your previous system setup and continue to process workload. D5. Installing PTF by InstallAnywhere ------------------------------------- 1. Install this PTF using IAW based on the chapter "Installing WebSphere BI for FN" in WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization. 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 D2. Steps on a customization system ----------------------------------- To update your current definition directory and the customized administrative scripts, and to create deployment instructions and vehicles: 1. Log on to AIX on the customization system as a customizer (ucust1). 2. Change to the customization directory: cd 3. Run your customization profile: . ./dnicus_ 4. Start the CDP in migration mode and use the following commands to migrate customization data: dnicdpm -i > export cdd/_UI19671.cdd > import cdd/_UI19671.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: - 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: If you continue, the current CDD will be overwritten by a new CDD." 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 exception: - do not execute the instructions provided for resource class CFGPF now; you will use them in step D13.3. D8. Additional 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 ---------------------------------------------------------------------------- NOT APPLICABLE. D11. Redeploy updated BAR files ------------------------------- 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: - Attributes added to CT DnqERMessageRightsDNIFUNDS add -ct DnqERMessageRightsDNIFUNDS -attr semt.021.001 -type P - Attributes added to CT DnqERMessageRightsDNIMX add -ct DnqERMessageRightsDNIMX -attr caaa.016.001 -type P add -ct DnqERMessageRightsDNIMX -attr caaa.017.001 -type P add -ct DnqERMessageRightsDNIMX -attr admi.011.001 -type P add -ct DnqERMessageRightsDNIMX -attr fxtr.007.001 -type P add -ct DnqERMessageRightsDNIMX -attr fxtr.012.001 -type P add -ct DnqERMessageRightsDNIMX -attr fxtr.013.001 -type P add -ct DnqERMessageRightsDNIMX -attr pacs.002.002 -type P add -ct DnqERMessageRightsDNIMX -attr pacs.002.003 -type P add -ct DnqERMessageRightsDNIMX -attr pacs.003.002 -type P add -ct DnqERMessageRightsDNIMX -attr pacs.003.003 -type P add -ct DnqERMessageRightsDNIMX -attr pacs.004.002 -type P add -ct DnqERMessageRightsDNIMX -attr pacs.004.003 -type P add -ct DnqERMessageRightsDNIMX -attr pacs.007.002 -type P add -ct DnqERMessageRightsDNIMX -attr pacs.007.003 -type P add -ct DnqERMessageRightsDNIMX -attr pacs.008.002 -type P add -ct DnqERMessageRightsDNIMX -attr pacs.008.003 -type P add -ct DnqERMessageRightsDNIMX -attr pacs.010.001 -type P add -ct DnqERMessageRightsDNIMX -attr pain.006.001 -type P add -ct DnqERMessageRightsDNIMX -attr pain.998.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.001.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.002.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.003.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.004.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.005.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.006.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.007.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.008.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.009.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.012.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.013.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.014.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.015.001 -type P add -ct DnqERMessageRightsDNIMX -attr seti.016.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.004.002 -type P add -ct DnqERMessageRightsDNIMX -attr setr.006.002 -type P add -ct DnqERMessageRightsDNIMX -attr setr.010.002 -type P add -ct DnqERMessageRightsDNIMX -attr setr.012.002 -type P add -ct DnqERMessageRightsDNIMX -attr setr.016.002 -type P add -ct DnqERMessageRightsDNIMX -attr setr.019.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.020.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.021.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.022.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.023.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.033.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.034.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.035.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.036.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.037.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.038.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.039.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.040.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.045.001 -type P add -ct DnqERMessageRightsDNIMX -attr setr.046.001 -type P add -ct DnqERMessageRightsDNIMX -attr supl.017.001 -type P add -ct DnqERMessageRightsDNIMX -attr supl.025.001 -type P add -ct DnqERMessageRightsDNIMX -attr tsmt.039.001 -type P - Attributes added to CO ALL of type DnqERMessageRightsDNIFUNDS add -ct DnqERMessageRightsDNIFUNDS -ou DNIvOU -co ALL -attr semt.021.001 - Attributes added to CO ALL of type DnqERMessageRightsDNIMX add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr admi.011.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caaa.016.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr caaa.017.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr fxtr.007.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr fxtr.012.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr fxtr.013.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pacs.002.002 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pacs.002.003 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pacs.003.002 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pacs.003.003 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pacs.004.002 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pacs.004.003 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pacs.007.002 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pacs.007.003 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pacs.008.002 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pacs.008.003 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pacs.010.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pain.006.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr pain.998.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.001.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.002.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.003.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.004.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.005.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.006.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.007.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.008.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.009.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.012.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.013.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.014.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.015.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr seti.016.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.004.002 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.006.002 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.010.002 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.012.002 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.016.002 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.019.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.020.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.021.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.022.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.023.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.033.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.034.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.035.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.036.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.037.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.038.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.039.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.040.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.045.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr setr.046.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr supl.017.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr supl.025.001 add -ct DnqERMessageRightsDNIMX -ou DNIvOU -co ALL -attr tsmt.039.001 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 UI19671cli.log where: 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. 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. Restarting all application servers - - - - - - - - - - - - - - - - - - - - - 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. D13.4. Migrating the enterprise application - - - - - - - - - - - - - - - - - - - - - - If the instructions created in step D2.4 contain the resource class CFGPF, follow this section now to update the enterprise applications. Note: A new web application may contain changed JavaScript and HTML files. To assure that the user works with the most current web application content it is recommended to clear the browser cache on each client workstation before the user logs in the next time. It is not sufficient to just reload the page. Please find the following sample description for the different browser types as reference for the user communication: Firefox 10.0.6 ESR and later From the menu bar select Tools -> Options. In the options dialog select the Advanced section. In the Advanced section select the Network notebook tab. Click on the "Clear Now" button to clear the browser cache. Internet Explorer 8 or later From the menu bar select Tools -> "Internet Options". On the General notebook page click the "Delete..." button in section "Browsing History". In the "Delete Browsing History" dialog check at least "Temporary Internet files" and click the Delete button to clear the browser cache. 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 ------------------------------------------------- You must update your Toolkit environment if you use at least one of the following components: - WebSphere BI for FN sample message flows as foundation for your own flow development - WebSphere BI for FN nodes in your own message flows - WebSphere BI for FN message set projects containing XML schema definitions, that, for example, are utilized by the XPath wizard Furthermore, you have to rebuild and redeploy your message flows if they are based on the WebSphere BI for FN API. The following resources are changed by this PTF: - WebSphere BI for FN sample message flows: DNQ_K_FIN1_4 DNQ_K_FIN2 DNQ_K_MX1_OUT DNQ_K_UA contained in projects: DNI_DnqErCommon.zip DNI_DnqErSwiftNetFin.zip DNI_DnqErSwiftNetMX.zip dnq.project.interchange.zip - WebSphere BI for FN nodes: none - WebSphere BI for FN message sets: none - WebSphere BI for FN message set projects: none To install the new versions of the Toolkit resources, follow the instructions of the listed sections provided in "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN Application Programming: - Transferring the WebSphere BI for FN resources - Installing the WebSphere BI for FN Eclipse plug-ins If you use WebSphere BI for FN sample message flows as foundation for your own flow development follow the instructions provided in "Using the sample routing flows" in WebSphere BI for FN Application Programming. Otherwise, continue with the instructions provided in "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN Application Programming: - Importing WebSphere BI for FN Base sample projects - Importing the message sets and sample routing flows Additionally, if you use WebSphere BI for FN message set projects containing XML schema definitions for your own flow development follow the instructions provided in section "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN Application Programming: - Importing the message sets and sample routing flows - Importing XSD files for SWIFT message payloads Important notice: The schema file for the general message structure "mtmsg.2014.xsd" is changed significantly in comparision to its 2013 version. D16. Verifying your Installation -------------------------------- This PTF contains updated version of the MER Facility enterprise application. To verify that an enterprise application is the most current version: 1. Log-on to the enterprise application. 2. Click the 'About' link in the upper right corner. A dialog box opens. 3. In the dialog box, locate the build number. Compare it to the driver level specified in the header of this readme file. Both numbers should be identical. *------------------------------------------------------------------------------* * End of Installation * *------------------------------------------------------------------------------* E. APAR details --------------- Fixes for the following APARs are contained in this PTF: PI17975 MM SWIFT SR2014: MESSAGE MANAGEMENT UPDATES FOR SWIFT SR2014 CHANGES Adaptions for S.W.I.F.T. Standard Release 2014 (SR2014) changes PI19785 MM AMOUNT VALUE COULD NOT SHOW PROPERLY WHEN RECEIVE MT N92 IN MER Formerly, for a received MT192, no amount value was shown in the MER message list. Now, if the embedded message of an MTn92, MTn95 or MTn96 contains field 32A or 32B, the amount value and currency for the embedded message is shown in the MER message list. PI18586 MM LOCALE SETTING IS NOT RECOGNIZED WHEN FILTERING THE MER MESSAGE LIST FOR AMOUNT Formerly, when using the Amount filter criterion to filter the content in the message list in MER, a dot (.) must be specified as decimal mark, regardless of the locale settings. Now, the Amount filter criterion is locale-aware and the locale-specific decimal mark must be used. PI17952 MM MISMATCH BETWEEN DNQ_K_UA.BAR AND THE CORRESPONDING PI (DNQ.PROJECT.INTERCHANGE.ZIP) Formerly, the message warehouse setting for message flow DNQ_K_UA was inconsistent between the DNQ_K_UA.bar file and the DNQ_K_UA message flow that was provided in the corresponding project interchange (dnq.project.interchange.zip). If the DNQ_K_UA.bar file was deployed, message warehouse was enabled for DNQ_K_UA, whereas message warehouse was disabled, when a BAR file was build and deployed based on the corresponding project interchange. DNQ_K_FIN1_4, DNQ_K_FIN2, and DNQ_K_MX1_OUT have been affected by the same problem. Now, the message warehouse setting is consistent for all routing samples. That is, message warehouse is enabled for all sample flows that are available in dnq.project.interchange.zip as well as in the prebuild BAR files. PI20173 MM LEAVE THIS FIELD EMPTY SHOULD NOT BE SHOWN ON MANDATORY FIELDS IN MER Formerly, even on mandatory fields in MER, which are marked with an asterisk, the text "leave this field empty" was the default in the dropdown list. This was confusing for the endusers, as mandatory fields can never be left empty. Now, this has been changed. PI14736 MM BAD PERFORMANCE ON CREATE QUEUE WHEN ASSOCIATED TEMPLATE QUEUE CONTAINS HIGH NUMBER OF TEMPLATES Formerly, when a template queue contains several thousands of templates, it could take several minutes to open the associated create queue in MER. Now, the template list has been reworked to no longer display all available templates at the same time, but a page of 20, 50 or 100 templates instead. Furthermore, the same filter criteria are now available as for the message list. F. Other changes ---------------- NOT APPLICABLE G. Known issues --------------- NOT APPLICABLE ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++