============================================================================== ============================================================================== 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 Base PTF UK74550 for APAR PM47966 = Date 2012-02-16 = ============================================================================== ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Preparation E Activating F APAR details G Other changes A. About this document ---------------------- If you install this PTF as part of the migration from WebSphere BI for FN Version 3.1.0 to Version 3.1.1 then do not follow the steps in this readme, but those described in the Migration Information 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 home directory of the application server profile. /usr/IBM/WebSphere/AppServer/profiles/AppSrv01 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: PM47697 BASE WEBSPHERE APPLICATION SERVER RMA SESSION HANDLING PM49193 BASE RESPONSE DNPA1110E TO THE RMA GUI ALSO SHOWS UP AS EVENT IN EVENT LOG PM49707 BASE THE "SERVICE" SELECTION LIST IN THE RMA GUI, CAN TAKE UP TO A MINUTE UNTIL THE LIST IS DISPLAYED PM50792 BASE ERROR 404: SRVE0190E AT RMA LOGIN PM47966 BASE ERRONOUS MESSAGE SHOULD BACKED OUT IN SEPARAT QUEUE PM48082 BASE RMA QUERY COULD BE ABLE TO DELETE OR EDIT A WRONG QUERY PM48059 BASE INPUT DATA TYPE MISMATCH WITHIN RMA TRACE PM48067 BASE DESCRIPTION OF DNFL9515E, DATE AND TIME PARAMETERS OF RM EXPORT COMMAND SHOULD BE IMPROVED PM48501 BASE INCLUDE RM IN THE MESSAGE TEXT OF DNFL9430E PM49273 BASE WRONG 'ACTION' IN DNFL1126E ERROR MESSAGE PM50081 BASE IMPROVEMENT OF INTERNAL ERROR EVENT DNFL2155E PM50178 BASE RMA FILTER FOR STALE BIC'S DOES NOT WORK AND THE QUERY LEADS TO A HIGH CPU TIME CONSUMPTION PM47793 BASE PROVIDE PUBLIC VIEW TO RMA HISTORY DATA PM51006 BASE MISSING UPDATE IN GRANT STATEMENT IN JOB DBGNT000 OR DBGNT001 PM52815 BASE NULLPOINTER IN DNICZBAP, WHEN NON-WBIFN MESSAGE FLOWS ARE DEPLOYED IN THE SAME BROKER PM51632 BASE AFTER APPLYING UK72501 EXECUTION OF THE DNICZBAP PROGRAM NO LONGER PRODUCES A DNICZBAP.LOG FILE PM51769 BASE AFTER THE MIGRATION TO V311 MSIF PROVIDED SCHEMA CAUSED SYNTAX ERRORS PM49967 BASE BROKER SHUTDOWN SHOULD BE ELIMINATED WHERE FEASIBLE DURING THE WBIFN MP MIGRATION AND MAINTENANCE TO REDUCE THE IMPACT PM53512 BASE OUT OF MEMORY DURING THE WBIFN 311 INSTALLATION PM54191 BASE DNICZBAP ENCOUNTERS ERROR WHEN DEPLOYING BAR FILES IN A MULTI-SERVER ENVIRONMENT Additional functional changes: - hover-help of close icon has been changed to "Close" - filter criteria that validity date is specified/not specified added - "Create Query" and "Create Authorization" buttons in conversion view - Queries and Authorisations can be created from the Conversation view Documentation updates: - Planning, Installation, and Customization - Messages and Codes - System Administration - RMA Users Guide - Information Center - Migration Information The following modules have been changed: /dniv311/admin/appsrv/dniinstapi.py /dniv311/admin/appsrv/res/dnf.rma.web.ear /dniv311/admin/data/DNFCOMMON.xml /dniv311/admin/data/DNFRMA.properties /dniv311/admin/data/DNFRMA.xml /dniv311/admin/data/DNICOMMON.xml /dniv311/admin/data/DnfRma_upd.py /dniv311/admin/data/dnfczcoy.cli /dniv311/admin/data/dnfczlacs.mq /dniv311/admin/data/dnfczlars.mq /dniv311/admin/data/dnfczlr1.ddl /dniv311/admin/data/dnfczlr2.ddl /dniv311/admin/data/dnfxzlacs.def /dniv311/admin/data/dnfxzlars.def /dniv311/admin/data/dnicdcig.ddl /dniv311/admin/data/dnicdcut.ddl /dniv311/admin/data/dnicddco.ddl /dniv311/admin/data/dnicdvap.ddl /dniv311/admin/data/dniczwcf.txt /dniv311/admin/toolkit/dni.schemas.comibmdni.zip /dniv311/run/bin/dnfczmlc.sh /dniv311/run/bin/dniczbap /dniv311/run/classes/dniczbap.jar /dniv311/run/classes/dnp.aspal.api.jar /dniv311/run/classes/dnp.aspal.impl.jar /dniv311/run/data/dnfczcoy.cli /dniv311/run/flows/DNF_RMA.bar /dniv311/run/flows/DNI_A_EVENT.bar /dniv311/run/jplugin/dnf.asp.imp.jar /dniv311/run/jplugin/dnf.rma.tr.jar /dniv311/run/msg/dnfccmsg.cat /dniv311/run/msg/dnfclmsg.cat /dniv311/run/msg/dnpcamsg.cat /dniv311/run/msg/dnpcjmsg.cat /dniv311/run/res/dnfclevt.xml /dniv311/run/res/dnfclmsg.xml /dniv311/run/res/dnicomsg.xml /dniv311/run/res/dnpcamsg.xml /dniv311/run/res/dnpcjmsg.xml The following modules are new: /dniv311/admin/data/dnfczla0s.mq /dniv311/admin/data/dnfxzla0s.def /dniv311/admin/data/dnicdm02.ddl /dniv311/admin/data/dnicdm2g.ddl /dniv311/admin/data/dnfczaco.ddl /dniv311/admin/data/dnfczaro.ddl C. Planning ----------- If you do not use the RMA Application you do not have to process the RMA related steps in the readme: E2, E11.1, and E11.3. 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: - UK71716 for APAR PM44564 (DELETE ACTION DOESN'T WORK WITH THE IMPORT RELATIONSHIP IN RMA - Base 3.1.1.3) This PTF supersedes the following PTF: - none Roles involved: The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - DB2 administrator (udb2adm1) - ESM administrator (uesm1) - WebSphere MQ administrator (uwmqadm1) - WebSphere MB administrator (uwmba1) - WebSphere Application Server administrator (uwasa1) - WebSphere Application Server operator (uwaso1) - 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 /dniv311/admin directory with your customization system. 5. Ensure that the group ownership of the /dniv311/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 /dniv311/admin 6. Share the files in the following directories with your runtime systems: /dniv311/run 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: chgrp -R dnilpp /dniv311/run 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/_UK74550.cdd > import cdd/_UK74550.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 * index DNIX3BIC added * views DNIvSN.DNF_RMAUTH_DNIvOU added * views DNIvSN.DNF_RMQAH_DNIvOU added - MQ * queue DNIvQPFX.DNF_L_TRERR added - MQAUT * permission on queue DNIvMQMN.DNIvQPFX.DNF_L_TRERR added - CFGPF (if SVB DNFRMA is assigned) * instructions and files required to update the WebSphere BI for FN enterprise applications running in the application server 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 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 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_6_sa_cre_co_com.cli 2. dnfczmlc_6_sa_cre_co_dep.cli 6. Enable the escape character for the 'list -ro' command if you have temporarily disabled it in step 3: 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: - none The file dnfczmlc_2_sa_ent_all.cli / dnfczmlc_6_sa_cre_co_com.cli contains the commands add -ct DniCinService -ou SYSOU -co DNF_L_TR -attr EnhancedErrorHandlingEnabled D4. 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 D4.1 - If not, follow the procedure described in D4.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. D4.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 35 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 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 35 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. - 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. E2. Stopping all application servers ------------------------------------ Stop all application servers. 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 /dniv311/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 /dniv311/run E5. Backing up configuration and security data in image copies -------------------------------------------------------------- NOT APPLICABLE. E6. Following the deployment instructions created in step D2.4 -------------------------------------------------------------- Follow the deployment instructions that were created in step D2.4 with the following exception: - do not execute the instructions provided for resource class CFGPF now; you will use them in step E11.3. E7. Additional activities ------------------------- E7.1. DB2 related activities ---------------------------- NOT APPLICABLE. E7.2. WebSphere MB related activities ---------------------------- NOT APPLICABLE. E7.3. WebSphere MQ 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 D5 proceed with step E9.1; otherwise, proceed with step E9.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 z/OS UNIX 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 35 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 --------------------------------- Execute the CLI command files generated in step D3 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_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 D4.2 and execute the generated CLI command files by entering the following command: dnicli -s -ou SYSOU -cft | tee -a PM40415_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_6_sa_cre_co_com.cli. E11. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ E11.1. Backing up the WebSphere Application Server configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Which resources you need to back up depends on whether you use a clustered application server environment or a single server: - If you have a clustered application server environment, back up your deployment manager profile and all other profiles on all nodes that belong to the cluster. - If you have a single application server environment, back up the application server profile. As the WebSphere Application Server operator (uwaso1), issue the following command for each profile that is to be backed up: On Windows: \bin\manageprofiles.bat -backupProfile -profileName -backupFile On other platforms: /bin/manageprofiles.sh -backupProfile -profileName -backupFile where represents the installation directory of the application server and represents the file name under which the backup should be stored. E11.2. Update the WebSphere Application Server environment - - - - - - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. E11.3. Migrating the enterprise application - - - - - - - - - - - - - - - - - - - - - - If the instructions created in step D2.4 contain the resource class CFGPF, follow this section now to update the enterprise applications. Before starting to update the enterprise applications, start the application server on which the enterprise application runs. If you use a clustered application server environment, start the deployment manager, node agent, and all members of the application server cluster. 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-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. 3. Start the WebSphere BI for FN Monitoring Enhancement. E13. Updating the Toolkit development environment ------------------------------------------------- If you use WebSphere BI for FN nodes or message sets in your own message flows, or if you modified WebSphere BI for FN sample message flows, you must update your Toolkit environment and redeploy your message flows. The following resources have changed in this PTF: -> schema definitions: - /dniv311/admin/toolkit/dni.schemas.comibmdni.zip To update your Toolkit environment: - Delete the old WebSphere BI for FN provided message set projects in your workspace. - To reinstall the new versions of the Toolkit resources, follow the instructions provided in the section of 'Application Programming' that describes how to prepare the WebSphere Message Broker Toolkit workstation. *-----------------------------------------------------------------------------* * End of Activating * *-----------------------------------------------------------------------------* F. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM47697 BASE WEBSPHERE APPLICATION SERVER RMA SESSION HANDLING Formerly, when you used RMA filtering and your http session timed out you got the error "DNFL1004E No user Session available".RMA didn't handle correctly timed out http session. Now, RMA has been changed to handle timed out http session correctly. PM49193 BASE RESPONSE DNPA1110E TO THE RMA GUI ALSO SHOWS UP AS EVENT IN EVENT LOG Formerly, when the ASPs were not imported yet, and a login to the RMA was performed, message "DNPA1110E No ASP for service 'SWIFTNET:swift.fin'" was issued to the user. This behavior was ok, but in parallel, the same message was put to the event log. Such behavior contradicts to the WebSphere BI for FN conventions, as an event is formatted differently and is meant to inform the system administrator to allow him perform necessary actions. When looking at the user response of DNPA1110E, it includes both: an eventual action which needs to be performed by the RMA user (here, the response is ok), but additionally an eventual action for the System administrator (here, a - separate - event would be required). When looking at other DNPAxxxxE responses, some of them showed the same problem - some even only included eventual actions which needed to be performed by the system administrator. The user only should get an informational response to inform the system administrator, while in parallel, the system administrator should get an event which could be monitored. Now, the messages and codes information has been improved for DNPAxxxxE messages and different messages are used for events. PM49707 BASE THE "SERVICE" SELECTION LIST IN THE RMA GUI, CAN TAKE UP TO A MINUTE UNTIL THE LIST IS DISPLAYED Formerly, when initially accessing the "service" selection list in the RMA GUI, it could take up to a minute until the list was displayed. The problem was caused by the fact, that the ASP had to be accessed and searched in order to display all available services. Now, access to the "service" selection list has been improved. PM50792 BASE ERROR 404: SRVE0190E AT RMA LOGIN Formerly, when the user accessed the following URL "/rma/login/LoginPanel.jsp" at the RMA front end with user and password, the error: "Error 404: SRVE0190E: File not found: {0}" showed up. At the second login - independent of user and password given - error "Login Failed The username or password you entered was incorrect. [Login] [Home]" showed up. Now, this has been corrected. PM47966 BASE ERRONOUS MESSAGE SHOULD BACKED OUT IN SEPARAT QUEUE Formerly, when a correspondent sent a swift.fin!p authorization with the correct DNs but a typo in the BIC within the authorization RMA message, DNF_L_TR reported the following error event and CIN stopped processing: DNFL2010E (date time DNFSYSOU DNF_L_TR BIC 'BIC' is not or is incompletly configured). The erroneous message stayed in the DNF_L_TR queue. Now, in case of such a configuration error those messages will be transfered in a separat backout queue for a better handling. PM48082 BASE RMA QUERY COULD BE ABLE TO DELETE OR EDIT A WRONG QUERY Formerly, RMA was not able to delete/edit an invalid query which failed to send with wrong Master Bic of an T&T Bic8. Now, this behavior has been corrected. PM48059 BASE INPUT DATA TYPE MISMATCH WITHIN RMA TRACE Formerly, when enabling the trace for RMA, the following error could be found: "RETURN com.ibm.db2.jcc.b.SqlWarning: ... Input data type mismatch, see chained exceptions; will retry execution using describe input information. Please change application to use an input data type that matches the database column type as required by JDBC semantics. ERRORCODE=4461, SQLSTATE=01000 ". Now, this has been corrected. PM48067 BASE DESCRIPTION OF DNFL9515E, DATE AND TIME PARAMETERS OF RM EXPORT COMMAND SHOULD BE IMPROVED Formerly, error message DNFL9515E (Error during RM export processing; no export file can be created) was misleading and has to be corrected. Additionally, the description of the Date and Time parameter in the export command in the SA guide was misleading, too. Now, this has been improved. PM48501 BASE INCLUDE RM IN THE MESSAGE TEXT OF DNFL9430E Formerly, when message DNFL9430E was reworked in WebSphere BI for FN V3.1.1 to include the new parameters for the new functionality, the keyword RM was removed from the message text. Now, for usability reasons, the message text of DNFL9430E includes the keyword RM authorisation, like in WebSphere BI for FN V3.1.0. PM49273 BASE WRONG 'ACTION' IN DNFL1126E ERROR MESSAGE Formerly, when you tried to save a filter and you received the error event DNFL1126E (date time DNFSYSOU DNF_L_UI DATABASE ERROR OCCURRED DURING ACTION BREAKLOCK :DNFL2205E: ERROR DURING DATABASE HANDLER PROCESSING: FAILED TO EXECUTE STATEMENT...) the action BREAKLOCK was wrong in this message. Now, this has been corrected to action "save filter" in the message. PM50081 BASE IMPROVEMENT OF INTERNAL ERROR EVENT DNFL2155E Formerly, if an RMA query without request reference was received, DNFL2000E was displayed indicating an internal error. Now, if an RMA query without request reference is received, the message DNFL2155E will be displayed indicating an invalid RMA message. PM50178 BASE RMA FILTER FOR STALE BIC'S DOES NOT WORK AND THE QUERY LEADS TO A HIGH CPU TIME CONSUMPTION Formerly, if the filter for Stale BICs is applied, it could be that an empty relationship list is displayed and an increase of the CPU consumption occurs. Now, this has been corrected. PM47793 BASE PROVIDE PUBLIC VIEW TO RMA HISTORY DATA Formerly, even the RMA history data is positioned to be used as audit information, there was no public interface other than the UI provided to that data. Therefore, it was not possible to create any reports based on history data. It was also not possible to access history data after a "delete stale" user action. Now, public views for the RMA history data has been created and documented. PM51006 BASE MISSING UPDATE IN GRANT STATEMENT IN JOB DBGNT000 OR DBGNT001 Formerly, the UPDATE privilege for table DNI_UPREF had not been granted to the DNIvSGRP group. Now, missing privilege is granted. PM52815 BASE NULLPOINTER IN DNICZBAP, WHEN NON-WBIFN MESSAGE FLOWS ARE DEPLOYED IN THE SAME BROKER Formerly, when besides WebSphere BI for FN message flows there were other message flows (non-WebSphere BI for FN message flows) deployed in the same broker the BAP if called with parameter "-update new" got a nullpointer exception. Now, the BAP has been reworked and tolerates non-WebSphere BI for FN message flows. PM51632 BASE AFTER APPLYING UK71716 EXECUTION OF THE DNICZBAP PROGRAM NO LONGER PRODUCES A DNICZBAP.LOG FILE Formerly, after applying UK71716 the BAP no longer created the DNICZBAP.log file. Now, the BAP has been reworked and DNICZBAP.log file is created. PM51769 BASE AFTER THE MIGRATION TO V311 MSIF PROVIDED SCHEMA CAUSED SYNTAX ERRORS Formerly, when migrating to WebSphere BI for FN Version 3.1.1 MSIF the provided schema caused syntax errors. That is, the MQRFH2_ComIbmDni_Dnf.xsd schema caused the errors. Now, the MQRFH2_ComIbmDni_Dnf.xsd schema has been corrected. PM49967 BASE BROKER SHUTDOWN SHOULD BE ELIMINATED WHERE FEASIBLE DURING THE WBIFN MP MIGRATION AND MAINTENANCE TO REDUCE THE IMPACT Formerly, the message broker must be stopped before executing the installation program of Websphere BI for FN PTF. Now, a warning message will be showed in the dialog. Installer could continue the installation even if message broker was runnuing. PM53512 BASE OUT OF MEMORY DURING THE WBIFN 311 INSTALLATION Formerly, the out of memory problem might be occurred while installer executing the installation program. Now, the maximum heap size is increased for the installation program. PM54191 BASE DNICZBAP ENCOUNTERS ERROR WHEN DEPLOYING BAR FILES IN A MULTI-SERVER ENVIRONMENT Formerly, when deploying to a multiple broker server environment the BAP erroneously disconnected after the first broker was deployed. Now, this behaviour has been corrected. G. Other changes ---------------- - Formerly, the hover-help of the close icon in "select values" of filter was "Cancel". Now, the hover-help of close icon has been changed to "Close". - Formerly, a filter criterion that validity date is specified/not specified was not available. Now, a filter criterion that validity date is specified/not specified has been added. - Message updates: * Changed response messages: DNPA1107E-DNPA1111E,DNPA1150E,DNPA1151E,DNPA1153E,DNPA1154E * New event messages: DNPA1125E-DNPA1129E,DNPA1175E-DNPA1178E - Formerly, authorisations and queries can only be created from the Relationship List view. Now, authorisations and queries can also be created from the Conversation view. - Formerly, the service field was placed after the correspondent BIC field. Now, the service field is placed at the top. - Formerly, the Q&A status icon was placed aligned with the first authorisation for a relationship. Now, the Q&A status icon is placed vertically centered. - Formerly, dnfczmlc generated a useless CLI. The dnfczmlc did not query "-ct Dni% -co DNQ%" combination correctly. Therefore, dnfczmlc did not know if "-ou SYSOU -ct DniCinService -co DNQ_P_PRT -attr CommandQueue -val DNQ_P_RST" exists in system or not Now, this has been corrected. The useless CLI will not be generated. - Message updates: * Changed response message: DNFL9515E (due to APAR PM48067) ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++