IBM corporation Readme file for WebSphere Partner Gateway V6.2.1 FixPack 1. Platforms: AIX, Linux, PowerLinux, Solaris, Windows Note: WebSphere Partner Gateway V6.2.1 FixPack 1 is not supported on HP-UX Maintenance Delivery Vehicle type: 6.2.1-WS-WPG-FP1_Advanced.pak 6.2.1-WS-WPG-FP1_Enterprise.pak These installables can be used across all WebSphere Partner Gateway supported platforms. © Copyright International Business Machines Corporation 2011. 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.1 Readme This document is the Readme documentation for version 6.2.1 FixPack 1 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.1 of IBM WebSphere Partner Gateway, Enterprise and Advanced Editions. IMPORTANT: 6.2.1 FixPack 1 can be installed and uninstalled ONLY by using IBM® Update Installer for WebSphere® software. FixPack 6.2.1.1 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 1 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 Update Installer for WebSphere Partner Gateway, would need to apply APAR JR38213 prerequisite before upgrading to 6.2.1 FixPack 1. The 6.2.0.0-WS-WPG-TFJR38213.pak can be downloaded along with the 6.2.1 FP1 pak file. ================================================== Server and Database support The WebSphere Partner Gateway Version 6.2.1 FixPack 1 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.37 2. WebSphere Application Server Network Deployment V7.0.0.15 3. IBM DB2 UDB V9.1 FixPack 10 4. IBM DB2 UDB V9.5 FixPack 7 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. After upgrading to WPG 6.2.1 FP1 from WPG 6.2 FP4a, the existing SFTP Receiver and SFTP Destination which were created using the Integrated SFTP Server will not be able to process the documents.For details on how to resolve this issue refer to http://www.ibm.com/support/docview.wss?uid=swg21449697 4. The WebSphere Partner Gateway (WPG) Receiver Cluster/Server needs to be restarted after switching authentication type from "User/Password" to "Private Key", or after switching authentication type from "Private Key" to "User/Password". This has also been technoted at http://www.ibm.com/support/docview.wss?uid=swg21450404 5. 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 6. If customer is using ORACLE database and WebSphere Application Server 7.0.0.15, BCGBUS/Messaging-engine may not start.For details on how to resolve this issue refer to http://www-01.ibm.com/support/docview.wss?uid=swg24029891&wv=1. 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. 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.1 FixPack 1 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 Oracle 10.2.0.5, then the "ORA-22996: NEXT extent size is smaller than LOB chunksize" error gets generated. Users intending to use Oracle 10.2.0.5 with WebSphere Partner Gateway 6.2 GA installation, would need to ignore the above error message, and apply WebSphere Partner Gateway 6.2.1 FixPack 1 immediately after installation of WebSphere Partner Gateway 6.2 GA. 3. 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. 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.1 FixPack 1 immediately after installation of WebSphere Partner Gateway 6.2 GA. 4. When you attempt to install WebSphere Partner Gateway v6.2 GA DBLoader directly on DB2 9.1 FP9, then the installation may fail on Base. Users intending to use DB2 9.1 FP9 with WebSphere Partner Gateway 6.2 GA installation, would need to ignore the above error message, and apply WebSphere Partner Gateway 6.2.1 FixPack 1 immediately after installation of WebSphere Partner Gateway 6.2 GA. 5. 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. 6. When a customer uninstalls WPG 6.2.1 Fixpack 1 to revert to 6.2 FP4a level, and then tries application of WPG 6.2.1 Fixpack 1 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 1 IBM WebSphere Partner Gateway Version 6.2.1 FixPack 1 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 JR38213 prerequisite before upgrading to 6.2.1 FixPack 1. 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 1 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 1. 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 1 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 1 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 -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.1 FixPack 1 file using update installer. 4. Following are the prerequisites for 6.2.1 FixPack 1 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 1 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 begins. When the installation completes, an appropriate installation success or failure message displays. Verify the logs present under /logs/update/<6.2.1 FP1 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 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 should be mandatorily 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.1 FixPack 1 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 -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.1 FixPack 1 file using update installer. 4. Following are the prerequisites for 6.2.1 FixPack 1 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 1 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 begins. When the installation completes, an appropriate installation success or failure message displays. Verify the logs present under /logs/update/<6.2.1 FP1 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.0-WS-WPG-FP5_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 seven scripts, from V6.2.0.1, only the last six, from V6.2.0.2, only the five 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 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.1. Note: If you are upgrading from 6.2.0.1 or higher to 6.2.1.1, 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-FP1_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 five scripts, from V6.2.0.1, only the last four, from V6.2.0.2, only the last three 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 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 1 IBM WebSphere Partner Gateway Version 6.2.1 FixPack 1 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 1 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 1 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 1 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 1 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 1 ========================================================== Component: Console Apar: JR38721 Description: During CPA import, you will be provided with a drop-down select field for selecting "PartyId Type" value from the CPA XML for populating it to the connection attribute for ebMS channel that is already created. Apar: JR39136 Description: With this FixPack, the Raw Document Viewer displays the document content without truncating more than one consecutive spaces to single space. Apar: JR39353 Description: While creating a SFTP receiver using the console during WebSphere Partner Gateway installation on a distributed topology, an Activation Specification was created on both - the Receiver and the DocMgr servers. Similarly, while creating a SFTP destination, Connection factory was created on DocMgr and Receiver servers. With this FixPack, the Activation Specification will be created for those nodes or servers only, where the receiver application is installed, and similarly, Connection Factory will be created for those nodes or servers only, where DocMgr application is installed. Component: Database Apar: JR39581 Description: Document report and document viewer were not working properly for custom protocols created with different name and code. Component: Destination SFTP Apar: JR39346 Description: SFTP Destinations having some special characters in the name like +, =, - , etc., were not getting deleted from the WebSphere Partner Gateway console. This problem is resolved in this FixPack. Component: Document Manager/EDI Apar: JR39436 Description: With this FixPack, the problem of ISA13 control number getting padded with trailing blank spaces instead of preceding zeroes, when the total number of digits is less than nine is resolved. Component: ebMS Apar: JR38839 Description: The PartyID Type element was not getting set in the ebMS acknowledgment. This problem is resolved in this FixPack. Apar: JR38920 Description: Though the Role Element (an optional attribute) was present in the ebMS Message Header, it was not getting set within the Acknowledgment Message. This problem is resolved in this FixPack. Apar: JR39060 Description: While sending an ebMS document using JMS, the Sequence Number status could not be reset, even though the x-aux header 'x_aux_seq_number_status' was reset. This problem is resolved in this FixPack. Apar: JR39464 Description: Earlier, WebSphere Partner Gateway used to set "MIME-Version: 1.0" header in the ebMS response message that was sent by WebSphere Partner Gateway; however, as per the EBMS specifications, "MIME-Version: 1.0" header must not appear as an HTTP header. With this FixPack, the "MIME-Version: 1.0" header does not appear as an HTTP header in the ebMS response message. Component: EDI Apar: JR39915 Description: With this FixPack, the Century Control year in the EDI transformation is corrected. Apar: JR38882 Description: With this FixPack, the problem in accepting the Alpha Numeric EDI Transaction Control Number, which starts with a numeric value is resolved. Apar: JR38716 Description: This FixPack enables truncation of ROD field length based on the user entry in the WebSphere Partner Gateway console. Component: Event Engine Apar: JR38513 Description: The time zone for activity log events from the Integrated FTP server had an incorrect value. This resulted in seeing an offset in the time values of these events in the Event Viewer of the WebSphere Partner Gateway console. This behavior is now rectified in this FixPack. Apar: JR39227 Description: With this FixPack, the problem with the external CBE, not adhering to the standard schema is resolved. Component: Integrated SFTP Server Apar: JR39479 Description: The SFTP public key authentication method does not work correctly. Using any private key, the SFTP client can connect to the integrated SFTP server. This applies to RSA keys only. The DSA keys work correctly. Apar: JR38561 Description: With this FixPack, the usage of "service.bat" script of the integrated FTP server prints correctly without any problems. Apar: JR38568 Description: Earlier, after installing WebSphere Partner Gateway, if the database password was changed, the FTPmanagement server was not getting started and displayed "user id and password is invalid" error message. With this FixPack, if the database password changes, you can enter the new password and start the SFTPmanagement server successfully from System Administration -> FTP Administration -> DataBase Properties of WebSphere Partner Gateway console. Component: RNIF Apar: JR38533 Description: In case of new schema based PIPs, date format data validation errors for 0A1 Failure Notification document are resolved. Component: Security Apar: JR38612 Description: With this FixPack, if the primary certificate expires in the multicluster environment, the secondary upgrade to primary upgrade does not fail. Apar: JR39507 Description: An error message "Setting DB not available status com.ibm.db2.jcc.a.SqlException: [ibm][db2][jcc][10120][10898] Invalid operation: result set is closed." is shown in the log file, when SSL client certificate is not present in the WebSphere Partner Gateway database. You can ignore this incorrect error message shown in the log file because at the receiver end for HTTPS, it is not mandatory to have the certificate available in the database. Component: SFTP Receiver/Destination Apar: JR39065 Description: The following exceptions were generated by the SFTP Receiver, which resulted into failure to receive messages available on the SFTP server: Caused by: java.sql.SQLException: DSRA9350E: Operation setAutoCommit is not allowed during a global transaction at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.setAutoCommit(WSJdbcConnection.java.2695) at com.ibm.bcg.co.db.DBManager.getConnection(DBManager.java:137) at com.ibm.bcg.co.db.DBManager.getStatement(DBManager.java:216) at com.ibm.bcg.server.receiver.ejb.SFTP_MDBBean.getReceiverInfo(Unknown Source) This problem was observed only in the environment where IBM Tivoli Composite Application Manager (ITCAM) Agent for WebSphere Applications, version 7.10 was installed with Data collectors configured for WebSphere Partner Gateway servers. This problem is resolved. Component: Summary Engine Apar: JR38906 Description: Earlier, summary engine failed due to unidentified operation mode existence in the database. Now, the summary engine works as expected for any operation mode. ===================================================== Notices and trademarks: http://www.ibm.com/legal/copytrade.shtml Terms of use: http://www.ibm.com/legal/us/en/