============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2013 All Rights Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ============================================================================== ============================================================================== README for IBM(R) WebSphere(R) Business Integration for Financial Networks for Multiplatforms V3.1.1 Base PTF UK95605 for APAR PM90825 Driver level: 3314 Date 2013-08-16 ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Installation E APAR details F Other changes G Known issues A. About this document ---------------------- Only the online version of this readme document is current. Before you install the corresponding PTF, download the latest version from: http://www.ibm.com/software/integration/wbifn/support Download the latest version of the WebSphere BI for FN product documentation from: http://www.ibm.com/software/integration/wbifn/library The structure of WebSphere BI for FN readme documents is identical for all PTFs. Sections that are not applicable are left blank. If you install more than one PTF at a time, combine the readme documents by merging the contents of each section. During the installation phase of this PTF 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: PM83078 Base OPTIMIZATION OF PERFORMANCE CRITICAL POINTS IN RMA PM89234 Base DNIVMQCHL ALLOWED CHARACTERS: ALLOW THE UNDERSCORE CHARACTER AS A VALID WBIFN CUSTOMIZATION PLACEHOLDER PM92778 Base FIX SPELLING ERRORS IN BIP3001I MESSAGE COMING FROM WBIFN PM92779 Base PERFORMANCE IS NOT GOOD WHEN CREATING A NEW MER ROLE VIA A&O PM90825 Base SWIFT SR2013: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION PM91847 Base INCOMING MESSAGE FAILS WHEN TAG 108 IS BLANK PM93171 Base AVOID UNNECESSARY SQL STATEMENTS WHEN A CT IS DEPLOYED PM93008 Base JAVADOC FIX FOR SECURITY PSIRT ADVISORY 1025 PM90722 Base Import of Bank Directory Plus and BIC Directory data added Functional changes: - S.W.I.F.T. Standard Release 2013 (SR2013) changes for FIN This PTF contains the message definition set 'fin2013' for S.W.I.F.T. Standard Release 2013 (SR2013) changes. The S.W.I.F.T. SR2013 live date is currently planned for 17 November 2013. You can install this PTF before this date and continue to process messages according to the SR2012 message definition set. The SR2013 message definition set is automatically activated on the planned live date. How to activate the message definition set 'fin2013' before its live date in a test environment is described in this readme in section D8.2. WebSphere MB related activities, Activation of the SR2013 message definition set. - S.W.I.F.T. Standard Release 2013 (SR2013) changes for MX This PTF contains the message definition set 'mx2013' for S.W.I.F.T. Standard Release 2013 (SR2013) changes. The S.W.I.F.T. SR2013 live date is currently planned for 17 November 2013. You can install this PTF before this date and continue to process messages according to the SR2012 message definition set. The SR2013 message definition set is automatically activated on the planned live date. How to activate the message definition set 'mx2013' before its live date in a test environment is described in this readme in section D8.2. WebSphere MB related activities, Activation of the SR2013 message definition set. Additional functional changes: - Base API node ComIbmDniMwhUpdate changed - The size of the WebHome application was significantly reduced. Documentation updates: The following manuals have been changed: - Concepts and Components - System Administration - Planning, Installation, and Customization - Messages and Codes The following modules have been changed: /dniv311/admin/appsrv/res/dnf.rma.web.ear /dniv311/admin/appsrv/res/dni.home.ear /dniv311/admin/appsrv/res/dnp.ado.web.ear /dniv311/admin/data/DNICOMMON.xml /dniv311/admin/data/DNFRMA.xml /dniv311/admin/data/DNIWEBHOME.xml /dniv311/admin/data/DNPAO.xml /dniv311/admin/data/dni.xml /dniv311/admin/data/dnicdcts.ddl /dniv311/admin/data/dnicdcut.ddl /dniv311/admin/toolkit/com.ibm.dni.api.jar /dniv311/admin/toolkit/dni.schemas.comibmdni.zip /dniv311/admin/toolkit/dni.schemas.swiftFin2010.zip /dniv311/admin/toolkit/dni.schemas.swiftFin2011.zip /dniv311/admin/toolkit/dni.schemas.swiftFin2012.zip /dniv311/run/classes/com.ibm.dni.msgstds.ibmapi.CommonMessageDomainService.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2012.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.mx2012.xml /dniv311/run/classes/dnicdcfg.jar /dniv311/run/classes/dni.msgstds.api.jar /dniv311/run/classes/dni.msgstds.impl.jar /dniv311/run/classes/dnicvcks.jar /dniv311/run/classes/dnicvcks_swiftmx.jar /dniv311/run/classes/dnicvcks_sfmtxml10.jar /dniv311/run/classes/dnicvcks_sfmtxml11.jar /dniv311/run/classes/dnicvcks_sfmtxml12.jar /dniv311/run/classes/dnicvrls_sfmtxml10.jar /dniv311/run/classes/dnicvrls_sfmtxml11.jar /dniv311/run/classes/dnicvrls_sfmtxml12.jar /dniv311/run/classes/dnicvrls_mx_all2012.jar /dniv311/run/classes/dnicvrls_mx_bulkpmt21.jar /dniv311/run/classes/dnicvrls_mx_cashrep50.jar /dniv311/run/classes/dnicvrls_mx_clearing20.jar /dniv311/run/classes/dnicvrls_mx_collmgmt20.jar /dniv311/run/classes/dnicvrls_mx_corpact10.jar /dniv311/run/classes/dnicvrls_mx_corpact12.jar /dniv311/run/classes/dnicvrls_mx_einvoice10.jar /dniv311/run/classes/dnicvrls_mx_proxyvote11.jar /dniv311/run/classes/dnicvrls_mx_proxyvote12.jar /dniv311/run/classes/dnicvrls_mx_swiftrem20.jar /dniv311/run/classes/dnicvrls_mx_transrep10.jar /dniv311/run/classes/dnicvrls_seni1.jar /dniv311/run/classes/dnicvrls_sfunds40.jar /dniv311/run/classes/dnicvrls_sfunds41.jar /dniv311/run/classes/dnicvrls_sfunds42.jar /dniv311/run/classes/dnicvrls_sfunds43.jar /dniv311/run/classes/dnicvrls_sfunds44.jar /dniv311/run/classes/dnicvrls_ssys63.jar /dniv311/run/classes/dnicvrls_ssys70.jar /dniv311/run/classes/dnprdu.jar /dniv311/run/classes/dnp.refdata.api.jar /dniv311/run/doc/dni.msgstds.api.doc.zip /dniv311/run/flows/DNI_RCP.bar /dniv311/run/flows/DNI_SYSADM.bar /dniv311/run/flows/DNI_SECADM.bar /dniv311/run/msg/DNFR_Msg.properties /dniv311/run/msg/DNIL_Msg.properties /dniv311/run/msg/DNIP_Msg.properties /dniv311/run/msg/DNIX_Msg.properties /dniv311/run/msg/DNIY_Msg.properties /dniv311/run/msg/DNPO_Msg.properties /dniv311/run/msg/DNPR_Msg.properties /dniv311/run/msg/dnpcomsg.cat /dniv311/run/msg/dnpcrmsg.cat /dniv311/run/msg/dnicymsg.cat /dniv311/run/res/dnpcomsg.xml /dniv311/run/res/dnpcrmsg.xml /dniv311/run/res/dnicymsg.xml The following are new modules: /dniv311/admin/data/dnicdi06.ddl /dniv311/admin/data/dnicdi46.ddl /dniv311/admin/data/dnicdmm3.ddl /dniv311/admin/data/dnicdm04.ddl /dniv311/admin/data/dnicdm6g.ddl /dniv311/admin/data/dnicdp02.ddl /dniv311/admin/toolkit/dni.schemas.swiftFin2013.zip /dniv311/run/classes/com.ibm.dni.msgstds.defset.corpact13.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2013.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.mx2013.xml /dniv311/run/classes/dnicvcks_sfmtxml13.jar /dniv311/run/classes/dnicvrls_sfmtxml13.jar /dniv311/run/classes/dnicvrls_mx_corpact13.jar /dniv311/run/classes/dnicvrls_mx_all2013.jar C. Planning ----------- C1. Checks to be done >>BEFORE<< installing a new PTF ----------------------------------------------------- 1. Ensure that all previously prepared deployment instructions were carried out. 2. Ensure that all previous CDD changes were implemented using the CDP. To check this, log on to AIX on the customization system as a customizer (ucust1) and enter the following command on your customization system: /dniv311/admin/bin/dnicdpst -i -cdefs where The name of the WebSphere BI for FN instance The name of the customization definitions directory as specified in the CDP ini file, for example: /var/dni_03_01/cus/defs If the response to this command indicates that a customization operation is still pending and it was carried out in: - Customization mode (dnicdp), implement the pending operation before continuing. - Migration mode (dnicdpm): - Ensure that you have not yet shared the files contained in this or any other PTF as described in section D5 step 2. - Implement the pending operation before continuing. 3. Until the migration for this PTF has been completely finished, ensure that no changes are made to the currently implemented CDD. 4. Ensure that all configuration administration changes have been deployed. To check this, enter the following commands: dnicli -s DNI_SYSADM -ou SYSOU > list -ou % -qo amorz > list -cos % -qo amorz > list -ct % -qo amorz Each list command should result in 'No [OU/COS/CT] match search criteria'. 5. Ensure that all security administration changes have been approved. To check this, enter the following commands for each OU: dnicli -s DNI_SECADM -ou > list -ro % -qo mor [only for SYSOU] > list -user % -qo mor Each list command should result in 'No roles found that match specified criteria'. C2. Prerequisite and supersede information ------------------------------------------ This PTF requires the following PTFs: - UK94069 for APAR PM84617 (Base 3.1.1.12, IMPROVE ADMINISTRATION AND OPERATION FACILITY SECURITY) This PTF should be installed together with: - UK95620 for APAR PM90826 (MM 3.1.1.10, SWIFT SR2013: MESSAGE MANAGEMENT UPDATES FOR SWIFT SR2013 CHANGES) C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - DB2 administrator (udb2adm1) - WebSphere MB application developer (uwmbad1) - WebSphere MB administrator (uwmba1) - WebSphere Application Server operator (uwaso1) - WebSphere Application Server administrator (uwasa1) - First WebSphere BI for FN system configuration administrator (sa1) - Second WebSphere BI for FN system configuration administrator (sa2) D. Installation --------------- D1. Stopping all sessions and services you use ---------------------------------------------- Stop all sessions and services, for example: - Stop all applications that send requests to WebSphere BI for FN. - Log out SIPN FIN LTs. - Close MSIF SnF input and output channels. - Release SWIFTNet SnF queues. - Stop the MSIF Message Transfer service. - Stop the Enhanced InterAct service. - Close all dnicli sessions. For further information, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration". D2. Stopping all application servers ------------------------------------ Stop all application servers. D3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- Stop all WebSphere BI for FN message brokers. D4. Backing up your system -------------------------- We recommend to backup your AIX LPAR so that in case of migration issues you can revert to your previous system setup and continue to process workload. D5. Installing PTF by InstallAnywhere ------------------------------------- 1. Install this PTF using IAW based on the chapter "Installing WebSphere BI for FN" in WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization, SH12-6942. Please be aware of the directory containing the installation data for this PTF has changed compared to the directory documented in this chapter, use the path Disk1/InstData/NoVM instead of Disk1/InstData/VM. 2. Ensure that the group ownership of the /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 3. Set the group ownership of the runtime directories and its files to group dnilpp. To do this, enter the following command in AIX: chgrp -R dnilpp /dniv311/run D6. Steps on a customization system ----------------------------------- To update your current definition directory and the customized administrative scripts, and to create deployment instructions and vehicles: 1. Log on to AIX on the customization system as a customizer (ucust1). 2. Change to the customization directory: cd 3. Run your customization profile: . ./dnicus_ 4. Start the CDP in migration mode and use the following commands to migrate customization data: dnicdpm -i > export cdd/_UK95605.cdd > import cdd/_UK95605.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 * add tablespace DNIBICI * remove tablespace DNIBIC * alter table DNI_BIC_INFO: column BIC_RECORD_KEY changed from char(8) to varchar(12) column BANK_PARENT_CODE changed from char(4) to varchar(12) column LOCATION changed from varchar(70) to varchar(105) column POB_LOCATION changed from varchar(70) to varchar(105) columns CTY_CODE and CTY_NAME now nullable column CITY_HEADING now nullable column ACTIVATION_DATE added * alter view DNI_BIC: column ACTIVATION_DATE added * add indices DNIY1BIC, DNIY2BIC, DNIY3BIC ON DNI_BIC_INFO * remove indices DNIX1BIC, DNIX2BIC, DNIX3BIC FROM DNI_BIC_INFO - DBGNT * grant SELECT permission for table DNI_BIC_INFO to group DNIvSGRP * grant INSERT,SELECT,UPDATE,DELETE permission for table DNI_BIC_INFO to group DNIvRGRP * grant INSERT,SELECT,UPDATE,DELETE permission for view DNI_BIC to group DNIvRGRP - DBSP * Replace procedure body of stored procedures - CFGPF (if SVB DNPAO or DNFRMA is assigned) * create 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 step D7. 5. Implement the customization definition data and quit the CDP session: > implement When the message "DNIZ9013I: Current Definition file already exists." is displayed enter 'y' to continue. > quit D7. Following the deployment instructions created in step D6 ------------------------------------------------------------ Follow the deployment instructions that were created in step D6 with the following exceptions: - do not execute the instructions provided for resource class CFGPF now; you will use them in step D13.3. Please be noticed, follow the instructions in resource class DBSP to modify the flag in Vehicle #2 for migrating WBI-FN system. D8. Additional activities ------------------------- D8.1. DB2 related activities - - - - - - - - - - - - - - - NOT APPLICABLE. D8.2. WebSphere MB related activities - - - - - - - - - - - - - - - - - - - 1. Update the WebSphere MB environment for SR2013 changes for FIN: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - If you have configured the CLASSPATH environment variable in the broker configuration as described in "Planning, Installation and Customization" the new message definition set libraries: dniv311/run/classes/dnicvrls_sfmtxml13.jar dniv311/run/classes/dnicvcks_sfmtxml13.jar and the new configuration file: dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2013.xml are automatically recognized as soon as you restart the message broker. Activation of the SR2013 message definition set for FIN: Note for production environment: The S.W.I.F.T. SR2013 live date is currently planned for 17 November 2013. Before this date the new message definition set should not be activated on a production environment. The activation date for the message definition set for SR2013 is set in file: dniv311/run/classes/com.ibm.dni.msgstds.defset.fin2013.xml The activation date in this file is set to the planned S.W.I.F.T. SR2013 live date, 17 November 2013. You should not change this file in a production environment. Note for test environment: To activate the message definition set for SR2013 in a business OU for the test environment refer to section D12.3. in this readme. 2. Update the WebSphere MB environment for SR2013 changes for MX: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - If you have configured the CLASSPATH environment variable in the broker configuration as described in "Planning, Installation and Customization" the new message definition set libraries: /dniv311/run/classes/dnicvrls_mx_all2013.jar /dniv311/run/classes/dnicvrls_mx_corpact13.jar and the new configuration file: /dniv311/run/classes/com.ibm.dni.msgstds.defset.mx2013.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.corpact13.xml are automatically recognized as soon as you restart the message broker. Activation of the SR2013 message definition set for MX: Note for production environment: The S.W.I.F.T. SR2013 live date is currently planned for 17 November 2013. Before this date the new message definition set should not be activated on a production environment. The activation date for the message definition sets for SR2013 is set in files: /dniv311/run/classes/com.ibm.dni.msgstds.defset.mx2013.xml /dniv311/run/classes/com.ibm.dni.msgstds.defset.corpact13.xml The activation date in these files is set to the planned S.W.I.F.T. SR2013 live date, 17 November 2013. You should not change this file in a production environment. Note for test environment: To activate the message definition set for SR2013 in a business OU for the test environment refer to section D12.4. in this readme. D8.3. WebSphere MQ related activities - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D9. Restarting all WebSphere BI for FN message brokers ------------------------------------------------------ Restart all WebSphere BI for FN message brokers. D10. Customize BAR files when using mqsideploy or the Toolkit to deploy them --------------------------------------------------------------------------- Customize BAR files ------------------- Perform this step only if you use mqsideploy or the Toolkit to deploy broker archive (BAR) files manually. If you use the BAP (dniczbap) to automatically deploy the BAR files, skip this step and later deploy the BAR files directly as described in step D11.2.2. If you are unsure which method to use, use the same method that you used when you initially created your instance as described in "Planning, Installation, and Customization". To customize the BAR files for manual deployment: 1. On the runtime system on which you use the BAP, log on to AIX as the WebSphere MB administrator (for example, uwmba1) and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a temporary directory to which you have read and write access and that has at least 35MB of free space. This is the directory in which dniczbap will store the customized BAR files. 3. The component to which the BAP deploys message flows depends on which version of WebSphere Message Broker is used: - For V6.1, the BAP deploys message flows to the configuration manager. - For V7, the BAP deploys message flows to the broker. Sometimes, the BAP cannot connect directly to this component, for example, when you use Broker V6.1 and the configuration manager is located on Windows. How you customize the BAR files depends on whether the BAP can connect to this component: a. If a connection is not possible, issue the following command to customize all BAR files: dniczbap -cmd prepare -all -dir where represents the output directory created in step 2. b. If a connection is possible, ensure that the configuration manager (if using Broker V6) and the brokers are running, and that no flows or execution groups are stopped. Issue the following command to cause the BAP to identify the BAR files that are to be updated: dniczbap -cmd prepare -update new -dir where represents the output directory created in step 2. Regardless of which method (a or b) you use, each of the customized BAR files in the output directory has a name of the form: ....bar where The name of your instance. The name of the broker to which the BAR file is to be deployed. The name of the execution group to which the BAR file is to be deployed. The name of the BAR file as provided by WebSphere BI for FN. 4. If you performed step 3.a, identify the BAR files that are listed in section "B. Summary of changes" and delete all other BAR files from the output directory. 5. Transfer, in binary mode, the customized BAR files in the output directory to the Toolkit or to the system on which you will later issue the mqsideploy command. 6. If you will use the Toolkit to deploy the message flows, import the customized BAR files. D11. Redeploy updated BAR files ------------------------------- Deploying the WebSphere BI for FN BAR files that are delivered in this PTF updates the message flows that run in the broker. For a list of flows contained in each BAR file, refer to "Planning execution groups" section of "Planning, Installation, and Customization". Each WebSphere BI for FN message flow has a suffix that represents its version. For example, the flow DNI_SYSADM_1141 has the version 1141. The version of a flow corresponds to the number of the PTF that most recently updated it. Refer to the header of this readme to determine the PTF number of this PTF. To deploy BAR files, you must have the access rights of the WebSphere MB administrator (uwmba1). D11.1 Deploy new message flows - - - - - - - - - - - - - - - NOT APPLICABLE. D11.2 Update existing message flows - - - - - - - - - - - - - - - - - - If you already prepared the customized BAR files as described in step D10, proceed with step D11.2.1; otherwise, proceed with step D11.2.2 D11.2.1 Deploying the BAR files customized in step D10 - - - - - - - - - - - - - - - - - - - - - - - - - - - - Use the Toolkit or the mqsideploy command to manually deploy the BAR files. Remove the old versions of the message flows that have been updated by the BAR files you deployed. If you neglect to do this, two different versions of the flows will run simultaneously with unpredictable results. D11.2.2 Deploying BAR files when step D10 was not performed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Use the BAP (dniczbap) to customize and automatically deploy the BAR files: 1. Ensure that: - The configuration manager is running (applies only for Broker V6.1) - The brokers are running - No flows or execution groups are stopped. Otherwise, old flow levels might not be deleted during the BAP update operation. 2. On the runtime system where you use the BAP, log on to AIX as the WebSphere MB administrator (for example, uwmba1) and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 3. Ensure that you have at least 35 MB of free space in the current directory. 4. Issue the following command: dniczbap -cmd prepare -update new -deploy 5. Issue the following command to verify that all previous versions of the updated message flows were removed successfully: dniczbap -cmd check The result should be: DNIZ1314I: No problems detected. If you receive the message DNIZ1313E follow the instructions provided in the user response to correct the problem. D11.3 Activating WebSphere BI for FN accounting - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D12. Migrating configuration data --------------------------------- D12.1. Generating configuration data migration scripts - - - - - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D12.2 Executing the migration scripts - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D12.3 Activate the message definition set for SR2013 for FIN - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Activate the message definition set for SR2013 in a business OU for the test environment: Note for test environment: To activate the message definition set for SR2013 in a business OU for the test environment: 1. On the runtime system, log on to AIX with the user ID of WebSphere BI for FN system configuration administrator (sa1 or sa2). 2. Execute your profile for the runtime environment, e.g.: . /var/dni_03_01/run/dniprofile 3. Start the command line interface (CLI): dnicli -ou SYSOU -s DNI_SYSADM 4. Enter the following commands in your CLI session to set the SR2013 message definition set attribute value and commit the change: add -ou -ct DniMsgDomain -co DNIFIN -attr TestMsgDefSet -val fin2013 com -ou 5. Log on to AIX with the user ID of another WebSphere BI for FN system configuration administrator. 6. Execute your profile for the runtime environment, e.g.: . /var/dni_03_01/run/dniprofile 7. Start the command line interface (CLI): dnicli -ou SYSOU -s DNI_SYSADM 8. Enter the following commands in your CLI session to approve and deploy the changes: app -ou dep -ou Note: In the previous steps, replace with the business OU for which you want to activate the SR2013 message definition set. D12.4. Activate the message definition set for SR2013 for MX - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Activate the message definition set for SR2013 in a business OU for the test environment: Note for test environment: To activate the message definition set for SR2013 in a business OU for the test environment: 1. On the runtime system, log on to AIX with the user ID of WebSphere BI for FN system configuration administrator (sa1 or sa2). 2. Execute your profile for the runtime environment, e.g.: . /var/dni_03_01/run/dniprofile 3. Start the command line interface (CLI): dnicli -ou SYSOU -s DNI_SYSADM 4. Enter the following commands in your CLI session to set the SR2013 message definition set attribute value and commit the change: add -ou -ct DniMsgDomain -co DNIMX -attr TestMsgDefSet -val mx2013 com -ou 5. Log on to AIX with the user ID of another WebSphere BI for FN system configuration administrator. 6. Execute your profile for the runtime environment, e.g.: . /var/dni_03_01/run/dniprofile 7. Start the command line interface (CLI): dnicli -ou SYSOU -s DNI_SYSADM 8. Enter the following commands in your CLI session to approve and deploy the changes: app -ou dep -ou Note: In the previous steps, replace with the business OU for which you want to activate the SR2013 message definition set. D13. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ D13.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. D13.2. Update the WebSphere Application Server environment - - - - - - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D13.3. Migrating the enterprise application - - - - - - - - - - - - - - - - - - - - - - If the instructions created in step D6 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. D14. Restarting all sessions and services ----------------------------------------- Restart all of the sessions and services that you use. How to do this depends on which WebSphere BI for FN features you use. For example: - Log in SIPN FIN LTs. - Subscribe MSIF to SAGs to enable file transfer and session monitoring. - Start the MSIF Message Transfer service. - Start the Enhanced InterAct service. - Acquire SWIFTNet SnF queues. - Open MSIF SnF input and output channels. - Start the applications that send requests to WebSphere BI for FN. For further information, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration". D15. Updating the Toolkit development environment ------------------------------------------------- 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: -> API nodes: - DniMwhUpdate -> schema definitions: - /dniv311/admin/toolkit/dni.schemas.comibmdni.zip - /dniv311/admin/toolkit/dni.schemas.swiftFin2010.zip - /dniv311/admin/toolkit/dni.schemas.swiftFin2011.zip - /dniv311/admin/toolkit/dni.schemas.swiftFin2012.zip - /dniv311/admin/toolkit/dni.schemas.swiftFin2013.zip 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. - 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. - Clean all projects and redeploy the message flows that you built using nodes that were provided by WebSphere BI for FN. D16. Verifying your Installation -------------------------------- This PTF contains updated versions of the RMA and AO Facility enterprise applications. To verify that an enterprise application is the most current version: 1. Log-on to the enterprise application. 2. Click the 'About' link in the upper right corner. A dialog box opens. 3. In the dialog box, locate the build number. Compare it to the driver level specified in the header of this readme file. Both numbers should be identical. This PTF has also modified Java database routines. To verify the installation of the Java database routines follow the steps described in Planning, Installation, and Customization guide, part "Verifying your customized installation", chapter "Verifying the installation of the Java database routines". Especially verify that the level of class file DniConfiguration.class is 'version 1.46.3.12'. *------------------------------------------------------------------------------* * End of Installation * *------------------------------------------------------------------------------* E. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM83078 Base OPTIMIZATION OF PERFORMANCE CRITICAL POINTS IN RMA Formerly, when the RMA was used with IE, the performance in certain situations was unacceptable. Now, this has been fixed. PM89234 Base DNIVMQCHL ALLOWED CHARACTERS: ALLOW THE UNDERSCORE CHARACTER AS A VALID WBIFN CUSTOMIZATION PLACEHOLDER Formerly, the underscore character (_) was not allowed to be used for placeholder DNIvMQCHL. Now, all characters that are valid for an WebSphere MQ channel name can be used for placeholder DNIvMQCHL. This includes the underscore character (_), the forward slash (/), and the percentage sign (%). PM92778 Base FIX SPELLING ERRORS IN BIP3001I MESSAGE COMING FROM WBIFN Formerly, a misspelled BIP3001I message has been logged in certain situations. Now, the spelling has been corrected. PM92779 Base PERFORMANCE IS NOT GOOD WHEN CREATING A NEW MER ROLE VIA A&O Formerly, when the AO facility was used with IE to create a new MER role, the performance in certain situations was unacceptable. Now, this has been fixed. PM90825 Base SWIFT SR2013: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION. This PTF delivers support for checking FIN messages according to the S.W.I.F.T. Standard Release 2013. PM91847 Base INCOMING MESSAGE FAILS WHEN TAG 108 IS BLANK Formerly, when a FIN message that contains only blanks in field 108 was validated, the message was considered as being incorrect. Now, this has been fixed. PM93171 Base AVOID UNNECESSARY SQL STATEMENTS WHEN A CT IS DEPLOYED The WebSphere BI for FN system administration command 'deploy CT' (dep -ct) potentially fails to complete or needs an excessive amount of time and potentially produces faulty data. The 'deploy CT' command has been corrected. Data that could be faulty is replaced by correct data. PM93008 Base JAVADOC FIX FOR SECURITY PSIRT ADVISORY 1025 Current versions of Javadoc generate HTML with embedded javascript that contains a frame-injection security vulnerability. This has been corrected, and the javadoc has been updated. PM90722 Base Import of Bank Directory Plus and BIC Directory data added Formerly, the Reference Data Utility (RDU) supports to import BIC Plus IBAN data. Now, it supports to import BIC Plus IBAN, BIC Directory, and Bank Directory Plus data. F. Other changes ---------------- - Message updates: * New response messages: DNPR2200E-DNPR2210E, DNPR2262I-DNPR2276I, DNPR2277E, DNPR2280E, DNPR2290E * Response messages changed: DNPO1320I, DNPR2109E, DNPR2110E, DNPR2111E, DNPR2119E, DNPR2153E, DNPR2154E, DNPR2155E, DNPR2192E, DNPR2197E - Base API node ComIbmDniMwhUpdate changed Formerly, the WebSphere BI for FN Base API node ComIbmDniMwhUpdate changes specific status values in the MWH request to an uppercase value. These values are: 'FINISHED', 'ERROR', 'PROCESS', 'DELETED' If the request contains one of the statuses above in any case, the value is stored in MWH completely UPPERCASE. In case of MER user action routing for the delete action this leads to a wrong MWH_MSG_STATUS value of 'DELETED' instead of the intended 'Deleted'. Now, this has been corrected. - The size of the WebHome application was significantly reduced. G. Known issues --------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++