============================================================================== ============================================================================== 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 UK54901 for APAR PM06260 = Date 2010-04-28 = ============================================================================== ============================================================================== ============================================================================== 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: PM06260 UPDATES FOR MESSAGE MANAGEMENT PM03344 MER MUST ISSUE A WARNING, WHEN TRYING TO DELETE A QUEUE FOR WHICH STILL MESSAGES EXIST PM03336 SQL -407 WHEN TRYING TO ROUTE A MESSAGE TO A PRINT QUEUE IN ENTRY AND REPAIR PM04849 WHEN CONFIGURING A PRINTDEVICE "", AS DESCRIBED IN SA GUIDE "CONFIGURING A PRINT Q FOR AN INSTANCE", PRINTING DOES NOT WORK PM04853 DNQFINSERVICEOUTPUT NODE SHOULD INCLUDE A PROPERTY, WHICH ALLOWS FOR SETTING THE REPLY-TO Q Functional changes: - MER now provides a possibility to apply certain operations to multiple messages. For more information refer to the User Guide. Documentation updates: The following manuals have been changed: - Messages and Codes - Application Programming - User Guide The following modules have been changed: /dnq_03_01/admin/data/dnqcpcqo.cli /dnq_03_01/admin/data/dnqczpct.ddl /dnq_03_01/admin/data/dnqczwcf.txt /dnq_03_01/admin/data/DNQPRINT.xml /dnq_03_01/admin/data/DNQROUTS.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/dnqccrem.py /dnq_03_01/run/classes/dnq.common.jar /dnq_03_01/run/classes/dnq.print.jar /dnq_03_01/run/classes/dnqcbsdf.jar /dnq_03_01/run/flows/DNQ_K_FIN1.bar /dnq_03_01/run/flows/DNQ_K_FIN2.bar /dnq_03_01/run/flows/DNQ_O_SFI.bar /dnq_03_01/run/flows/DNQ_O_SFO.bar /dnq_03_01/run/flows/DNQ_P_CMD.bar /dnq_03_01/run/flows/DNQ_P_DSP.bar /dnq_03_01/run/flows/DNQ_P_PRT.bar /dnq_03_01/run/msg/dnqcbmsg.cat /dnq_03_01/run/msg/dnqccmsg.cat /dnq_03_01/run/msg/dnqcdmsg.cat /dnq_03_01/run/msg/dnqcemsg.cat /dnq_03_01/run/msg/dnqckmsg.cat /dnq_03_01/run/msg/dnqcomsg.cat /dnq_03_01/run/msg/dnqcpmsg.cat /dnq_03_01/run/msg/dnqcrmsg.cat /dnq_03_01/run/msg/dnqcwmsg.cat /dnq_03_01/run/res/dnqcbevt.xml /dnq_03_01/run/res/dnqccevt.xml /dnq_03_01/run/res/dnqccidf.xml /dnq_03_01/run/res/dnqcdevt.xml /dnq_03_01/run/res/dnqceevt.xml /dnq_03_01/run/res/dnqckevt.xml /dnq_03_01/run/res/dnqcoevt.xml /dnq_03_01/run/res/dnqcpevt.xml /dnq_03_01/run/res/dnqcpsdf.xml /dnq_03_01/run/res/dnqcrevt.xml /dnq_03_01/run/res/dnqcwevt.xml /dnq_03_01/run/samples/dnqcbsdf.sh The following modules are new: /dnq_03_01/admin/data/dnqczp00.ddl 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: - UK51830 for APAR PK97166 (UPDATES FOR MESSAGE MANAGEMENT) This PTF should be installed together with: - UK54898 for APAR PM08215 (Base March Update PTF). 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) - DB2 administrator (udbadm1) - WebSphere MB application developer (uwmbad1) - WebSphere MB administrator (uwmba1) - WebSphere Application Server operator (uwaso1) - WebSphere Application Server administrator (uwasa1) - WebSphere MQ administrator (uwmqadm1) D. Preparation -------------- D1. Installation ---------------- 1. This PTF requires the Base PTF V3.1.0.3 (UK54898 for APAR PM08215) and the previous Message Management for Multiplatforms V3.1.0.2 (UK51830 for APAR PK97166), please install the Base PTF V3.1.0.3 first. This PTF will overwrite partial installed files. After installation, the V.R.M.F will upgrade to V3.1.0.3. 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/flows 5. 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/flows chgrp -R dnilpp /dnq_03_01/run/classes 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/_PM06260.cdd > import cdd/_PM06260.cdd > prepare This step generates deployment data for migration of the run-time system for the following resource classes: - DB (if service bundle DNQPRINT is assigned) * create the new index DNQX1PMS on table DNQP_MESSAGE - MQ (if service bundle DNQROUTS is assigned) * OU related routing sample alias queues are removed and recreated: -> DNIvINST.DNIvOU.DNQ_O_SFI -> DNIvINST.DNIvOU.DNQ_O_SFO -> DNIvINST.DNIvOU.DNQ_O_SMX * Follow the steps in E7 to grant MQ authority manually. Deployment instructions are generated in the file '///instructions.txt'. You will need this later in the 'E. Activating' section. 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. Copy DB2 modules --------------------------------- NOT APPLICABLE. D4. Generating configuration data migration scripts --------------------------------------------------- NOT APPLICABLE. D5. 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 D5.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 D5.2. 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. D5.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 ------------------------------------ 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 ------------------------- If service bundle DNQROUTS is assigned, please execute following procedure to grant the authority of alias queues. 1. Log on to AIX as the WebSphere MQ administrator (uwmqadm1). 2. Issue following commands: (the value of placeholder can be found in the file '/defs/.cdd') setmqaut -m -t qmgr -g +connect +inq setmqaut -m -n -t queue -g +put +inq +alladm setmqaut -m -n -t queue -g +put +inq +alladm setmqaut -m -n -t queue -g +put +inq +alladm 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. E9.1. Deploying the BAR files customized in step D5 - - - - - - - - - - - - - - - - - - - - - - - - - - Use the Toolkit or the mqsideploy command to deploy the BAR files. 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 ------------------------------------------------------------ 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 agent, 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. 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 '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 changed in this PTF: -> API nodes: - DnqPrintInputAdapter - DnqFinServiceOutput - DnqErQueueInput -> sample message flows in these projects: - DNI_DnqErCommon - DNI_DnqErSwiftNetFin - DNI_DnqErSwiftNetMX - DNI_DnqErRouting -> schema files: - dnq.schemas.comibmdni.zip 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 the 'Application Programming' manual 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: PM06260 MM UPDATES FOR MESSAGE MANAGEMENT The WebSphere BI for FN Message Management feature is updated as described in this document. PM03344 MM MER MUST ISSUE A WARNING, WHEN TRYING TO DELETE A QUEUE FOR WHICH STILL MESSAGES EXIST Formerly, after deleting a MER queue from the configuration for which messages were still contained in the database a NullPointerException was thrown when opening a queue list. Now, a queue list can be displayed even if there are messages in the database where the queues have been removed from the configuration. Additionally, during startup of the MER enterprise application it will check for messages in the database for which no queue was found in the configuration. An event will inform the administrator if such messages are found. PM03336 MM SQL -407 WHEN TRYING TO ROUTE A MESSAGE TO A PRINT QUEUE IN ENTRY AND REPAIR Formerly, when trying to route a message to a Print Queue in MER SQL error -407 occurred. Now, this behavior is corrected. PM04849 MM WHEN CONFIGURING A PRINTDEVICE "", AS DESCRIBED IN SA GUIDE "CONFIGURING A PRINT Q FOR AN INSTANCE", PRINTING DOES NOT WORK Formerly, when a PrintDevice was configured, and an empty set of double quotes ("") was specified, printing did not work. Now, this behavior is corrected. PM04853 MM DNQFINSERVICEOUTPUT NODE SHOULD INCLUDE A PROPERTY, WHICH ALLOWS FOR SETTING THE REPLY-TO Q Formerly, when using a DnqFinServiceOutput node in Message Management Routing without setting the Reply-To-Queue during routing explicitly error DNQO1103E occurred because no Reply-To-Queue was set for the message. Now, the DnqFinServiceOutput node has two additional properties to set the Reply-To-Queue as well as the Reply-To-QMgr. G. Other changes ---------------- Printing: - Deadlocks no longer occur when a large number of messages is printed. Message Entry and Repair: - Deadlocks no longer occur when many different users simultaneously process messages. - The performance has been improved when many parallel users are working. - The 'Fin2008' message definition set is no longer offered during message creation. - After you have successfully created a new message MER will display its ID. SDF: - Control messages are automatically deleted when a SDF task finishes successfully. - SDF template startup script dnqcbsdf.sh now also contains the parameter DNQ_CB_MSD. Other areas: - Routing service sample alias queues DNQ_O_SFI, DNQ_O_SFO and DNQ_O_SMX now refer to the correct local queues. - The DnqErQueueInput node did create an invalid field in the MQRFH2. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++