============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2014 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 (3.1.1.22) PTF UI22202 for APAR PI21851 Driver level: 4491 Date 2014-12-19 ============================================================================== ============================================================================== 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-01.ibm.com/support/docview.wss?uid=swg27041133 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 names of users, groups, files, and directories are the same as those used in WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PI21851 Base SECURE WBIFN SEMAPHORES ON GROUP LEVEL TO AVOID ALTERATION BY OTHER APPLICATIONS PI23704 Base VALIDATION ERROR AFTER RECEIVING AN RM AUTHORISATION TOSND PI24530 Base RMA Q&A STATUS INCORRECT FOR REFUSED QUERIES OR ANSWERS PI26110 Base A&O SHOWS MQ ERROR WHEN RETRIEVING A LARGE NUMBER OF CONFIGURATION OBJECTS PI25651 Base MISLEADING ERROR RESPONSE WHEN A DNI_SYSADM COMMAND IS ISSUED IN THE BUSINESS OU PI25675 Base DNF_L_ADM QUERY COMMAND SOMETIMES RETURNS AUTHORISATIONS TWICE PI25610 Base DNICDPM RAISES JAVANULLPOINTEREXCEPTION IN PREPARE COMMAND PI27174 Base 0D (CR) GETS LOST IN AN MT021, WHEN PROCESSED BY A DNQERQUEUEINPUT NODE IN MER (SR2014) PI30628 Base EMBEDDED MT202 COV IN MTX92 MAY CAUSE VALIDATION ERROR DNIY0018E Additional functional changes: - none Documentation updates: The following manuals have been changed: - Application Programming 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/DNFRMA.xml /dniv311/admin/data/DNIWEBHOME.xml /dniv311/admin/data/DNPAO.xml /dniv311/admin/toolkit/dni.schemas.comibmdni.zip /dniv311/run/bin/dnfczrmc /dniv311/run/bin/dnprdu /dniv311/run/classes/dnicrypto.jar /dniv311/run/classes/dnicvcks_sfmtxml14.jar /dniv311/run/classes/dnp.jab.jar /dniv311/run/classes/dnprdu.jar /dniv311/run/flows/DNF_RM.bar /dniv311/run/flows/DNI_SYSADM.bar /dniv311/run/jplugin/dnf.rma.tr.jar /dniv311/run/lib/libdnigbip.a /dniv311/run/lib/libdnigbip64.a /dniv311/run/lib/libdnicpshm.a /dniv311/run/lib/libdnicpshm64.a /dniv311/run/lil/dnicpn.lil /dniv311/run/lil/dnfrmexp.lil /dniv311/run/lil64/dnicpn64.lil /dniv311/run/lil64/dnfrmexp64.lil C. Planning ----------- C1. Checks to be done >>BEFORE<< installing a new PTF ----------------------------------------------------- 1. Check if you have any efixes (emergency fixes) applied in your WebSphere BI for FN installation. In case you have efixes installed after your previous WebSphere BI for FN PTF installation and migration contact your IBM support before installing and migrating this PTF. 2. Ensure that all previously prepared deployment instructions were carried out. 3. 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. 4. Until the migration for this PTF has been completely finished, ensure that no changes are made to the currently implemented CDD. 5. 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'. 6. 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 -rg % -qo mor [only for SYSOU] > list -user % -qo mor The list command should result in 'No roles/role groups/users found that match specified criteria'. C2. Prerequisite and supersede information ------------------------------------------ This PTF requires the following PTFs: - UI21662 for APAR PI26005 (Base 3.1.1.21, WEBSPHERE BI FOR FN BASE UPDATES FOR SWIFT VL/142014) C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - WebSphere MB application developer (uwmbad1) - WebSphere MB administrator (uwmba1) - WebSphere Application Server operator (uwaso1) - WebSphere Application Server administrator (uwasa1) 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. - 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: 3.1. Verify your customization profile: Ensure that the setting of the DNI_JAVA environment variable is set to the /bin subdirectory of the Java 6 64-bit home directory, for example: DNI_JAVA=/usr/lpp/java/J6.0_64/bin 3.2. 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/_UI22202.cdd > import cdd/_UI22202.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: - CFGPF (if SVB DNPAO or DNFRMA is assigned) * 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: If you continue, the current CDD will be overwritten by a new CDD." 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 exception: - do not execute the instructions provided for resource class CFGPF now; you will use them in step D13.4. D8. Additional activities ------------------------- NOT APPLICABLE. D9. Restarting all WebSphere BI for FN message brokers ------------------------------------------------------ Restart all WebSphere BI for FN message brokers. D10. Prepare BAR file deployment -------------------------------- D10.1. Backup the BTD repository - - - - - - - - - - - - - - - - 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 backup of your BTD repository. The location of this directory depends on the version of WebSphere Message Broker you are using: - for version 6.1: $DNI_BAP_PATH/bap/$DNI_QMGR_CFG - for version 7 or version 8: $DNI_BAP_PATH/bap/$DNI_I where the values of the environment variables DNI_BAP_PATH, DNI_QMGR_CFG and DNI_I correspond to the settings made in your dniprofile. For example, to create a backup of a Broker V7 or Broker V8 BTD repository by copying the corresponding directory, enter the following commands: mkdir -p $DNI_BAP_PATH/bap/UI22202/$DNI_I cp -R $DNI_BAP_PATH/bap/$DNI_I/ $DNI_BAP_PATH/bap/UI22202/$DNI_I D10.2. Customize BAR files when using mqsideploy or the Toolkit to deploy them - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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 or V8, 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 in WebSphere BI for FN 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 or CDP generated output - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - Note: If you have configured multiple broker servers you must deploy the BAR files to each broker server. 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Note: If you are using Broker V7 or V8 and you have configured multiple broker servers you must perform the following steps on each broker server. 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 systems 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 -broker The parameter -broker is only required if you use multiple broker servers. 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 --------------------------------- NOT APPLICABLE. 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. Restarting all application servers - - - - - - - - - - - - - - - - - - - - - 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. D13.4. 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. Note: A new web application may contain changed JavaScript and HTML files. To assure that the user works with the most current web application content it is recommended to clear the browser cache on each client workstation before the user logs in the next time. It is not sufficient to just reload the page. Please find the following sample description for the different browser types as reference for the user communication: Firefox 10.0.6 ESR and later From the menu bar select Tools -> Options. In the options dialog select the Advanced section. In the Advanced section select the Network notebook tab. Click on the "Clear Now" button to clear the browser cache. Internet Explorer 8 or later From the menu bar select Tools -> "Internet Options". On the General notebook page click the "Delete..." button in section "Browsing History". In the "Delete Browsing History" dialog check at least "Temporary Internet files" and click the Delete button to clear the browser cache. 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. - 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 ------------------------------------------------- You must update your Toolkit environment if you use at least one of the following components: - WebSphere BI for FN sample message flows as foundation for your own flow development - WebSphere BI for FN nodes in your own message flows - WebSphere BI for FN message set projects containing XML schema definitions, that, for example, are utilized by the XPath wizard Furthermore, you have to rebuild and redeploy your message flows if they are based on the WebSphere BI for FN API. The following resources are changed by this PTF: - WebSphere BI for FN message sets: - dni.schemas.comibmdni.zip To install the new versions of the Toolkit resources, follow the instructions of the listed sections provided in "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN Application Programming: - Transferring the WebSphere BI for FN resources - Installing the WebSphere BI for FN Eclipse plug-ins If you use WebSphere BI for FN sample message flows as foundation for your own flow development follow the instructions provided in "Using the sample routing flows" in WebSphere BI for FN Application Programming. Otherwise, continue with the instructions provided in "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN Application Programming: - Importing WebSphere BI for FN Base sample projects - Importing the message sets and sample routing flows Additionally, if you use WebSphere BI for FN message set projects containing XML schema definitions for your own flow development follow the instructions provided in section "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN Application Programming: - Importing the message sets and sample routing flows - Importing XSD files for SWIFT message payloads D16. Verifying your Installation -------------------------------- This PTF contains updated versions of the RMA or 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: PI21851 Base SECURE WBIFN SEMAPHORES ON GROUP LEVEL TO AVOID ALTERATION BY OTHER APPLICATIONS Formerly, the semaphores created by WebSphere BI for FN were not secured. Other applications could read these semaphores and even alter them. In certain situations, this could lead to unforeseeable results like performance issues, lock situations or even abends. Now, the semaphores created by WebSphere BI for FN are accessible only by the owner (the message broker administrator user ID) and all members that belong to the effective group of the owner. PI23704 Base VALIDATION ERROR AFTER RECEIVING AN RM AUTHORISATION TOSND Formerly, when an RM authorisation ToSnd is received from a correspondent with whom an old, imported bootstrap authorisation existed, the WBIFN RMA tried to send out an authorisation PDU for the imported bootstrap authorisation. This is unwanted and should not happen. The imported bootstrap authorisation should only be replaced by the received authorisation ToSnd. Due to the fact, that a bootstrap authorisation doesn't contain an Issued Date/Time value, this authorisation PDU fails validation and is not send to the counterpart. Now, this has been fixed. PI24530 Base RMA Q&A STATUS INCORRECT FOR REFUSED QUERIES OR ANSWERS Formerly, when using RMA, the relationship list displays for each relationship the Q&A status. The Q&A status indicates whether an action is required for any query or answer that belongs to the same relationship. When the pending changes for a query or answer are refused, those changes must be discarded afterwards or must be corrected and submitted again. However, the Q&A status for refused queries or answers states that no action is required. Now, the Q&A status for refused queries or answers indicates that an action is required. PI26110 Base A&O SHOWS MQ ERROR RETRIEVING A LARGE NUMBER OF CONFIGURATION OBJECTS Formerly, the AO Facility used a single request message to retrieve the configuration data required to display the resources for an MER or RMA role. With a large number of configuration objects being available, this resulted in a ComIbmDni folder larger than 511K in size and caused an MQ error in a Shared Queue environment. Now, the AO Facility uses multiple requests to retrieve the configuration data in smaller parts. PI25651 Base MISLEADING ERROR RESPONSE WHEN A DNI_SYSADM COMMAND IS ISSUED IN THE BUSINESS OU Formerly, when a DNI_SYSADM command was issued in a business OU, but the user did not have the permissions to issue the command, the following response message was displayed in certain situations: DNIP3252E Internal error in User Audit service. However, this is not correct. Instead, a message should be displayed indicating that access is denied. Now, this has been fixed and an appropriate message is displayed. PI25675 Base DNF_L_ADM QUERY COMMAND SOMETIMES RETURNS AUTHORISATIONS TWICE Formerly, when using the DNF_L_ADM query -t verbose command to display a list of all authorisations, in certain circumstances, authorisations are displayed twice. Now, this has been fixed. PI25610 Base DNICDPM RAISES JAVANULLPOINTEREXCEPTION IN PREPARE COMMAND Formerly, when trying to execute the dnicdpm prepare command without having implemented the previous cdd, then the dnicdpm program may issue an error message with a null pointer exception and terminates. Now, such an invalid call of the prepare command is handled without running into a null pointer exception. PI27174 Base 0D (CR) GETS LOST IN AN MT021, WHEN PROCESSED BY A DNQERQUEUEINPUT NODE IN MER (SR2014) Formerly, when node DnqErQueueInput was used during routing in MER and the fin2014 message definition set was used, the "0d" (CR) was lost from a "0d0a" (CRLF) within an MT021. Now, this has been corrected. PI30628 Base EMBEDDED MT202 COV IN MTX92 MAY CAUSE VALIDATION ERROR DNIY0018E Formerly, an embedded MT202 COV in a MTx92, for example, a MT292, may cause validation error DNIY0018E. Now, this has been corrected. F. Other changes ---------------- - Tracing Now the CPN initializes the trace buffers. - Reference Data Utility (RDU) The usage description of parameter -future and -migrate has been corrected. A Java file not found exception has been corrected. - Browser-based printing in Message Management feature Element "Printed" added to XML schema definition of ERUserActionType. G. Known issues --------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++