============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2012 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 UK79973 for APAR PM37343 Driver level: 2302 = Date 2012-07-31 = ============================================================================== ============================================================================== ============================================================================== 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 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/dniv311/cus is used in examples. The deployment directory. The directory /var/dniv311/cus/depdata is used in examples. The name of the WebSphere BI for FN instance. The name INST1 is used in examples. The name of the organizational unit. Depending on the context, this might be SYSOU, DNFSYSOU, or the name of a business OU. The names of users, groups, files, and directories are the same as those used in WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization, SH12-6942-08. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PM64013 BASE DNIENHANCEDEXCEPTIONTOEVENT NODE CREATES UNNECCESARY EVENTS PM37343 BASE MANDATORY BASE PTF FOR BROKER 7 SUPPORT PM64164 BASE RMA APPROVAL PROCESS CONFIGURATION IS IGNORED PM62848 BASE ASP: UPDATE RELATIONSHIP MANAGMENT FLOWS TO IMPORT MORE ASP DATA PM62850 BASE ASP: UPDATE RM STORED PROCEDURE TO QUERY MORE ASP DATA PM63486 BASE DNI_ROLE_RESOLVED TABLE CAN BE INCOMPLETE PM67131 BASE RMA FILTER CRITERIA DOES NOT WORK PROPERLY SEARCHING FOR Q&A STATUS Additional functional changes: - The BAP has been enhanced to support WebSphere Message Broker V7. - Enhancement of filter for Own BIC and Correspondent BIC Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Concepts and Components - Messages and Codes - System Administration - Application Programming The following modules have been changed: /dniv311/admin/data/DNFCOMMON.xml /dniv311/admin/data/DNICOMMON.xml /dniv311/admin/data/DNFRMA.xml /dniv311/admin/data/DNFRMR.xml /dniv311/admin/data/dnfczlcr.ddl /dniv311/admin/data/dnfczlrr.ddl /dniv311/admin/data/dnicdi02.ddl /dniv311/admin/data/dnicdico.ddl /dniv311/admin/data/dniczdlq.mq /dniv311/admin/data/dniczrlq.mq /dniv311/admin/data/dnixzr02.def /dniv311/admin/data/dnixzs02.def /dniv311/admin/data/dnfczcat.cli /dniv311/admin/data/dnfczcoy.cli /dniv311/admin/data/dnfczcah.lst /dniv311/admin/appsrv/res/dnf.rma.web.ear /dniv311/admin/toolkit/com.ibm.dni.api.jar /dniv311/run/bin/dniczbap /dniv311/run/data/dnfczcat.cli /dniv311/run/data/dnfczcoy.cli /dniv311/run/data/dnfczcah.lst /dniv311/run/classes/com.ibm.dni.msgstds.domain.DNIFIN.xml /dniv311/run/classes/dni.msgstds.impl.jar /dniv311/run/classes/dniczbap.jar /dniv311/run/classes/dnipcfg.jar /dniv311/run/classes/dnp.aspal.api.jar /dniv311/run/classes/dnp.aspal.impl.jar /dniv311/run/classes/dnp.jab.jar /dniv311/run/flows/DNF_BACKOUT.bar /dniv311/run/flows/DNF_RM.bar /dniv311/run/flows/DNF_R_EXP.bar /dniv311/run/flows/DNF_V_ADM.bar /dniv311/run/flows/DNI_AGATHER.bar /dniv311/run/flows/DNI_DEPLOY.bar /dniv311/run/flows/DNI_RCP.bar /dniv311/run/flows/DNI_RSP.bar /dniv311/run/flows/DNI_R_AUDIT.bar /dniv311/run/flows/DNI_SAMPLE.bar /dniv311/run/flows/DNI_SECADM.bar /dniv311/run/flows/DNI_SYSADM.bar /dniv311/run/flows/DNI_SYSOP.bar /dniv311/run/flows/DNI_TIMER.bar /dniv311/run/jplugin/dnf.asp.imp.jar /dniv311/run/lib/libdnipjni64.a /dniv311/run/lil64/dnicin64.lil /dniv311/run/samples/dniczpro.prf The following modules are new: /dniv311/admin/data/dniczm08.mq /dniv311/admin/data/dnixzm08.def /dniv311/admin/data/dnicdi03.ddl /dniv311/admin/data/dnfczlm4.ddl /dniv311/admin/data/dnfczl01.ddl /dniv311/admin/data/dnfczl2g.ddl /dniv311/admin/data/dnicdrrc.ddl /dniv311/admin/data/dnicdrrd.ddl /dniv311/admin/data/dnicdrrr.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 is required before you plan to migrate your WebSphere Message Broker V6.1 to Broker V7. The migration is described in WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization. Please also check the System Information for the prerequisites for Message Broker V7. Download the System Information from: http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21496514 This PTF requires the following PTFs: - UK77970 for APAR PM55951 (Base 3.1.1.5, DNICZBAP THROWS NULLPOINTEREXCEPTION DURING RECUSTOMIZATION) 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) - WebSphere Application Server operator (uwaso1) - First WebSphere BI for FN system configuration administrator (sa1) 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/_UK79973_temp.cdd > supplement cdd/_UK79973_temp.cdd cdd/_UK79973.cdd Open the supplemented CDD and search for each occurrence of the string value=" and specify the appropriate placeholder values. The new placeholder DNIvTPFX will appear. > import cdd/_UK79973.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: - MQ * new TOPIC('DNIvTPFX.DNI.EVENTID') introduced * new TOPIC('DNIvTPFX.DNI.TYPECODE') introduced - MQAUT * add group authority to DNIvMQMN.DNIvTPFX.DNI.EVENTID * add group authority to DNIvMQMN.DNIvTPFX.DNI.TYPECODE - CFGPF (if SVB DNFRMA is assigned) * instructions and files required to update the WebSphere BI for FN enterprise applications running in the application server - DB * update RM filtering stored procedure - DBGNT * grant RM filtering stored procedure - DBCNT * add missing entries to table DNI_ROLE_RESOLVED 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. 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 3. Create a temporary directory where dnfczmlc.sh stores the CLI command files which will contain the configuration migration statements. 4. 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_3_sa_rem_co_com.cli 2. dnfczmlc_3_sa_rem_co_dep.cli 3. dnfczmlc_4_sa_rem_ct_com.cli 4. dnfczmlc_4_sa_rem_ct_dep.cli 5. dnfczmlc_5_sa_cre_ct_com.cli 6. dnfczmlc_5_sa_cre_ct_dep.cli 5. 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 2. This PTF changes the following configuration entities: - removes the attribute 'NoAuthentication' from CO 'DnfExceptMsgAttr' - removes the attribute 'NoAuthentication' from CT 'DnfExceptMsgAttr' - adds the attribute 'MsgValRcvExceptionQueue' to CT 'DnfExceptionOptionSet' - adds the attribute 'MsgValRcvExceptionQMgr' to CT 'DnfExceptionOptionSet' 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, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration" 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 following directories with your runtime systems: /dniv311/run 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. following exception: - do not execute the instructions provided for resource class CFGPF now; you will use them in step E11.3. E7. Additional 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. Note: After all message flows have been deployed, you can check the driver levels of the flows, i.e. the bar files provided with this PTF. The driver level is listed in the header of this readme. To determine the levels of all deployed message flows, you can enter the following command: dniczbap -cmd list The output contains messages that indicate the level of each message flow, for example: DNIZ1466I Flow name1: DNF_ILS_ACK_9213, where 9213 shows the driver level of this flow. 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 35 MB of free space. 3. Issue the following command: dniczbap -cmd prepare -update new -deploy 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_3_sa_rem_co_com.cli by the first SA (sa1) - dnfczmlc_3_sa_rem_co_dep.cli by the second SA (sa2) - dnfczmlc_4_sa_rem_ct_com.cli by the first SA (sa1) - dnfczmlc_4_sa_rem_ct_dep.cli by the second SA (sa2) - dnfczmlc_5_sa_cre_ct_com.cli by the first SA (sa1) - dnfczmlc_5_sa_cre_ct_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 D3.3 and execute the generated CLI command files by entering the following command: dnicli -s -ou SYSOU -cft | tee -a UK79973_cli.log where: DNI_SYSADM for files executed by the system configuration administrators, abbreviated as SA The CLI command file name, for example dnfczmlc_3_sa_rem_co_com.cli. E11. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ 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 ----------------------------------------- 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". 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 been changed in this PTF: -> API nodes: - DniEnhancedExceptionToEvent This PTF contains the updated WebSphere BI for FN Eclipse plug-in Additionally this PTF contains the updated WebSphere BI for FN Eclipse plug-in com.ibm.dni.api.jar that makes it compatible with Toolkit V7. To update your Toolkit environment: - If you modified samples that were provided by WebSphere BI for FN and want to keep your modifications, rename the projects. However, these saved projects will not be updated. - Delete the old WebSphere BI for FN provided projects in your workspace. - To reinstall the new versions of the Toolkit resources, follow the instructions provided in the section of 'Application Programming' that describe how to prepare the WebSphere Message Broker Toolkit workstation. - Clean all projects and redeploy the message flows that you built using nodes that were provided by WebSphere BI for FN. *-----------------------------------------------------------------------------* * End of Activating * *-----------------------------------------------------------------------------* F. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM64013 Base DNIENHANCEDEXCEPTIONTOEVENT NODE CREATES UNNECCESARY EVENTS Formerly, in special error situations the DniEnhancedExceptionToEvent Node, used in almost all WebSphere BI for FN message flows, created obsolete events with an empty parameter list. For example: "DNIE4497E 11/28/11 1:57:35 PM HYVEDEM0 DNF_ILC_FIN Exception without valid message ID; exception data: message catalog='', error number='', parameters='', component=''." Now, these obsolete events are suppressed. Some flows used to issue event DNFR7499E, now DNIE4497E is issued instead. PM37343 Base MANDATORY BASE PTF FOR BROKER 7 SUPPORT This WebSphere BI for FN V3.1.1 Base PTF provides the necessary fixes to support WebSphere Message Broker Version 7. PM64164 Base RMA APPROVAL PROCESS CONFIGURATION IS IGNORED. Formerly, if the name of a business OU follows SYSOU when sorted alphabetically, the configuration for the RMA approval process was ignored and the default values were used instead (Approval Steps = 1, Approval User Restriction = NotPrevious). Now, the RMA approval process follows the configuration. PM62848 BASE ASP: UPDATE RELATIONSHIP MANAGMENT FLOWS TO IMPORT MORE ASP DATA Formerly, the RM filtering stored procedure did not query the ASP data to determine if a FIN MT requires RM filtering or not. Now, the RM filtering stored procedure examines ASP data to determine if a FIN MT requires RM filtering. PM62850 BASE ASP: UPDATE RM STORED PROCEDURE TO QUERY MORE ASP DATA Formerly, the RM filtering stored procedure did not query the ASP data to determine if a FIN MT requires RM filtering or not. Now, the RM filtering stored procedure examines ASP data to determine if a FIN MT requires RM filtering. PM63486 BASE DNI_ROLE_RESOLVED TABLE CAN BE INCOMPLETE Formerly, after creation of new OUs, the DNI_ROLE_RESOLVED table was incompletly populated. Some required rows were not inserted into this table. The effect to the user was that the user did not see the new OUs in MER, although he had the required roles. Now, on creation of a OU all required rows are inserted into table DNI_ROLE_RESOLVED. Rows missing for existing OUs are added. PM67131 Base RMA FILTER CRITERIA DOES NOT WORK PROPERLY SEARCHING FOR Q&A STATUS Formerly, when searching RMA filter criteria for Q&A Status "Action Required" the resulting hits are not shown as number of hits, but only the the total number is shown. Now, the number of hits is shown. G. Other changes ---------------- - Message updates: * New response messages: DNIZ1324E, DNIZ1325E, DNIZ1326I, DNIZ1327I, DNIZ1328E - The BAP has been enhanced to support WebSphere Message Broker V7. - The sample profile dniczpro.prf has been enhanced: * It now ensures that Java is available in the PATH environment * The environment variable DNI_QMGR_BAP is no longer needed and has been removed. * Editorial changes have been done to get it more readable - The filter for Own BIC and Correspondent BIC has been enhanced. * Now, BICs can be filtered by institution code, country code or location code. H. Known issues --------------- WebSphere Message Broker migration from Version 6 to Version 7 may cause the WebSphere BI for FN CPU load of the services that process FIN, InterAct, and FileAct transfers to increase by up to 15%, the actual amount depending on how these services are used. Thus, it is likely that these services will experience slightly decreased throughput. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++