IBM corporation Readme file for WebSphere Partner Gateway 6.2 FixPack 3. Platforms: AIX, HP-UX, Linux, PowerLinux, Solaris, Windows Maintenance Delivery Vehicle type: 6.2.0-WS-WPG-FP3_Advanced.pak 6.2.0-WS-WPG-FP3_Enterprise.pak These installables can be used across all WebSphere Partner Gateway supported platforms. © Copyright International Business Machines Corporation 2010. 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.0.3 Readme Readme documentation for version 6.2 FixPack 3 IBM® WebSphere Partner Gateway, including installation-related instructions, prerequisites, and known issues. This fixpack includes and supersedes all previous fixpacks for the same version and edition of WPG. These notes describe the changes made in FixPack 6.2.0.3 of IBM WebSphere Partner Gateway, Enterprise and Advanced Editions. IMPORTANT: 6.2 FixPack 3 can be installed and uninstalled ONLY by using IBM® Update Installer for WebSphere® software. 6.2 Fixpack 3 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 FixPack 3 when WebSphere Partner Gateway is installed on an existing cell, see the technote http://www-01.ibm.com/support/docview.wss?uid=swg21402404. 2) For customers who have setup the Update Installer for WebSphere Partner Gateway already , would need to apply the pre-requisite APAR JR35713 before upgrading to 6.2 Fixpack 3. The 6.2.0.0-WS-WPG-TFJR35713.pak can be downloaded along with the 6.2 FP3 pak file. ================================================== Operating System, Server and Database support The WebSphere Partner Gateway Version 6.2.0.0 FixPack 3 extends support for the following Server and Database, other than those available in the base release. 1. WebSphere Application Server Network Deployment V6.1.0.29 2. IBM DB2 UDB V9.5 FixPack5 3. Red Hat Enterprise Linux Server 5.5 (32-bit and 64-bit) For more details, refer to system requirements: http://www-01.ibm.com/support/docview.wss?uid=swg27013981 ================================================== 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. Client Authentication for FTPS mode may not work when an invalid primary and a valid secondary certificates are uploaded. When using client authentication for FTPS mode in case of an expired primary certificate and a properly configured valid secondary certificate, the document processing fails. The transition of secondary to primary certificate happens in WebSphere Partner Gateway configuration. The workaround solution is to perform a restart of WebSphere Partner Gateway Document Manager server. 3. When Secondary to primary transition of a certificate happens, events "BCG240027- Certificate Is Expired" and "BCG108011-Secondary Certificate changed to Primary Certificate" may not get logged. 4. When SSL client authentication is configured for FTP scripting destination with FTPS mode enabled, and a revoked CA certificate is uploaded at the hub operator profile, the events "BCG240024 -CertPath validation failed" and "BCG240033 -No valid SSL client certificate found" may not get logged. The following specific workarounds would need to be applied: 1. When you attempt to install WebSphere Partner Gateway v6.2 GA DBLoader directly on Oracle 11.1.0.7, then the "ORA-22996: NEXT extent size is smaller than LOB chunksize" error gets generated .This problem has been resolved with WebSphere Partner Gateway 6.2 FixPack 3. Users intending to use Oracle 11.1.0.7 with WebSphere Partner Gateway 6.2 GA installation, would need to ignore the above error message, and apply WebSphere Partner Gateway 6.2 FixPack 3 immediately after installation of WebSphere Partner Gateway 6.2 GA. 2. When you attempt to install WebSphere Partner Gateway v6.2 GA DBLoader directly on DB2 9.5 FP5, then the installation may fail on Base .This problem has been resolved with WebSphere Partner Gateway 6.2 FixPack 3.Users intending to use DB2 9.5 FP5 with WebSphere Partner Gateway 6.2 GA installation, would need to ignore the above error message, and apply WebSphere Partner Gateway 6.2 FixPack 3 immediately after installation of WebSphere Partner Gateway 6.2 GA. 3. 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 below 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 above technote, do not need to perform the addition steps again. ==================================================== Installing WebSphere Partner Gateway 6.2 FixPack 3 IBM WebSphere Partner Gateway Version 6.2 FixPack 3 can be installed, ONLY by using IBM® Update Installer for WebSphere Software (7.0.0.1 and above). Installing the FixPack is a four step operation: Step A - Setup the IBM Update Installer environment. Step B - Take the backup of WebSphere Partner Gateway application Database. Step C - Apply needed pre-requisites Step D or Step E can be performed next based on whether you need to manually upgrade the DB or if the DB has to be upgraded 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 - Setup 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/, / responsefiles/ are performed. 3. Apply pre-requisite APAR JR35713 before upgrading to 6.2 Fixpack 3. This APAR will update the WPG 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. Step B - Taking the backup of existing database Take the backup of the existing WebSphere Partner Gateway Application database. This is a mandatory step, and the database backup taken at this point is to be retained and used, as necessary, during uninstallation of WebSphere Partner Gateway 6.2 FixPack 3. The backup step is required as 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 FixPack 2 is uninstalled. For more information on data back up and restore, see "Migrating the database" of WebSphere Partner Gateway Installation Guide. Step C - Apply needed pre-requisites Refer to the section at the begin of this page to know about the pre-requisites that need to be applied. Step D - Applying the FixPack - Upgrade WPG Application database automatically through UPDI Note: - Customers upgrading to 6.2 Fixpack 3 on DB2 8.1/8.2 please refer to http://www-01.ibm.com/support/docview.wss?uid=swg21426898 to upgrade the DB 1. In case of applying the FixPack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed); the 6.2 FixPack 3 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 The below given steps need to be performed on the nodes where Receiver hub, Console hub, and DocMgr hub (WebSphere Partner Gateway components) are installed. You do not have to apply this FixPack on bcgapps location. 2. Make sure that value for -Wupdate.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 FixPack 3 file using update installer. 4. Following are the prerequisites for 6.2 FixPack 3 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 FixPack 3 pak file. 9. In the Available Maintenance Package to Install window, ensure that the check box for FixPack 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 will start and after it completes, an appropriate message, that is, Success or Failed will be displayed. Verify the logs present under /logs/update/<6.2 FP3 pak name>.install for more information on the FixPack installation. 10. Perform all the above steps on all machines where Receiver hub, Console hub, and DocMgr hub (WebSphere Partner Gateway components) are installed. Step E - Applying the FixPack - Manually upgrade WPG Application database. Note: - The FixPack .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. These ^M characters would mandatorily need to be removed, before performing manual steps. 1. In case of applying the FixPack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed); the 6.2 FixPack 3 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 The below given steps need to be performed on the nodes where Receiver hub, Console hub, and DocMgr hub (WebSphere Partner Gateway components) are installed. You do not have to apply this FixPack on bcgapps location. 2. Make sure that value for -Wupdate.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 FixPack 3 file using update installer. 4. Following are the prerequisites for 6.2 FixPack 3 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 FixPack 3 pak file. 9. In the Available Maintenance Package to Install window, ensure that the check box for FixPack 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 will start and after it completes, an appropriate message, that is, Success or Failed will be displayed. Verify the logs present under /logs/update/<6.2 FP3 pak name>.install for more information on the FixPack installation. 10. Perform all the above steps on all machines where Receiver hub, Console hub, and DocMgr hub (WebSphere Partner Gateway components) are installed. 11. Stop all WPG servers before performing the next few steps to upgrade the database. 12. To manually upgrade the DB now follow the below listed steps: Run the following commands On DB2 Note: - Customers upgrading to 6.2 Fixpack 3 on DB2 8.1/8.2 please refer to http://www-01.ibm.com/support/docview.wss?uid=swg21426898 to upgrade the DB a. UNIX: su - db2inst1 WINDOWS: Start the DB2CLP and make sure you are logged in as the user that owns the DB2 database. b. start (if the database is not started) Steps required to upgrade WPG APPLICATION DATABASE. c. db2 connect to bcgapps d. cd /WPGUpdate/6.2.0-WS-WPG-FP3_Enterprise/database/db2 e. Run the applicable scripts from below. Determine the level you are starting from. (That is from V6.2.0.0, run all three scripts, from V6.2.0.1, only the last two, from V6.2.0.2, only the last script.) 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 f. Then run the Set_Grants script using the command given below: db2 -td! -f /scripts/DB2/Set_Grants.sql -z /home/db2inst1/Set_Grants.log Steps required to be upgrade WPG MAS DATABASE. Not applicable for Simple Mode installation. The next set of commands need to be run only if you are upgrading from 6.2.0.0 to 6.2.0.3. If you are upgrading from 6.2.0.1/6.2.0.2 to 6.2.0.3 the next few steps do not need to be executed. g. Use the command to disconnect from application database. db2 connect reset h. Log on to the WPG mas database db2 connect to E.g. db2 connect to bcgmas i. Run the below mentioned command to fetch the configuration parameter of mas database. db2 get db cfg for >> "/mascfg.log" E.g. db2 get db cfg for bcgmas >> "/home/db2inst1/mascfg.log" j. Open file mascfg.log and search for "LOGFILSIZ" parameter .If the value for this 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. cd /WPGUpdate/6.2.0-WS-WPG-FP3_Enterprise/database/oracle c. Run the applicable scripts from below. Determine the level you are starting from. (That is from V6.2.0.0, run all three scripts, from V6.2.0.1, only the last two, from V6.2.0.2, only the last script.)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 spool off d. Then run the Grants_Syns script using the command given below: sqlplus -L bcgapps/ @/bcgdbloader/scripts/Oracle/Grants_Syns.sql ===================================================== Uninstalling WebSphere Partner Gateway 6.2 FixPack 3 IBM WebSphere Partner Gateway Version 6.2 FixPack 3 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 FixPack 3 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 Note: In case of uninstalling the FixPack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed), the FixPack .pak file needs to 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 needs to 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 FixPack 3 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 the 6.2 FixPack 3 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 on which location. 7.After this the uninstallation will start and once it is complete the appropriate message i.e., Success or Failed will be displayed. Please verify the logs <.updateconfig.log> present under /logs/ update/<6.2 FixPack 3 pak name>.uninstall for more information on the FixPack uninstallation. Note: These steps should be performed in all machines where WebSphere Partner Gateway components are installed. Step B - Restoring the Application Database Once the uninstallation is successfully complete, restore the database using the backup taken before applying the FixPack. ===================================================== List of Fixes in WebSphere Partner Gateway 6.2 FixPack 3 ===================================================== Component: Archiver Apar: JR34164 Description: Sometimes the Restored documents were not visible in the "Search Restored Documents" page of the console. On click of raw restored document, a "Message not found" error was displayed. Though DB data was restored properly, the file data was not getting resolved. Apar: JR35963 Description: WebSphere Partner Gateway archiver failed to archive data when DB2 was installed in Swedish locale. Component: AS2 / Document Manager Apar: JR35029 Description: On AIX, randomly, encrypted and signed documents sent to https destinations failed during the first delivery attempt, but were successfully delivered in the second gateway retry. However, the trading partner received both transmissions with the first one having only the http header without the message body. The second transmission had both https header and message body. Component: Console Apar: JR33533 Description: When using WebSphere Partner Gateway Console to manage the FTP server, the start and stop buttons did not work. This error was seen when console was installed using hostname and ftp server was installed using IP or vise versa. An error message was displayed - "FTP Console server not reachable. Please verify the host name and port number." Apar: JR34499 Description: The Destination Queue Summary page displayed a blank page with only the "close window" button. Apar: JR34624 Description: While creating a new FTP user in an LDAP enabled hub, the user is not able to set the password. Apar: JR34635 Description: The Console was not saving the create page of volume alert with the correct frequency. This problem occurred whenever the defined frequency was more than 7 days. Apar: JR34680 Description: When updating the password for a FTP user, if the password did not adhere to the rules, an exception was written to the log. But a warning message was not displayed in the console. Apar: JR35576 Description: In the validation maps page, the search criteria was not maintained when results were displayed. The same problem persisted whenever the user navigated to the first page of the results. Apar: JR35961 Description: While uploading a new chain certificates in WebSphere Partner Gateway console, the error 'Cert path is not valid' occurred on click of "Validate" button. This error was not observed after restarting the WebSphere Partner Gateway servers. The issue was because the cache refresh was not happening and the new certificates were not loaded in the cache. Component: Console/EBMS Apar: JR35973 Description: The ebMS Viewer and the document viewer displayed incorrect timestamp. The timestamp for the retried document was same as the timestamp of the original received document. Component: Console/Resend Apar: JR35962 Description: Target resend from console for Rosettanet document was failing. Apar: JR35964 Description: Target resend from console for AS document was failing. Apar: JR35966 Description: Target resend from console for ebMS document was failing. Component: Destination/Receivers Apar: JR35217 Description: Web Mail box feature is included in WebSphere Partner gateway. For more details about this feature and its implementation steps, refer to the http://www-01.ibm.com/support/docview.wss?uid=swg27018316. Component: Document Manager Apar: JR34850 Description: From this fix pack onwards, BinaryChannelParse will not override the Document ID in case it is already set by a "Receiver User Exit". Apar: JR35243 Description: From this fix pack onwards, the performance has been improved for summary engine. Apar: JR35574 Description: AS transactions were failing because the CHARSET attribute was getting set to "N/A" by default. Apar: JR35960 Description: When WebSphere Partner Gateway was installed in distributed mode with multiple routers, it intermittently throwed an error - "*_PROT.TMP DOES NOT EXIST". This triggered the "BCG250002" event while routing the documents. Apar: JR35971 Description: For Oracle, during custom XML transactions, WebSphere Partner Gateway intermittently logged the error "SQLException ORA-00001: unique constraint violated". Component: Document Manager/EBMS Apar: JR35152 Description: The packaged ebMS document in WebSphere Partner Gateway contains a MessageID element. Earlier, the MessageID had the value provided by the x-aux-message-id. But as the ebMS specification mandates that the generated MessageId has to have a unique value each time, the MessageID is set with a unique value from the backend. Apar: JR35430 Description: The ebMS transactions were not possible because the retry count was set to NULL. A "NumberFormatException" was generated, which led to the failure of all ebMS transactions. Apar: JR35972 Description: Both retried documents of ebMS and outbound acknowledgement were posted to internal queue of MAIN_INBOUNDQ. This led to message pile up on the MAIN_INBOUNDQ. As a result, critical messages or acknowledgements on the MAIN_INBOUNDQ were picked up after a lot of delay in turn generating unwanted ebMS retries. Apar: JR35977 Description: XML Signature verification failed for signed ebMS document whenever there was multiple verification certificates uploaded onto the receiver hub. Component: EDI Apar: JR35182 Description: There was a problem with Enveloper locking, and because of which some EDI Documents were getting stuck in "In-Progress" state indefinitely. Apar: JR34595 Description: Large EDI documents failed during De-Enveloping, with BufferOverFlow Exception. Apar: JR34598 Description: From this fix pack onwards, the inbound EDIFACT Envelope having Alphanumeric Interchange Control Number will not be rejected. Component: Receiver/FTP Scripting Apar: JR35974 Description: In case of FTP Scripting receivers with LOCK USER set to Yes, stray locks in the LG_LOCK_FTPSCRIPT table resulted in indefinite wait time for a lock. As a result, the FTP Scripting receivers were not polling. Component: Install Apar: JR34912 Description: Earlier, the WebSphere Partner Gateway Fixpacks could not be installed on DB2 8.1/8.2. This issue is rectified and steps to apply a Fixpack on Db2 8.1/8.2 are available at http://www-01.ibm.com/support/docview.wss?uid=swg21426898. Apar: JR36107 Dexcription: When applying WPG 6.2 Fix Pack 1 or Fix Pack 2. Database updates would fail when applying, if the sql files were run manually. An issue was found with ^M characters in the sql text files used by WPG to update the BCGAPPS and BCGMAS databas, which would effect Unix systems. ===================================================== Notices and trademarks: http://www.ibm.com/legal/copytrade.shtml Terms of use: http://www.ibm.com/legal/us/en/