============================================================================== ============================================================================== 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.1 Messaging Services for SWIFTNet InterAct and FileAct PTF UK68443 for APAR PM40419 Date 2011-08-05 ============================================================================== ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Preparation E Activating F APAR details G Other changes H Known issues A. About this document ---------------------- If you install this PTF as part of the migration from version 3.1 to 3.1.1 then do not follow the steps in this readme, but those described in the Migration Guide. 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 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: PM40419 MSIF UPDATES FOR V311 WEBSPHERE BI FOR FN MSIF PM41483 MSIF ACCOUNTING DATA MISSING PM41455 MSIF RECEIVE REQUESTS ARE REJECTED WHILE THE SUBSCRIBE REQUEST IS RUNNING PM41482 MSIF THE MSIF API INTERFACE STRUCTURES FOR INTERACT SCENARIOS MISS SOME ESSENTIAL TIMESTAMPS RELATED TO SWIFTNET PROCESSING. Functional changes: The MSIF transfer service is changed to: - control the message priority in SendFile scenarios - include the business message in an InterAct SnF response - re-open an input channel and switch an SAG in case the queue session was lost - return the delivery time to the application Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Concepts and Components - Messages and Codes - System Administration - Application Programming - Information Center - Migration Information - Release Information The following modules have been changed: /dnfv311/run/jplugin/dnfco.jar /dnfv311/run/msg/dnfcomsg.cat /dnfv311/run/res/dnfcomsg.xml /dnfv311/run/flows/DNF_O_FT.bar /dnfv311/run/data/dnfczoch.lst /dnfv311/run/data/dnfczoct.cli /dnfv311/run/data/dnfczocy.cli /dnfv311/admin/data/DNFEFAS.xml /dnfv311/admin/data/dnfczoch.lst /dnfv311/admin/data/dnfczoct.cli /dnfv311/admin/data/dnfczocy.cli /dnfv311/admin/data/dnfcocic.cli /dnfv311/admin/data/dnfcocms.cli /dnfv311/admin/data/dnfczoct.ddl /dnfv311/admin/data/dnfczocs.mq /dnfv311/admin/data/dnfczors.mq /dnfv311/admin/data/dnfxzocs.def /dnfv311/admin/data/dnfxzors.def The following modules are new: /dnfv311/admin/data/dnfczo0s.mq /dnfv311/admin/data/dnfxzo0s.def /dnfv311/admin/data/dnfczo01.ddl 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: - UK68439 for APAR PM40373 (UPDATES FOR V311 WEBSPHERE BI FOR FN BASE). 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) - First WebSphere BI for FN security configuration administrator (ua1) - Second WebSphere BI for FN security configuration administrator (ua2) 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, 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. 4. Share the files in the /dnfv311/admin directory with your customization system. 5. Ensure that the group ownership of the /dnfv311/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 /dnfv311/admin 6. Share the files in the following directories with your runtime systems: /dnfv311/run/data /dnfv311/run/flows 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 /dnfv311/run/data chgrp -R dnilpp /dnfv311/run/flows 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 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/_UK68443.cdd > import cdd/_UK68443.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: - DB * table DNFO_FSM_RCV_MSG changed, column DELIVERY_TIME_UTS added * table DNFO_FSM_ICHL changed, column PREVIOUS_STATE added * index DNFYAOFA on table DNFO_FSM_STATE added - MQ * queue DNF_O_FTERR added - MQAUT * permission on queue DNF_O_FTERR added 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 --------------------------------------------------- To prepare the migration of configuration entities: 1. Restart all WebSphere BI for FN message brokers. 2. 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 3. Check if you have enabled wildcard escaping for the 'list -ro' command and disable it temporarily. To check if you have configured an escape character enter the following commands: dnicli -s DNI_SYSADM -ou SYSOU > list -ou SYSOU -co DniSecAdm.list -attr DniEscapeCharacter -lo osv If the response is 'No OUs match search criteria.' no escape character is defined. Otherwise note the value displayed and enter the following command in the CLI session to temporarily disable the escape character: > rem -ou SYSOU -ct DniSecAdm.list -co DniSecAdm.list -attr DniEscapeCharacter Commit, approve and deploy the OU SYSOU. Close the CLI session: > .quit 4. Create a temporary directory where dnfczmlc.sh stores the CLI command files which will contain the configuration migration statements. 5. 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.sh creates the following CLI command files: If dual authorization is not used (-dual NO): 1. dnfczmlc_2_sa_ent_all.cli 2. dnfczmlc_3_ua_cre_ro_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 5. dnfczmlc_8_ua_cre_ro_com.cli 6. dnfczmlc_8_ua_cre_ro_app.cli 6. Enable the escape character for the 'list -ro' command if you have temporarily disabled it in step 2: dnicli -s DNI_SYSADM -ou SYSOU > add -ou SYSOU -co DniSecAdm.list -ct DniSecAdm.list -attr DniEscapeCharacter -val where is the value that was displayed in response to the list command in step 3. This PTF changes the following configuration entities: - adds the attribute 'SnFReturnBusMsg' to CT 'DnfEfaMsgSendOptionSet' - adds the attribute 'SagMPOptionSetGroup' to CT 'DnfEfaInputChannel' The file dnfczmlc_2_sa_ent_all.cli / dnfczmlc_6_sa_cre_co_com.cli contains the commands add -ct DnfEfaMsgSendOptionSet -ou DNIvOU -co -attr SnFReturnBusMsg -val Error D.4. Manually customize updated BAR files when not using the BAP to deploy them -------------------------------------------------------------------------------- If you use the BAP (dniczbap) to deploy the updated broker archive (BAR) files, the BAR files will be automatically customized during deployment, so you can skip this step. If you do not use the BAP to deploy the updated BAR files, which of the following procedures you must follow depends on whether there is a connection to the configuration manager: - If so, follow the procedure described in D.4.1 - If not,follow the procedure described in D.4.2 Note: Ensure that configuration manager is running and no flows or execution groups are stopped during the deployment of updated BAR files. Otherwise it may happen that old flow levels are not deleted during the BAP update operation (-cmd prepare -update new). To verify that the update was successful you can use the BAP list command. There should be no flows running with the same name but a different version. D.4.1. Customize BAR files without connection to the configuration manager - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Carry out the following steps when there is no connection to the configuration manager, for example, because the 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. 1. On the runtime system, log on to AIX 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 35MB 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 on which you will issue the mqsideploy command. 6. If you want to deploy using the Toolkit, import the customized BAR files. D.4.2. Customize BAR files with connection to the configuration manager - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Carry out the following steps when there is a connection to the configuration manager. The connection enables the configuration manager to automatically detect updated 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 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 35MB 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. - 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, sessons, and services" in "WebSphere BI for FN for Multiplatforms: System Administration", SH12-6943. E.2. Stopping all application servers ------------------------------------ NOT APPLICABLE. E.3. 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 /dnfv311/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: chgrp -R dnilpp /dnfv311/run E5. Backing up runtime database ------------------------------- Back up the WebSphere BI for FN runtime database: 1. On the system where the DB2 subsystem resides, log on to AIX as a DB2 administrator (udb2adm1). 2. Issue the following command: db2 backup db 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. E.7. Additional activities ------------------------- NOT APPLICABLE. E.8. 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 D.5 proceed with step E.9.1; otherwise, proceed with step E.9.2. Note: Ensure that configuration manager is running and no flows or execution groups are stopped during the deployment of updated BAR files. Otherwise it may happen that old flow levels are not deleted during the BAP update operation (-cmd prepare -update new). To verify that the update was successful you can use the BAP list command. There should be no flows running with the same name 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. Remove the old versions of the flows which have been updated by this PTF as otherwise two different versions of the flows are running. You can list the flows running in the broker to identify the names including their version suffix. You can also refer to the Planning, Installation, and Customization manual for a list of flows contained in each BAR file. 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 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 E.9.3. Activating WebSphere BI for FN accounting - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. E.10. Migrating configuration data --------------------------------- 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 D3.3. Execute the CLI command files generated in step D4 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 - dnfczmlc_3_ua_cre_ro_all.cli by any ua 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) - dnfczmlc_8_ua_cre_ro_com.cli by the first ua (ua1) - dnfczmlc_8_ua_cre_ro_app.cli by the second ua (ua2) Enter the following command: dnicli -s -ou SYSOU -cft | tee -a UK68443.cli.log where: DNI_SYSADM for files executed by the system configuration administrators, abbreviated as sa DNI_SECADM for files executed by the security administrators, abbreviated as ua The CLI command file name, for example dnfczmlc_5_sa_cre_ct_com.cli. 3. If applicable, execute the cli-commands generated in D3.6. E11. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ NOT APPLICABLE. E12. Restarting all sessions and services ----------------------------------------- 1. 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", SH12-6943. 2. A subscription to receive FileAct events is needed for each SAG that the MSIF Transfer Service uses to conduct file transfers. Because one of the previous steps erased all subscriptions from the WebSphere BI for FN database, for each SAG that the MSIF Transfer Service is to use to conduct file transfers, resubscribe manually by issuing the "subscribe" command. E13. Updating the Toolkit development environment ------------------------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Activating * *------------------------------------------------------------------------------* F. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM40419 MSIF APAR UPDATES FOR V311 WEBSPHERE BI FOR FN MSIF The listed WebSphere BI for FN V3.1.0 APARs and functional enhancements in section J have been added. Fixes for the following WebSphere BI for FN V3.1.0 APARs are now added to WebSphere BI for FN V3.1.1: PM41383 MSIF MSIF ACCOUNTING DATA MISSING Formerly, MSIF collected accounting data for MsgReceived scenarios that used automatic response mode. Now, it collects accounting data for both automatic and flexible response mode. PM41445 MSIF EFA RECEIVE REQUESTS ARE REJECTED WHILE THE SUBSCRIBE REQUEST IS RUNNING When a "subscribe" command is issued for an SAG to which the MSIF transfer service is already subscribed, the subscription state is changed from "subscribed" to "subscribe in progress". Formerly, when a request was received from an SAG for which the subscription was in this state, the request was rejected with the rejection info "Reason=NoSubscription". Now, such requests are accepted. Note: This is the sysrouted WebSphere BI for FN V3.1.1 APAR of the original WebSphere BI for FN V2.2.0 APAR PM36992. PM41482 MSIF THE MSIF API INTERFACE STRUCTURES FOR INTERACT SCENARIOS MISS SOME ESSENTIAL TIMESTAMPS RELATED TO SWIFTNET PROCESSING. Formerly, the MSIF AP interface structures for InterAct scenarios missed some essential timestamps related to SWIFTNet processing. Now, the MSIF API interface structures for InterAct scenarios have been enhanced to provide the SNF Input Time and the DeliveryTime for InterAct store and foreward message transfers. G. Other changes ---------------- - Formerly, the MSIF transfer service processed application requests in FIFO order. Now, the MQMD.Priority field of a request message determines the priority with which it is processed. - Formerly, an InterAct SnF response contained the business message of the corresponding request only if an error occurred that prevented the request from being delivered to the SnF queue. Now, the SnFReturnBusMsg message send option determines under which circumstances an InterAct SnF response contained the business message of the corresponding request. - A "queue event" is an event issued by an SAG to indicate that a session to an SnF queue has been interrupted. Formerly, when an SAG issued a queue event, the MSIF transfer closed the corresponding input channel. Now, the MSIF transfer service tries to reopen the input channel. If the connection to the SAG cannot be reestablished, and if the SAG MP option set is the member of an option set group, the MSIF transfer service switches to the next SAG MP option set in the group. - Formerly, in a SendMsg or SendFile scenario, the value of the Sw:DeliveryTime field of the corresponding SWIFT primitive was not passed to the application. Now, the application messages include the delivery time. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++