IBM corporation Readme file for WebSphere Partner Gateway V6.2.1 FixPack 2. Platforms: AIX, Linux, Linux pSeries, Solaris, Windows Note: WebSphere Partner Gateway V6.2.1 FixPack 2 is not supported on HP-UX Maintenance Delivery Vehicle type: 6.2.1-WS-WPG-FP2_Advanced.pak 6.2.1-WS-WPG-FP2_Enterprise.pak These installables can be used across all WebSphere Partner Gateway supported platforms. © Copyright International Business Machines Corporation 2012. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ================================================== WebSphere Partner Gateway 6.2.1.2 Readme This document is the Readme documentation for version 6.2.1 FixPack 2 IBM® WebSphere Partner Gateway, which includes installation-related instructions, prerequisites, and known issues. This FixPack includes and supersedes all previous FixPacks for the same version and edition of WebSphere Partner Gateway. These notes describe the changes made in FixPack 6.2.1.2 of IBM WebSphere Partner Gateway, Enterprise and Advanced Editions. IMPORTANT: 6.2.1 FixPack 2 can be installed and uninstalled ONLY by using IBM® Update Installer for WebSphere® software. FixPack 6.2.1.2 can be installed with Administrative security enabled for only "Standalone LDAP registry" realm definition. For details on how to configure Update Installer for WPG refer to IBM®WebSphere® Partner Gateway Update Installer available at: http://www-01.ibm.com/support/docview.wss?uid=swg27015150. ================================================== Prerequisites 1)For applying 6.2.1 Fixpack 2 when WebSphere Partner Gateway is installed on an existing cell, see the technote on Prerequisite steps to be followed before using Update Installer with WebSphere Partner Gateway v6.2 on existing cell. 2)For customers who have already setup the IBM® Update Installer for WebSphere Partner Gateway, would need to apply APAR JR38213 ( If not applied already )as prerequisite before upgrading to 6.2.1 Fixpack 2. The 6.2.0.0-WS-WPG-TFJR38213.pak can be downloaded along with 6.2.1-WS-WPG-FP2_Enterprise.pak file. 3)Make sure WPG integrated FTP and SFTP management servers are stopped when you apply Fixpack on hub location. 4)With this Fixpack onwards SFTP receiver and destination do not depend on WebSphere FTP adapter. Users who are using or planning to use SFTP client must follow the instructions in this link http://www-01.ibm.com/support/docview.wss?uid=swg27027527 5)Customers who are using WPG 6.2.1.2 with Oracle 11.2.0.x , its mandatory to follow instructions give in given link after applying WPG 6.2.1 FP2 - http://www-01.ibm.com/support/docview.wss?uid=swg27028554 6)WPG 621 Fixpack 2 pak file should be transferred in Binary mode on Non-Windows systems. In case of performing ASCII transfers or using Binary transfers with some FTP clients, the ^M characters may get introduced in the transferred contents of the .pak file. If user is applying database scripts manually these ^M characters should be mandatorily be removed before performing manual steps ================================================== Server and Database support The WebSphere Partner Gateway Version 6.2.1 FixPack 2 extends support for the following WAS ,WMQ and Database, other than those available in the base release. 1. WebSphere Application Server Network Deployment V6.1.0.43 2. WebSphere Application Server Network Deployment V7.0.0.23 3. IBM DB2 UDB V9.1 FixPack 11 4. IBM DB2 UDB V9.5 FixPack 9 5. IBM DB2 UDB V9.7 FixPack 5 6. Oracle 11.2.0.3 7. IBM WebSphere MQ 7.0.1.8 8. IBM WebSphere MQ 7.1.0.1 ( More additional information please visit link http://www-01.ibm.com/support/docview.wss?uid=swg21577137 ) For more details, refer to system requirements at: http://www-01.ibm.com/support/docview.wss?uid=swg27020525. ================================================== Known problems and workarounds The following problems exist in this FixPack: 1. The Partner Migration export on DB2 does not import on Oracle for EDI maps. This issue is found while importing a map using the console on Oracle and then importing some exported data from a DB2 system that has the same map ID. This corrupts the existing map on Oracle, and does not allow the same map to get imported in WebSphere Partner Gateway (using Import Utility and console). 2. In this FixPack, when you upload a JKS certificate after uploading a PEM for SFTP server authentication, and when you restart the SFTP server, an error may get logged in the SFTP log file. The workaround to resolve this problem is to restart the SFTP server. 3. No validation is performed on certificates uploaded using the "Load SFTP keys" page. More information regarding the same is available at http://www.ibm.com/support/docview.wss?uid=swg21450676 4. When WPG MAS DB is hosted on DB2 and DB2 is upgraded from any version to DB2 v9.1 FP5 , when you start MAS cluster ,messaging engine does not start . To resolve this issue refer to link http://www-304.ibm.com/support/docview.wss?uid=swg21590281 5. WebSphere Partner Gateway 6.2 GA installation fails on Oracle 11.2.x Following specific workaround would need to be applied for using Oracle 11.2.x with WPG 6.2.1.2 http://www-01.ibm.com/support/docview.wss?rs=2310&uid=swg21598385 The following specific workarounds would need to be applied: 1. Certificate expiry related events and alerts were not getting triggered. From 6.2 FixPack 2 onwards, such events and alerts will be triggered. Users who want to use this fix, need to follow the additional steps provided in the following link, after applying the FixPack http://www.ibm.com/support/docview.wss?uid=swg21414906. Users who are upgrading from 6.2 FixPack2 to current FixPack, and have performed the additional steps as provided in the fix readme, need not perform the additional steps again. 2. When a customer uninstalls WPG 6.2.1 Fixpack 2 to revert to 6.2 FP4a level, and then tries application of WPG 6.2.1 Fixpack 2 again, an error stating - "Unsupported product" may be seen. To resolve this go to "/properties/version" location and edit the WPG.product file. Here, set the version from 6.2.0.4a to 6.2.0.4 ==================================================== Installing WebSphere Partner Gateway 6.2.1 FixPack 2 IBM WebSphere Partner Gateway Version 6.2.1 FixPack 2 can be installed, ONLY by using IBM® Update Installer for WebSphere Software (7.0.0.1 and above). Along with this Fix Pack we are introducing a Tool - WPG Update Installer (UPDI) Validator. The WPG UPDI validator can setup the UPDI, deploy the UPDI Validator console changes,and validate the UPDI response file values. This utility is provided so as to ease the WPG UPDI setup and validate response file values. For more details on this tool please refer to url - http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27022133 Note : The below steps are also applicable, when WPG Customer has already migrated the WPG profiles to WebSphere Application Server 7. Installing the FixPack is a five step operation: Step A - Setting up the IBM Update Installer environment Step B - Performing the backup of WPG Application Database Step C - Apply the needed prerequisites. Subsequently, you can perform Step D or Step E based on whether you need to manually upgrade the DB, or upgrade it automatically through UPDI Step D - Applying the FixPack - Upgrade WPG Application database automatically through UPDI Step E - Applying the FixPack - Manually upgrade WPG Application database Step A - Setting up the IBM Update Installer environment 1. Download the IBM® Update Installer for WebSphere Software from http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg24020212. 2. Follow the instructions at: http://www-01.ibm.com/support/docview.wss?uid=swg27015150, to download and apply the WebSphere Partner Gateway specific Update Installer changes. Ensure that the necessary updates to the responsefile bcgupdate_.txt present under /responsefiles/ and / responsefiles/ are performed. 3. Apply APAR JR38213 prerequisite before upgrading to 6.2.1 FixPack 2. This APAR will update the WebSphere Partner Gateway UPDI related jars and upgrade these to the latest levels. For customers who have already setup UPDI as per step 1 and 2 only need to follow step 3. Now, IBM Update Installer is ready to install WebSphere Partner Gateway fixes and FixPacks on your environment. Note: For applying 6.2.1 FixPack 2 when WebSphere Partner Gateway is installed on an existing cell, see the technote at http://www-01.ibm.com/support/docview.wss?uid=swg21402404. Step B - Performing the backup of WPG Application Database Performing the backup of WPG Application Database is a mandatory step, and the database backup taken at this point should be retained and used, as necessary, during uninstallation of WebSphere Partner Gateway 6.2.1 FixPack 2. The backup step is required because the uninstallation of the FixPack using IBM Update Installer does not restore the database to its previous version of WebSphere Partner Gateway. The database restoration step is to be performed manually, and it is mandatory whenever WebSphere Partner Gateway 6.2.1 FixPack 2 is uninstalled. For more information on data backup and restore, see "Migrating the database" topic of WebSphere Partner Gateway Installation Guide. Step C - Apply the needed prerequisites Refer to the section at the beginning of this page to know and apply the needed prerequisites. Step D - Applying the FixPack - Upgrade WebSphere Partner Gateway Application database automatically through UPDI 1. In case of applying the FixPack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed); the 6.2.1 FixPack 2 pak file needs should be applied using the Update Installer on all machines that host the following WebSphere Partner Gateway components in the specified order: a. WebSphere Partner Gateway Deployment Manager b. WebSphere Partner Gateway Hub c. WebSphere Partner Gateway Application Database d. WebSphere Partner Gateway MAS Database e. WebSphere Partner Gateway Integrated FTP Server The following steps should be performed on the nodes where Receiver hub, Console hub, and DocMgr hub (WebSphere Partner Gateway components) are installed. 2. Make sure that value of -W update.RunSQLFiles is set to "Yes" in the Update Installer response parameter file. 3. In case of applying the FixPack on WebSphere Partner Gateway simple mode installation, provide the product location corresponding to the WebSphere Partner Gateway Hub location to apply the 6.2.1 FixPack 2 file using update installer. 4. Following are the prerequisites for 6.2.1 FixPack 2 installation: a) While applying the FixPack on simple mode deployment, make sure that the server is up and running. b) Make sure that the Deployment Manager (DMGR) and all node agents are up and running for simple distributed and fully distributed deployments. c) Stop all WebSphere Partner Gateway clusters in case of simple distributed and fully distributed deployment before applying the FixPack. 5. Execute the script "update.bat" for Windows and "update.sh" for non-Windows to launch Update Installer. 6. In the Product Selection window, enter the DMGR installed location as the value for directory path. 7. In the Maintenance Operation Selection window, select Install maintenance package. 8. In the Maintenance Package Directory Selection window, provide the location of the 6.2.1 FixPack 2 pak file. 9. In the Available Maintenance Package to install window, ensure that the check box for 6.2.1 FixPack 2 pak file is selected. Note that, when using the IBM Update Installer for WebSphere Partner Gateway, select only one pak file at a time for installation else it may give unexpected results. Installation Summary window will list the details about the pak file to be installed on selected location. Installation begins. When the installation completes, an appropriate installation success or failure message displays. Verify the logs present under /logs/update/<6.2.1 FixPack 2 pak name>.install for more information on the FixPack installation. 10. Perform all the above steps on all machines where Receiver hub, Console hub, DocMgr hub and Integrated FTP server (WebSphere Partner Gateway components) are installed. Step E - Applying the FixPack - Manually upgrade WPG Application database 1. In case of applying the FixPack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed); the 6.2.1 FixPack 2 pak file needs to be applied using update installer on all machines that host the following WebSphere Partner Gateway components in the specified order: a. WebSphere Partner Gateway Deployment Manager b. WebSphere Partner Gateway Hub c. WebSphere Partner Gateway Application Database d. WebSphere Partner Gateway MAS Database e. WebSphere Partner Gateway Integrated FTP Server 2. Make sure that the value for -W update.RunSQLFiles is set to "No" in the Update Installer response parameter file. 3. In case of applying the FixPack on WebSphere Partner Gateway simple mode installation, provide the product location corresponding to the WebSphere Partner Gateway Hub location to apply the 6.2.1 FixPack 2 file using update installer. 4. Following are the prerequisites for 6.2.1 FixPack 2 installation: a) While applying the FixPack on simple mode deployment, make sure that the server is up and running. b) Make sure that the Deployment Manager (DMGR) and all node agents are up and running for simple distributed and fully distributed deployments. c) Stop all WebSphere Partner Gateway clusters in case of simple distributed and fully distributed deployment before applying FixPack. 5. Execute the script "update.bat" for Windows and "update.sh" for non-Windows to launch Update Installer. 6. In the Product Selection window, enter the DMGR installed location as the value for Directory Path. 7. In the Maintenance Operation Selection window, select Install maintenance package. 8. In the Maintenance Package Directory Selection window, provide the location of the 6.2.1 FixPack 2 pak file. 9. In the Available Maintenance Package to install window, ensure that the check box for 6.2.1 FixPack 2 pak file is selected. Note that, when using the IBM Update Installer for WebSphere Partner Gateway, select only one pak file for installation, else it may give unexpected results. Installation Summary window will list the details about the pak file to be installed on selected location. Installation begins. When the installation completes, an appropriate installation success or failure message displays. Verify the logs present under /logs/update/<6.2.1 FixPack 2 pak name>.install for more information on the FixPack installation. 10. Perform all the above steps on all machines where Receiver hub, Console hub, DocMgr hub and Integrated FTP Server (WebSphere Partner Gateway components) are installed. 11. Stop all WebSphere Partner Gateway servers before performing the next few steps to upgrade the database. 12. To manually upgrade the DB, follow the steps given below: Run the following commands: On DB2 a. UNIX: su - db2inst1. WINDOWS: Start the DB2CLP and make sure you are logged in as the user that owns the DB2 database. Steps required to upgrade WPG Application Database: b. Start the database, if it is not already started. c. db2 connect to bcgapps d. cd /WPGUpdate/6.2.1-WS-WPG-FP2_Enterprise/database/db2 e. Run the following applicable scripts. Determine the level you are starting from (that is, from V6.2.0.0, run all eight scripts, from V6.2.0.1, only the last seven, from V6.2.0.2, only the last six scripts and so on.) db2 -td! -f 6.2.0.0_to_6.2.0.1/BCGUpgrade_620_620FP1.sql -z /home/db2inst1/BCGUpgrade_620_620FP1.log. db2 -td! -f 6.2.0.1_to_6.2.0.2/BCGUpgrade_620FP1_620FP2.sql -z /home/db2inst1/BCGUpgrade_620FP1_620FP2.log. db2 -td! -f 6.2.0.2_to_6.2.0.3/BCGUpgrade_620FP2_620FP3.sql -z /home/db2inst1/BCGUpgrade_620FP2_620FP3.log. db2 -td! -f 6.2.0.3_to_6.2.0.4/BCGUpgrade_620FP3_620FP4.sql -z /home/db2inst1/BCGUpgrade_620FP3_620FP4.log. db2 -td! -f 6.2.0.4_to_6.2.0.5/BCGUpgrade_620FP4_620FP5.sql -z /home/db2inst1/BCGUpgrade_620FP4_620FP5.log. db2 -td! -f 6.2.0.5_to_6.2.1.0/BCGUpgrade_620FP5_621.sql -z /home/db2inst1/BCGUpgrade_620FP5_621.log db2 -td! -f 6.2.1.0_to_6.2.1.1/BCGUpgrade_621_621FP1.sql -z /home/db2inst1/BCGUpgrade_621_621FP1.log db2 -td! -f 6.2.1.1_to_6.2.1.2/BCGUpgrade_621FP1_621FP2.sql -z /home/db2inst1/BCGUpgrade_621FP1_621FP2.log f. Then run the "Set_Grants" script using the following command: db2 -td! -f /scripts/DB2/Set_Grants.sql -z /home/db2inst1/Set_Grants.log Steps required to upgrade WPG MAS DATABASE. Not applicable for Simple Mode installation. The next set of commands should be run only if you are upgrading from 6.2.0.0 to 6.2.1.2. Note: If you are upgrading from 6.2.0.1 or higher to 6.2.1.2, do not execute the following steps: g. Run the following command to disconnect from application database: db2 connect reset h. Run the following command to log on to the WebSphere Partner Gateway MAS database: db2 connect to For example, db2 connect to bcgmas i. Run the following command to fetch the configuration parameter of the MAS database: db2 get db cfg for >> "/mascfg.log" For example, db2 get db cfg for bcgmas >> "/home/db2inst1/mascfg.log" j. Open the mascfg.log file, and search for "LOGFILSIZ" parameter. If the value is equal to or more than 10000, then do not execute the next step. k. Run the following command: db2 "UPDATE DATABASE CONFIGURATION FOR < WPG mas database > USING logfilsiz 10000 immediate" On Oracle: Run the following commands: a. UNIX: su - oracle. WINDOWS: Make sure you are logged in as the owner of the Oracle database. b. Go to the following location: cd /WPGUpdate/6.2.1-WS-WPG-FP2_Advanced/database/oracle c. Run the following applicable scripts. Determine the level you are starting from (that is from V6.2.0.0, run all eight scripts, from V6.2.0.1, only the last seven, from V6.2.0.2, only the last six scripts and so on). The spool commands need to be run irrespective of the FixPack you are upgrading from. spool /home/oracle/FPUpgrade.log sqlplus -L bcgapps/ @6.2.0.0_to_6.2.0.1/BCGUpgrade_620_620FP1.sql sqlplus -L bcgapps/ @6.2.0.1_to_6.2.0.2/BCGUpgrade_620FP1_620FP2.sql sqlplus -L bcgapps/ @6.2.0.2_to_6.2.0.3/BCGUpgrade_620FP2_620FP3.sql sqlplus -L bcgapps/ @6.2.0.3_to_6.2.0.4/BCGUpgrade_620FP3_620FP4.sql sqlplus -L bcgapps/ @6.2.0.4_to_6.2.0.5/BCGUpgrade_620FP4_620FP5.sql sqlplus -L bcgapps/ @6.2.0.5_to_6.2.1.0/BCGUpgrade_620FP5_621.sql sqlplus -L bcgapps/ @6.2.1.0_to_6.2.1.1/BCGUpgrade_621_621FP1.sql sqlplus -L bcgapps/ @6.2.1.1_to_6.2.1.2/BCGUpgrade_621FP1_621FP2.sql spool off d. Then run the "Grants_Syns" script using the following command: sqlplus -L bcgapps/ @/bcgdbloader/scripts/Oracle/Grants_Syns.sql Uninstalling WebSphere Partner Gateway 6.2.1 FixPack 2 IBM WebSphere Partner Gateway Version 6.2.1 FixPack 2 can be uninstalled using IBM® Update Installer for WebSphere Software (7.0.0.1 and above). Note: Uninstallation of the FixPack using Update Installer does not restore the database to its previous version of WebSphere Partner Gateway. The database restoration step is to be performed manually, and is mandatory whenever WebSphere Partner Gateway 6.2.1 FixPack 2 is uninstalled. Uninstalling the FixPack is a two step operation: Step A - Uninstall the FixPack using IBM Update Installer Step B - Restore the WebSphere Partner Gateway application Database Step A - Uninstalling the FixPack using IBM Update Installer Note: In case of uninstalling the FixPack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed), the FixPack .pak file should be uninstalled using IBM Update Installer on all machines that host the following WebSphere Partner Gateway components in the specified order: a. WebSphere Partner Gateway Hub b. WebSphere Partner Gateway Deployment Manager In case of uninstalling the FixPack on WebSphere Partner Gateway simple mode installation, the FixPack .pak file should be uninstalled using IBM Update Installer, providing the product location as corresponding to the location of WebSphere Partner Gateway Hub. Following are the prerequisites for 6.2.1 FixPack 2 uninstallation: 1. Stop the WebSphere Partner Gateway servers. 2. Go to the IBM® Update Installer installed location, and launch the same by executing the script "update.bat" for Windows and "update.sh" for non-Windows. 3. Provide the Directory Path in the Product Selection window as the DMGR installed location. 4. In the Maintenance Operation Selection window, select Uninstall maintenance package. 5. Select the maintenance package to uninstall; here, it is the 6.2.1 FixPack 2 pak file. Note that, when using the IBM Update Installer for WebSphere Partner Gateway, only one pak file should be selected for uninstallation, else it may give unexpected results. 6. Uninstallation Summary window will list the details about the pak file to be uninstalled. 7. After this, the uninstallation begins, and when it completes, an appropriate uninstallation success or failure message displays. Please verify the logs <.updateconfig.log> present under /logs/ update/<6.2.1 FixPack 2 pak name>.uninstall for more information on the FixPack uninstallation. Note: These steps should be performed on all machines where WebSphere Partner Gateway components are installed. Step B - Restore the WebSphere Partner Gateway application Database Once the uninstallation completes successfully, restore the database using the backup taken before applying the FixPack. ========================================================== List of Fixes in WebSphere Partner Gateway 6.2.1 FixPack 2 ========================================================== Component: Console Apar: JR41899 Description: Default destinations for Partner connection were not being shown on Connection advance search page on WPG console. Apar: JR40569 Description: The Home directory of any FTP user on FTP configuration page on WPG console is enhanced to accept upto 128 characters. Earlier only 30 characters could be entered in this field. Apar: JR40992 Description: Community console fails to upload WSDL file, issuing message: "Error Uploading file". Apar: JR41094 Description: Deleted ftp users were being shown in the search result of FTP User Management page on WPG console. Apar: JR40042 Description: Now with this fixpack WPG event Viewer and document viewer shows source IP as well , so as to know where the request is coming from. Component: Summary Engine Apar: JR40801 Description: The number of messages received was incorrectly shown on summary report page on WPG console. Component: Install Apar: JR42689 Description: Added support for Oracle version 11.2.0.x from this Fixpack. To use this Oracle version with WPG 6.2.1.2 follow instructions given in link - http://www.ibm.com/support/docview.wss?uid=swg27028554 Apar: JR41520 Description: When Update Installer is used to apply any fix/fixpack on WPG in silent mode , the response file path specified in the update.sh/.bat command line, should always be WPG UPDI default directory and default response file name. Please refer to this technote for more inforamation.http://www.ibm.com/support/docview.wss?uid=swg21576337 Component: Archiver Apar: JR40913 Description: WPG Archiver was failing if any transaction was made using Integrated FTP/SFTP server in WPG. Component: Partner Migration Apar: JR41310 Description: Partner Migration utility was not able to export SFTP receiver handlers. Component: Event Engine Apar: JR41321 Description: Event BCG103203 was getting issued wrongly for successfully delivered documents. Component: ebMS Apar: JR41454 Description: An ebMS acknowledgements with missing mime headers (which WPG expects as per ebMS specifications) was always displayed with in-progress state on WPG console. Apar: JR40341 Description: Added support for multiple CPAs between two partners. For more information refer to link . http://www-01.ibm.com/support/docview.wss?rs=2310&uid=swg21598956 Apar: JR39721 Description:According to the ebMS 2.0 specification it is recommended to have 'start' parameter in ebMS document header.This is corrected. Apar: JR40787 Description: When a document (non ebMS) with source packaging as Backend Integration is being processed by WPG, Document ID appearing on Document Viewer was same as x-aux-system-msg-id. Now with this Fixpack this value will be same as x-aux-msg-id header. Apar: JR40844 Description: When an ebMS flow configured for retries (e.g. setting Retry count and Retry interval), TimeToLive and timestamp values of an identical retried message are retained from the original document. Apar: JR41174 Description: The char set value contained with double quotes in ebMS headers were not be accepted by WPG. This has been fixed. Component: Database Apar: JR40148 Description: To update WPG supplied DB2 jars with later levels of DB2 jars, please follow the steps in this - http://www-304.ibm.com/support/docview.wss?uid=swg21509070 Component: Migration Apar: JR39622 Description: If a WPG 6.2 was migrated from older releases (WPG v6.0.x and WPG v6.1.0.x) certificates were not getting uploaded using WPG console. Component : RNIF Apar: JR41691 Description: WPG was failing validation of RosettaNet schema PIP when configured for a Custom XML to RNIF(v2.00) flow. In the current fixpack the validation happens successfully Apar: JR40212 Description: The