======================================================================= = IBM WebSphere Business Integration for Financial Networks = 5724-D96 for Multiplatforms Extending Features V2.2.0 = PTF UK22416 ======================================================================== 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 E1. Transferring the WebSphere BI for FN resources to the WebSphere MB Toolkit workstation E2. Setting the Toolkit version and directories E3. Backing up all WebSphere BI for FN resources installed in a WebSphere MB Toolkit workstation E4. Installing the changed WebSphere BI for FN plug-ins E5. Perparing BAR files with the updated WebSphere BI for FN flows E6. Stop and restart the WebSphere BI for FN message brokers E7. Deploying all affected WebSphere BI for FN message flows F. APARs addressed by this PTF A. How to use this document --------------------------- This document assumes the following: 1. The installation directory of Extension for SWIFTNet is /opt/IBM/dnf_02_02 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. Important notes --------------- If you use SAG6, this PTF also requires an update of your SAG AddOn. Please download the SAG AddOn version for APAR PK39881 from the following website: ftp://ftp.software.ibm.com/ps/products/wbifn/ptfs/WBIFN_SAGAddOn/V2R2/SAGAddOn_for_SAG6 B Changes to your current system --------------------------------- The following have been changed: /dnf_02_02/admin/win/com.ibm.dnf.SagCfg.zip /dnf_02_02/run/lil/dnfcfpin.lil C Post-installation -------------------- After you have installed the PTF using InstallShield: 1. Share the files with your customization and run-time systems. 2. Ensure that the group ownership of the /opt/IBM/dni_02_02/admin, /opt/IBM/dnf_02_02/admin directory and all subdirectories and files therein is set to group dniadmin. To do this, enter the following commands in AIX shell: chgrp -R dniadmin /opt/IBM/dni_02_02/admin chgrp -R dniadmin /opt/IBM/dnf_02_02/admin 3. Ensure that the group ownership of the /opt/IBM/dni_02_02/run, /opt/IBM/dnf_02_02/run directory and all subdirectories and files therein is set to group dnilpp. To do this, enter the following commands in AIX shell: chgrp -R dnilpp /opt/IBM/dni_02_02/run chgrp -R dnilpp /opt/IBM/dnf_02_02/run D. Steps on a customization system ----------------------------------- No steps on the customization system required. 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 this and the next 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: a. /dnf_02_02/admin/win/com.ibm.dnf.SagCfg.zip b. /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.SagCfg.zip cd /dni_02_02/admin/win 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 stores following data into a compressed backup file: - links: all files "com.ibm.dn*.link" from \eclipse\links - WebSphere BI for FN eclipse plugins: all subdirectories of directories "com.ibm.dn*" within - WebSphere BI for FN project directories: all directories of the form "DNI_" within \eclipse\workspace 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 Administration Perspective'. c. Select all projects with names like "DNI_*", right-click and select 'Refresh', then right-click and select 'Rebuild Project' E5. Perparing 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. E6. Stop and restart the WebSphere BI for FN message brokers - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Stop and restart all WebSphere Message Brokers to update the libraries they use. E7. 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. F. Falling back to the previous PTF level ------------------------------------------ To fall back to the previous PTF level: F1. Uninstall the PTF. F2. Restore the saved WebSphere BI for FN resources into the WebSphere MB Toolkit: a. Change to the directory you used in step E1. and E3. b. Enter the command: dninires where is the name of the zip-file you created in E3. "Backing up all WebSphere BI for FN resources installed in the WebSphere MB Toolkit". c. Start the Message Brokers Toolkit with the -clean option. d. In the Message Brokers Toolkit, open the 'Broker Administration Perspective'. e. Select all projects with names like "DNI_*", right-click and select 'Refresh', then right-click and select 'Rebuild Project' F3. Re-deploy previous versions of the message flows that were updated in step E7. Note: The steps you have to take are identical to those to install this PTF, but with the restored resources from step F2 the resulting broker archives will be different. Note: Ensure that the directory used in step E1. still contains all transferred files and do not change it during fallback. It contains information required to identify which message flows have to be re-deployed during fallback. F3.1 Create broker archives with the previous message flows. Follow the instructions in step E5. "Perparing BAR files with the updated WebSphere BI for FN flows". F3.2 Deploy the previous versions of the message flows. Follow the instructions in step E7. "Deploying all affected WebSphere BI for FN message flows". *------------------------------------------------------------------------* * End of Migration * *------------------------------------------------------------------------* G. APARs addressed by this PTF ------------------------------ PK39881 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. PK40028 EVENT LOG AND QUERY CMD DO NOT SHOW SAME LT STATUS +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++