IBM corporation Readme file for WebSphere Partner Gateway V6.2 FixPack 5. Platforms: AIX, HP-UX, Linux, PowerLinux, Solaris, Windows Maintenance Delivery Vehicle type: 6.2.0-WS-WPG-FP5_Advanced.pak 6.2.0-WS-WPG-FP5_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.5 Readme This document is the Readme documentation for version 6.2 FixPack 5 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.0.5 of IBM WebSphere Partner Gateway, Enterprise and Advanced Editions. IMPORTANT: 6.2 FixPack 5 can be installed and uninstalled ONLY by using IBM® Update Installer for WebSphere® software. FixPack 6.2.0.5 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 5 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 JR37556 prerequisite before upgrading to 6.2 FixPack 5. The 6.2.0.0-WS-WPG-TFJR37556.pak can be downloaded along with the 6.2 FP5 pak file. ================================================== Server and Database support The WebSphere Partner Gateway Version 6.2.0.0 FixPack 5 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.31 2. Oracle 10g Enterprise Edition Release 2 - 10.2.0.5 3. IBM DB2 UDB V9.1 FixPack9 For more details, refer to system requirements at: 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. 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. For WebSphere Partner Gateway FixPack 5, all new additions related to console will be seen in English language only. No other languages are supported. 4. After upgrading to WPG 6.2 FP5 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 5. 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 6. 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 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 FixPack 5 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 FixPack 5 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 FixPack 5 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 FixPack 5 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 above technote, need not perform the addition steps again. 6. When a customer uninstalls WPG 6.2 Fixpack 5 to revert to 6.2 FP4a level and then tries application of WPG 6.2 Fixpack 5 again an error stating "Unsupported product" may be seen. To resolve this go to location /properties/version 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 FixPack 5 IBM WebSphere Partner Gateway Version 6.2 FixPack 5 can be installed, ONLY by using IBM® Update Installer for WebSphere Software (7.0.0.1 and above). 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 JR37556 prerequisite before upgrading to 6.2 FixPack 5. 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 FixPack 5 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 is to be retained and used, as necessary, during uninstallation of WebSphere Partner Gateway 6.2 FixPack 5. 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 5 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 about the prerequisites that need to be applied. Step D - Applying the FixPack - Upgrade WebSphere Partner Gateway Application database automatically through UPDI Note: - Customers upgrading to 6.2 FixPack 5 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 5 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 The following steps need to 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 FixPack 5 file using update installer. 4. Following are the prerequisites for 6.2 FixPack 5 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 FixPack 5 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 FP5 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 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 5 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 FixPack 5 file using update installer. 4. Following are the prerequisites for 6.2 FixPack 5 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 5 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 FP5 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 Note: Customers upgrading to 6.2 FixPack 5 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 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 five scripts, from V6.2.0.1, only the last four, from V6.2.0.2, only the three 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. 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 needs to be run only if you are upgrading from 6.2.0.0 to 6.2.0.5. Note: If you are upgrading from 6.2.0.1 or 6.2.0.2 to 6.2.0.5, 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.0-WS-WPG-FP5_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 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 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 FixPack 5 IBM WebSphere Partner Gateway Version 6.2 FixPack 5 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 5 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 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 5 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 FixPack 5 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 FixPack 5 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 FixPack 5 ======================================================== Component: AS Apar: JR36114 Description: With this FixPack, the “Resend” works as expected. Component: Archiver Apar: JR35684 Description: While purging DB table data, WebSphere Partner Gateway Archiver displayed "SQL error: SQLCODE: -532, SQLSTATE: 23504" an exception for DB foreign key constraint violation. Component: Archiver Apar: JR36757 Description: WebSphere Partner Gateway Archiver has been improved to delete WebSphere Partner Gateway created temp files. Component: BPE Apar: JR35132 Description: This FixPack resolves the problem encountered in handling documents in process during WebSphere Partner Gateway shutdown. It includes stage recovery in reliable fashion, which ultimately resolves BPE's cyclic document processing problem. Component: BPE Apar: JR36116 Description: With this FixPack, the problem of signature verification failure, which encountered inappropriately during WebShpere Partner Gateway shutdown is resolved. Component: BPE/Console Apar: JR37676 Description: The option to change the duplicate field declaration in the System Administration properties was not taking effect, this is corrected. Component: BPE/ebMS Apar: JR35429 Description: During secure ebMS message flows, it was noticed that the security operations failed when the BCGBPE application was restarted. Component: BPE/ebMS Apar: JR37687 Description: This FixPack has resolved the problem of failing security operations upon restarting the BCGBPE application during ebMS secure message flow. Component: Console Apar: JR35330 Description: When using WebSphere Partner Gateway Console to edit partner with large number of business IDs (more than 200), the edit and save operation takes long time to display the page. With this FixPack, the performance is considerably improved. Component: Console Apar: JR35603 Description: While deleting one version of a PIP, the information pertaining to other versions (for example, shared attributes and validation maps) was deleted. With this FixPack, dependency check happens before deleting the associated attributes and maps so that the other PIP definitions are not affected. Component: Console Apar: JR35647 Description: The "Destination Queue" page in the WebSphere Partner Gateway console takes a long time to display the page, if the number of destinations configured for the partner are large (more than 600). Component: Console Apar: JR35717 Description: Associated handlers for any POP3 type receivers were seen missing from the configuration XML data, that was exported using the Partner Migration utility. Component: Console Apar: JR35736 Description: With this FixPack, you can successfully create a custom SFTP destination. Component: Console Apar: JR35745 Description: The hub’s default internal partner was set to wrong partner after importing the partner migration data. Component: Console Apar: JR35990 Description: While starting the DocMgr application, the "NumberFormatExceptions" exception which was thrown in the scheduler, was causing the "DeliverySchedulerBean" to stop and report errors. These exceptions were thrown because the FTPScripting destination configurations having POLLINTERVAL displayed 0.0 seconds. With this FixPack, the POLLINTERVAL value is validated to have a non-zero positive integer while creating the destination. Component: Console Apar: JR36069 Description: The "Password" field was not masked while creating a destination or a receiver using custom transport. Component: Console Apar: JR36402 Description: When a custom user, who is not a member of "hubadmin" group, login to the WebSphere Partner Gateway console, this user was not able to view or configure handler and its attribute for receivers or destinations even when the user had read/write permission for the receiver and destination modules. Component: Console Apar: JR36916 Description: Exported WebSphere Partner Gateway configuration XML data through Partner Migration utility was missing “Folder Name” attribute and it’s value for web mailbox type destinations. Component: Console Apar: JR37255 Description: Deleting of a user in the WebSphere Partner Gateway happened without prompting for any confirmation. With this FixPack, a confirmation dialogue box appears before deleting the user from database to avoid any unintentional delete of user. Component: Console Apar: JR37692 Description: The Time zone setting option drop down list for the user confirmation was listing only important time zone regions without listing all sub-regions with different DST scheme for that region. Component: Console/ebMS Apar: JR34693 Description: In Websphere Partner Gateway console, the Document Viewer or the ebMS Viewer did not display the document timestamp of the outbound ebMS document. Component: Console/ebMS Apar: JR35911 Description: In the current implementation, the WebSphere Partner Gateway uses fixed key length for the defined encryption algorithms, and hence the Encryption Key Length attribute, which is provided as the ebMS connection attribute is redundant, so it has been removed from the console. Component: Console/ebMS Apar: JR37690 Description: In the current Websphere Partner Gateway implementation, the supported "syncReplyMode" values for ebMS are none and mshSignals only. This FixPack removes the other redundant options listed in the "SyncReplyMode" drop down from the connection attributes for ebMS. Component: Console/FTP Configuration Apar: JR35234 Description: With this FixPack, you can now edit the "The bcg.config.ftpmanagement.allowedIPs" property of the Integrated FTP Server by navigating to: System Administration -> FTP Administration page in the WebSphere Partner Gateway console. Component: CPA Editor Apar: JR35411 Description: When opening the CPA using the CPA Editor, the following error was seen "java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(UnknownSource)". Component: CPA Editor Apar: JR35542 Description: When the CPA was edited in the CPA Editor, the user was unable to upload the edited CAP in the WebSphere Partner Gateway console. This error occurred because the CPA editor incorrectly adds the element Persist Duration to the CPA. Nevertheless, the Persist Duration is not a mandatory element, so it is wrong to add it without the other dependencies being present. Component: Database Apar: JR36742 Description: While updating WebSphere Partner Gateway to any latest fix pack, channel attribute “EXCLUDEDCONTENTTYPESFORCANONICALIZATION” was getting reset. Component: Destination - FTP scripting destination Apar: JR37055 Description: When the APPEND command was used, the FTPScripting destination used to throw nullpointer exception in SystemErr.log. This exception was seen when the FTP server was returning a warning code '000'. Component: Destination/HTTP Apar: JR29147 Description: With this FixPack, while sending the HTTP document, you can configure a value, which will use the transfer encoding as chunked. You can configure this value as number of bytes by using the "bcg.http.requestSizeForChunking" parameter from the System Properties. Note that, you can still retain the default value - 2147483647, unless it is required to change. Component: Document Manager Apar: JR35606 Description: Errors relating to "java.lang.ArrayIndexOutOfBoundsException" were logged as MDNs did not generate. With this FixPack, all such problems seen on a multi-machine setup have been resolved. Component: Document Manger Apar: JR35716 Description: When a certificate is uploaded using WebSphere Partner Gateway console, an error -"com.ibm.bcg.server.cache.docmgr.DocMgrConfigCache refreshDocMgr Error in refreshing the cache java.lang.NullPointerException" was seen in the “SystemOut” log files because there were Docmgrconfig cache updates happening for the Archiver EAR. Component: Document Manager Apar: JR35897 Description: Earlier, the checking of the AS2 duplicate documents happened frequently. With this FixPack, the checking of the AS2 duplicate documents happen only when the channel attribute is set to “No”. Component: Document Manager Apar: JR37807 Description: The removal of the oldest entry in the channel cache and cache refresh were not synchronized, which could lead to unexpected results/entries in the channel cache. Component: Document Manager/ebMS Apar: JR34571 Description: For the ebMS document, the retry count is updated in the database only when the retried message is processed by the BPE. This exceeded the maximum retry count of unwanted retries, when the messages are stuck in the MAIN_INBOUNDQ. Component: Document Manager/AS Apar: JR36527 Description: With this FixPack, logging of Duplicate AS documents is handled efficiently. Component: Document Manager/ebMS Apar: JR37675 Description: With this FixPack, now if the "PartyID" has a type other than "urn:duns", and if it is configured in the connection attribute for that partner, then that value is used during the packaging of the ebMS acknowledgement. Component: Document Manager/ebMS Apar: JR37684 Description: According to an interop consensus line item, "SOAPAction" header is not mandatory for synchronous ebMS response. This FixPack allows processing of a synchronous response message even if the SOAPAction header is absent. Component: Document Manager/ebMS Apar: JR37685 Description: During ebMS message flows, it was observed that the "MessageId element" value was not setting up correctly on the ebMS Ping message that was sent outbound. This resulted in having an incorrect RefToMessageId in the ebMS PONG message, and "a B2B capability not found" error message for the received EBMS Pong message. This problem is resolved in this FixPack. Component: Document Manager/ebMS Apar: JR37688 Description: With this FixPack, as per the ebMS specification, the "Timestamp" element in the StatusResponse displays the time when the request message, whose status is being queried was received. Component: Document Manager/ebMS Apar: JR37689 Description: The WebSphere Partner Gateway rejects the stray acknowledgement received for an ebMS request document that is not in the WebSphere Partner Gateway system without logging any error messages in the log files. Component: Document Manager/ebMS Apar: JR37691 Description: With this FixPack, the "PersistDuration" is correctly inserted or updated as currentTimeStamp + PersistDuration set in the "BP_RM_STATE_DTL" table. Component: Document Manager/ebMS Apar: JR37693 Description: The way the Persist Duration value for an ebMS document is calculated has been changed as follows: a) If the "x-aux-TimeToLive" attribute is not present, then the source side attribute value of Persist Duration is used as the message TimeToLive. b) If the PersistDuration is set to an incorrect value that results in NumberFormatException, then a value of RetryInterval * (Retry Count +1) is used as the PersistDuration. c) If the PersistDuration attribute is set as 0 or -1, then the PersistDuration defaults to 7 days. Component: Document Manager/EDI Apar: JR34071 Description: The FA generated during EDI Interchange Validation action did not contain FA for each of the transaction present in the EDI document being validated. Component: Document Manager/EDI Apar: JR35640 Description: When the action EDI Validate Interchange was used, duplicate EDI transaction was not rejected. Component: Document Manager/EDI Apar: JR36013 Description: Earlier, Functional Acknowledgement (FA) for an EDI document did not get associated with the document for which it was generated. Component: Document Manager/EDI Apar: JR36031 Description: During the validation of an EDI Interchange, the validation events generated using the action EDI Validate Interchange were not shown in the document viewer details. Component: Document Manager/EDI Apar: JR36068 Description: With this FixPack, the RE-ENVELOPED EDI-X12 Document’s transaction segment count remains the same and does not increment by 2. Component: Document Manager/EDI Apar: JR36078 Description: Earlier, the RE-ENVELOPED EDI-X12 Document's transaction segment count was expected to remain the same, but it incremented by 2. With this FixPack, the RE-ENVELOPED EDI-X12 Document's transaction segment count remains the same. Component: Document Manager/EDI Apar: JR36243 Description: While using EDI interchange validation, BCGEDIVA0011 related errors were issued. The failure happened because SV504 and SV505 erroneously reported as missing. Component: Document Manager/EDI Apar: JR36395 Description: While processing a 40 MB document of type-837 edi having HL Loops, out of memory problem used to occur. Component: Document Manager/EDI Apar: JR36537 Description: Earlier, when the action was "EDIValidateInterchange", the EDI X12 997 FA document was not getting processed. Component: Document Manager/EDI Apar: JR36560 Description: Earlier, the EDI ReEnveloper was setting the UNT01 (TRANSACTION SEGMENT COUNT) with a wrong number. Additionally, the UNT01 (TRANSACTION SEGMENT COUNT) of the incoming document and the outgoing document should be the same, but was different. Component: Document Manager/EDI Apar: JR37076 Description: With this FixPack, the redundant logging of the "FileNotFound" exception has been removed. Component: Document Manager/EDI Apar: JR37181 Description: While using EDISplitter, if any failures were seen, WebSphere Partner Gateway would not move the files from the receiver directory to reject the directory if any failures were seen while using the eEDISplitter. Component: Document Manager/EDI Apar: JR37412 Description: Earlier, during reenveloping with deenveloping, large messages failed due to the validation of the documents, which was not required. Component: ebMS Apar: JR36989 Description: If an ebMS document fails with unsupported ebMS version event, then all subsequent ebMS documents would fail even if they were supported ebMS versions. Component: ebMS Apar: JR37062 Description: With this FixPack, the document is marked as failed for any unsupported version of ebMS. Component: eBMS Apar: JR37686 Description: With this FixPack, the problem in having the "Syncreply" element, when the "MessageOrder" element is present is corrected. Now, as per the specifications, when the the "MessageOrder" element is present, only "DuplicateElimination" element will be present in the ebMS document, but the "Syncreply" element will not be present. Component: Event Engine Apar: JR34907 Description: With this FixPack, event 'BCG250008', 'Document delivery to Partner Destination failed' gets logged appropriately. Component: FTP Scripting / FTP Client Apar: JR37694 Description: With this FixPack, support for passive mode has been provided for the FTP Client. Component: Installation/FTP Server Apar: JR31636 Description: When an integrated FTP server was installed as a Windows service, it could not be started as Windows services. Component: Integrated SFTP server Apar: JR36766 Description: While using with WebSphere Partner Gateway Integrated SFTP Server, the posting of a document delivery to a SFTP destination failed and displayed "com.ibm.j2ca.ftp.exception.FTPOperationsException: 2: No such file: " error message. Component: Integrated SFTP server Apar: JR37476 Description: While accessing the WebSphere Partner Gateway integrated SFTP server, the absolute path for example - "remote directory is /opt/IBM/PG62/Ftpserver/data/config/ftpadmin" of user directory was being exposed to SFTP client. Component: Integrated SFTP server Apar: JR37753 Description: When WebSphere Partner Gateway was installed on DB2 9.5 on Windows 32 bit environment, the "startsftpmgmtserver" script displayed "Warning: No host key defined for the server" warning message while starting the sftpmanagement server. Component: Integrated SFTP server Apar: JR37932 Description: For Integrated SFTP User, WPG would need the private key of the user to be uploaded along with the passphrase for public key verification. Component: Receiver Apar: JR36241 Description: With this FixPack, the POP3 User Exit Receiver Handler works with the WebSphere Partner Gateway without any problem. Component: Receiver/FTP Directory Apar: JR35549 Description: Earlier, an unhandled exception in the "FTPDirectoryReceiver" resulted in the ObjectFIFO object growing continuously. This resulted in logging of OutOfMemory exceptions in the log files. Component: Receiver/FTP receiver Apar: JR36077 Description: After creation or deletion of any folders from the FTP Root Directory when the polling of WebSphere Partner Gateway FTP receiver was on, the FTP Directory receiver - 'FTP Receiver' used to hang. As a result of this, the files were not picked up from any of the FTP receivers created. Component: Receiver/HTTP Apar: JR35521 Description: Earlier, an HTTP 401 response was sent back without the required "WWW-Authenticate" HTTP header, when a partner sent a message to the HTTP receiver without having the user ID and or password authentication. With this FixPack, the "WWW-Authenticate" header will be present in the HTTP 401 response as per the information specified at http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html. Component: Receiver/JMS Apar: JR37683 Description: With this FixPack, additional trace statements are introduced for finding the cause of jms receiver failures. Component: RNIF Apar: JR36844 Description: The 0A1 mandates the presence of the “GlobalSupplyChainCode” and “GlobalPartnerClassificationCode” elements. The incoming 4A5 V11.00.00 needs to supply this information. There is no place in the 4A5 ,3B2,7C7 , 7C8 RNIF PIP Packages to handle this. Component: Security Apar: JR37328 Description: When doing Client Authentication for FTPS destination using chain certificates, if only leaf certificate was uploaded at the FTP Server then SSL Client authentication would fail at WebSphere Partner Gateway. WebSphere Partner Gateway would expect that the entire chain of certificates be uploaded at the FTP Server end. This behaviour has now been corrected. Component: Security Apar: JR37695 Description: When an invalid primary, and a valid secondary certificates were uploaded, Client Authentication for FTPS mode did not work. Component: Security Apar: JR37806 Description: When the Private Key was being read from the Database, extraneous data was being written to the internal output buffer when the Private Key was large in size. Component: Server-AS2 Apar: JR35698 Description: Earlier, when the value of the Content-Disposition was set to "Attachment", the positive MDN was received in the WebSphere Partner Gateway console displaying "MDN Disposition Errors" error message. Component: Server performance Apar: JR36701 Description: With this FixPack, the temp files will be written in the rolling directories in a tmp folder, which will be created at the location defined under “bcg.bpe_temp_directory.main” directory. This has substantially improved the performance. Component: Server resend Apar: JR37442 Description: Earlier, resending of the target document failed and displayed "File does not exist" error message. ===================================================== Notices and trademarks: http://www.ibm.com/legal/copytrade.shtml Terms of use: http://www.ibm.com/legal/us/en/