============================================================================== = 5724D-9621 IBM WebSphere Business Integration for Financial Networks = = for Multiplatforms Extending Features V2.2.0 = = PTF UK69438 for APAR PM38598 = ============================================================================== 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 implemented by this PTF H. Known issues A. How to use this document --------------------------- The PTF for APAR UK52552 (WBI-FN FIN summary PTF) and the PTF UK46581 (WBI-FN Base summary PTF) are pre-requisites for this PTF. Please install the PTFs first. 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. 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 Stop all sessions and services you use' and continues until you finished the migration. We recommend that you download the latest version of the documentation from the following web site: www.ibm.com/software/integration/wbifn/library This document assumes the following: 1. The installation directory of WebSphere BI for FN is , i.e. for example /opt/IBM/ 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. B. Changes to your current system --------------------------------- The following modules have been changed: /dnf_02_02/admin/data/DNFFIN.xml /dnf_02_02/admin/win/com.ibm.dnf.FinInterfaceLayer.zip /dnf_02_02/admin/win/com.ibm.dnf.PrivateFinancialMessageTransferFin.zip /dnf_02_02/run/lil/dnfdgst.lil /dnf_02_02/run/res/dnfchrsp.xml /dnf_02_02/run/msg/dnfccmsg.cat /dnf_02_02/run/bin/dnfcfsfs /dnf_02_02/run/bin/dnfcfsfd /dnf_02_02/run/lib/libdnfcf.a /dnf_02_02/run/lib/libdnfcwdbs.a /dnf_02_02/run/data/dnfcwdbs.bnd C. Post-Installation -------------------- After you have installed this PTF using tar file: 1. Share the files with your customization and run-time systems. 2. Ensure that the group ownership of the /dnf_02_02/admin directory and all subdirectories and files therein is set to group dniadmin. To do this, enter the following command in AIX shell: chgrp -R dniadmin /dnf_02_02/admin 3. Ensure that the group ownership of the /dnf_02_02/run directory and all subdirectories and files therein is set to group dnilpp. To do this, enter the following command in AIX shell: chgrp -R dnilpp /dnf_02_02/run Note: Depending on the modules changes you may need step C.2, or step C.3, or both steps C2. and C3.. D. Steps on a customization system ---------------------------------- Before you start the customization migration you should ensure that earlier migrations are completed using the CDP 'implement' command. Otherwise the CDP might generate migration statements again, which may cause the deployment vehicles to fail. To update your current definition directory and the customized administrative scripts, and to create deployment instructions and vehicles: D1. Log on to AIX on the customization - - - - - - - - - - - - - - - - - - - - - - Log on to AIX on the customization system as a customizer (ucust1). D2. Change to the customization directory - - - - - - - - - - - - - - - - - - - - - Change to the customization directory by issuing the following command: cd /var/dni_02_02/cus D3. Run your customization profile - - - - - - - - - - - - - - - - - Run your customization profile by issuing the following command: . ./dnicus_ D4. Start the CDP in migration mode - - - - - - - - - - - - - - - - - - Start the CDP in migration mode by issuing the following command: dnicdpm -i D5. Identify your current CDD - - - - - - - - - - - - - - - If you are not sure whether your .cdd reflects your current WebSphere BI for FN instance layout, generate a CDD using the CDP export command. How to this is described in "Planning, Installation, and Customization", Appendix E "CDP command reference". D6. Import your current CDD as the target CDD - - - - - - - - - - - - - - - - - - - - - - - Import your current CDD as the target CDD by issuing the following command: import cdd/.cdd D7. Prepare customization data - - - - - - - - - - - - - - - Update the customized administrative scripts for FIN in the directory '//admin' by entering the following command: prepare Depending on the service bundles you have assigned and the superseded PTFs you already have applied this command may generate deployment vehicles for the following resource classes: 'DB', 'DBBND' and 'DBGNT' and deployment instructions in the file /var/dni_02_02/cus/depdata///instructions.txt. You will need this later in step 'E8 Updating the run-time system resources'. D8. Implement the customization changes - - - - - - - - - - - - - - - - - - - - Implement this CDD as your current CDD to update your 'current definition directory' by entering the following command: implement When the message "DNIZ9013I: Current Definition file already exists." is displayed enter 'y' to continue. D9. Quit the CDP session - - - - - - - - - - - - Quit the CDP session by entering the following command: quit E. Steps on a run-time system ----------------------------- E1. Transferring 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: /dnf_02_02/admin/win/com.ibm.dnf.FinInterfaceLayer.zip /dnf_02_02/admin/win/com.ibm.dnf.PrivateFinancialMessageTransferFin.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 /dnf_02_02/admin/win get com.ibm.dnf.FinInterfaceLayer.zip get com.ibm.dnf.PrivateFinancialMessageTransferFin.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 "Preparing to create an instance", "Preparing the WebSphere MB Toolkit workstation", -> "Setting the Toolkit version and directories" E3. Backing up all 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 your workspace directory 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 updated WebSphere BI for FN Eclipse plug-ins and flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To install the updated WebSphere BI for FN Eclipse plug-ins and message flows: 1. In the Command Prompt window and change to the temporary directory you used in step E1. 2. Enter the command: dnininst This command will install the updated Eclipse plugins. A warning message is displayed for each installed file that did already exist. If the dnininst program issues an error message, check the log file for more information about the reason for the error. 3. Enter the command: dninimcp This command will install the updated message flows. A warning message is displayed for each installed file that did already exist. To refresh the meta data in the Message Brokers Toolkit: 1. Start the Toolkit with the -clean parameter. 2. In the Message Brokers Toolkit, open the 'Broker Application Development Perspective'. 3. Select all projects with names of the form DNI_DnMainflows. 4. Right-click and select 'Refresh' from the pop-up menu. To re-build the WebSphere BI for FN projects: - For Message Broker Toolkit V5: a) Select all projects with names of the form DNI_DnMainflows. b) Right-click and select "Rebuild" from the pop-up menu. - For Message Broker Toolkit V6.0 or V6.1: a) Disable the "Build Automatically" feature. To do this, deselect the "Projects"->"Build Automatically" item in the pull-down menu. b) For all 'DNI_DnMainflows' projects: 1) In the "Resource navigator" window, select the projects. 2) From the main menu, select "Projects->Clean..." 3) In the popup window, select "Clean selected project" (Toolkit V6.0), or "Clean projects selected below" (Toolkit V6.1) and ensure "Start a build immediately" is selected. 4) Press "OK". 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 for the existing message flows: 1. Ensure that the WebSphere MB configuration manager is running. 2. Stop the Message Brokers Toolkit. 3. 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, which are: - DNF_ILC_FIN - DNF_ILS_ACK - DNF_ILS_FIN - DNF_PF_IS 4. Check the log file dniupdbd.log to ensure that the files were successfully prepared. 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. Updating the run-time system resources - - - - - - - - - - - - - - - - - - - - - Follow the deployment instructions created in step D7. to update the run-time system resources such as database tables and queues. Depending on the WebSphere BI for FN maintenance level you already have applied the deployment may bring the following changes to your system: -> if you have assigned the DNFFIN service bundle DB2 related changes: - bind a new package for the SFD After you have successfully deployed the resources you have to implement the customization changes as described in step D8 in order to ensure that future migrations do not prepare the current deployment data again. If you have already closed the CDP session you have to repeat step D1 to D6, but not D7, before you continue with step D8. E9. Tuning access to FIN database tables - - - - - - - - - - - - - - - - - - - - N/A. E10. Update the WebSphere MB environment - - - - - - - - - - - - - - - - - - - - N/A. E11. Restart all WebSphere BI for FN message brokers - - - - - - - - - - - - - - - - - - - - - - - - - - Restart all WebSphere BI for FN message brokers. E12. Deploying all affected WebSphere BI for FN message flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To deploy the broker archive files for the existing message flows: 1. Ensure that the WebSphere MB configuration manager is running. 2. Ensure that the Message Brokers Toolkit is stopped. 3. 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). 4. Check the log file dniupdbd.log to ensure that the files were successfully deployed. E13. Migrate configuration data - - - - - - - - - - - - - - - - N/A. E14. 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'. E15. Cleanup - - - - - - N/A. *----------------------------------------------------------------------------* * End of Migration * *----------------------------------------------------------------------------* F. APARs addressed by this PTF ------------------------------ PM38598 SR2011: FIN/FMT UPDATES TO SUPPORT NEW SSI MESSAGES SWIFT Standard Release 2011 (SR2011) requires the FIN messaging interfaces to support the new Standing Settlement Instructions (SSI) Messages. This WebSphere BI for FN PTF implements the required FIN and FMT updates. G. Other changes implemented by this PTF ---------------------------------------- N/A. H. Known issues --------------- N/A. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++