============================================================================== ============================================================================== 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 UK94069 for APAR PM84617 Driver level: 3250 Date 2013-07-18 ============================================================================== ============================================================================== 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: PM80628 Base CHANGE OF CLASSIFICATION CATEGORY OF DNIVRSN PLACEHOLDER PM82134 Base CATEGORY FOR PLACEHOLDER DNIVMBRK IS WRONG PM78252 Base AVOID IMPLEMENT PROBLEMS IN CDP MIGRATION MODE PM85695 Base RELATIONSHIP LIST FILTERING MAY RETURN ONLY A SUBSET OF THE EXPECTED RESULT PM74133 Base RMA DOES NOT SHOW CORRECT AUTH RESULT IN BROWSER WHEN FILTERING WITH VALUE "REVOKED". PM88542 Base RMA FILTER'S NAME DOES NOT DISPLAY CORRECTLY WHEN IT CONTAINS CHINESE CHARACTERS PM86987 Base BASE UPDATES FOR MESSAGE MANAGEMENT AIX APARS PM85709, PM86067, PM86803 PM84617 Base IMPROVE ADMINISTRATION AND OPERATION FACILITY SECURITY PM87073 Base BASE UPDATES FOR FIN AIX APAR PM82056 (IMPROVE FIN BEHAVIOUR IN CASE OF INCONSISTENT ASP DATA) PM87621 Base HY014 MAY OCCUR ON LIST -OU IN TRANSACTIONAL MODE PM88541 Base CANNOT ISSUE DNI SYSOP COMMAND ON A&O Additional functional changes: - Changes applied for WebSphere BI for FN Message Management(MER) APAR PM82591 (USER CAN'T CUSTOMIZE THE LOGOUT URL ON MER/A&O/RMA GUI) have been applied also for WebSphere BI for FN Base RMA and A&O applications - Changes applied for WebSphere BI for FN Messaging Services for SWIFTNet InterAct and FileAct (MSIF) APAR PM85699 (MSIF PROCESSING FOR BIG SEPA FILEACT FILES) require DB updates of WebSphere BI for FN Base tables DNFMWHOEF_DNFSYSOU and DNFMWHOEF_DNIvOU (alter data type of columns). - Migrate two queues increasing maxdepth MQ MAXDEPTH values defined: * MAXDEPTH(999999) for local queue DNIvQPFX.DNI_N_EVENT * MAXDEPTH(50000) for model queue DNIK.REPLY.MODEL.QUEUE Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Concepts and Components - Messages and Codes - System Administration - Application Programming - Administration and Operation Facility User's Guide - Information Center 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/bin/dnicdp.jar /dniv311/admin/data/dnf.xml /dniv311/admin/data/DNFCOMMON.xml /dniv311/admin/data/dnfczart.ddl /dniv311/admin/data/dnfczcat.cli /dniv311/admin/data/dnfczoact.ddl /dniv311/admin/data/dnfczoco.ddl /dniv311/admin/data/DnfRma_upd.py /dniv311/admin/data/DnfRma.py /dniv311/admin/data/DNFRMA.xml /dniv311/admin/data/dni.properties /dniv311/admin/data/dni.xml /dniv311/admin/data/dnicdcig.ddl /dniv311/admin/data/DNICOMMON.xml /dniv311/admin/data/dniczdlq.mq /dniv311/admin/data/dniczdmq.mq /dniv311/admin/data/DNIWAS.xml /dniv311/admin/data/DniWebHome_upd.py /dniv311/admin/data/DniWebHome.py /dniv311/admin/data/DNIWEBHOME.xml /dniv311/admin/data/dnp.xml /dniv311/admin/data/DnpAo_upd.py /dniv311/admin/data/DnpAo.py /dniv311/admin/data/DNPAO.xml /dniv311/admin/data/dnpclaph.applist /dniv311/admin/data/dnpczcoy.cli /dniv311/admin/data/dnpczoar.cli /dniv311/admin/data/dnpczocr.cli /dniv311/admin/toolkit/dni.schemas.comibmdni.zip /dniv311/run/bin/dnfczmlc.sh /dniv311/run/bin/dnfczml2.awk /dniv311/run/bin/dnfczrmc /dniv311/run/classes/dni.sec.jar /dniv311/run/classes/dnicvcks_sfmtxml10.jar /dniv311/run/classes/dnicvcks_sfmtxml11.jar /dniv311/run/classes/dnicvcks_sfmtxml12.jar /dniv311/run/classes/dnicvcks.jar /dniv311/run/classes/dnicvrls_sfmtxml10.jar /dniv311/run/classes/dnicvrls_sfmtxml11.jar /dniv311/run/classes/dnicvrls_sfmtxml12.jar /dniv311/run/classes/dnp.jab.jar /dniv311/run/classes/dnp.util.model.jar /dniv311/run/data/dnfczcat.cli /dniv311/run/data/dnpczcoy.cli /dniv311/run/data/dnpczocr.cli /dniv311/run/flows/DNI_SECADM.bar /dniv311/run/flows/DNI_SYSADM.bar /dniv311/run/jplugin/dnf.rma.tr.jar /dniv311/run/lil/dnicpn.lil /dniv311/run/lil64/dnicpn64.lil /dniv311/run/msg/DNIF_Msg.properties /dniv311/run/msg/DNIU_Msg.properties /dniv311/run/msg/DNIW_Msg.properties /dniv311/run/msg/dnpcfmsg.cat /dniv311/run/msg/DNPF_Msg.properties /dniv311/run/res/dnicfevt.xml /dniv311/run/res/dnicwevt.xml /dniv311/run/res/dnpcfmsg.xml /dniv311/run/samples/dniczpro.prf The following modules are new: /dniv311/admin/data/dnpczo01.ddl /dniv311/admin/data/dnfcdo01.ddl /dniv311/admin/data/dnfcdoo1.ddl /dniv311/admin/data/dnicdm5g.ddl /dniv311/admin/data/dniczm10.mq /dniv311/admin/data/dniczpe1.txt /dniv311/admin/data/dniczpe2.txt /dniv311/admin/data/dniczpe3.txt /dniv311/admin/data/dniczpe4.txt /dniv311/admin/data/dniczpe5.txt /dniv311/admin/data/dniczpe6.txt /dniv311/admin/data/dniczpe7.txt /dniv311/admin/data/dniczpe8.txt /dniv311/admin/data/dniczpe9.txt /dniv311/admin/data/dniczpu1.txt /dniv311/admin/data/dniczpu2.txt /dniv311/admin/data/dniczpu3.txt /dniv311/admin/data/dnpczcat.cli /dniv311/admin/data/dnpczdat.cli /dniv311/run/bin/dnpczmca /dniv311/run/data/dnpczcat.cli 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: - UK79663 for APAR PM75464 (Base 3.1.1.11, TRY TO RE-ESTABLISH CONNECTION TO DB2 WHEN CONNECTION FROM THE WAS WAS LOST) C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - DB2 administrator (udb2adm1) - WebSphere MQ administrator (uwmqadm1) - 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) - First WebSphere BI for FN security administrator (ua1) - Second WebSphere BI for FN security administrator (ua2) 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/_UK94069_temp.cdd > supplement cdd/_UK94069_temp.cdd cdd/_UK94069.cdd Edit the supplemented CDD. Search for each occurrence of the new placeholder DNIvLOGOUTURL. Only change the value of this placeholder if you want to use your own URL. If you delete it or keep it unchanged your system works as before. > import cdd/_UK94069.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 * alter tables DNFMWHOEF_DNFSYSOU and DNFMWHOEF_DNIvOU: alter data type of columns - DBGNT * grant select permission for tables DNI_CT, DNI_OU, DNI_ROLE, DNI_RO_CT_ATTR_REL, DNI_ROLEGROUP, DNI_RG_ROLE_REL, DNI_USER, DNI_USER_RESOLVED, DNI_USR_RG_REL, DNI_USR_ROLE_REL, DNI_STATUS_COMMENT to group DNIvUGRP - MQ * MAXDEPTH(999999) defined for local queue DNIvQPFX.DNI_N_EVENT * MAXDEPTH(50000) defined for model queue DNIK.REPLY.MODEL.QUEUE - 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.4. D8. Additional activities ------------------------- D8.1. DB2 related activities ---------------------------- NOT APPLICABLE. D8.2. WebSphere MB related activities ------------------------------------- NOT APPLICABLE. D8.3. WebSphere MQ related activities ------------------------------------- NOT APPLICABLE. D8.4 Update your current dniprofile ----------------------------------- The following changes were made in the delivered sample profile dniczpro.prf: a. Runtime environment expanded with: a. Environment variable DNI_SN added b. Environment variable DNI_DSN added b. Pre-requisite product information restructured and a. Environment variable DB2_PATH added b. LIBPATH variable expanded (DB2 libraries prepended) c. CLASSPATH variable expanded (DB2 libraries prepended) To make the changes effective, you must upgrade your current dniprofile: 1. Backup your dniprofile. 2. Obtain a copy of the revised dniprofile according to section "Preparing a user profile for a runtime system on which a broker runs" in the Planning, Installation, and Customization Guide and set the environment variables as described. You can download the latest version of the WebSphere BI for FN product documentation from: http://www.ibm.com/software/integration/wbifn/library Note, that the revised dniprofile has been restructured. If you want to keep and upgrade your current dniprofile, you must compare the old and new dniprofile and integrate any of the changes described above. 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 --------------------------------------------------- a) If the service bundle DNPAO is not assigned to an OU-server combination, skip this step. Otherwise, log on to AIX as the system configuration administrator, for example, sa1, and issue the following commands: dnicli -s DNI_SYSADM -ou DNFSYSOU > add -ou DNFSYSOU -ct DniConfigSVB -co DNPAO -attr ctfile -val dnpczcat.cli > add -ou DNFSYSOU -ct DniConfigSVB -co DNPAO -attr migfile -val dnpczmca > com -ou DNFSYSOU > app -ou DNFSYSOU > dep -ou DNFSYSOU If dual authorization is enabled, the 'app' command must be issued by a system configuration administrator other than the one who issued the 'com' command. b) 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. Create a temporary directory where dnfczmlc stores the CLI command files which will contain the configuration migration statements. 3. 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 2. dnfczmlc_3_ua_cre_ro_all.cli If dual authorization is used (-dual YES): 1. dnfczmlc_5_sa_cre_ct_com.cli 2. dnfczmlc_5_sa_cre_ct_dep.cli 3. dnfczmlc_8_ua_cre_ro_com.cli 4. dnfczmlc_8_ua_cre_ro_app.cli This PTF changes the following configuration entities: - Adds the new attributes AspSndExceptionQueue and AspSndExceptionQMgr to CT DnfExceptionOptionSet: add -ct DnfExceptionOptionSet -attr AspSndExceptionQueue add -ct DnfExceptionOptionSet -attr AspSndExceptionQMgr - if SVB DNPAO is assigned * creates the new CT DnpAoSec cre -ct DnpAoSec -desc 'AO Facility security permissions' add -ct DnpAoSec -attr DISPLAYUSER -type P add -ct DnpAoSec -attr ASSIGNUSER -type P add -ct DnpAoSec -attr APPROVEUSER -type P add -ct DnpAoSec -attr DISPLAYROLE -type P add -ct DnpAoSec -attr MODIFYROLE -type P add -ct DnpAoSec -attr APPROVEROLE -type P * creates the following roles: cre -ro DnpAoSecDisplayUser -desc 'Use the AO Facility to display role assignments for users.' add -ro DnpAoSecDisplayUser -ct DnpAoSec -co * -attr DISPLAYUSER cre -ro DnpAoSecAssignUser -desc 'Use the AO Facility to modify role assignments for users.' add -ro DnpAoSecAssignUser -ct DnpAoSec -co * -attr ASSIGNUSER cre -ro DnpAoSecApproveUser -desc 'Use the AO Facility to approve role assignments for users.' add -ro DnpAoSecApproveUser -ct DnpAoSec -co * -attr APPROVEUSER cre -ro DnpAoSecDisplayRole -desc 'Use the AO Facility to display roles.' add -ro DnpAoSecDisplayRole -ct DnpAoSec -co * -attr DISPLAYROLE cre -ro DnpAoSecModifyRole -desc 'Use the AO Facility to modify roles.' add -ro DnpAoSecModifyRole -ct DnpAoSec -co * -attr MODIFYROLE cre -ro DnpAoSecApproveRole -desc 'Use the AO Facility to approve roles.' add -ro DnpAoSecApproveRole -ct DnpAoSec -co * -attr APPROVEROLE D12.2 Executing the migration scripts - - - - - - - - - - - - - - - - - - - Execute the CLI command files generated in step D12.1 in the following sequence and using the following user authorization: If dual authorization was not used (-dual NO): - dnfczmlc_2_sa_ent_all.cli by any SA - dnfczmlc_3_ua_cre_ro_all.cli by any UA If dual authorization was on (-dual YES): - dnfczmlc_5_sa_cre_ct_com.cli by the first SA (sa1) - dnfczmlc_5_sa_cre_ct_dep.cli by the second SA (sa2) - dnfczmlc_8_ua_cre_ro_com.cli by the first UA (ua1) - dnfczmlc_8_ua_cre_ro_app.cli by the second UA (ua2) 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 D12.1 and execute the generated CLI command files by entering the following command: dnicli -s -ou SYSOU -cft | tee -a UK94069cli.log where: DNI_SYSADM for files executed by the system configuration administrators, abbreviated as SA DNI_SECADM for files executed by the security administrators, abbreviated as UA The CLI command file name, for example dnfczmlc_5_sa_cre_ct_com.cli. 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: -> message sets: - DNI_DnqMsgSetMqrfh2 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 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. *------------------------------------------------------------------------------* * End of Installation * *------------------------------------------------------------------------------* E. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM80628 Base CHANGE OF CLASSIFICATION CATEGORY OF DNIVRSN PLACEHOLDER Formerly, when changing the value for placeholder DNIvRSN the CDP did not generate any deployment data but showed the following message: Changing the value of this placeholder results in changes to the runtime environment that are so far-reaching that the CDP is unable to generate deployment vehicles that implement them. The only way to make these changes is to alter the affected subsystem directly. If the current preparation step generated any deployment vehicles, it is important that the far-reaching changes be made before any of the generated deployment vehicles are run. After the changes have been made, and after the generated deployment vehicles (if any) have been run, enter the "implement" CDP command to indicate that the current CDD conforms to the actual runtime environment. Now, when the value for the following placeholders has been changed, the CDP generates appropriate deployment data and deployment instructions describing how to change the value in the according subsystem: DNIvRSN, DNIvRDSN, DNIvRDBHOST, DNIvRDBPORT DNIvMQTRANS, DNIvMQHOST, DNIvMQPORT, DNIvMQCHL DNFvRMACONTROOT, DNPvAOCONTROOT DNIvWCLUS, DNIvWSRV, DNIvWNODE DNIvWCLUSHOME, DNIvWSRVHOME, DNIvWNODEHOME DNIvWCLUSRMA, DNIvWSRVRMA, DNIvWNODERMA DNIvWCLUSMER, DNIvWSRVMER, DNIvWNODEMER DNIvWCLUSAO, DNIvWSRVAO DNIvWNODEAO PM82134 Base CATEGORY FOR PLACEHOLDER DNIVMBRK IS WRONG Formerly, when changing the value for placeholder DNIvMBRK the CDP did not generate any deployment data but has showed the following message: Changing the value of this placeholder results in changes to the runtime environment that are so far-reaching that the CDP is unable to generate deployment vehicles that implement them. The only way to make these changes is to alter the affected subsystem directly. If the current preparation step generated any deployment vehicles, it is important that the far-reaching changes be made before any of the generated deployment vehicles are run. After the changes have been made, and after the generated deployment vehicles (if any) have been run, enter the "implement" CDP command to indicate that the current CDD conforms to the actual runtime environment. Now, when the value for the placeholder DNIvMBRK has been changed, the CDP generates appropriate deployment data and deployment instructions describing how to change the value in the according subsystem: DNIvMBRK PM78252 Base AVOID IMPLEMENT PROBLEMS IN CDP MIGRATION MODE Formerly, when a "implement' command has been issued either in migration or customization mode but the incomplete customization process was processed in the other mode, the implemented customization data could be in a unpredictable state. Now, the CDP has been improved by: 1. a start up mode check: A start in migration mode is not possible, if a customization has not been finished (no 'implement' has been issued) A start in customization mode is not possible, if a migration has not been finished (no 'implement' has been issued) 2. a new command 'status': The new command status shows the preparation status, whether an migration or a customization is pending, or no customization or migration is pending. 3. an action log: An action log is introduced that keeps a history of all CDP activities. 4. a copy of the last used customization data A copy of the customization data that has been used with the last preparation of deployment data is saved. This requires additional 10 MB space for the file system of the customization system. PM85695 Base RELATIONSHIP LIST FILTERING MAY RETURN ONLY A SUBSET OF THE EXPECTED RESULT Formerly, when user entered a lot of filter criteras (eg. more than 9 items), some criteria were truncated, and user could not see the whole criteria list. Now, this has been corrected, and user can see the whole list. PM74133 Base RMA DOES NOT SHOW CORRECT AUTH RESULT IN BROWSER WHEN FILTERING WITH VALUE "REVOKED". Formerly, when filtering with value "Revoked" was done, RMA did not show the correct authentication result in the browser. Now, the correct result is displayed. PM88542 Base RMA FILTER'S NAME DOES NOT DISPLAY CORRECTLY WHEN IT CONTAINS CHINESE CHARACTERS Formerly, when filter name contained Chinese characters it was not displayed correctly. Now, the filter name is displayed correctly. PM86987 Base BASE UPDATES FOR MESSAGE MANAGEMENT AIX APARS PM85709, PM86067, PM86803 This PTFs provides the changes required for WebShpere BI for FN Message Management APARs PM85709, PM86067, and PM86803. Descriptions of problems refer to APARs PM85709, PM86067, and PM86803. PM87073 Base BASE UPDATES FOR FIN AIX APAR PM82056 (IMPROVE FIN BEHAVIOUR IN CASE OF INCONSISTENT ASP DATA) This PTFs provides the changes required for WebShpere BI for FN FIN APAR PM82056. Descriptions of problem refer to APAR PM82056. PM87621 Base HY014 MAY OCCUR ON LIST -OU IN TRANSACTIONAL MODE Formerly, if the system administration service (DNI_SYSADM) was used to process more than 253 list -ou commands in transactional command-file mode, the processing might fail with an HY014. Now, the system administration service (DNI_SYSADM) is able to process more than 253 list -ou commands in transactional command-file mode. PM84617 Base IMPROVE ADMINISTRATION AND OPERATION FACILITY SECURITY The security of the Administration and Operation facility has been improved. PM88541 Base CANNOT ISSUE DNI SYSOP COMMAND ON A&O Formerly, when user tried to issue command DNI_SYSOP from A&O, user got an error message "DNPJ3533E : Response message contains invalid data." Now, this has been corrected. F.Other changes ---------------- - Message updates: * New response messages: DNIZ9391E, DNIZ9392I, DNIZ9393I, DNIZ9394E, DNIZ9395E, DNIZ9396E, DNIZ9397E * Response messages changed: DNIZ9017E, DNIZ9335E, DNIZ9349I, DNPF0116E - Changes applied for WebSphere BI for FN Message Management(MER) APAR PM82591 (USER CAN'T CUSTOMIZE THE LOGOUT URL ON MER/A&O/RMA GUI) have been applied also for WebSphere BI for FN Base RMA and A&O applications. - Changes applied for WebSphere BI for FN Messaging Services for SWIFTNet InterAct and FileAct (MSIF) APAR PM85699 (MSIF PROCESSING FOR BIG SEPA FILEACT FILES) require DB updates of WebSphere BI for FN Base tables DNFMWHOEF_DNFSYSOU and DNFMWHOEF_DNIvOU (alter data type of columns). - MQ MAXDEPTH new values defined: * MAXDEPTH(999999) for local queue DNIvQPFX.DNI_N_EVENT * MAXDEPTH(50000) for model queue DNIK.REPLY.MODEL.QUEUE - Formerly, when removing SVB DNFRMA after PTF UK79663 for APAR PM75464 was installed, the removal of the non-existing table space DNFRMYS did fail. Now, the modul that removes the RMA table spaces was adapted to specify the correct table space name DNFRMY. G. 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 ++++