=============================================================================== = 5724D-9620 IBM WebSphere Business Integration for Financial Networks = = for Multiplatforms Base = = PTF UK38897 for APAR PK68951 = =============================================================================== 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 A. How to use this document --------------------------- Only the online version of this document is up to date. We strongly recommend that you download the latest version from http://www.ibm.com/software/integration/wbifn/support before you install this PTF. We recommend that you download the latest version of the documentation from the following web site: www.ibm.com/software/integration/wbifn/library This PTF requires PTF UK36062 for APAR PK65304. 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. Deploying all affected WebSphere BI for FN message flows' and continues until you finished the migration. This document assumes the following: The installation directory of Websphere BI for FN is: /opt/IBM The names of users, groups, files, and directories are the same as those used in the "Planning, Installation and Customization" manual. If you use different values, use those values instead of the values shown here. B. Changes to your current system --------------------------------- The following files have been changed: /dni_02_02/admin/win/com.ibm.dni.Event.zip /dni_02_02/admin/win/com.ibm.dni.MessageAudit.zip /dni_02_02/run/lil/dnicin.lil where represents the installation directory C. Post-Installation -------------------- After you have installed the PTF : 1. Share the files with your customization and run-time system. 2. Ensure that the group ownership of the /opt/IBM/dni_02_02/admin directory and all subdirectories and files therein is set to group dniadmin. To do this, enter the following commands: chgrp -R dniadmin /opt/IBM/dni_02_02/admin 3. Ensure that the group ownership of the /opt/IBM/dni_02_02/run directory and all subdirectories and files therein is set to group dnilpp. To do this, enter the following commands: chgrp -R dnilpp /opt/IBM/dni_02_02/run D. Steps on a customization system ----------------------------------- There are no steps required on the customization system. E. Steps on a run-time system ------------------------------ E1. 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: /dni_02_02/admin/win/com.ibm.dni.Event.zip /dni_02_02/admin/win/com.ibm.dni.MessageAudit.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 /dni_02_02/admin/win get com.ibm.dni.Event.zip get com.ibm.dni.MessageAudit.zip mget dni* bye E2. Setting the Toolkit version and directories - - - - - - - - - - - - - - - - - - - - - - - - To set the correct environment for the tools used in the subsequent steps follow the instructions in the "Planning, Installation, and Customization" manual in "Chapter 3. Preparing to create an instance", "Preparing the WebSphere MB Toolkit workstation", -> "Setting the Toolkit version and directories" E3. 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 E1. 2. Enter the command: dninibak This command creates backup files with names of the form: _dn.zip where represents a letter or letters that indicate to which product feature or features the backup file applies: i The Base feature f All extending features except Enhanced Support for SWIFTNet FileAct fo The Enhanced Support for SWIFTNet FileAct feature Each backup file contains: Links All files in the directory \eclipse\links that have names of the form "com.ibm.dn.link" WebSphere BI for FN eclipse plugins All subdirectories of with names of the form "com.ibm.dn" WebSphere BI for FN project directories All subdirectories of the directory \eclipse\workspace that have names that begin with "DNI_Dn" Note: The dninibak command issues messages to inform you of directories it was unable to find. For example: - If the Enhanced Support for SWIFTNet FileAct feature is not installed, dninibak issues a message to inform you that it was unable to find directories or projects for the feature "dnfo". - If none of the other extending features are installed, dninibak issues a message to inform you that it was unable to find directories or projects for the feature "dnf". If you do not use the corresponding features, you can safely ignore such messages. E4. Installing the 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 E1., 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' E5. Preparing BAR files with the updated WebSphere BI for FN flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To activate the changes within the WebSphere BI for FN eclipse plugins all affected message flows need to be deployed to all execution groups on all brokers where they are running. 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. Note: Nearly all of the WebSphere BI for FN message flows are affected by the changes contained in this PTF. c. Check the log file dniupdbd.log to ensure that the files were successfully prepared. E6. 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 E1. and E5., enter dniupdbd -deploy -q [-p ] [-h ] [-t ] where The name of the queue manager to which the WebSphere MB configuration manager (CM) is connected. The port required to connect to the queue manager. The default is 1414. The host address of the machine running the CM. The default is 127.0.0.1 (localhost). The wait interval for configuration manager and broker response. The default is 600 seconds (10min). This step deploys the broker archive files prepared in step E5. and contained in the current directory to the broker(s). b. Check the log file dniupdbd.log to ensure that the files were successfully deployed. E7. Restart all WebSphere BI for FN message brokers - - - - - - - - - - - - - - - - - - - - - - - - - - Restart all WebSphere BI for FN message brokers. *------------------------------------------------------------------------* * End of Migration * *------------------------------------------------------------------------* F. APARs addressed by this PTF ------------------------------- PK67124 OPTIMIZE CONCATENATION IN MESSAGE AUDIT TO BE ABLE TO LOWER THREADSTACK DEFINITION WITHOUT IMPACTING PERFORMANCE Formerly, the file size in Enhanced FileAct was limited. Now, the Enhanced FileAct file size limitation can be suspended without degradation of FIN performance. PK67847 SOME WBI-FN EVENTS CANNOT BE DISPLAYED IN SYSLOG BY DNI_N_EVENT SERVICE Formerly, some WBI-FN event messages (e.g. DNFL9498I,DNFL9499I) were not displayed in the SYSLOG. Instead, the event message 'DNIM5251E - DNI_N_EVENT Internal error' was shown in the SYSLOG. Now, those event messages are displayed in the SYSLOG. PK68951 PERFORMANCE DEGRADATION WHEN CIN (CONTROLLED INPUT NODE) RUNS IN MULTIPLE INSTANCES Formerly, when used multi-threaded, the internal locking causes all threads to wait until a single thread retrieved a message from one of the input queues. Now, performance degradation is eliminated. +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++