============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2010 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.0 Base PTF UK63961 for APAR PM29159 = Date 2011-04-29 = ============================================================================== ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Preparation E Activating F APAR details G Other changes A. About this document ---------------------- Only the online version of this readme document is current. Before you install the corresponding PTF, download the latest version from: http://www.ibm.com/software/integration/wbifn/support Download the latest version of the WebSphere BI for FN product documentation from: http://www.ibm.com/software/integration/wbifn/library The structure of WebSphere BI for FN readme documents is identical for all PTFs. Sections that are not applicable are left blank. If you install more than one PTF at a time, combine the readme documents by merging the contents of each section. The installation of this PTF is done in two phases: 1. Preparation - During this phase your system can continue to process messages as usual. 2. Activation - During this phase your system cannot process messages. This readme document uses the following variables: The installation directory of WebSphere BI for FN. The directory /opt/IBM is used in examples. The name of the WebSphere BI for FN instance. The name INST1 is used in examples. The name of the organizational unit. Depending on the context, this might be SYSOU, DNFSYSOU, or the name of a business OU. The names of users, groups, files, and directories are the same as those used in the "Planning, Installation, and Customization" maunal. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PM28856 Base DURING THE DNFCZMLC RUN THE FOLLOWING ERROR OCCURED: DNIP3142E CT STILL REFERRED TO BY ROLE CT CANNOT BE DELETED PM26601 Base IMPROVEMENT OF EXPLANATION FOR MESSAGE DNIZ9058E RELATED TO UPDATE OF MSG CATALOG PM29159 Base NO WARNING MESSAGE WHEN A CIN STOP DUE TO A DATABASE PROBLEM PM30436 Base GETTING UNNECCESSARY SQL CODE -803 WRITTEN TO THE CONSOLE USING MSIF AND DOING A MWH INSERT PM30983 RM WARNING MESSAGES REPEATED IN SYSLOG WITH A FAILED CLI ATTEMPT Please note: This is the sysrouted WebSphere BI for FN V3.1 APAR of the original WebSphere BI for FN V2.2 Field-APAR PM30638. PM35010 Base THE LIST ROLE COMMAND DOES NOT RETRIEVE ALL THE OBJECTS IF THE ROLE FOR CO AND OR AN ATTRIBUTE CONTAINS AN ASTERISK PM33300 Base CLASSCASTEXCEPTION IN MESSAGE VALIDATION Functional changes: NOT APPLICABLE. Documentation updates: - Messages and Codes The following modules have been changed: /dni_03_01/admin/bin/dnicdp.jar /dni_03_01/admin/toolkit/com.ibm.dni.api.jar /dni_03_01/run/bin/dnicli /dni_03_01/run/bin/dnfczmcf /dni_03_01/run/bin/dnfczmlc.sh /dni_03_01/run/bin/dnfczml1.awk /dni_03_01/run/bin/dnfczml2.awk /dni_03_01/run/classes/dnicgtrc.jar /dni_03_01/run/classes/dnicvcks.jar /dni_03_01/run/classes/dnicvrls_sfmtxml10.jar /dni_03_01/run/classes/dnicvcks_sfunds41.jar /dni_03_01/run/doc/dni.msgstds.api.doc.zip /dni_03_01/run/flows/DNI_R_EVENT.bar /dni_03_01/run/flows/DNF_RM.bar /dni_03_01/run/flows/DNI_SECADM.bar /dni_03_01/run/lil/dnicin.lil C. Planning ----------- Before installing a new PTF, ensure that: - All previously prepared deployment instructions have been carried out. - All previous CDD changes have been implemented using the CDP. - All configuration administration changes have been deployed. To check this, enter the following commands: dnicli -s DNI_SYSADM -ou SYSOU > list -ou % -qo amorz > list -cos % -qo amorz > list -ct % -qo amorz Each list command should result in 'No [OU/COS/CT] match search criteria'. - All security administration changes have been approved. To check this, enter the following commands for each OU: dnicli -s DNI_SECADM -ou > list -ro % -qo mor [only for SYSOU] > list -user % -qo mor Each list command should result in 'No roles found that match specified criteria'. Customization changes other than those described in a PTF readme document are not allowed during PTF installation. Prerequisite and supersede information: This PTF requires the following PTFs: - UK62356 for APAR PM26603 (Base 3.1.0.5, DATABASE CHANGES REQUIERED FOR APAR PM24367) This PTF supersedes the following PTFs: not applicable Roles involved: The activities in this PTF involve the following roles: - Installer (root) - WebSphere MB administrator (uwmba1) - First WebSphere BI for FN system configuration administrator (sa1) D. Preparation -------------- D1. Installation ---------------- 1. Stop all sessions and services, for example: - Stop all applications that send requests to WebSphere BI for FN. - Log out SIPN FIN LTs. - Release SWIFTNet SnF queues. - Stop the MSIF Transfer service. - Stop the Enhanced InterAct services. - Close all dnicli sessions. For further information, refer to the section of 'System Administration' that describes how to operate components, sessions, and services. 2. Stop all WebSphere BI for FN message brokers. 3. Install this PTF using as described in the 'Installing WebSphere BI for FN' in 'Planning, Installation and Customization' manual. 4. Share the files in the /dni_03_01/admin directory with your customization system. 5. Ensure that the group ownership of the /dni_03_01/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 /dni_03_01/admin 4. Set the group ownership of these directories and files to group dnilpp. To do this, enter the following command in AIX: chgrp -R dnilpp /dni_03_01/run 5. Restart all WebSphere BI for FN message brokers. D2. Steps on a customization system ----------------------------------- NOT APPLICABLE. D3. Generating configuration data migration scripts --------------------------------------------------- NOT APPLICABLE. D4. Customize updated BAR files when not using the BAP (dniczbap) to deploy them -------------------------------------------------------------------------------- Which of the following sections applies depends on how you plan to deploy broker archive (BAR) files: - If your configuration manager runs on Windows, you cannot use the BAP (dniczbap) to deploy BAR files, and must follow the procedure described in D4.1. - If your configuration manager runs on AIX, and if you want to prepare BAR files without directly deploying them, follow the procedure described in D4.2. Note: Before deploying updated BAR files, ensure that the configuration manager is running and that no flows or execution groups are stopped. Otherwise, old flow levels might not be deleted during the BAP update operation (that is, when you enter the "prepare -update new" command). To verify that the update was successful, issue the BAP list command and ensure that no flow is running that has the same name as another flow but a different version. D5.1. Update BAR files when there is no connection to the configuration manager - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Carry out these steps when your configuration manager runs on Windows. The BAP customizes all BAR files that it processed earlier, for example, during installation of WebSphere BI for FN. You then select which files are to be updated for the current PTF. To customize the BAR files 1. On the runtime system, log on to AIX as the system configuration administrator, for example, SA1, or as the WebSphere MB administrator, for example uwmba1, and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a temporary directory where dniczbap stores the customized BAR files. You will need up to 30MB free space in this directory. 3. Issue the following command: dniczbap -cmd prepare -all -dir where represents the directory created in the previous step. Each of the customized BAR files has a name of the form: ...bar where The name of the broker to which the BAR file is to be deployed. The name of the execution group to which the BAR file is to be deployed. The name of the BAR file as provided by WebSphere BI for FN. 4. Identify the BAR files that are listed in section 'B. Summary of changes' and delete all other BAR files in the temporary output directory. 5. Transfer, in binary mode, the customized BAR files to the Toolkit or to the system where you will run the mqsideploy command. 6. If you want to deploy using the Toolkit import the customized BAR files. D4.2. Use the configuration manager to automatically detect updated BAR files - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Carry out these steps when your configuration manager runs on AIX but you do not want to deploy BAR files using the BAP (dniczbap). To customize the BAR files: 1. Ensure that the configuration manager is started. 2. On the runtime system on which the configuration manager runs, log on to AIX as the WebSphere MB administrator, for example, uwmba1, and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 3. Create a temporary directory where dniczbap stores the customized BAR files. You will need up to 30MB free space in this directory. 4. Issue the following command: dniczbap -cmd prepare -update new -dir where represents the directory created in the previous step. Each of the customized BAR files has a name of the form: ...bar where The name of the broker to which the BAR file is to be deployed. The name of the execution group to which the BAR file is to be deployed. The name of the BAR file as provided by WebSphere BI for FN. *------------------------------------------------------------------------------* * End of Preparation * *------------------------------------------------------------------------------* E. Activating ------------- E1. Stopping all sessions and services you use ---------------------------------------------- Stop all sessions and services. How to do this depends on which WebSphere BI for FN features you use. For example: - Stop all applications that send requests to WebSphere BI for FN. - Log out SIPN FIN LTs. - Release SWIFTNet SnF queues. - Stop the MSIF Message Transfer service. - Stop the Enhanced InterAct services. - Close all dnicli sessions. For further information, refer to the section of the 'System Administration' manual that describes how to operate components, sessions, and services. E2. Stopping all application servers ------------------------------------ NOT APPLICABLE. E3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- Stop all WebSphere BI for FN message brokers. E4. Sharing the runtime directory structure ------------------------------------------- 1. Share the files in the /dni_03_01/run directory with the runtime systems. 2. Set the group ownership of these directories and files to group dnilpp. To do this, enter the following command in AIX: chgrp -R dnilpp /dni_03_01/run E5. Backing up configuration and security data in image copies -------------------------------------------------------------- NOT APPLICABLE. E6. Following the deployment instructions created in step D2.4 -------------------------------------------------------------- NOT APPLICABLE. E7. Additional activities ------------------------- NOT APPLICABLE. E8. Restarting all WebSphere BI for FN message brokers ------------------------------------------------------ Restart all WebSphere BI for FN message brokers. E9. Redeploy updated BAR files ------------------------------ To customize and deploy the updated WebSphere BI for FN BAR files, you must have the access rights of the WebSphere MB administrator (uwmba1). To redeploy updated BAR files: 1. Ensure that the configuration manager is running. 2. If you already have prepared the customized BAR files as described in step D5 proceed with step E9.1; otherwise, proceed with step E9.2. Note: Before deploying updated BAR files, ensure that the configuration manager is running and that no flows or execution groups are stopped. Otherwise, old flow levels might not be deleted during the BAP update operation (that is, when you enter the "prepare -update new" command). To verify that the update was successful, issue the BAP list command and ensure that no flow is running that has the same name as another flow but a different version. E9.1. Deploying the BAR files customized in step D4 - - - - - - - - - - - - - - - - - - - - - - - - - - Use the Toolkit or the mqsideploy command to deploy the BAR files. Remove the old versions of the flows which have been updated by this PTF as otherwise two different versions of the flows are running. You can list the flows running in the broker to identify the names including their version suffix. You can also refer to the Planning, Installation, and Customization manual for a list of flows contained in each BAR file. E9.2. Updating BAR files when step D5 has not been performed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Use these steps when your configuration manager runs on AIX and you want to deploy directly using the BAP (dniczbap). To customize and deploy the BAR files: 1. On the runtime system on which the configuration manager runs, log on to AIX as the WebSphere MB administrator, for example, UWMBA1, and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Ensure that you have sufficient free space in the current directory. To deploy all message flows requires about 30 MB of free space. 3. Issue the following command: dniczbap -cmd prepare -update new -deploy E9.3. Activating WebSphere BI for FN accounting - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. E10. Migrating configuration data --------------------------------- NOT APPLICABLE. E11. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ NOT APPLICABLE. E12. Restarting all sessions and services ----------------------------------------- Restart all of the sessions and services that you use. How to do this depends on which WebSphere BI for FN features you use. For example: - Log in SIPN FIN LTs. - Start the MSIF Message Transfer service. - Start the Enhanced InterAct services. - Acquire SWIFTNet SnF queues. - Start the applications that send requests to WebSphere BI for FN. For further information, refer to the section of the 'System Administration' manual that describes how to operate components, sessions, and services. E13. Updating the Toolkit development environment ------------------------------------------------- If you use WebSphere BI for FN nodes or message sets in your own message flows, or if you modified WebSphere BI for FN sample message flows, you must update your Toolkit environment and redeploy your message flows. The following resources have been changed in this PTF: -> API nodes: - DniEventStore To update your Toolkit environment: - If you modified samples that were provided by WebSphere BI for FN and want to keep your modifications, rename the projects. However, these saved projects will not be updated. - Delete the old WebSphere BI for FN provided projects in your workspace. - To reinstall the new versions of the Toolkit resources, follow the instructions provided in the section of 'Application Programming' that describe how to prepare the WebSphere Message Broker Toolkit workstation. - Clean all projects and redeploy the message flows that you built using nodes that were provided by WebSphere BI for FN. *------------------------------------------------------------------------------* * End of Activating * *------------------------------------------------------------------------------* F. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM28856 Base DURING THE DNFCZMLC RUN THE FOLLOWING ERROR OCCURED: DNIP3142E CT STILL REFERRED TO BY ROLE CT CANNOT BE DELETED Formerly, when an attribute of a CT was removed or changed, dnfczmlc did not generate related "remove" cli commands for these useless attributes assigned to a role. Now, the remove of useless attributes from a role have been added to the logic for generating related "remove" cli commands. PM26601 Base IMPROVEMENT OF EXPLANATION FOR MESSAGE DNIZ9058E RELATED TO UPDATE OF MSG CATALOG Formerly, the explanation of error event DNIZ9058E in the dnicdp process only pointed to 'Invalid type' while there might be other possible reasons. That can be missing settings for ServiceBundleSetFile and Service Bundles definitions. Now, the description in the explanation part of DNIZ9058E has been improved. PM29159 Base NO WARNING MESSAGE WHEN A CIN STOP DUE TO A DATABASE PROBLEM Formerly, when a CIN stop occurred because of a database severe issue, user might not get any any warning message or log about this incident. Now, an event is passed to the SYSLOG even when WBIFN can not write to the database. And, when the CIN is still stopped after a broker restart an event about this problem is issued to inform the user. PM30436 Base GETTING UNNECCESSARY SQL CODE -803 WRITTEN TO THE CONSOLE USING MSIF AND DOING A MWH INSERT Formerly, when MWH is enabled and a request was passed to DNF_O_FT, MSIF tried a MWHInsert. When MSIF received an SQL -803, a MWHUpdate was done instead, then. While this processing was correct, the handled exception SQLCODE -803 should not be written to the console. Now, the processing of handled exception SQLCODE -803 was changed. It is no longer written to the console. PM30983 RM WARNING MESSAGES REPEATED IN SYSLOG WITH A FAILED CLI ATTEMPT Please note: This is the sysrouted WebSphere BI for FN V3.1 APAR of the original WebSphere BI for FN V2.2 Field-APAR PM30638. PM35010 Base THE LIST ROLE COMMAND DOES NOT RETRIEVE ALL THE OBJECTS IF THE ROLE FOR CO AND OR AN ATTRIBUTE CONTAINS AN ASTERISK Formerly, when the role for CO and/or an attribute contained an asterisk the list role command did not retrieve all the qualifying object patterns. The error occured only under DB2 V10. Now, this has been corrected. The list role command works under DB2 V10 as it does under DB2 V8 on or DB2 V9. PM33300 Base CLASSCASTEXCEPTION IN MESSAGE VALIDATION Formerly, when loading a message definition a ClassCastException could occur. Under rare circumstances, loading of a new message definition failed with a ClassCastException. Messages could still be processed with previously loaded definitions, but a broker restart was required to load other message definitions. Now, WebSphere BI for FN has been changed to ensure that all message definitions are loaded with the same class loader. G. Other changes ---------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++