============================================================================== ============================================================================== 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 UK94070 for APAR PM82139 Driver level: 3220 Date 2013-06-24 ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Installation E APAR details F Other changes G Known issues 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 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: PM82139 FIN FIN / RP USER SYNCHRONISATION WAS NOT WORKING AFTER ABORT COMMAND FOR ONE LT PM82056 FIN IMPROVE FIN BEHAVIOUR IN CASE OF INCONSISTENT ASP DATA PM76872 FIN FIN AND FMT SUPPORT FOR ADMINISTRATION AND OPERATION WITH LONG USERIDS PM83425 FIN ACCESS ERROR WHEN MQ SECURITY TURNED ON FOR FIN PM86973 FIN FIN CHANGES NECESSARY TO SUPPORT WEBSPHERE BI FOR FN BASE CDP APAR PM78252 Additional functional changes: - none Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Messages and Codes - System Administration The following modules have been changed: /dnfv311/admin/data/dnfcfcce.cli /dnfv311/admin/data/dnfczfcy.cli /dnfv311/admin/data/DNFFCOMMON.xml /dnfv311/admin/data/DNFFIN.xml /dnfv311/admin/data/DNFFMTFIN.xml /dnfv311/admin/data/dnfxzfco.def /dnfv311/admin/data/dnfxzpco.def /dnfv311/run/bin/dnfcfsfd /dnfv311/run/bin/dnfcfsfs /dnfv311/run/data/dnfczfcy.cli /dnfv311/run/flows/DNF_ILC_CMD.bar /dnfv311/run/flows/DNF_ILC_FIN.bar /dnfv311/run/flows/DNF_ILS_ACK.bar /dnfv311/run/flows/DNF_ILS_FIN.bar /dnfv311/run/flows/DNF_PF_CMD.bar /dnfv311/run/flows/DNF_PF_IR.bar /dnfv311/run/flows/DNF_PF_IS.bar /dnfv311/run/flows/DNF_SNF_CMD.bar /dnfv311/run/jplugin/dnf.asp.acc.jar /dnfv311/run/lib/libdnfcf.a /dnfv311/run/msg/dnfcfmsg.cat /dnfv311/run/res/dnfcersp.xml /dnfv311/run/res/dnfchevt.xml /dnfv311/run/res/dnfchrsp.xml /dnfv311/run/res/dnfcjevt.xml /dnfv311/run/res/dnfcjrsp.xml The following modules are new: /dnfv311/admin/data/dnfxzf0s.def /dnfv311/admin/data/dnfxzp0s.def /dnfv311/run/msg/DNFA_Msg.properties /dnfv311/run/msg/DNFE_Msg.properties /dnfv311/run/msg/DNFF_Msg.properties /dnfv311/run/msg/DNFH_Msg.properties /dnfv311/run/msg/DNFJ_Msg.properties /dnfv311/run/msg/DNFP_Msg.properties 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. To check this, log on to AIX on the customization system as a customizer (ucust1) and enter the following command on your customization system: /dniv311/admin/bin/dnicdpst -i -cdefs where The name of the WebSphere BI for FN instance The name of the customization definitions directory as specified in the CDP ini file, for example: /var/dni_03_01/cus/defs If the response to this command indicates that 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 shared the files contained in this or any other PTF as described in section D5 step 2. - Implement the pending operation before continuing. 3. Until the migration for this PTF has been completely finished, ensure that no changes are made to the currently implemented CDD. 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: - UK90682 for APAR PM76806 (CSN 3.1.1.6, MT021 RESPOND MSG (MT103,MT298, MT202 COV) WITH DNFH3860E DIGEST VALIDATION FAILED - UK94069 for APAR PM84617 (Base 3.1.1.12, IMPROVE ADMINISTRATION AND OPERATION FACILITY SECURITY) C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - DB2 administrator (udb2adm1) - WebSphere MQ administrator (uwmqadm1) - WebSphere MB administrator (uwmba1) - First WebSphere BI for FN system configuration administrator (sa1) - Second WebSphere BI for FN system configuration administrator (sa2) 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. Log on to AIX 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/_UK94070_temp.cdd > supplement cdd/_UK94070_temp.cdd cdd/_UK94070.cdd Edit the supplemented CDD to specify a value for the new placeholder DNFvPATH. Search for each occurrence of the string value=" and specify the appropriate placeholder values. > import cdd/_UK94070.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: - MQAUT * update permission on queue DNIvMQMN.DNIvINST.DNIvOU.DNF_ILC_FIN for group DNIvSGRP * update permission on queue DNIvMQMN.DNIvINST.DNIvOU.DNF_PF_IS for group DNIvSGRP Deployment instructions are generated in the file '///instructions.txt'. You will need this later in the step D7. 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 D7. Following the deployment instructions created in step D6 ------------------------------------------------------------ Follow the deployment instructions that were created in step D6. D8. Additional activities ------------------------- D8.1. DB2 related activities ---------------------------- NOT APPLICABLE. D8.2. WebSphere MB related activities ------------------------------------- NOT APPLICABLE. D8.3. WebSphere MQ related 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 number of the PTF that most recently updated it. Refer to the header of this readme to determine the PTF number 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 - DNF_ILS_ACK.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 mqsichangeflowstats -a -e '' -f 'DNF_ILS_ACK_' -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 --------------------------------- D12.1 Generating configuration data migration scripts ----------------------------------------------------- To prepare the migration of configuration entities: 1. On the runtime system on which the message broker runs, log on to AIX as the system configuration administrator, for example, sa1, and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a temporary directory where dnfczmlc stores the CLI command files which will contain the configuration migration statements. 3. Switch to this directory and enter the following command: dnfczmlc.sh -i [-dual YES|NO] [-to timeout] where: -i The name of the instance. -dual YES|NO Specifies whether files are to be created for a system that uses dual authorization for SYSOU. The default is -dual YES. Specify -dual NO only if dual authorization is to be turned off for both DNI_SYSADM and DNI_SECADM in SYSOU at the time when the created files are executed. Whether dual authorization is switched on or off for other OUs is irrelevant. -to timeout The number of milliseconds that the CLI waits for a response to this command before it issues an error message. The default is 100000 (100 seconds). It must be a whole number between 20000 and 9999999. Note: This command starts a long-running task that might take several minutes to complete. Check the file dnfczmlc.log to ensure that it completed successfully. The program dnfczmlc creates the following CLI command files: If dual authorization is not used (-dual NO): 1. dnfczmlc_2_sa_ent_all.cli If dual authorization is used (-dual YES): 1. dnfczmlc_5_sa_cre_ct_com.cli 2. dnfczmlc_5_sa_cre_ct_dep.cli 3. dnfczmlc_6_sa_cre_co_com.cli 4. dnfczmlc_6_sa_cre_co_dep.cli 4. Replace the placeholder "DNFvPATH" in dnfczmlc_6_sa_cre_co_com.cli with the value specified in _UK94070.cdd by step 4 of D6. This PTF changes the following configuration entities: - Creates CO DnfMessageFilesFin of type DniFileDir add -ou SYSOU -ct DniFileDir -co DnfMessageFilesFin -attr Path -val DNFvPATH/run/msg add -ou SYSOU -ct DniFileDir -co DnfMessageFilesFin -attr read - Expands CO of type DnfExceptionOptionSet ;add -ou DNIvOU -ct DnfExceptionOptionSet -co -attr AspSndExceptionQueue -val ;add -ou DNIvOU -ct DnfExceptionOptionSet -co -attr AspSndExceptionQMgr -val where The name of the option-set for exception processing. If you want any of these commands to be executed, set the value as needed and remove the comment character (;) from in front of the corresponding add statement. Note: With Base PTF for APAR PM84617 new attributes AspSndExceptionQueue and AspSndExceptionQMgr are added to CT DnfExceptionOptionSet Scripts for CO changes are only created if you have configured exception queues. Note: With PTF UK80316 for APAR PM62849 (ASP: UPDATE RM STORED PROCEDURE TO QUERY MORE ASP DATA) an ASP Error-Receive exception queue is used for messages received (with an invalid message type, or where no ASP profile is found for the corresponding FIN Copy service). This queue needs to be defined now. D12.2 Executing the migration scripts ------------------------------------- Execute the CLI command files generated in step D12.1 in the following sequence and using the following user authorization: If dual authorization was not used (-dual NO): - dnfczmlc_2_sa_ent_all.cli by any SA If dual authorization was on (-dual YES): - dnfczmlc_5_sa_cre_ct_com.cli by the first SA (sa1) - dnfczmlc_5_sa_cre_ct_dep.cli by the second SA (sa2) - dnfczmlc_6_sa_cre_co_com.cli by the first SA (sa1) - dnfczmlc_6_sa_cre_co_dep.cli by the second SA (sa2) 1. On the runtime system, log on to AIX as the indicated user and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Switch to the temporary directory you created in step D12.1 and execute the generated CLI command files by entering the following command: dnicli -s -ou SYSOU -cft | tee -a UK94070_cli.log where: DNI_SYSADM for files executed by the system configuration administrators, abbreviated as SA The CLI command file name, for example dnfczmlc_5_sa_cre_ct_com.cli. 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. D16. Verifying your Installation -------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Installation * *------------------------------------------------------------------------------* E. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM82139 FIN FIN / RP USER SYNCHRONISATION WAS NOT WORKING AFTER ABORT COMMAND FOR ONE LT Formerly, FIN/RP user synchronisation did not work properly after LT abort (signal timeout) because of race condition between SFD client and server process. Now, internal abort command is reset to allow FIN/RP user synchronisation. PM82056 FIN IMPROVE FIN BEHAVIOUR IN CASE OF INCONSISTENT ASP DATA FIN behaviour has been improved in case of inconsistent ASP data. Now, when ASP data is not updated in the system, or the data is inconsistent, and a FIN message type is detected which is not defined in an ASP, FIN acts as follows: * On the sending side: - An error response with code Failed and MPU DNFH3713E is sent back to the sending application. - If exception queues are configured, messages failing with DNFH3713E are sent to distinct queue AspSndExceptionQueue. * On the receiving side: - The message is enriched with error indication DNFH3713E and passed to the receiving FIN application queue with reason code Failed. - If exception queues are configured, messages failing with DNFH3713E are sent to distinct queue MsgValRcvExceptionQueue. PM76872 FIN FIN AND FMT SUPPORT FOR ADMINISTRATION AND OPERATION WITH LONG USERIDS Formerly, you could not use an userid with more than 12 characters in the Administration and Operation Facility to operate FIN and FMT services. Now, an userid with more than 12 characters can be used. PM83425 FIN ACCESS ERROR WHEN MQ SECURITY TURNED ON FOR FIN Formerly, WebSphere BI for FN Message Management could not put requests into the FIN interface queue. The reason was, that the group DNIvSGRP, in which the broker userid resides did not have access to FIN interface queue DNIvINST.DNIvOU.DNF_ILC_FIN. Only members of groups DNIvOGRP and DNFvCUSR were allowed to access it. Now, authorization is assigned for DNIvINST.DNIvOU.DNF_ILC_FIN queue (FIN) and for DNIvINST.DNIvOU.DNF_PF_IS queue (FMT) to group DNIvSGRP. PM86973 FIN FIN CHANGES NECESSARY TO SUPPORT WEBSPHERE BI FOR FN BASE CDP APAR PM78252, PM80628, PM82134 This FIN PTF contains the changes necessary to support WebSphere BI for FN Base CDP Apars PM78252, PM80628, PM82134. Please refer to these Apars for further description. F. Other changes ---------------- - Message updates: * Event messages changed (only textual changes): DNFJ3030E, DNFH3794E * Response messages new: DNFH3501E * Response messages changed (only textual changes): DNFH3503E - DNFH3553I, DNFH3559I, DNFH3560I, DNFH3764E, DNFE3265E, DNFJ3240I, DNFJ3247I - Now A&O can display the error messages from CSN. G. Known issues --------------- WebSphere Message Broker migration from Version 6 to Version 7 may cause the WebSphere BI for FN CPU load of the services that process FIN, InterAct, and FileAct transfers to increase by up to 15%, the actual amount depending on how these services are used. Thus, it is likely that these services will experience slightly decreased throughput. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++