=============================================================================== = 5724-D96 IBM WebSphere Business Integration for Financial Networks for AIX = Version 2 Release 2 = Base Feature = PTF for APAR PK86658 =============================================================================== 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 changes to your system A. How to use this document --------------------------- Only the online version of this document is current. We strongly recommend that you download the latest version from http://www.ibm.com/software/integration/wbifn/support before you install this PTF. This document describes how to upgrade your WebSphere BI for FN installation for use with WebSphere Message Brokers Toolkit Version 6.1 (Toolkit 6.1). It describes how to re-install non-customizable WebSphere BI for FN resources for use with Toolkit 6.1, and how to move customized resources from the previous Toolkit version to the new version. To ensure that you are able to fall back to the earlier version, install Toolkit 6.1 in a location that is different from that of the current Toolkit version. This document assumes the following: - The installation directory of WebSphere BI for FN is /opt/IBM/ - 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 modules have been changed: The following files have been changed: /dni_02_02/admin/win/dniupdbd.jar /dni_02_02/admin/win/dnininst.jar /dni_02_02/admin/win/dniupdbd.cmd /dni_02_02/admin/win/dninienv.cmd /dni_02_02/admin/win/dninigen.cmd /dni_02_02/admin/win/dninicps.vbs /dni_02_02/admin/win/dninirf.vbs /dni_02_02/admin/win/dniniws.vbs /dni_02_02/admin/data/dnicztmt.txt /dni_02_02/admin/bin/dnicdp.jar /dni_02_02/run/lib/libdnic.a /dni_02_02/run/lib/libdnig.a /dni_02_02/run/lib/libdnicpcac.a /dni_02_02/run/classes/dnicisup.jar /dni_02_02/run/msg/dniccmsg.cat where represents the installation directory C. Post-Installation -------------------- After you have installed the PTF through ISMP: 1. Share the files with your run-time system. 2. Ensure that the group ownership of the /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 /dni_02_02/admin 3. Ensure that the group ownership of the /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 /dni_02_02/run D. Steps on a customization system ----------------------------------- There are no steps on the customization system. E. Steps on a run-time system ----------------------------- E0. install this PTF - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2. Install BASE Summary PTF to replace the old driver. E1. Prepare the Toolkit 6.1 installation - - - - - - - - - - - - - - - - - - - - 1. Download the latest version of the documentation from: www.ibm.com/software/integration/wbifn/library 2. After you install Toolkit 6.1, prepare it as described in "Planning, Installation, and Customization", section "Preparing the WebSphere Message Broker Toolkit workstation". E2. Copy resources from the previous Toolkit installation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1. Ensure that Toolkit 6.1 is not running. 2. Copy the customized resources from the previous Toolkit installation: - Locate the Eclipse workspace directory of your previous Tookit installation - In Toolkit 5.0, the workspace directory was the directory \eclipse\workspace - In Toolkit 6.0, the default workspace directory was the directory \IBM\wmbt6.0\workspace - For each DNI_DnMainflows directory, copy all *.msgflow files to the corresponding DNI_DnMainflows directory of Toolkit 6.1 E3. Check the workspace integrity - - - - - - - - - - - - - - - - - Start Toolkit 6.1 and clean all projects: 1. Select "Projects->Clean...->Clean all projects->OK" Note: Check before if 'Start a build immediately' check mark is set. 2. Verify that the workspace does not contain errors in the Problems view. E4. Verify the Toolkit 6.1 installation - - - - - - - - - - - - - - - - - - Step E5 and E9 will help you to verify that Toolkit 6.1 was successfully installed: Step E5: Generate BAR files that contain the WebSphere BI for FN message flows. This will expose any errors in the BAR file generation process. This verification step is highly recommended. Step E9: Redeploy all WebSphere BI for FN message flows and verify their functions. This will expose any errors in the BAR file deployment process. Because such errors are relatively rare, and this verification might entail extensive retesting, this verification step, although recommended, is optional. E5. Generate BAR files for all WebSphere BI for FN flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To verify the BAR file generation process: 1. Ensure that the WebSphere Message Broker Configuration Manager is running. 2. Stop the Message Brokers Toolkit. 3. In the Command Prompt window and from the directory you used in step E1 during the procedure described in "Transferring the non-customizable WebSphere BI for FN resources", enter: dniupdbd -prepare -d . -q [-p ] [-h ] where The name of the queue manager to which the WebSphere Message Broker Configuration Manager is connected. The port required to connect to the queue manager. The default is 1414. The host address of the machine in which the Configuration Manager runs. The default is 127.0.0.1 (localhost). 4. Check the log file dniupdbd.log to ensure that the BAR files that contain the WebSphere BI for FN message flows were successfully created. 5. If you want to redeploy and verify all WebSphere BI for FN message flows, continue with step E9. Otherwise, skip step E9 and delete the generated BAR files. E6. Stop all sessions and services you use - - - - - - - - - - - - - - - - - - - - - Stop all sessions and services you use. How to do this depends on the features of WebSphere BI for FN that you are using. For instance: - Stop all applications that send requests to WebSphere BI for FN. - Log out SIPN FIN LTs. - Release SWIFTNet SnF queues. - Stop Enhanced FileAct File Transfer service. - Stop Enhanced InterAct service. - Close all dnicli sessions. For further information refer to the System Administration manual, chapter: 'Operating components, sessions, and services'. E7. Stop all WebSphere BI for FN message brokers - - - - - - - - - - - - - - - - - - - - - - - - Stop all WebSphere BI for FN message brokers. E8. Restart all WebSphere BI for FN message brokers - - - - - - - - - - - - - - - - - - - - - - - - - - Restart all WebSphere BI for FN message brokers. E9. Redeploy and verify all WebSphere BI for FN message flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To verify the BAR file deployment process: Deploy the broker archive files for all existing message flows: a. Ensure that the WebSphere MB configuration manager is running. b. Ensure that the Message Brokers Toolkit is stopped. c. In the Command Prompt window and from the directory you used in step E1, part 'Transferring the non-customizable WebSphere BI for FN resources', and E5., enter: dniupdbd -deploy -q [-p ] [-h ] [-t ] where The name of the queue manager to which the WebSphere MB Configuration Manager is connected. The port required to connect to the queue manager. The default is 1414. The host address of the machine in which the Configuration Manager runs. The default is 127.0.0.1 (localhost). The wait interval for Configuration Manager and broker response. The default is 600 seconds (10min). This command deploys to the brokers the BAR files that were prepared in step E5 and that are contained in the current directory. d. Check the log file dniupdbd.log to ensure that the files were successfully deployed. E10. Restart all sessions and services you use - - - - - - - - - - - - - - - - - - - - - - - Restart all sessions and services you use. How to do this depends on the features of WebSphere BI for FN that you are using. For instance: - Log in SIPN FIN LTs. - Start Enhanced FileAct File Transfer service. - Start Enhanced InterAct service. - Acquire SWIFTNet SnF queues. - Start the applications that send requests to WebSphere BI for FN. For further information refer to the System Administration manual, chapter: 'Operating components, sessions, and services'. *----------------------------------------------------------------------------* * End of Migration * *----------------------------------------------------------------------------* F. APARs addressed by this PTF ------------------------------ PK73629 SUPPORT WEBSPHERE MB TOOLKIT V6.1 IN WEBSPHERE BI for FN WebSphere MB Toolkit V6.1 differs from WebSphere MB Toolkit V6.0 in many aspects (for example, the directory structure changed). WebSphere BI for FN considers these changes now and supports WebSphere MB Toolkit V6.1 too. Consequently, if you have more than one version of WebSphere MB Toolkit installed on the workstation you must specify which toolkit version you want to prepare for WebSphere BI for FN. PK80116 "EXTRACT" METHOD OBTAINED A IBM-417 TO IBM-417 CONVERTER Formerly, a static memory buffer which held the codepage name might not be thread-safe. It caused the incorrect initialization of codepage converter. Now, the converter initialization is thread-safe. G. Other problems addressed by this PTF ---------------------------------------- BASE APPLICATION ABEND WHILE BROKER IS SHUTTING DOWN Module libdnig.a was unloaded before the referral routine shutting down. Code changes to provide a work around:Add a function "removeDnigController" which destruct the DnigController instance. BASE Segmentaion fault occured with cpn node on AIX 6.1 Change the code in function "DNIP_INT DnipCacheSrvProc" to fix segmentation fault on AIX 6.1 +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++