============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2013 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.1 SUPPORT FOR SWIFTNET FIN AND FINANCIAL MESSAGE TRANSFER PTF UK90682 for APAR PM76806 Driver level: 3050 = Date 2013-02-27 = ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Installation E APAR details F 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. During the installation phase of this PTF 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 names of users, groups, files, and directories are the same as those used in WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization, SH12-6942. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PM76806 FIN MT021 RESPOND MSG (MT103,MT298,MT202 COV) WITH DNFH3860E DIGEST VALIDATION FAILED PM76017 FIN TNG TRAILER LENGTH CHECKING OF MT940 WITH 2000 CHARACTER SWIFT RETURNED A NAK WITH CODE "M50" (MESSAGE TOO LONG) PM76980 FIN MT21 WILL GOT DNFH3713E WHILE REQUEST A SYSTEM MSG PM77870 FIN DURING COMMAND 'QUERY -LT LTNAME -QO M' NOT ACCURATE QUERY RESPONSE IN FIN MESSAGES ACKNOWLEDGED WHEN LT BELONGS TO LTGROUP PM76522 FIN CONFIGURATION VALUE FOR ATTRIBUTE FINCOPYCONFIGERROR IS IGNORED BY DNF_ILS_FIN PM61457 FIN IMPROVE CONNECT TO REMOTE DB2 PM75506 FIN FSM RP RE-SYNCH IMPROVEMENT IN CASE OF SWIFT MESSAGE L14 PM76526 FIN AUDIT ENABLED FOR DNF_ILC_FIN DOESN'T CAPTURE ERROR REPLIES Additional functional changes: - Provide 32 bit db2swit module for Message Broker 7 user. Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Messages and Codes The following modules have been changed: /dnfv311/admin/data/DNFFIN.xml /dnfv311/run/flows/DNF_ILS_FIN.bar /dnfv311/run/flows/DNF_ILC_FIN.bar /dnfv311/run/flows/DNF_ILC_CMD.bar /dnfv311/run/flows/DNF_PF_IS.bar /dnfv311/run/jplugin/dnf.asp.acc.jar /dnfv311/run/msg/dnfcfmsg.cat /dnfv311/run/res/dnfchrsp.xml /dnfv311/run/lib/libdnfcf.a /dnfv311/run/lib/libdnfcwbas.a /dnfv311/run/lib/libdnfcwetc.a /dnfv311/run/lib/libdnfcwdbs.a /dnfv311/run/lib/libdnfcwqio.a /dnfv311/run/bin/dnfcfsfs /dnfv311/run/bin/dnfcfsfd /dnfv311/run/data/dnfcwdbs.bnd The following modules are new: /dnfv311/run/lib/db2swit32 /dnfv311/run/bin/dnfmanagexalinks C. Planning ----------- C1. Checks to be done >>BEFORE<< installing a new PTF ----------------------------------------------------- 1. Ensure that all previously prepared deployment instructions were carried out. 2. Ensure that all previous CDD changes were implemented using the CDP. If a customization operation is still pending and it was carried out in: - Customization mode (dnicdp), implement the pending operation before continuing. - Migration mode (dnicdpm): - Ensure that you have not yet installed the files contained in this or any other PTF as described in section D5 step 2. - Implement the pending operation before continuing. 3. Until this PTF has been fully installed, ensure that no changes are made to the currently implemented CDD except for the changes described in this PTF readme document. 4. Ensure that 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'. 5. Ensure that 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'. C2. Prerequisite and supersede information ------------------------------------------ This PTF requires the following PTFs: - UK82437 for APAR PM73208 (Base 3.1.1.9, ASP PROCESSING THREAD HANDLING WITH 2 DIFFERENT SYMPTOMS 'DNPA1153E: MISSING ELEMENT' AND NULLPOINTER EXCEPTION) - UK78394 for APAR PM74470 (CSN 3.1.1.5, DUMP MAY OCCUR WHEN VERIFYING A B-DIGEST) This PTF should be installed together with: - none This PTF supersedes the following PTFs: - UK83660 for APAR PM76806 C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - DB2 administrator (udb2adm1) - WebSphere MB administrator (uwmba1) D. Installation --------------- D1. 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. - 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. For further information, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration". D2. Stopping all application servers ------------------------------------ NOT APPLICABLE. D3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- Stop all WebSphere BI for FN message brokers. D4. Backing up your system -------------------------- We recommend to backup your AIX LPAR so that in case of migration issues you can revert to your previous system setup and continue to process workload. D5. Installation ---------------- 1. 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, SH12-6942. Please be aware of the directory containing the installation data for this PTF has changed compared to the directory documented in this chapter, use the path Disk1/InstData/NoVM instead of Disk1/InstData/VM. 2. Ensure that the group ownership of the /dnfv311/admin directory and all of its subdirectories and files, is set to group dniadmin. To do this, enter the following command in AIX: chgrp -R dniadmin /dnfv311/admin 3. Set the group ownership of the runtime directories and its files to group dnilpp. To do this, enter the following command in AIX: chgrp -R dnilpp /dnfv311/run D6. Steps on a customization system ----------------------------------- To update your current definition directory and the customized administrative scripts, and to create deployment instructions and vehicles: 1. Change to the customization directory: cd 2. Run your customization profile: . ./dnicus_ 3. Start the CDP in migration mode and use the following commands to migrate customization data: dnicdpm -i > export cdd/_UK90682.cdd > import cdd/_UK90682.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 * bind the database for FIN service. Deployment instructions are generated in the file '///instructions.txt'. You will need this later in the step D7. 4. 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 D7. Following the deployment instructions created in step D6 -------------------------------------------------------------- Follow the deployment instructions that were created in step D6. This will update the run-time system resources. D8. Additional activities ------------------------- NOT APPLICABLE. D9. Restarting all WebSphere BI for FN message brokers ------------------------------------------------------ Restart all WebSphere BI for FN message brokers. D10. Customize BAR files when using mqsideploy or the Toolkit to deploy them ------------------------------------------------------------------------------ Backup the BTD repository ------------------------- NOT APPLICABLE. Customize BAR files ------------------- Perform this step only if you use mqsideploy or the Toolkit to deploy broker archive (BAR) files manually. If you use the BAP (dniczbap) to automatically deploy the BAR files, skip this step and later deploy the BAR files directly as described in step D11.2.2. If you are unsure which method to use, use the same method that you used when you initially created your instance as described in "Planning, Installation, and Customization". To customize the BAR files for manual deployment: 1. On the runtime system on which you use the BAP, log on to AIX 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 to which you have read and write access and that has at least 35MB of free space. This is the directory in which dniczbap will store the customized BAR files. 3. The component to which the BAP deploys message flows depends on which version of WebSphere Message Broker is used: - For V6.1, the BAP deploys message flows to the configuration manager. - For V7, the BAP deploys message flows to the broker. Sometimes, the BAP cannot connect directly to this component, for example, when you use Broker V6.1 and the configuration manager is located on Windows. How you customize the BAR files depends on whether the BAP can connect to this component: a. If a connection is not possible, issue the following command to customize all BAR files: dniczbap -cmd prepare -all -dir where represents the output directory created in step 2. b. If a connection is possible, ensure that the configuration manager (if using Broker V6) and the brokers are running, and that no flows or execution groups are stopped. Issue the following command to cause the BAP to identify the BAR files that are to be updated: dniczbap -cmd prepare -update new -dir where represents the output directory created in step 2. Regardless of which method (a or b) you use, each of the customized BAR files in the output directory has a name of the form: ....bar where The name of your instance. 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. If you performed step 3.a, identify the BAR files that are listed in section "B. Summary of changes" and delete all other BAR files from the output directory. 5. Transfer, in binary mode, the customized BAR files in the output directory to the Toolkit or to the system on which you will later issue the mqsideploy command. 6. If you will use the Toolkit to deploy the message flows, import the customized BAR files. D11. Redeploy updated BAR files ------------------------------ Deploying the WebSphere BI for FN BAR files that are delivered in this PTF updates the message flows that run in the broker. For a list of flows contained in each BAR file, refer to "Planning execution groups" section of "Planning, Installation, and Customization". Each WebSphere BI for FN message flow has a suffix that represents its version. For example, the flow DNI_SYSADM_1141 has the version 1141. The version of a flow corresponds to the driver level of the PTF that most recently updated it. Refer to the header of this readme to determine the driver level of this PTF. To deploy BAR files, you must have the access rights of the WebSphere MB administrator (uwmba1). D11.1 Deploy new message flows - - - - - - - - - - - - - - - NOT APPLICABLE. D11.2. Update existing message flows - - - - - - - - - - - - - - - - - - If you already prepared the customized BAR files as described in step D10, proceed with step D11.2.1; otherwise, proceed with step D11.2.2 D11.2.1 Deploying the BAR files customized in step D10 Use the Toolkit or the mqsideploy command to manually deploy the BAR files. Remove the old versions of the message flows that have been updated by the BAR files you deployed. If you neglect to do this, two different versions of the flows will run simultaneously with unpredictable results. D11.2.2 Deploying BAR files when step D10 was not performed Use the BAP (dniczbap) to customize and automatically deploy the BAR files: 1. Ensure that: - The configuration manager is running (applies only for Broker V6.1) - The brokers are running - No flows or execution groups are stopped. Otherwise, old flow levels might not be deleted during the BAP update operation. 2. On the runtime system where you use the BAP, log on to AIX 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. Ensure that you have at least 35 MB of free space in the current directory. 4. Issue the following command: dniczbap -cmd prepare -update new -deploy 5. Issue the following command to verify that all previous versions of the updated message flows were removed successfully: dniczbap -cmd check The result should be: DNIZ1314I: No problems detected. If you receive the message DNIZ1313E follow the instructions provided in the user response to correct the problem. D11.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 To activate the accounting, the WebSphere MB administrator, for example, uwmba1, must enter the following commands: mqsichangeflowstats -a -e '' -f 'DNF_ILS_FIN_' -c active -b 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 name: DNF_ILS_FIN_9213 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. D12. Migrating configuration data --------------------------------- NOT APPLICABLE. D13. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ NOT APPLICABLE. D14. 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. - Subscribe MSIF to SAGs to enable file transfer and session monitoring. - Start the MSIF Message Transfer service. - Start the Enhanced InterAct service. - Acquire SWIFTNet SnF queues. - Open MSIF SnF input and output channels. - Start the applications that send requests to WebSphere BI for FN. For further information, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration". D15. Updating the Toolkit development environment ------------------------------------------------- NOT APPLICABLE. *-----------------------------------------------------------------------------* * End of Installation * *-----------------------------------------------------------------------------* E. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM76017 FIN TNG TRAILER LENGTH CHECKING OF MT940 WITH 2000 CHARACTER SWIFT RETURNED A NAK WITH CODE "M50" (MESSAGE TOO LONG) Formerly, M50 NAK could be received when a FIN message got too long due to appending TNG trailer. Now, for Test and Training messages that have no TNG trailer appended, yet, length of TNG trailer is respected in message length checking. PM77870 FIN DURING COMMAND 'QUERY -LT LTNAME -QO M' NOT ACCURATE QUERY RESPONSE IN FIN MESSAGES ACKNOWLEDGED WHEN LT BELONGS TO LTGROUP Formerly, the number of acknowledged messages for LTs that belong to an LT Group was displayed incorrectly. Now, the query command has been corrected. PM76522 FIN CONFIGURATION VALUE FOR ATTRIBUTE FINCOPYCONFIGERROR IS IGNORED BY DNF_ILS_FIN Formerly, when a FIN message with a FINCopy service was received but no ASP profile for the given FINCopy service could be found, the FIN message was kept in DNF_IAMS table regardless of the configured value of attribute FinCopyConfigError. Now, the message is delivered to the FIN application if the value of attribute FinCopyConfigError is set to 'deliver'. PM61457 FIN IMPROVE CONNECT TO REMOTE DB2 Formerly, FIN service only support the architecture of connecting to local DB2. Now, FIN service support the architecture of connecting to remote DB2. PM75506 FIN FSM RP RE-SYNCH IMPROVEMENT IN CASE OF SWIFT MESSAGE L14 Formerly, when receiving a SWIFT Msg L14 request to remove LT, FSM correctly generates SL ABORT request, but should not initiate a RP resynch process. Now, RP resynch process is disabled; because of SWIFT protocol modification, a normal termination is performed. PM76526 FIN AUDIT ENABLED FOR DNF_ILC_FIN DOESN'T CAPTURE ERROR REPLIES Formerly, some FIN messages that failed processing in DNF_ILC_FIN were not stored in message audit. Now, all messages processed by DNF_ILC_FIN flow are stored in message audit and their error replies are stored additionally. Fixes for the following APARs from superseded PTFs are also contained in this PTF: PM76806 FIN MT021 RESPOND MSG (MT103,MT298,MT202 COV) WITH DNFH3860E DIGEST VALIDATION FAILED An application can request, from the SIPN, a copy of an earlier message. To do this, the application sends an MT020 message to the SIPN. The SIPN responds by sending the application an MT021 message that contains the requested copy. Formerly, WebSphere BI for FN attempted to validate the message digest of the message nested within the MT021 message, regardless of whether the nested message was a FIN input (ISN) or FIN output (OSN) message. For a nested FIN input message, this led to WebSphere BI for FN erroneously issuing the following error message: "DNFH3860E Digest validation on 'MESSAGE' digest of FIN output message failed.". Now, WebSphere BI for FN validates the message digest of the nested message only if that message is a FIN output (OSN) message. PM76980 FIN MT21 WILL GOT DNFH3713E WHILE REQUEST A SYSTEM MSG Formerly, when trying to retrieve a system message (MT0xx) or service message (LOGIN, SELECT, etc.) with an MT020, the retrieved MT021 got error message DNFH3713E Message type ':00 is not listed in the current ASP because these kind of messages is not listed in the ASP at all. The message was not delivered to the receiving FIN application. Now, WebSphere BI for FN does not attempt to validate system messages and service messages against the ASP, but deliveres them to the receiving FIN application. F. Other changes ---------------- - Provide 32 bit db2swit module for Message Broker 7 user. For more details, please refer to the documemtation WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization. - Message updates: * New response messages: * Updated response messages: DNFH3753E * New event messages: * Updated event message: ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++