IBM corporation Readme file for WebSphere Partner Gateway V6.2.1 FixPack 4. Platforms: AIX, Linux, PowerLinux, Solaris, Windows Note: WebSphere Partner Gateway V6.2.1 FixPack 4 is not supported on HP-UX Maintenance Delivery Vehicle type: 6.2.1-WS-WPG-FP4_Advanced.pak 6.2.1-WS-WPG-FP4_Enterprise.pak These installables can be used across all WebSphere Partner Gateway supported platforms. © Copyright International Business Machines Corporation 2015. 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.4 Readme This document is the Readme documentation for version 6.2.1 FixPack 4 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.4 of IBM WebSphere Partner Gateway, Enterprise and Advanced Editions. For customers who are planning to setup WebSphere Partner Gateway v6.2.1.x in new machine, the WebSphere Partner Gateway v6.2 passport advantage eImage is refreshed with new media (eImage only) and includes the 6.2.1.4 Fix Pack on or after Apr 10, 2015. IMPORTANT: 6.2.1 FixPack 4 can be installed and uninstalled ONLY by using IBM® Update Installer for WebSphere® software. FixPack 6.2.1.4 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 4 when WebSphere Partner Gateway is installed on an existing cell, see the technote at http://www-01.ibm.com/support/docview.wss?uid=swg21402404. 2) For customers who have already setup the IBM® Update Installer for WebSphere Partner Gateway, would need to apply APAR JR47647 ( If not applied already )as prerequisite before upgrading to 6.2.1 FixPack 4. The 6.2.1.0-WS-WPG-IFJR47647.pak can be downloaded along with 6.2.1-WS-WPG-FP4_Advanced.pak file. 3) Make sure WPG integrated FTP and SFTP management servers are stopped when you apply fixpack on hub location. 4) From 621 fixpack 2 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 http://www.ibm.com/support/docview.wss?uid=swg27028554, if not already done. 5) Customers who are using WPG 6.2.1.4 with Oracle 11.2.0.x , its mandatory to follow instructions given in http://www-304.ibm.com/support/docview.wss?uid=swg27027527 after applying WPG 6.2.1 FP4, if not already done. 6) WPG 621 FixPack 4 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 4 extends support for the following Server ,WMQ and Database, other than those available in the base release. 1. WebSphere Application Server Network Deployment V6.1.0.47 2. WebSphere Application Server Network Deployment V7.0.0.35 3. WebSphere Application Server Network Deployment V8.5.5.4 (only JDK 6 is supported) 4. IBM DB2 UDB V9.1 Fixpack 12 5. IBM DB2 UDB V9.5 Fixpack 10 6. IBM DB2 UDB V9.7 Fixpack 10 7. IBM DB2 UDB V10.1 Fixpack 4 8. IBM DB2 UDB V10.5 Fixpack 5 9. Oracle 11.2.0.4 10. Oracle 12.1.0.1 11. IBM WebSphere MQ 7.0.1.12 12. IBM WebSphere MQ 7.1.0.6 13. IBM WebSphere MQ 7.5.0.3 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.4 http://www-01.ibm.com/support/docview.wss?rs=2310&uid=swg21598385 6. Certificate expiry related events and alerts were not getting triggered. From 6.2 FixPack 3 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. 7. When a customer uninstalls WPG 6.2.1 FixPack 4 to revert to 6.2 FP4a level, and then tries application of WPG 6.2.1 FixPack 4 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 8. WPG 621 FP4 application fails on WPG 621 FP1 when installed with DB2. Please refer to http://www-01.ibm.com/support/docview.wss?uid=swg21701457 for details. ==================================================== Installing WebSphere Partner Gateway 6.2.1 FixPack 4 IBM WebSphere Partner Gateway Version 6.2.1 FixPack 4 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/, / responsefiles/ are performed. 3. Apply APAR JR47647 prerequisite (if not applied already) before upgrading to 6.2.1 FixPack 4. This APAR will update the WPG UPDI related jars and upgrade these to the latest level. 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 4 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 4. 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 4 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 4 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 4 file using update installer. 4. Following are the prerequisites for 6.2.1 FixPack 4 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 4 pak file. 9. In the Available Maintenance Package to install window, ensure that the check box for 6.2.1 FixPack 4 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 4 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 4 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 4 file using update installer. 4. Following are the prerequisites for 6.2.1 FixPack 4 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 4 pak file. 9. In the Available Maintenance Package to install window, ensure that the check box for 6.2.1 FixPack 4 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 4 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-FP4_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 ten scripts, from V6.2.0.1, only the last eight, from V6.2.0.2, only the last seven 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 db2 -td! -f 6.2.1.2_to_6.2.1.3/BCGUpgrade_621FP2_621FP3.sql -z /home/db2inst1/BCGUpgrade_621FP2_621FP3.log db2 -td! -f 6.2.1.3_to_6.2.1.4/BCGUpgrade_621FP3_621FP4.sql -z /home/db2inst1/BCGUpgrade_621FP3_621FP4.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.4. Note: If you are upgrading from 6.2.0.1 or higher to 6.2.1.4, 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-FP3_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 ten scripts, from V6.2.0.1, only the last nine, from V6.2.0.2, only the last eight 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 sqlplus -L bcgapps/ @6.2.1.2_to_6.2.1.3/BCGUpgrade_621FP2_621FP3.sql sqlplus -L bcgapps/ @6.2.1.3_to_6.2.1.4/BCGUpgrade_621FP3_621FP4.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 4 IBM WebSphere Partner Gateway Version 6.2.1 FixPack 4 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 4 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 4 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 4 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 4 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 4 ========================================================== Component : Console Apar: JR48391 Description: NullPointerExcepion while uploading specific WSDL in WPG console. Apar: JR50264 Description: Apache Struts 1.X could allow a remote attacker to execute arbitrary code on the system, caused by the failure to restrict the setting of Class Loader attributes. An attacker could exploit this vulnerability using the class parameter of an ActionForm object to manipulate the ClassLoader and execute arbitrary code on the system. This vulnerability is fixed now in WPG ADV/ENT. Apar: JR49910 Description: Error while opening archiver report when the archiver task is in running state Apar: JR50999 Description: WPG console is free from Cross-Site Request Forgery (CSRF) attack now. Component : Receiver Apar: JR48210 Description: Original file name and absolute path information were added to file directory receiver reject error report Apar: JR49091 Description: Some of the bcg_tmp files were lying in file directory receiver when receiver server was being shutdown from WAS admin console. This issue is resolved Apar: JR49216 Description: In a multi node topology POP3 receiver picked up the message from mail server twice. This issue is fixed as part of this Fixpack Apar: JR50184 Description: On Solaris platform SFTP Receiver and Destination do not work with WPG 6.2.1.3 and throw error "java.lang.NoClassDefFoundError: com/ibm/jvm/util/ByteArrayOutputStream". This issue is fixed Apar: JR50185 Description: SQL Exception "ORA-20999: 20100 - PR_RCVATTRU: No Data Found " while editing existing JMS receivers in an upgraded setup. This issue has been resolved. Apar: JR51850 Description: Repeated error messages logged by SFTP receiver when there are no files to be processed in the target directory Apar: JR48979 Description: In this APAR fix, the FTP Scripting receiver/destination problems occurring after applying 6.2.1.3 fixpack have been resolved. Apar: JR51878 Description: FTP directory receiver picking up same file twice in fully distributed mode. This issue is fixed. Component : Security Apar: JR49313 Description: SFTP Server was allowing SFTP-Client to connect over weak algorithms like HMACMD5,HMACSHA196,HMACMD596. As per security compliance. ISFTP Server should accept connection over HMACSHA1. Apar: JR51100 Description: Security truststore cache refreshes to fail intermittently during new certifictate upload Apar: JR51575 Description: SSLv3 contains a vulnerability that has been referred to as the Padding Oracle On Downgraded Legacy Encryption (POODLE) attack. Component : Integrated FTP/ SFTP JRE Apar: JR47328 Description: WebSphere Partner Gateway Integrated FTP/SFTP server uses IBM JRE which is based on Oracle JDK and vulnerable to TLS attack as published in Oracle April 2013 CPU Apar: JR48705 Description: This APAR is to upgrade WPG integrated FTP/SFTP JRE to address. PSIRT advisory 1285. JRE will be upgraded to JAVA 6 SR 15 Apar: JR49650 Description: WebSphere Partner Gateway Advanced/Enterprise uses IBM SDK for Java that is based on Oracle JDK . Oracle has released January 2014 critical patch updates (CPU) which contain security vulnerability fixes. The IBM SDK for Java has been updated to incorporate these fixes. Apar: JR51079 Description: There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition, that is used by WebSphere Partner Gateway. These issues were disclosed as part of the IBM Java SDK updates in July 2014 Apar: JR51896 Description: There are multiple vulnerabilities in IBM® Runtime Environment Java™ Technology Edition, Version 6 that is used by WebSphere Partner Gateway Advanced/Enterprise. This also includes a fix for the Padding Oracle On Downgraded Legacy Encryption (POODLE) SSLv3 vulnerability (CVE-2014-3566). These were disclosed as part of the IBM Java SDK updates in October 2014. Apar: JR52543 Description: There are multiple vulnerabilities in IBM® Runtime Environment Java™ Technology Edition, Version 6 that is used by WebSphere Partner Gateway Advanced/Enterprise. These were disclosed as part of the IBM Java SDK updates in January 2015. Component: Destination Apar: JR49035 Description: WebSphere Partner Gateway reported errors when processing a particular HTTP chunked response from a HTTPS partner.In this Fixpack HTTP chunked response is handled correctly. Component : EBMS Apar: JR51068 Description: "Too many open files" issue in EBMS document processing when the document size is more than 10 KB Apar: JR48750 In releases WPG 621 and above, If the property "bcg.global.common.deletetempfiles" is set to "Yes" and the ebMS connection's "ebMS Split and Parse" action is configured, the routing of ebMS child documents were failing. This issue is fixed Component : Alerts Apar: JR50504 DataBase exception (DB2 SQL error: SQLCODE: -811, SQLSTATE or SQLException: ORA-01422: exact fetch returns more than requested number) during event alert generation in a multi router setup after upgrading to WPG 6.2.1.3. Component : RNIF Apar: JR52491 Description: When setting up a RNIF/RNSC package, the current XPATH expression only works with elements, not attributes or standard xpath functions such as concat(). The Doc ID and Doc time stamp are not able to be recognized in WPG without fixes to the XPATH matching. In this fix advanced XPATH query functionality has been implemented for Doc ID and Doc time stamp. Apar: JR51577 Description: Failure to log RosettaNet validation error event when the error message length is greater than 4000 characters Apar: JR51647 Description: Intermittent failures were seen in RosettaNet retries when all the required files are not present in the file system. Apar: JR51875 Description: Incorrect GlobalPartnerClassificationCode set in RosettaNet Recipet Acknowledgment Component : Runtime Apar: JR49329 Description: DB connection leak in WPG document manager component ===================================================== Notices and trademarks: http://www.ibm.com/legal/copytrade.shtml Terms of use: http://www.ibm.com/legal/us/en/