IBM Corporation Readme file for WebSphere Partner Gateway V6.2.1 FixPack 3. Platforms: AIX, Linux, PowerLinux, Solaris, Windows Note: WebSphere Partner Gateway V6.2.1 FixPack 3 is not supported on HP-UX Maintenance Delivery Vehicle type: 6.2.1-WS-WPG-FP3_Advanced.pak 6.2.1-WS-WPG-FP3_Enterprise.pak These installables can be used across all WebSphere Partner Gateway supported platforms. © Copyright International Business Machines Corporation 2013. 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.3 Readme This document is the Readme documentation for version 6.2.1 FixPack 3 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.3 of IBM WebSphere Partner Gateway, Enterprise and Advanced Editions. IMPORTANT: 6.2.1 FixPack 3 can be installed and uninstalled ONLY by using IBM® Update Installer for WebSphere® software. FixPack 6.2.1.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.1 FixPack 3 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 3. The 6.2.1.0-WS-WPG-IFJR47647.pak can be downloaded along with 6.2.1-WS-WPG-FP3_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.3 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 FP3, if not already done. 6) WPG 621 FixPack 3 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 3 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.45 2. WebSphere Application Server Network Deployment V7.0.0.29 3. IBM DB2 UDB V9.1 FixPack 12 4. IBM DB2 UDB V9.5 FixPack 10 5. IBM DB2 UDB V9.7 FixPack 8 6. Oracle 11.2.0.3 7. IBM WebSphere MQ 7.0.1.10 8. IBM WebSphere MQ 7.1.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 cant be installed on Oracle 11.2 The following specific workarounds would need to be applied: 1. 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. 2. When a customer uninstalls WPG 6.2.1 FixPack 3 to revert to 6.2 FP4a level, and then tries application of WPG 6.2.1 FixPack 3 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 3 IBM WebSphere Partner Gateway Version 6.2.1 FixPack 3 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 3. 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 3 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 3. 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 3 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 3 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 3 file using update installer. 4. Following are the prerequisites for 6.2.1 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 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 3 pak file. 9. In the Available Maintenance Package to install window, ensure that the check box for 6.2.1 FixPack 3 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 3 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 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 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 3 file using update installer. 4. Following are the prerequisites for 6.2.1 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.1 FixPack 3 pak file. 9. In the Available Maintenance Package to install window, ensure that the check box for 6.2.1 FixPack 3 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 3 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-FP3_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 db2 -td! -f 6.2.1.2_to_6.2.1.3/BCGUpgrade_621FP2_621FP3.sql -z /home/db2inst1/BCGUpgrade_621FP2_621FP3.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.3. Note: If you are upgrading from 6.2.0.1 or higher to 6.2.1.3, 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_Enterprise/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 sqlplus -L bcgapps/ @6.2.1.2_to_6.2.1.3/BCGUpgrade_621FP2_621FP3.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 3 IBM WebSphere Partner Gateway Version 6.2.1 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.1 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 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 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, it is the 6.2.1 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. 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 3 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 3 ========================================================== Component: Console Apar: JR42977 Description: When FTP/SFTP user details are changed and saved, WPG expects the FTP/SFTP server to be running. When the FTP/SFTP server is down appropriate message will be displayed on WPG Console Apar: JR43264 Description: While creating a new destination by default "Server verification" option should be in disable mode Apar: JR44003 Description: Partial binary file processed by WPG due to small file unchanged interval in File Directory receiver. Fix provided to allow the file unchanged interval field to accept bigger value Apar: JR44395 Description: Apar: Description: Input field is too short to provide JMS Provider Url on console at System Administration --> DocmgrAdministration --> event engine --> external events Now maximum limit of characters to be entered is 250 chars earlier it was 50 characters Apar: JR45337 Description: LDAP enabled users were redirected to error page instead of login page after session time out. This issue is being fixed Apar: JR46405 Description: SFTP destination edit page always resets field "Use Unique Filename" checked. This issue has been corrected Apar: JR46650 Description: SFTP receiver poll interval field is enhanced to take value up to 8 digits. Component: SFTP receivers/destinations Apar: JR44443 Description: In some cases , even if SFTP Destination is configured with "Use Unique File Name" not checked, the file is delivered with a doc ID used as unique name. Such behavior is corrected Apar: JR43555 Description: In SFTP destination configuration, some passwords were being used incorrectly by runtime to make connection with SSH server. This behavior has been corrected, Apar: JR44090 Description: In some cases SFTP destination was successfully delivering file to the server, however the console was showing the transaction as failed with event: BCG250011 - First Delivery Attempt Failed for message due to 'com.ibm.bcg.bcgdk.common.exception.BCGException: Unable to send files to server due to exception No such file', on Destination 'XYZ¨' Such behavior has been corrected. Apar: JR44464 Description: If file on SFTP server gets consumed as soon as WPG SFTP sender post . stat command fails to run and WPG console shows delivery failed with event 250011.Such behavior is corrected. Apar: JR45183 Description: This fix introduces a new parameter called "Enable Rekey" on SFTP receiver configuration page, to enable/disable "Rekeying" between SFTP Server and Client.From WPG 6.2.1 fixpack 3 and onwards, WPG SFTP client (i.e. SFTP receiver) sends Rekey command to SFTP server if connection is kept idle for long time. If SFTP client connects to a SFTP server which does not support "Rekey" command, user may face some hung situation while polling files from server. For such SFTP servers, users may disable rekeying on this particular WPG SFTP receiver. Note: When fix will be applied, value of this new parameter for all existing SFTP receivers will be populated with default value True (i.e. the "Enable Rekey" option is checked). It is advisable to always have the Rekey enabled, you may disable it only when SFTP server does not support Rekeying. Component: Security Apar: JR43952 Description: From this FixPack onwards WPG complies with guidelines defined by NIST Special Publications 800-131a . For more details refer to link Apar: JR47724 Description: The critical issues reported by Rational Application Scan and Static Scan tool are fixed in this FixPack Component:Integrated FTP Server Apar: JR43536 Description: Inegrated FTP server is enhanced to make the below Listener properties visible on WPG console. bcg.ftp.config.listeners.clientauth.address bcg.ftp.config.listeners.clientauth.data-connection.passive.address bcg.ftp.config.listeners.default.data-connection.passive.external-address bcg.config.ftpserver.FTPInstallHostIp Component:Integrated SFTP Server Apar: JR47323 Description: WPG not taking into consideration the time zone offset while validating the SFTP certificate during SFTP server start. This issue is fixed Component: ebMS Apar: JR44653 Description: When sending ebMS messages over HTTPS IPV6 destination, the HTTP header was malformed. This has been fixed. Apar: JR44972 Description: In an ebMS flow, Content-ID field of the SOAP header contains hostname information. Fix provided to have an option to exclude the hostname from the Content-ID field. This can be done by going to System Administration - DocMgr Administration - Process Admin - ebMS and setting the "bcg.ebXML.excludeHostnameFromContentID" property to true. Component: Alerts Apar: JR43014 Description: SQL error “com.ibm.bcg.alertEng.AlertDB dbError AlertDB.getDocumentInfo - Error: java.sql.SQLException: Numeric Overflow" seen when generating alerts for large file transfer. This issue has been fixed. Apar: JR43598 Description: From this FixPack onwards event alerts are enhanced to include eventid along with event details. Component: Certificate management Apar: JR43320 Description: When a certificate is uploaded/deleted, the FTP management server had to be restarted for changes to get reflected. In this fix, the certificate upload/delete changes get reflected without restarting the FTP management server. Component: Install/UPDI Apar: JR46064 Description: bcgChangeDmgrHostname.bat/sh fails to execute in WAS 7 migrated environment. This issue has been fixed. Apar: JR44591 Description: Update installer used to fail while installing/Uninstalling any fix or fixpack on WPG running on security enabled WebSphere Application Server 7.0.0.x , if user uninstalls WebSphere Application Server 6.1.0.x on same machine. This has been corrected. Component: Archiver Apar: JR43394 Description: WPG Archiver is enhanced to archive records related to web mailbox function Apar: JR44275 Description: WPG Archiver failing intermittently on Windows/DB2 with the exception AR_EXPORT failed. Apar: JR46752 Description: Archiver appears to be in running state for long with SQL Exceptions in the logs while executing DELETE FROM LG_ACTIVITY Apar: JR46778 Description: Archiver status shows successful even if the archiver fails to delete records from all the required tables. Component: EDI Apar: JR44566 Description: EDI enveloper failure when using transaction mask with group control number and a sequence number Component: RNIF Apar: JR43470 Description: "BCG240500 - ROSETTANET STATE ENGINE ERROR" event was getting generated while performing RNIF or AS flows because there were uncommitted transactions. This has been fixed Component : Runtime/AS2 Apar: JR43243 Description: WPG is unable to unpackage the MDN from partner and generates event “BCG240409 - AS Unpackaging Failed” This issue has been fixed. Component : Runtime Apar: JR45736 Description: Document manager restart was required to reflect the certificate set change at partner connection level. This issue is fixed Apar: JR45779 Description: During RNIF process retry, if StaleConnection exception occurs then additional retries were not made. This issue is being fixed Apar: JR44352 Description: Receiver incorrectly sends 0 bytes source file to DocMgr for processing Component : Partner Migration Apar: JR44091 Description: WPG Partner Migration Utility failing with error "com.ibm.icu.util.SimpleTimeZone is not present on the local classpath" to import certificates when installed with WAS 6.1.0.43 or later and WAS 7.0.0.23 or later Apar: JR44735 Description: File name was missing in the event description for event BCG620006. This has been rectified Component: Integrated FTP/SFTP JRE Apar: JR46069 Description: Integrated FTP/SFTP JRE is updated as per Oracle Critical Patch Update June 2013 ===================================================== Notices and trademarks: http://www.ibm.com/legal/copytrade.shtml Terms of use: http://www.ibm.com/legal/us/en/