============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2010 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 Messaging Services for SWIFTNet InterAct and FileAct PTF UK56356 for APAR PM12411 Date 2010-07-02 ============================================================================== ============================================================================== ============================================================================== 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 ---------------------- 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. /opt/IBM is used in examples. The customization directory. The directory /var/dni_03_01/cus is used in examples. The deployment 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 path and name of the PTF driver. 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-6906. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PM12411 MSIF SWITCHING SAG MP OPTION SETS PM12647 MSIF NEW METRIC TO MEASURE WBI FN FILEACT TRAFFIC PM13677 MSIF WRONG RESULT AFTER ENTERING LIST -LUDT CMD PM14331 MSIF CHANGE EVENT DNFO1020E INTO DNFO1020I PM14134 MSIF DNFO9501E & NULLPOINTEREXCEPTION WHILE APPHDR FORMAT IS WRONG Functional changes: - Added automatic SAG-switching capability for SendFile and SendMsg scenarios - Added automatic re-subscription to receive FileAct events from restarted SAGs - Added new accounting metric to more precisely measure FileAct traffic Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Concepts and Components - Messages and Codes - System Administration - Application Programming - Information Center - Migrating an instance within its current environment - Migrating an instance to a new environment The following modules have been changed: /dnf_03_01/admin/data/DNFEFAS.xml /dnf_03_01/admin/data/dnfczoct.ddl /dnf_03_01/admin/data/dnfczogt.ddl /dnf_03_01/admin/data/dnfczort.ddl /dnf_03_01/admin/data/dnfczoct.cli /dnf_03_01/admin/data/dnfczocb.cli /dnf_03_01/admin/data/dnfczocr.cli /dnf_03_01/admin/data/dnfcocto.cli /dnf_03_01/admin/data/dnfcocsm.cli /dnf_03_01/admin/data/dnfcocdo.cli /dnf_03_01/run/data/dnfczoct.cli /dnf_03_01/run/data/dnfczocr.cli /dnf_03_01/run/data/dnfczocb.cli /dnf_03_01/run/flows/DNF_O_CMD.bar /dnf_03_01/run/flows/DNF_O_FT.bar /dnf_03_01/run/jplugin/dnfco.jar /dnf_03_01/run/msg/dnfcomsg.cat /dnf_03_01/run/res/dnfcomsg.xml /dnf_03_01/run/res/dnfcosdf.xml The following modules are new: /dnf_03_01/admin/data/dnfczo02.ddl /dnf_03_01/admin/data/dnfczo92.ddl /dnf_03_01/admin/data/dnfczo2g.ddl /dnf_03_01/admin/data/dnfczom7.ddl /dnf_03_01/admin/data/dnfczom8.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 return a message of the form: '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 return a message of the form: '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: - PTF UK51523 for APAR PK97164 (WEBSPHERE BI FOR FN MSIF UPDATES). - PTF UK54898 for APAR PM08215 (WEBSPHERE BI FOR FN BASE UPDATES). 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) - 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) Planning transfer option sets: Formerly, the SagMPOptionSetGroup option of a transfer option set was used only for ReceiveMsg, ReceiveFile, ProvideFileForDownload, and RespondDownload scenarios, to determine which SAG MP option set to use when an SAG employed traffic distribution. Now, it is used also by SendMsg and SendFile scenarios that employ SAG MP option set switching. If this new behavior is not desired, plan to create new transfer option sets for the SendMsg and SendFile scenarios, and use your current transfer option sets exclusively for ReceiveMsg and ReceiveFile scenarios. For more information about the use of SAG MP option set groups, see "Option set groups" in "WebSphere BI for FN for Multiplatforms: Concepts and Components", SH12-6905. List of MSIF event messages that are to be monitored has changed: The section "Operating and administering the MSIF Transfer Service" of "WebSphere BI for FN for Multiplatforms: System Administration", SH12-6907 contains a list of event messages that indicate situations that typically require an MSIF administrator or operator to take immediate corrective action. This list has been modified to reflect changes to the event messages and the modules that issue them. The following message IDs have been changed: - DNFO1020E --> DNFO1020I - DNFO1606E --> DNFO1606I The following message IDs have become obsolete: - DNFO1070I - DNFO1071E - DNFO1101E - DNFO1306E Switch to MSIF roles -------------------- The following pre-configured roles, which were first introduced for the Enhanced Support for SWIFTNet FileAct (EFA) feature of WebSphere BI for FN V2.2, are now obsolete: - DnfEfaSender - SWIFTNetEfaSnfOperator Instead, use the following pre-configured roles, which were introduced for the Messaging Services for SWIFTNet InterAct and FileAct (MSIF) feature of WebSphere BI for FN V3.1, which superceded and replaced the EFA feature: - DnfEfaApplication (replaces DnfEfaSender) - DnfEfaSwiftOperator (replaces SWIFTNetEfaSnfOperator) To check whether the EFA roles are still used, enter the following command for each OU to which the DNFEFAS service bundle has been assigned, as well as for SYSOU and DNFSYSOU: dnicli -i -s DNI_SECADM -ou -c "list -user % -lo nb" Note that more than one user administrator user ID might be necessary to do this. Examine each list and determine whether any users have one of the EFA roles assigned and do not have the corresponding MSIF role assigned. If so, for each of these users, assign the MSIF role and remove the EFA role by using the following commands: dnicli -s DNI_SECADM -ou > rem -user -ro DnfEfaSender -ou > rem -user -ro SWIFTNetEfaSnfOperator -ou > add -user -ro DnfEfaApplication -ou > add -user -ro DnfEfaSwiftOperator -ou > com -user > app -user > .quit D. Preparation -------------- D1. Installation ---------------- 1. Install this PTF. 2. Share the files in the /dnf_03_01/admin directory with your customization system. 3. 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 4. Share the files in the following directories with your runtime systems: /dnf_03_01/run/data /dnf_03_01/run/flows These files are already needed during the preparation phase and do not influence normal operation. 5. Set the group ownership of these directories and files to group dnilpp. To do this, enter the following commands in AIX shell: chgrp -R dnilpp /dnf_03_01/run/data chgrp -R dnilpp /dnf_03_01/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/_UK56356.cdd > import cdd/_UK56356.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 * Tablespace DNIvDB01.DNFOMP added * Tablespace DNIvDB01.DNFOLH added * Tablespace DNIvDB01.DNFOMI2S added * Table DNIvSN.DNFO_SMPGROUPS added * Table DNIvSN.DNFO_FSM_STATE expanded (columns INITIAL_MPOS, CURRENT_MPOS, and SWITCH_TIME added) * Index DNIvSN.DNFY7OFA added on table DNIvSN.DNFO_FSM_STATE * Index DNIvSN.DNFU1OSG added for new table - DBGNT * DB2 privileges granted for table: DNIvSN.DNFO_SMPGROUPS 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. 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. If you configured an escape character to mark wildcards in role list output, 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 configured. Otherwise: a. Note the configured escape character. b. Disable the escape character by issuing the following command on a single line: > rem -ou SYSOU -ct DniSecAdm.list -co DniSecAdm.list -attr DniEscapeCharacter c. Commit, approve and deploy the OU SYSOU. d. Close the CLI session by issuing the following command: > .quit 3. Create a temporary directory where dnfczmlc stores the CLI command files which will contain the configuration migration statements. 4. Switch to this directory and issue 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 YES. Specify 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 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 5. If you disable an escape character in step 2: a. Re-enable it by issuing the following commands: > dnicli -s DNI_SYSADM -ou SYSOU > add -ou SYSOU -co DniSecAdm.list -ct DniSecAdm.list -attr DniEscapeCharacter -val where is the escape character. b. Commit, approve, and deploy the SYSOU. c. Close the CLI session by issuing the following command: > .quit 6. If, in "C. Planning", "Planning transfer option sets", you planned to use different transfer option sets for your send and receive scenarios, prepare a CLI script to configure the corresponding COs.. This PTF changes the following configuration entities: CTs - Adds attribute 'set' to CT 'DnfEfaCmdAccessControl' - Adds attribute 'query.mposgrp' to CT 'DnfEfaCmdAccessControl' Roles - Adds attribute 'set' to role 'DnfEfaSwiftOperator' that corresponds to CO 'DnfEfaSwiftOpAccessControl' of type 'DnfEfaCmdAccessControl' - Adds attribute 'query.mposgrp' to role 'DnfEfaSwiftOperator' that corresponds to CO 'DnfEfaSwiftOpAccessControl' of type 'DnfEfaCmdAccessControl' COs - Adds attribute 'set' to CO 'DnfEfaSwiftOpAccessControl' of type 'DnfEfaCmdAccessControl' - Adds attribute 'query.mposgrp' to CO 'DnfEfaSwiftOpAccessControl' of type 'DnfEfaCmdAccessControl' D4. 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 to Step E. If you do not use the BAP to deploy the updated BAR files, which of the following procedures you must follow depends on whether the BAP has access to the files on the configuration manager: - If so, follow the procedure described in D4.1 - If not, follow the procedure described in D4.2 D4.1. Customize BAR files without access to the configuration manager --------------------------------------------------------------------- Carry out the following steps when BAP does not have access to the files on the configuration manager, for example, because the configuration manager runs on a Windows workstation. 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 on which the configuration manager runs, 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 30 MB 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. D4.2. Customize BAR files with access to the configuration manager ------------------------------------------------------------------ Carry out the following steps when the BAP has access to the files on the configuration manager and can automatically detect which BAR files need to be updated. 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 30 MB 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 services. - 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-6907. 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: chgrp -R dnilpp /dnf_03_01/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 _UK56356 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 ---------------------------- 1. On the system where the DB2 subsystem resides, log on to AIX as a DB2 administrator (udb2adm1). 2. To remove interfering rows that might have been left over from a previous maintenance level and to migrate column values for this APAR: Use an SQL processor such as 'DB2 command line' to run the SQL statements contained in the file dnfczom8.ddl Issue the following commands: db2 connect to db2 -t -n -s -f //admin/dnfczom8.ddl -l dnfczom8.log db2 connect reset Verify that all SQL codes returned by DB2 are successfully. 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. 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 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 ----------------------------------------------- NOT APPLICABLE. E10. 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 D3.4 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 UK56356.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. - 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, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration", SH12-6907. 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: PM12411 MSIF SWITCHING SAG MP OPTION SETS See section G. PM12647 MSIF NEW METRIC TO MEASURE WBI FN FILEACT TRAFFIC See section G. PM13677 MSIF WRONG RESULT AFTER ENTERING LIST -LUDT CMD Formerly, when the list-command was issued to service DNF_O_CMD: - If the -ludt (last update date, to) parameter was specified but the -lutt (last update time, to) parameter was not specified, the -ludt parameter was ignored and the default value (the current date) was used. - If the -lutt parameter was specified but the -ludt parameter was not specified, the -lutt parameter was ignored and the default value (0:00 a.m.) was used. In both cases, all scenarios that changed their state before 0:00 a.m. on the current date were listed. Now, the processing of the -ludt and -lutt parameters has been corrected: - If the -ludt parameter is specified but the -lutt parameter is not specified, the value specified for the -ludt parameter is used, and the default value of the -lutt parameter (0:00 a.m.) is used. All scenarios that changed their state before 0:00 a.m. on the specified date are listed. - If the -lutt parameter is specified but the -ludt parameter is not specified, the value specified for the -lutt parameter is used, and the default value of the -ludt parameter (the current date) is used. All scenarios that changed their state before the specified time on the current date are listed. PM14331 MSIF CHANGE EVENT DNFO1020E INTO DNFO1020I The user action for event DNFO1020E instructed the user to check whether the corresponding scenario was in the transfer condition inError and, if so, to issue a recover command. However, the transfer condition of a scenario is never set to inError due to event DNFO1020E, and no user action is required when this event is issued. Consequently, the event classification was changed from "eventual action" to "information", and the message ID of this event was changed from DNFO1020E to DNFO1020I. It is not necessary for this event to be monitored in order to ensure that the MSIF Transfer Service continues to run properly. PM14134 MSIF DNFO9501E & NULLPOINTEREXCEPTION WHILE APPHDR FORMAT IS WRONG Formerly, when the MSIF Transfer Service received an SAG message that contained an SNL request or response primitive, if the value of the AppHdr.CrDate field of that primitive was not in a date and time format defined by ISO 8601, an internal error caused the MSIF Transfer Service to stop. Now, the MSIF Transfer Service continues to run, and passes a corresponding application message to the application. The value of the AppHdr.CrDate field in this message is the value that was specified in the primitive, formatted as a string. The message also contains an additional reason with code PARTIAL_OK that describes the problem. PM10369 MSIF CIN STOPPED PROCESSING DURING THE STORING OF EVENT DATA IN DNFO_REASON TABLE INDICATED AS SQLSTATE=22001 Formerly, when the MSIF Transfer Service inserted SwGbl:Status event information into table DNFO_REASON, it did not check whether the information to be stored was larger than the defined column size. If the information exceeded the size limit (1023 Bytes), the CIN stopped and indicated SQLSTATE=22001. Now, the length of SwGbl:Status event information is checked before it is inserted or updated, and if it exceeds 1023 Bytes it is truncated. Note: This is the sysrouted WebSphere BI for FN V3.1 APAR of the original WebSphere BI for FN V2.2 Field-APAR (PM09881). PM12641 MSIF DNFO9501E ERROR EVENT DURING THE DELIVERY NOTIFICATION PROCESS DUE TO THE MISSING MESSAGE PARTNER Formerly, during a real-time FileReceived scenario, when the MSIF Transfer Service attempted to send a delivery notification, if a message partner was not configured in the SAG MP option set that was used, the MSIF Transfer Service raised a null-pointer exception. Now, if a message partner is not configured, the MSIF Transfer Service uses the message partner of the incoming SNL request. PM12350 MSIF FILE CORRELATION PROBLEM WITH COMMTYPE = MQHA Formerly, when using in MSIF CommType=MQHA without chunking to transfer several files to the SAG in parallel, correlation problems could occur and the MSIF Transfer Service might sometimes send the wrong file. This has been corrected. G. Other changes ---------------- New/changed functions: - Automatic SAG MP option set switching for SendFile and SendMsg scenarios: A SendFile or SendMsg scenario can use an SAG MP option set group instead of a particular SAG MP option set. If such a scenario encounters a recoverable error and exhausts all if its automatic recovery attempts (for example, because the SAG specified by the first SAG MP option set in the group is not running), the MSIF Transfer Service, instead of returning an error response, switches to the next SAG MP option set in the group and tries again. For further information, see "WebSphere BI for FN for Multiplatforms: Concepts and Components", SH12-6905. - Automatic re-subscription for restarted SAGs: When an SAG at release level 6.3 or later is restarted, the MSIF Transfer Service now automatically re-subscribes to receive the FileAct events issued by that SAG. If an automatic re-subscription attempt fails, it is regarded as a recoverable error. - New metric to more precisely measure FileAct traffic: Formerly, the MSIF Transfer Service collected accounting information with service type DnfEfaF, which reported the number of file transfers and the number of kilobytes of data that was transferred. Now, two additional service types have been added: - DnfEfaFx reports the number of file transfers conducted by the MSIF Transfer Service for which the TtlNbOfTxs field was specified in the HeaderInfo folder of the corresponding FileAct primitive, and the total number of transactions specified in the TtlNbOfTxs fields for these file transfers. - DnfEfaFs collects the number of file transfers conducted by the MSIF Transfer Service for which the TtlNbOfTxs field was not specified in the HeaderInfo folder of the corresponding FileAct primitive, and the number of kilobytes of data that was transferred for these file transfers. - Formerly, for a MsgReceived and FileReceived scenario, if the SAG MP option set that was used specified a group but no message partner (MP), when the MSIF Transfer Service sent a delivery notification, a null pointer exception occurred. Now, if the SAG MP option set used for a MsgReceived and FileReceived scenario: - Specifies a group, it must also specify an MP. If it does not, a validation error occurs and the transfer is rejected. - Does not specify a group, any MP it might specify is ignored. The MP specified in the envelope of the incoming SWIFT request is used for the delivery notification. For RespondDownload and ProvideFileForDownload scenarios, the MP attribute in the SAG MP option set is still mandatory. - Formerly, if the .. or .. element of a SendMsg request or response was empty, this element was not passed to the application. Now, empty . elements are also passed. - Formerly, for a SendFile scenario, if an automatically recoverable error occurred and if the value of the InErrorAction attribute of the CO DnfEfaBouParameters was set to App, the ReasonList field of the response message that was sent back to the application contained both a general error message and a more specific error message, and the general error message used the wrong message ID to refer to the more specific error message. Now, the ReasonList field of the response message contains only the more specific error message. - Previously, when receiving a delivery notification for a real-time file transfer, the MSIF Transfer Service used the same authoriser DN that it used for the corresponding file-transfer request primitive. If the delivery notification was received from a message partner (MP) that was different from the MP that sent the file: - If the MPs used different authoriser DNs, the wrong DN was used and this resulted in an error. - If the MPs used the same authoriser DN, the correct DN (coincidentally) was used and this did not result in an error. Now, the MSIF Transfer Service uses an SAG MP option set group to automatically determine the correct authoriser DN to use. However, this requires that you reconfigure the SAG MP option sets of both MPs so that they are members of the same SAG MP option set group, even if the MPs use the same authoriser DN and no errors have occurred. - Formerly, the configuration template file dnfcocto.cli did not define the SagMPOptionSetGroup attribute of the CT DnfEfaTransferOptionSet. This has been corrected. - Formerly, the configuration template file dnfcocsm.cli did not define the Group attribute of the CT DnfEfaSagMPOptionSet. This has been corrected. - Formerly, the configuration template file dnfcocdo.cli did not define the ProductInfoOptionSet attribute of the CT DnfEfaDownloadOptionSet. This has been corrected. H. Known issues ---------------- - MSIF distinguishes between recoverable and unrecoverable errors. For a scenario that encounters a recoverable error, the transfer condition of the scenario is set to "inErrror". After the problem that caused the error has been fixed, a user can issue the "recover" command to manually recover the scenario. Before MSIF introduced SAG MP option set switching capability, it regarded an error in the configuration of an SAG MP option set (for example, a missing mandatory option) to be an unrecoverable error. This was because a stalled scenario is not refreshed with changed configuration data, so even if the error were corrected, the scenario in progress would remain unaffected. The only way to address this situation was to cancel the scenario and initiate a new scenario. However, when SAG MP option set switching is used, such a configuration error does not necessarily mean that the scenario will fail. If one SAG MP option set is misconfigured, the next SAG MP option set in the group is used. If that option set is configured correctly, and if there are no other problems, the scenario will succeed. Consequently, MSIF no longer regards an error in the configuration of an SAG MP option set to be an unrecoverable error. However, if a scenario fails because the last SAG MP option set in the group is configured incorrectly, even though the transfer condition of the scenario is set to "inErrror", the "recover" command will not work, and the scenario must be canceled. For this reason, it is important that you ensure that all option sets are correctly configured before you begin using them in a production environment. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++