============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2011 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.0 SUPPORT FOR SWIFTNET FIN, SWIFTNET INTERACT, FINANCIAL MESSAGE TRANSFER PTF UK69437 for APAR PM38599 Date 2011-07-31 ============================================================================== ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Preparation E Activating F APAR details G Other changes 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.ibm.com/software/integration/wbifn/library 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. The installation of this PTF is done in two phases: 1. Preparation - During this phase your system can continue to process messages as usual. 2. Activation - During this phase 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 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 name of the organizational unit. Depending on the context, this might be SYSOU, DNFSYSOU, or the name of a business OU. The name of the runtime database. The name DNIDBRUN is used in examples. The names of users, groups, files, and directories are the same as those used in "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: PM36182 EIA WBIFN V310 EIAS SERVICE CANNOT START IF MQ V7.0.1 IS INSTALLED PM38599 FIN SR2011: FIN/FMT UPDATES TO SUPPORT NEW SSI MESSAGES Documentation updates: - Messages and Codes The following modules have been changed: /dnf_03_01/admin/data/DNFFIN.xml /dnf_03_01/run/flows/DNF_ILS_ACK.bar /dnf_03_01/run/flows/DNF_ILS_FIN.bar /dnf_03_01/run/flows/DNF_ILC_FIN.bar /dnf_03_01/run/flows/DNF_PF_IS.bar /dnf_03_01/run/msg/dnfcfmsg.cat /dnf_03_01/run/res/dnfchrsp.xml /dnf_03_01/run/lil/dnfdgst.lil /dnf_03_01/run/lib/libdnfcf.a /dnf_03_01/run/bin/dnfcfsfs /dnf_03_01/run/bin/dnfcfsfd /dnf_03_01/run/classes/dnfcecom.jar /dnf_03_01/run/classes/dnfceias.jar /dnf_03_01/run/lib/libdnfcwdbs.a /dnf_03_01/run/data/dnfcwdbs.bnd C. Planning ----------- Before installing a new PTF, ensure that: - All previously prepared deployment instructions have been carried out. - All previous CDD changes have been implemented using the CDP. - 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'. - 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 -user % -qo mor Each list command should result in 'No roles found that match specified criteria'. Customization changes other than those described in a PTF readme document are not allowed during PTF installation. Prerequisite and supersede information: This PTF requires the following PTFs: - UK67874 for APAR PM42536 (Base 3.1.0.7, USE THE @ TO MARK A GROUP WITH ACCESS AUTHORITY IN CDD) - UK64651 for APAR PM35684 (CSN 3.1.0.6, DUMP IN FIN FSM WHEN THE LIBPATH EXCEEDS 999 CHARS) Roles involved: The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - DB2 administrator (udb2adm1) - WebSphere MB administrator (uwmba1) - First WebSphere BI for FN system configuration administrator (sa1) D. Preparation -------------- D1. Installation ---------------- 1. 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. 2. Stop all WebSphere BI for FN message brokers. 3. 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. 4. Share the files in the /dnf_03_01/admin directory with your customization system. 5. Ensure that the group ownership of the /dnf_03_01/admin directory and all of its subdirectories and files, is set to group dniadmin. To do this, enter the following command in AIX shell: chgrp -R dniadmin /dnf_03_01/admin 6. Share the files in the following directories with your runtime systems: /dnf_03_01/run/data /dnf_03_01/run/flows /dnf_03_01/run/classes These files are already needed during the preparation phase and do not influence normal operation. 7. Set the group ownership of these directories and files to group dnilpp. To do this, enter the following command in AIX shell: chgrp -R dnilpp /dnf_03_01/run/data chgrp -R dnilpp /dnf_03_01/run/flows chgrp -R dnilpp /dnf_03_01/run/classes 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 shell 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/_PM38599.cdd > import cdd/_PM38599.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: - DBBND (if service bundle DNFFIN is assigned): - admin module to rebind package DNFCWDBS Deployment instructions are generated in the file '///instructions.txt'. You will need this later in the 'E. Activating' section. 5. Implement the customization definition data and quit the CDP session: > implement When the message "DNIZ9013I: Current Definition file already exists." is displayed enter 'y' to continue. > quit D3. Generating configuration data migration scripts --------------------------------------------------- NOT APPLICABLE. D4. Customize updated BAR files when not using the BAP (dniczbap) to deploy them -------------------------------------------------------------------------------- Which of the following sections applies depends on how you plan to deploy broker archive (BAR) files: - If your configuration manager runs on Windows, you cannot use the BAP (dniczbap) to deploy BAR files, and must follow the procedure described in D4.1. - If your configuration manager runs on AIX, and if you want to prepare BAR files without directly deploying them, follow the procedure described in D4.2. Note: Before deploying updated BAR files, ensure that the configuration manager is running and that no flows or execution groups are stopped. Otherwise, old flow levels might not be deleted during the BAP update operation (that is, when you enter the "prepare -update new" command). To verify that the update was successful, issue the BAP list command and ensure that no flow is running that has the same name as another flow but a different version. D4.1. Update BAR files when there is no connection to the configuration manager - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Carry out these steps when your configuration manager runs on Windows. The BAP customizes all BAR files that it processed earlier, for example, during installation of WebSphere BI for FN. You then select which files are to be updated for the current PTF. To customize the BAR files 1. On the runtime system, log on to AIX shell as the system configuration administrator, for example, sa1, or as the WebSphere MB administrator, for example uwmba1, and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a temporary directory where dniczbap stores the customized BAR files. You will need up to 30MB free space in this directory. 3. Issue the following command: dniczbap -cmd prepare -all -dir where represents the directory created in the previous step. Each of the customized BAR files has a name of the form: ...bar where The name of the broker to which the BAR file is to be deployed. The name of the execution group to which the BAR file is to be deployed. The name of the BAR file as provided by WebSphere BI for FN. 4. Identify the BAR files that are listed in section 'B. Summary of changes' and delete all other BAR files in the temporary output directory. 5. Transfer, in binary mode, the customized BAR files to the Toolkit or to the system where you will run the mqsideploy command. 6. If you want to deploy using the Toolkit import the customized BAR files. D4.2. Use the configuration manager to automatically detect updated BAR files - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Carry out these steps when your configuration manager runs on AIX but you do not want to deploy BAR files using the BAP (dniczbap). To customize the BAR files: 1. Ensure that the configuration manager is started. 2. On the runtime system on which the configuration manager runs, log on to AIX shell as the WebSphere MB administrator, for example, uwmba1, and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 3. Create a temporary directory where dniczbap stores the customized BAR files. You will need up to 30MB free space in this directory. 4. Issue the following command: dniczbap -cmd prepare -update new -dir where represents the directory created in the previous step. Each of the customized BAR files has a name of the form: ...bar where The name of the broker to which the BAR file is to be deployed. The name of the execution group to which the BAR file is to be deployed. The name of the BAR file as provided by WebSphere BI for FN. *------------------------------------------------------------------------------* * End of Preparation * *------------------------------------------------------------------------------* E. Activating ------------- E1. 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. - Release SWIFTNet SnF queues. - Stop the MSIF Transfer service. - Stop the Enhanced InterAct service. - Close all dnicli sessions. For further information, refer to the section of "System Administration" that describes how to operate components, sessions, and services. E2. Stopping all application servers ------------------------------------ NOT APPLICABLE. E3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- Stop all WebSphere BI for FN message brokers. E4. Sharing the runtime directory structure ------------------------------------------- 1. Share the files in the /dnf_03_01/run directory with the runtime systems. 2. Set the group ownership of these directories and files to group dnilpp. To do this, enter the following command in AIX shell: chgrp -R dnilpp /dnf_03_01/run E5. Backing up configuration and security data in image copies -------------------------------------------------------------- NOT APPLICABLE. E6. Following the deployment instructions created in step D2.4 -------------------------------------------------------------- Follow the deployment instructions that were created in step D2.4. This will update the run-time system resources. E7. Additional activities ------------------------- E7.1. DB2 related activities - - - - - - - - - - - - - - NOT APPLICABLE. E7.2. WebSphere MB related activities - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. E8. Restarting all WebSphere BI for FN message brokers ------------------------------------------------------ Restart all WebSphere BI for FN message brokers. E9. Redeploy updated BAR files ------------------------------ To customize and deploy the updated WebSphere BI for FN BAR files, you must have the access rights of the WebSphere MB administrator (uwmba1). To redeploy updated BAR files: 1. Ensure that the configuration manager is running. 2. If you already have prepared the customized BAR files as described in step D4 proceed with step E9.1; otherwise, proceed with step E9.2. Note: Before deploying updated BAR files, ensure that the configuration manager is running and that no flows or execution groups are stopped. Otherwise, old flow levels might not be deleted during the BAP update operation (that is, when you enter the "prepare -update new" command). To verify that the update was successful, issue the BAP list command and ensure that no flow is running that has the same name as another flow but a different version. E9.1. Deploying the BAR files customized in step D4 - - - - - - - - - - - - - - - - - - - - - - - - - - Use the Toolkit or the mqsideploy command to deploy the BAR files. E9.2. Updating BAR files when step D4 has not been performed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Use these steps when your configuration manager runs on AIX and you want to deploy directly using the BAP (dniczbap). To customize and deploy the BAR files: 1. On the runtime system on which the configuration manager runs, log on to AIX shell as the WebSphere MB administrator, for example, uwmba1, and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Ensure that you have sufficient free space in the current directory. To deploy all message flows requires about 30 MB of free space. 3. Issue the following command: dniczbap -cmd prepare -update new -deploy E9.3. Activating WebSphere BI for FN accounting - - - - - - - - - - - - - - - - - - - - - - - - After all message flows have been deployed, activate the WebSphere BI for FN accounting: SIPN FIN and FMT FIN services: The following bar files are changed with this PTF and deployed: - DNF_ILS_FIN.bar - DNF_ILS_ACK.bar To activate the accounting, the WebSphere MB administrator, for example, uwmba1, must enter the following commands: mqsichangeflowstats -s -e '' -f 'DNF_ILS_FIN_' -c active -n basic -o XML mqsichangeflowstats -s -e '' -f 'DNF_ILS_ACK_' -c active -n basic -o XML where: The name of the broker. The name of the execution group. The level of the message flow. To determine the levels of all deployed message flows, enter the following command: dniczbap -cmd list The output contains messages that indicate the level of each message flow, for example: DNIZ1466I Flow name1: DNF_ILS_ACK_0300 If you deployed the above mentioned bar files to multiple execution groups, repeat the steps for each execution group in which the bar files are deployed. E10. Migrating configuration data --------------------------------- NOT APPLICABLE. E11. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ NOT APPLICABLE. E12. 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. - Start the MSIF Transfer service. - Start the Enhanced InterAct service. - Acquire SWIFTNet SnF queues. - Start the applications that send requests to WebSphere BI for FN. For further information, refer to the section of "System Administration" that describes how to operate components, sessions, and services. E13. Updating the Toolkit development environment ------------------------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Activating * *------------------------------------------------------------------------------* F. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM36182 EIA WBIFN V310 EIAS SERVICE CANNOT START IF MQ V7.0.1 IS INSTALLED Formerly, when EIAS was used with MQ V7.0.1, the EIAS service could not start. DNFE3344E error event with reason code 2033 was issued, indicating that OUTBOUND DNF_EI_LRT EIAS service could not access the WebSphere MQ queue DNF_EI_CMD1 due to an exception. Now, the MQ exception MQRC_NO_MSG_AVAILABLE is caught by WBIFN and retries accessing DNF_EI_CMD1 queue after 300 milliseconds. PM38599 FIN 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 ---------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++