============================================================================== ============================================================================== 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 MER enterprise application for Sun Solaris PTF UK61129 for APAR PM22475 = Date 2010-10-15 = ============================================================================== ============================================================================== ============================================================================== A. About this document ---------------------- This PTF contains the MER enterprise application for use on a WebSphere Application Server running on Sun Solaris in conjunction with WebSphere BI for FN for z/OS. This readme document uses the following variables: The installation directory of MER enterprise application for Sun Solaris. The directory '/opt/IBM' is used in examples. Prerequisites ------------- The following WebSphere BI for FN for z/OS PTFs must be applied: - UK58117 for APAR PM07598 (SWIFT SR2010: NEW CHECKS AND RULES FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION) - UK59697 for APAR PM13490 (MESSAGE MANAGEMENT UPDATES FOR SWIFT SR2010 CHANGES) B. Summary of changes --------------------- APARs addressed by this PTF: PM22475 MM NAK CODES FOR SR2010 CHANGES (see functional changes below for details) Functional changes: - NAK codes changed for SR2010: B01, C01, C02, C03, C05, C28, C29, C32, C34, C35, C38, C39, C41, C42, C50, C58, C59, C62, C65, C71, C80, C87, C89, D07, D19, D25, D29, D36, D56, D57, D92, E03, E24, E37, E41, E57, E58, E59, E76, E77, E78, E80, E82, E84, E87, E99, G05, G08, G17, G24, H55, Knn, M75, S72, T03, T04, T14, T27, T39, T45, T47, T61, T85, T86, U00, V21, V62 - NAK codes new for SR2010: S76, V69, V70, V71, V72, V73, V74 - New functionality has been added to allow to use IBM Cognos report from within the WebSphere BI for FN Message Management V3.1.0 environment. For further information, please refer to documentation on the WebSphere BI for FN support web-site. Documentation updates: The following manuals have been changed: - none The following modules have been changed: /dnq_03_01/run/appsrv/dnq.app.main.ear C. Installation ---------------- This PTF requires the previous MER enterprise application for Sun Solaris V3.1.0.4 (UK58149 for APAR PM13495), and will overwrite partial installed files. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------- If the MER enterprise application is not deployed, deploy the MER enterprise application with dnqccins.py in step 3.2. If the MER enterprise application is already deployed by V3.1.0.4 (UK58149 for APAR PM13495), follow the steps of this section to update the MER enterprise application. 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. 2. Update the WebSphere Application Server environment - - - - - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. 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. 3.1 Remove the enterprise application ------------------------------------- Issue the following command with the user ID of the WebSphere Application Server operator (uwaso1) to remove the deployed application: /bin/wsadmin.sh -user -password -lang jython -f /dnqccrem.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. 3.2 Install the enterprise application -------------------------------------- 1. Create a directory which will store the resource files created by CDP. 2. Download the resource files in binary mode, includes - /com.ibm.dnf.CFGPF/dnqccins.properties - /com.ibm.dnf.CFGPF/dnqccmqc.properties to the directory . In addition, replace the placeholders "DNQvWCLUS" and "DNQvWSRV" in dnqccmqc.properties with the values according to the target WebSphere Application Server configuration. The values must be the same as assigned to "Cluster_name" and "Server_name" in dnqccins.properties. 3. Issue the following command with the user ID of the WebSphere Application Server operator (uwaso1) to deploy the application: /bin/wsadmin.sh -user -password -lang jython -f /dnqccins.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 directory created in step 1. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++