============================================================================== ============================================================================== 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 Message Management PTF UK58149 for APAR PM13495 = Date 2010-08-31 = ============================================================================== ============================================================================== ============================================================================== 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 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 "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: PM13495 MM MESSAGE MANAGEMENT UPDATES FOR SWIFT SR2010 CHANGES Functional changes: - Adaptions for S.W.I.F.T. Standard Release 2010 (SR2010) changes - The schema of the messages in the definition set 'fin2010' differs from the schema of messages in 'fin2009' to increase compatibility with SWIFTs MT/XML Schema Library. - A new possibility is provided to activate a message definition set for test purposes even before its official activation date. WebSphere BI for FN Base V3.1.0 Base PTF UK58117 for APAR PM07598 adds CT: DniMsgDomain, attr: TestMsgDefSet. You can create a CO with the name of the message domain and set the value of the attribute to any message definition set, e.g. to activate the SR2010 changes: cre -ou -ct DniMsgDomain -co DNIFIN -attr TestMsgDefSet -val 'fin2010'. WebSphere BI for FN Message Management V3.1.0 modifies the following COS and role of to cover COs of the new CT: - COS DnqERCos - role DnqERCfg - Support for SWIFTNet Exceptions and Investigations 1.1 (Bank-to-Bank) was added in the 'eni12' message definition set. Support for SWIFTNet Exceptions and Investigations 1.2 (Bank-to-Corporate) is still available in the same message definition set. Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Concepts and Components - Messages and Codes - System Administration - Application Programming - User's Guide - Information Center The following modules have been changed: /dnq_03_01/admin/data/dnqczcar.cli /dnq_03_01/admin/data/dnqczcas.cli /dnq_03_01/admin/data/dnqczwcf.txt /dnq_03_01/admin/data/DNQERWAS.xml /dnq_03_01/admin/toolkit/com.ibm.dnq.api.jar /dnq_03_01/admin/toolkit/dnq.schemas.comibmdni.zip /dnq_03_01/run/appsrv/dnq.app.main.ear /dnq_03_01/run/appsrv/dnqccupd.py /dnq_03_01/run/appsrv/dnqccrem.py /dnq_03_01/run/appsrv/dnqccmig.py /dnq_03_01/run/appsrv/dnqccins.py /dnq_03_01/run/config/com.ibm.dnq.maxhf.domain.DNIFIN.xml /dnq_03_01/run/classes/dnq.maxhf.api.jar /dnq_03_01/run/classes/dnq.print.jar /dnq_03_01/run/data/dnqczcar.cli /dnq_03_01/run/data/dnqczcas.cli /dnq_03_01/run/flows/DNQ_K_FIN1.bar /dnq_03_01/run/flows/DNQ_K_FIN2.bar /dnq_03_01/run/flows/DNQ_K_MX1.bar /dnq_03_01/run/flows/DNQ_O_SFI.bar The following are new modules: /dnq_03_01/run/config/com.ibm.dnq.maxhf.defset.fin2010.xml /dnq_03_01/admin/toolkit/dnq.schemas.swiftFin2010.zip 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: - UK54901 for APAR PM06260 (UPDATES FOR MESSAGE MANAGEMENT) - UK58142 for APAR PM07599 (SWIFT SR2010: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION) This PTF should be installed together with: - UK58142 for APAR PM07599 (SWIFT SR2010: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION) Update your MER enterprise application as described in step E11 of this readme document. 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) - First WebSphere BI for FN system configuration administrator (sa1) - Second WebSphere BI for FN system configuration administrator (sa2) - First WebSphere BI for FN security configuration administrator (ua1) - Second WebSphere BI for FN security configuration administrator (ua2) D. Preparation -------------- D1. Installation ---------------- 1. This PTF requires the Base PTF V3.1.0.4 (UK58142 for APAR PM07599) and the previous Message Management for Multiplatforms V3.1.0.3 (UK554901 for APAR PM06260), please install the Base PTF V3.1.0.4 first. This PTF will overwrite partial installed files. After installation, the V.R.M.F will upgrade to V3.1.0.4. The detail steps of installation could be found in "Installing WebSphere BI for FN", in the "Planning, Installation and Customization" manual. 2. Share the files in the /dnq_03_01/admin directory with your customization system. 3. Ensure that the group ownership of the /dnq_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 /dnq_03_01/admin 4. Share the files in the following directories with your runtime systems: /dnq_03_01/run/data /dnq_03_01/run/flows /dnq_03_01/run/classes /dnq_03_01/run/config 5. Set the group ownership of these directories and files to group dinlpp. To do this, enter the following command in AIX: chgrp -R dnilpp /dnq_03_01/run/data chgrp -R dnilpp /dnq_03_01/run/flows chgrp -R dnilpp /dnq_03_01/run/classes chgrp -R dnilpp /dnq_03_01/run/config D2. Steps on a customization system ----------------------------------- To update your current definition directory 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/_PM13495.cdd > import cdd/_PM13495.cdd > prepare 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 D3. Generating configuration data migration scripts --------------------------------------------------- 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. Check if you have enabled wildcard escaping for the 'list -ro' command and disable it temporarily. To check if you have configured an escape character enter the following commands: dnicli -s DNI_SYSADM -ou SYSOU > list -ou SYSOU -co DniSecAdm.list -attr DniEscapeCharacter -lo osv If the response is 'No OUs match search criteria.' no escape character is defined. Otherwise note the value displayed and enter the following command in the CLI session to temporarily disable the escape character: > rem -ou SYSOU -ct DniSecAdm.list -co DniSecAdm.list -attr DniEscapeCharacter Commit, approve and deploy the OU SYSOU. Close the CLI session: > .quit 3. Create a temporary directory where dnfczmlc stores the CLI command files which will contain the configuration migration statements. 4. 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_7_sa_cre_cos_com.cli 2. dnfczmlc_7_sa_cre_cos_dep.cli 3. dnfczmlc_8_ua_cre_ro_com.cli 4. dnfczmlc_8_ua_cre_ro_app.cli 5. Enable the escape character for the 'list -ro' command if you have temporarily disabled it in step 2: dnicli -s DNI_SYSADM -ou SYSOU > add -ou SYSOU -co DniSecAdm.list -ct DniSecAdm.list -attr DniEscapeCharacter -val where is the value that was displayed in response to the list command in step 2. Commit, approve and deploy the OU SYSOU. Close the CLI session: > .quit This PTF changes the following configuration entities: - COs of the new CT 'DniMsgDomain' are added to COS DnqERCos - COs of the new CT 'DniMsgDomain' are added to role DnqERCfg 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 you 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. D4.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, 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 service. - Close all dnicli sessions. For further information, refer to the section of 'System Administration' that describes how to operate components, sessions, and services. E2. Stopping all application servers ------------------------------------ Stop all application servers. 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 /dnq_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 /dnq_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 -------------------------------------------------------------- Follow the deployment instructions that were created in step D2.4. This will update the run-time system resources. 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. E9.2. Updating BAR files when step D4 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 --------------------------------- Execute the CLI command files generated in step D4 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_7_sa_cre_cos_com.cli by the first SA (sa1) - dnfczmlc_7_sa_cre_cos_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 D3.2 and execute the generated CLI command files by entering the following command: dnicli -s -ou SYSOU -cft | tee -a PM13495cli.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. E11. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ E11.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: /bin/backupConfig.sh where represents the file name under which the backup should be stored. E11.2. Update the WebSphere Application Server environment - - - - - - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. E11.3. Migrating the enterprise application - - - - - - - - - - - - - - - - - - - - - - Start the application server on which the enterprise application runs. If you use a clustered application server environment, start the deployment manager, node agents, and all members of the application server cluster. Issue the following command with the user ID of the WebSphere Application Server operator (uwaso1): /bin/wsadmin.sh -user -password -lang jython -f /dnqccupd.py where: The user ID of the WebSphere Application Server administrator (uwasa1). The password of the user. The path to the migration script: /dnq_03_01/run/appsrv. The path to the MER ear file: /dnq_03_01/run/appsrv. 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 service. - Acquire SWIFTNet SnF queues. - Start the applications that send requests to WebSphere BI for FN. For further information, refer to the section of 'System Administration' 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: - DnqErFinInput - DnqErFinOutput - DnqErMsifInput - DnqErMsifOutput - DnqErQueueInput - DnqFinInput - DnqFinServiceOutput -> sample message flows in these projects: - DNI_DnqRouting 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 * *------------------------------------------------------------------------------* I. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM13495 MM MESSAGE MANAGEMENT UPDATES FOR SWIFT SR2010 CHANGES The WebSphere BI for FN Message Management feature is updated as described in this document. J. Other changes ---------------- - New optional element value The ComIbmDni folder of the SendMsg.Request.TransferOptions gets the new, optional element value. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++