=============================================================================== = 5724D-9620 IBM WebSphere Business Integration for Financial Networks = = for Multiplatforms Base = = PTF UK36062 for APAR PK65304 = =============================================================================== Table of contents ----------------- A. How to use this document B. Changes to your current system C. Post-Installation D. Steps on a customization system E. Steps on a run-time system F. Enhancements and new functions delivered with this PTF G. APARs addressed by this PTF A. How to use this document --------------------------- Only the online version of this document is up to date. We strongly recommend that you download the latest version from http://www.ibm.com/software/integration/wbifn/support before you install this PTF. We recommend that you download the latest version of the documentation from the following web site: www.ibm.com/software/integration/wbifn/library This PTF supersedes the following PTFs: UK22415, UK28383, UK33896 The installation of this PTF is done in two phases: 1. Preparation phase During this timeframe your system can continue to process the workload as usual. This phase contains the steps up to and including 'E5. Preparing BAR files with the updated WebSphere BI for FN flows'. 2. Migration phase During this timeframe your system cannot process workload. This phase begins with step 'E6. Stop all sessions and services you use' and continues until you finished the migration. This document assumes the following: The installation directory of Websphere BI for FN is: /opt/IBM The names of users, groups, files, and directories are the same as those used in the "Planning, Installation and Customization" manual. If you use different values, use those values instead of the values shown here. B. Changes to your current system --------------------------------- The following files have been changed: /dni_02_02/admin/bin/dniccclt.jar /dni_02_02/admin/bin/dnicdp.jar /dni_02_02/admin/bin/dniclcs.sh /dni_02_02/admin/bin/dnicdp /dni_02_02/admin/bin/dnicdpm /dni_02_02/admin/data/dnicdcig.ddl /dni_02_02/admin/data/dnicdcws.ddl /dni_02_02/admin/data/dnicdi01.ddl /dni_02_02/admin/data/dnicdmn0.ddl /dni_02_02/admin/data/dnicdo01.ddl /dni_02_02/admin/data/dnicdo02.ddl /dni_02_02/admin/data/dniczdmq.mq /dni_02_02/admin/data/dniczdol.mq /dni_02_02/admin/data/dniczm05.mq /dni_02_02/admin/data/dniczdsn.txt /dni_02_02/admin/data/dnicztmd.txt /dni_02_02/admin/data/dni.xml /dni_02_02/admin/data/DNICOMMON.xml /dni_02_02/admin/data/DNIOU.xml /dni_02_02/admin/win/dninibak.cmd /dni_02_02/admin/win/dninigen.cmd /dni_02_02/admin/win/dniupdbd.cmd /dni_02_02/admin/win/dnininst.jar /dni_02_02/admin/win/dniupdbd.jar /dni_02_02/admin/win/dninirf.vbs /dni_02_02/admin/win/dniniws.vbs /dni_02_02/admin/win/com.ibm.dni.AccessControl.zip /dni_02_02/admin/win/com.ibm.dni.ControlledInput.zip /dni_02_02/admin/win/com.ibm.dni.ElementValidator.zip /dni_02_02/admin/win/com.ibm.dni.MessageAudit.zip /dni_02_02/admin/win/com.ibm.dni.MessageWarehouse.zip /dni_02_02/admin/win/com.ibm.dni.SysAdm.zip /dni_02_02/run/bin/dnicli /dni_02_02/run/bin/dnixdcsp /dni_02_02/run/classes/dnicgtrc.jar /dni_02_02/run/classes/dnicrypto.jar /dni_02_02/run/lib/libdnibip.a /dni_02_02/run/lib/libdnic.a /dni_02_02/run/lib/libdnicpcac.a /dni_02_02/run/lib/libdnicpshm.a /dni_02_02/run/lib/libdnidata.a /dni_02_02/run/lib/libdnig.a /dni_02_02/run/lib/libdnimes.a /dni_02_02/run/lib/libdnixml.a /dni_02_02/run/lil/dnicin.lil /dni_02_02/run/lil/dnicnp.lil /dni_02_02/run/lil/dnievn.lil /dni_02_02/run/lil/dnimfp.lil /dni_02_02/run/lil/dniscpn.lil /dni_02_02/run/msg/dniccmsg.cat /dni_02_02/run/res/dnicjevt.xml /dni_02_02/run/res/dnicprsp.xml The following are new files: /dni_02_02/admin/data/dnicdcar.ddl /dni_02_02/admin/data/dnicddar.ddl /dni_02_02/admin/data/dnicdm2g.ddl /dni_02_02/run/classes/dnicdrtn.jar /dni_02_02/run/classes/dnipcfg.jar /dni_02_02/run/lib/libdnipjni.a where represents the installation directory C. Post-Installation -------------------- After you have installed the PTF : 1. Share the files with your run-time system. 2. Ensure that the group ownership of the /opt/IBM/dni_02_02/admin directory and all subdirectories and files therein is set to group dniadmin. To do this, enter the following commands: chgrp -R dniadmin /opt/IBM/dni_02_02/admin 3. Ensure that the group ownership of the /opt/IBM/dni_02_02/run directory and all subdirectories and files therein is set to group dnilpp. To do this, enter the following commands: chgrp -R dnilpp /opt/IBM/dni_02_02/run D. Steps on a customization system ----------------------------------- Before you start the customization migration you should ensure that earlier migrations are completed using the CDP command 'implement'. Otherwise the CDP might generate migration statements again, which may cause the deployment vehicles to fail. To update your current definition directory and generate deployment data: 1. Log on to AIX on the customization system as a customizer (ucust1). 2. Change to the customization directory by issuing the following command: cd /var/dni_02_02/cus 3. Run your customization profile by issuing the following command: . ./dnicus_ 4. Copy new definitions to the CDP's customization definitions directory: cp $DNI_PATH/admin/data/dni.xml ./defs//dni 5. Start the CDP in migration mode by issuing the following command: dnicdpm -i 6. If you are not sure whether your .cdd reflects your current WebSphere BI for FN instance layout, generate a CDD using the CDP export command. How to this is described in "Planning, Installation, and Customization", Appendix E "CDP command reference". 7. Import your current CDD by issuing the following command: import cdd/.cdd 8. Update the customized administrative scripts in the directory '//admin' and generate deployment data for the run-time system migration by entering the following command: prepare Depending on the service bundles you have assigned and the superseded PTFs you already have applied this command may generate deployment vehicles for the following resource classes: 'MQ', 'DBSP' and 'DBGNT' deployment instructions in the file /var/dni_02_02/cus/depdata///instructions.txt. You will need this later in step 'E8. Updating the run-time system resources'. 9. After you have successfully deployed the changes in step 'E8. Updating the run-time system resources.', implement this CDD as your current CDD to update your 'current definition directory' by entering the following command: implement 10. Quit the CDP session by entering the following command: quit E. Steps on a run-time system ------------------------------ E1. Transferring the WebSphere BI for FN resources to the WebSphere MB Toolkit workstation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To prepare the WebSphere BI for FN resources located on the WebSphere MB Toolkit workstation in the following steps, you must have the authority of the WebSphere MB domain administrator (uwbimbd1). The access rights of this user are described in the "Planning, Installation, and Customization" manual in Chapter 1. Planning, in the section "Roles, users, and user groups". To transfer the WebSphere BI for FN resources to a WebSphere MB Toolkit workstation: 1. Log on to the Toolkit workstation. 2. Create a temporary directory to store the files to be transferred from the installation system. 3. Open a Command Prompt window and change to this directory. 4. Transfer, in binary mode, from the installation system to this temporary directory following files: /dni_02_02/admin/win/com.ibm.dni.AccessControl.zip /dni_02_02/admin/win/com.ibm.dni.ControlledInput.zip /dni_02_02/admin/win/com.ibm.dni.ElementValidator.zip /dni_02_02/admin/win/com.ibm.dni.MessageAudit.zip /dni_02_02/admin/win/com.ibm.dni.MessageWarehouse.zip /dni_02_02/admin/win/com.ibm.dni.SysAdm.zip /dni_02_02/admin/win/dni* For example, you can use the following File Transfer Program (FTP) commands to transfer the files: ftp bin prompt cd /dni_02_02/admin/win get com.ibm.dni.AccessControl.zip get com.ibm.dni.ControlledInput.zip get com.ibm.dni.ElementValidator.zip get com.ibm.dni.MessageAudit.zip get com.ibm.dni.MessageWarehouse.zip get com.ibm.dni.SysAdm.zip mget dni* bye E2. Setting the Toolkit version and directories - - - - - - - - - - - - - - - - - - - - - - - - To set the correct environment for the tools used in the subsequent steps follow the instructions in the "Planning, Installation, and Customization" manual in "Chapter 3. Preparing to create an instance", "Preparing the WebSphere MB Toolkit workstation", -> "Setting the Toolkit version and directories" E3. Backing up all WebSphere BI for FN resources installed in a WebSphere MB Toolkit workstation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To save the current level of all WebSphere BI for FN resources installed on a WebSphere MB Toolkit: 1. Open a Command Prompt window and change to the temporary directory you used in step E1. 2. Enter the command: dninibak This command creates backup files with names of the form: _dn.zip where represents a letter or letters that indicate to which product feature or features the backup file applies: i The Base feature f All extending features except Enhanced Support for SWIFTNet FileAct fo The Enhanced Support for SWIFTNet FileAct feature Each backup file contains: Links All files in the directory \eclipse\links that have names of the form "com.ibm.dn.link" WebSphere BI for FN eclipse plugins All subdirectories of with names of the form "com.ibm.dn" WebSphere BI for FN project directories All subdirectories of the directory \eclipse\workspace that have names that begin with "DNI_Dn" Note: The dninibak command issues messages to inform you of directories it was unable to find. For example: - If the Enhanced Support for SWIFTNet FileAct feature is not installed, dninibak issues a message to inform you that it was unable to find directories or projects for the feature "dnfo". - If none of the other extending features are installed, dninibak issues a message to inform you that it was unable to find directories or projects for the feature "dnf". If you do not use the corresponding features, you can safely ignore such messages. E4. Installing the changed WebSphere BI for FN plug-ins - - - - - - - - - - - - - - - - - - - - - - - - - - - - To install the changed WebSphere BI for FN plug-ins: In the Command Prompt window and from the temporary directory you used in step E1., enter dnininst If the dnininst program issues an error message, check the log file for more information about the reason for the error. To refresh the meta data in the Message Brokers Toolkit: a. Start the Toolkit with the -clean parameter. b. In the Message Brokers Toolkit, open the 'Broker Application Development Perspective'. To re-build the WebSphere BI for FN projects: - For Message Broker Toolkit V5: a) Select all projects with names of the form DNI_DnMainflows. b) Right-click and select "Refresh" from the pop-up menu. c) Right-click and select "Rebuild" from the pop-up menu. - For Message Broker Toolkit V6: a) Disable the "Build Automatically" feature. To do this, deselect the "Projects"->"Build Automatically" item in the pull-down menu. b) For all 'DNI_DnMainflows' projects: 1) In the "Resource navigator" window, select the projects. 2) From the main menu, select "Projects->Clean..." 3) In the popup window, select "Clean selected project" and ensure "Start a build immediately" is selected. 4) Press "OK". E5. Preparing BAR files with the updated WebSphere BI for FN flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To activate the changes within the WebSphere BI for FN eclipse plugins all affected message flows need to be deployed to all execution groups on all brokers where they are running. To prepare the broker archive files: a. Ensure the Message Brokers Toolkit is not running. b. In the Command Prompt window and from the temporary directory you used in step E1., enter dniupdbd -prepare -d . -q [-p ] [-h ] where The name of the queue manager to which the WebSphere MB configuration manager (CM) is connected. The port required to connect to the queue manager. The default is 1414. The host address of the machine running the CM. The default is 127.0.0.1 (localhost). This step creates broker archive files containing all WebSphere BI for FN message flows affected by the changes contained in this PTF, wich are: -> WebSphere BI for FN Base flows - DNI_A_EVENT - DNI_ACCADM - DNI_AGATHER - DNI_MONITOR - DNI_N_EVENT - DNI_R_AUDIT - DNI_R_MWH - DNI_RCP - DNI_SECADM - DNI_SYSADM -> WebSphere BI for FN Extending Features flows - DNF_BACKOUT - DNF_SAGOP - DNF_SAGOPRE - DNF_SAGCFG - DNF_SAGCFGR - DNF_FSM_QRY - DNF_FSM_STA - DNF_ILS_FIN - DNF_ILC_FIN - DNF_ILC_CMD - DNF_ILC_SLS - DNF_ILS_ACK - DNF_PF_IS - DNF_PF_CMD - DNF_L_ADM - DNF_L_IMP - DNF_UB_IN - DNF_UB_OUT - DNF_FTPOST - DNF_FTPROC - DNF_FTEVNTS - DNF_FTVAL - DNF_FTRESUB - DNF_DIAS_CS - DNF_DIAS_CR - DNF_DIAS_SS - DNF_DIAS_SR - DNF_SNF_RSP - DNF_SNF_CMD - DNF_EI_CMD - DNF_EI_CS - DNF_EI_RSP -> WebSphere BI for FN Enhanced Support for SWIFTNet FileAct flows - DNF_OSNFCMD - DNF_O_FT - DNF_O_CMD - DNF_OSNFRSP c. Check the log file dniupdbd.log to ensure that the files were successfully prepared. E6. Stop all sessions and services you use - - - - - - - - - - - - - - - - - - - - - Stop all sessions and services you use. How to do this depends on the features of WebSphere BI for FN that you are using. For instance: - Stop all applications that send requests to WebSphere BI for FN. - Log out SIPN FIN LTs. - Release SWIFTNet SnF queues. - Stop Enhanced FileAct File Transfer service. - Stop Enhanced InterAct service. - Close all dnicli sessions. For further information refer to the System Administration manual, chapter: 'Operating components, sessions, and services'. E7. Stopping all WebSphere BI for FN message brokers - - - - - - - - - - - - - - - - - - - - - - - - - - Stop all WebSphere BI for FN message brokers. E9. Updating the run-time system resources - - - - - - - - - - - - - - - - - - - - - Follow the deployment instructions created in step D8. to update the run-time system resources such as database tables and queues. Depending on the WebSphere BI for FN maintenance level you already have applied the deployment may bring the following changes to your system: - alters the following queues to set MAXMSGL to 104857600: - DNIvQPFX.DNI_R_AUDIT - DNIvQPFX.DNI_R_AUDIT.BACKOUT - DNIvQPFX.DNI_R_MWH - DNIvQPFX.DNI_R_MWH.BACKOUT - alters the following queue to set MAXMSGL to 20971520: - DNIK.REPLY.MODEL.QUEUE - creates 3 functions DNIBLOB2VARCHAR (with different sets of parameters) and grants 'execute' privilege on them to 'public' After you have successfully deployed the resources you have to implement the customization changes as described in step D9 in order to ensure that future migrations do not prepare the current deployment data again. If you have already closed the CDP session you have to repeat step D1 to D7, but not D8, before you continue with step D9. E10. Update the WebSphere BI MB environment - - - - - - - - - - - - - - - - - - - - - - To make the dnipcfg.jar file available to WebSphere BI for FN, ensure that the CLASSPATH environment variable includes: /dni_02_02/run/classes/dnipcfg.jar The location of the broker-specific WebSphere MB configuration data and how to activate changed configuration data depends on the WebSphere MB version used. Please see the WebSphere BI for FN 'Planning, Installation and Customization' manual, chapter 'Preparing a message broker' for further details. E11. Restart all WebSphere BI for FN message brokers - - - - - - - - - - - - - - - - - - - - - - - - - - Restart all WebSphere BI for FN message brokers. E12. Deploying all affected WebSphere BI for FN message flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To deploy the broker archive files: a. In the Command Prompt window and from the temporary directory you used in step E1. and E5., enter dniupdbd -deploy -q [-p ] [-h ] [-t ] where The name of the queue manager to which the WebSphere MB configuration manager (CM) is connected. The port required to connect to the queue manager. The default is 1414. The host address of the machine running the CM. The default is 127.0.0.1 (localhost). The wait interval for configuration manager and broker response. The default is 600 seconds (10min). This step deploys the broker archive files prepared in step E5. and contained in the current directory to the broker(s). b. Check the log file dniupdbd.log to ensure that the files were successfully deployed. E13. Restart all sessions and services you use - - - - - - - - - - - - - - - - - - - - - - - Restart all sessions and services you use. How to do this depends on the features of WebSphere BI for FN that you are using. For instance: - Log in SIPN FIN LTs. - Start Enhanced FileAct File Transfer service. - Start Enhanced InterAct service. - Acquire SWIFTNet SnF queues. - Start the applications that send requests to WebSphere BI for FN. For further information refer to the System Administration manual, chapter: 'Operating components, sessions, and services'. *----------------------------------------------------------------------------* * End of Migration * *----------------------------------------------------------------------------* F. Enhancements and new functions delivered with this PTF ---------------------------------------------------------- - Contents of messages in message audit log now readable WebSphere BI for FN now provides a DB2 user-defined function (UDF) that can be used to convert the message contents stored in a message audit log from binary large object (BLOB) data to variable-length character (VARCHAR) data. For more information refer to 'System Administration', appendix 'User-defined functions'. - Message warehouse adjunct tables interface now available WebSphere BI for FN Base message warehouse API is enhanced to allow applications to fill the message warehouse adjunct tables. For more information refer to 'Application Programming', chapter 'WebSphere BI for FN nodes', section 'DniMwhInsert node' and 'DniMwhUpdate node'. G. APARs addressed by this PTF ------------------------------ PK65304 WEBSPHERE BI FOR FN BASE SUMMARY PTF There are many separate PTFs with dependencies to each other for WebSphere BI for FN Base 2.2. These available PTFs are replaced (superseded) by this Summary PTF to easily bring an environment to the current maintenance level. PK65294 IMPROVE WBI-FN TRACE ERROR MESSAGE Formerly, if WebSphere BI for FN was not able to write traces into the trace directory, it wrote an unspecific error message in the file /var/tmp/dnigtrace. Now, if WebSphere BI for FN is not able to write traces into the trace directory, it writes an error message indicating the reason in the file /var/tmp/dnigtrace. APARs from superseded PTFs: PK65280 DEPLOY PROBLEM IN SCRIPT DNIUPDDB IF TOOLKIT WORKSTATION USES DIFFERENT TIME THAN CONFIG MANAGER Formerly, the tool dniupdbd used during migrations to update the WebSphere BI for FN message flows encountered problems during deployment of BAR files when the configuration manager was located on a system other than the Toolkit system and the time between those two systems was not synchronized. Now, dniupdbd will synchronize itself with the configuration manager during deploy operations. PK61211 PROVIDE CONTROLLED INPUT NODE REQUIRED FOR EFA APAR PK60641 The PTF for EFA APAR PK60641 requires a new function in WebSphere BI for FN Base. PK61218 DNICLI LOOPS, IF IT IS NOT ENDED CORRECTLY Formerly, when you did not close the dnicli session but instead just terminated the terminal emulation the CLI continued to run and use CPU. Now the CLI will terminate when the terminal emulation is closed. PK65277 DNF_L_ADM QUERY COMMAND FAILS ON WRITING THE COMMAND AUDIT RESPONSE Certain commands like listing a huge number of events or a lot of RM relationships may result in large response messages which exceed the size of the CLI's reply-to queue. Furthermore, if command audit is enabled these response messages will also exceed the size of the remote audit queue. Now the size of certain queues is changed: DNIvQPFX.DNI_R_AUDIT and DNIvQPFX.DNI_R_AUDIT.BACKOUT, DNIvQPFX.DNI_R_MWH and DNIvQPFX.DNI_R_MWH.BACKOUT -> MAXMSGL is set to maximum value (100MB), as audit and warehouse records are allowed to reach this size. DNIK.REPLY.MODEL.QUEUE -> MAXMSGL set to 20MB. If this value is not sufficient for your environment than you can increase it. However, a lot of queues created from this model queue may exist at the same time as each instance of dnicli creates its own reply-to queue. PK55683 CLI HANGS-UP WHEN STARTING IT WITH INVALID ARGUMENTS Formerly, when calling dnicli with invalid arguments it reported a syntax error and then did hang-up. You had to terminate the CLI. Now the CLI will exit properly after displaying the syntax error. PK52429 REMOTE MWH MAY DELETE PAYLOAD ON UPDATE, IF IT IS NOT PROVIDED AGAIN If an earlier message warehouse request stored the message contents and a succeeding update request did not update this information again, the message content stored in the message warehouse was erroneously deleted. This has been corrected. Note: The remote message warehouse interface is currently only used in WebSphere BI for FN Enhanced InterAct service. This services provides the payload in each warehouse request so that it was not affected by this problem. PK50389 PROVIDE ELEMENT VALIDATION NODE REQUIRED FOR APAR PK48348 The fix for APAR PK48348 for WebSphere BI for FN Extending Features requires to validate XML elements according to their type definitions. This functionality will be introduced. PK48928 MESSAGE AUDIT NEEDS TO SUPPORT STORAGE OF FUNCTION FOLDER Formerly, the message audit service was not able to store the function folder of a request message. However, certain extensions of WebSphere BI for FN Base do require this. The message audit was enhanced to support this scenario. PK48237 MIGRATION UPDATES THE CURRENCY TABLE WITH VERY OLD DATA. Formerly, when migrating to WebSphere BI for FN 2.2 the currency table DNIvSN.DNI_CURRENCY was reloaded with default content and the user data was overwritten. Now migration will not change the contents of the currency table. PK47524 DNIERROR: CANNOT FIND XML API LIBRARY: The PTF installation tool to prepare and deploy WebSphere BI for FN message flows did not find the XML API library on WebSphere BI MB Toolkit 5.1 environments due to a version mismatch. The tool can now also use the version of the XML API library which is available on the WBI MB Toolkit 5.1. PK44454 INSUFFICIENT JAVAHEAPSIZE DURING MIGRATION TO WBIFN V2.2.0 JAVA.LANG.OUTOFMEMORY ERROR Formerly, when processing large configurations with for instance more than 30 OU's the Customization Definition Program (CDP) ran out of memory. With this PTF the default of 64MB is increased to 256MB. PK41025 DEPLOY TOOL GETS CLASSCASTEXCEPTION ON MB TOOLKIT 6.0.2 FOR FILEACT RELATED DEPLOYMENT PREPARATION The PTF installation tool to prepare and deploy WebSphere BI for FN message flows has been updated to comply with MB Toolkit API changes. PK39881 UPDATES FOR THE PTF INSTALLATION TOOL The PTF installation tool to prepare and deploy WebSphere BI for FN message flows has been updated. PK51360 DNIZ9364E ERROR WHEN INSTALLING BASE COMPONENT ONLY The PTF fix "placeholder group 'DniTableSpaces' of SVB set 'com.ibm.dni' doesn't exist error. +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++