IBM corporation Readme file for WebSphere Partner Gateway 6.1 Fix pack 3. Platforms: AIX, HP-UX, Linux, PowerLinux, Solaris, Windows Maintenance Delivery Vehicle type: 6.1.0-WS-WPG-Advanced-FP3.pak 6.1.0-WS-WPG-Enterprise-FP3.pak These installables can be used across all WebSphere Partner Gateway supported platforms. © Copyright International Business Machines Corporation 2009. 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.1.0.3 Readme Readme documentation for version 6.1 FixPack 3 IBM® WebSphere Partner Gateway, including installation-related instructions, prerequisites,and known issues. These notes describe the changes made in FixPack 6.1.0.3 of IBM WebSphere Partner Gateway, Enterprise and Advanced Editions. This FixPack is cumulative and includes all fixes released in earlier FixPacks for the 6.1 release. IMPORTANT: 6.1 Fixpack3 can be installed and uninstalled ONLY by using IBM® Update Installer for WebSphere® software. Refer to IBM®WebSphere® Partner Gateway Update Installer technical document available at http://www.ibm.com/support/docview.wss?uid=swg27015150. ================================================== Prerequisites Problems were identified with certain functionalities of WebSphere Partner Gateway because of the specific versions of WebSphere Application Server (6.1 FP11 and earlier) and DB2(9.1 FP2 and earlier). To avoid these problems: Pre-requisite APAR fixes for WebSphere Application Server and DB2 must be applied. For instructions on applying and downloading these APAR fixes, see http://www-01.ibm.com/support/docview.wss?rs=2311&uid=swg21257037. OR The minimum level of WebSphere Application Server and DB2 required for WebSphere Partner Gateway v 6.1.0.3 is WebSphere Application Server 6.1 FP13 and DB2 9.1 FP3. For system requirements of WebSphere Partner Gateway Enterprise and Advanced Editions Version 6.1.0.0, see http://www-01.ibm.com/support/docview.wss?rs=2311&uid=swg27009429. ================================================== New in this FixPack This Fix Pack will be installed / uninstalled using IBM® Update Installer for WebSphere® software version 7.0.0.1 and above. For more information, see section Installation instructions. ================================================== Server and Database support The Enterprise and Advanced Editions of WebSphere Partner Gateway Version 6.1.0 FixPack 3 extends support for the following: * WebSphere Application Server Network Deployment V6.1.0.21 * IBM DB2 UDB V9.1 FixPack 6 * IBM DB2 UDB V8.1 FixPack 16 * Oracle 10g Enterprise Edition Release 2 - 10.2.0.4 * Oracle 10g Enterprise Edition Release 1 - 10.1.0.5 For more details, refer to Supported software versions by WebSphere Partner Gateway levels - http://www-01.ibm.com/support/docview.wss?rs=2311&uid=swg27010376. ================================================== Known issues The following problems exists in this fix pack: 1.If you do not change the default value of JMS Queue Factory Name in the External Events section of the console, then events will not be published to the queue. Steps to change the default values of JMS Queue Factory Name: a. Login to the WebSphere Application Server Admin Console and create a new Queue Connection Factory. b. In the WebSphere partner Gateway console, navigate to Administration > Docmgr Administration > Event Engine > External Events. c. Provide the name of Queue Connection factory created in the step 1 for "JMS Queue Factory Name". 2.In Simple Distributed mode of Installation, if just one Application Server(Node) is uninstalled with the Deployment Manager running, then the entire WebSphere Partner Gateway application maybe removed. For more details, please see Steps to Uninstall Simple Distributed mode. 3.When Websphere Partner Gateway 6.1.0 is installed on HP-UX 11i v3 platform, it installs fine, but the uninstaller is not created in the \_uninst folder. a.Stop all the servers b.Change directory by executing: cd /opt/IBM/bcgappsdb/_uninst c.Set the following environment variable: JAVA_HOME= (eg: /opt/IBM/WebSphere/AppServer/java) d.Execute the following to uninstall Websphere Partner Gateway: $JAVA_HOME/bin/java -jar uninstall.jar For more details, refer to Webshpere Partner Gateway support for HP-UX 11i v3. 4. In case of setups where only MAS is installed on a machine and the customer is moving from 6.1.0.0 to 6.1.0.3, bcgEnableRemoteME.jacl must be run manually to create Remote ME. The usage information to run bcgEnableRemoteME.jacl and the script for configuring direct Remote ME communication instead of Local ME communication is as follows: # # Usage: # # Note: To invoke on the Windows platform use wsadmin.bat from the # \bin directory. # # Invocation from /bin: # ./wsadmin.sh -f bcgEnableRemoteME.jacl # ClusterName may be bcgserverCluster for simple distributed mode # ClusterName may be bcgconsoleCluster/bcgdocmgrCluster/bcgreceiverCluster for full distributed mode # # e.g. - Simple Distributed # # ./wsadmin.sh -f /scripts/bcgEnableRemoteME.jacl wpgCell bcgserverCluster Bharathi.in.ibm.com 54276 # # e.g. - Full Distributed # # ./wsadmin.sh -f /scripts/bcgEnableRemoteME.jacl wpgCell bcgconsoleCluster Bharathi.in.ibm.com 54276 # # In case of full distributed mode this script has to be executed on all the clusters except MAS cluster. # # The script has to be run as WPG user and the servers have to be stopped before executing the script. This is applicable only for simple distributed and fully distributed modes. 5. When WebSphere Partner Gateway 6.1 FP3 is installed in Simple mode on Unix Systems, logging into the WebSphere Partner Gateway (WPG) Console fails. This is observed if Update Installer (used to apply WPG 6.1 FP3) is run as a root user and not as a WPGUser. Refer to http://www-01.ibm.com/support/docview.wss?rs=2311&uid=swg21386500 for more details. =============================================================== Installing WebSphere Partner Gateway 6.1 Fixpack 3 IBM WebSphere Partner Gateway Version 6.1 Fixpack 3 can be installed, ONLY by using IBM® Update Installer for WebSphere Software (7.0.0.1 and above). Installing the fixpack is a three step operation. Step A - Setup the IBM Update Installer environment. Step B - Take the backup of WebSphere Partner Gateway application Database. Step C - Install the fixpack. Step A - Setup the IBM Update Installer environment IBM Update Installer Related steps: 1) Download the IBM® Update Installer for WebSphere Software from http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg24020212 2) Follow through 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 necessary updates to the responsefile bcgupdate_.txt present under /responsefiles/, /responsefiles/, and /responsefiles/ are performed. Now you should be ready to use the IBM Update Installer to install WebSphere Partner Gateway fixes and fixpacks on your environment. Step B - Taking the backup of existing database Take the backup of the existing WebSphere Partner Gateway Application database. This is a mandatory step and the database backup taken at this point is to be retained and used as necessary during uninstallation of WPG 6.1 FP3. The backup step is required as uninstallation of the Fix Pack 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 is mandatory whenever WPG 6.1 fix pack 3 is uninstalled. Step C - Applying the fixpack Note: In Case of applying the Fix pack on WPG distributed mode installations (Simple distributed and Fully Distributed); the fixpack .pak file needs to be applied using update installer on all machines that host following WPG components in the specified order: a. WebSphere Partner Gateway Deployment Manager, b. WebSphere Partner Gateway Hub, c. WebSphere Partner Gateway Application DB. In case of applying the Fix pack on WPG simple mode installation, the fix pack .pak file needs to be applied using update installer providing the product location as corresponding to the WPG component locations of: a. WebSphere Partner Gateway Hub and b. WebSphere Partner Gateway Application DB. On Unix machines for Simple mode installation, UPDI is required to be run as WPGUser. This is ONLY applicable for applying WPG 6.1 FP3 pak file using UPDI at the WebSphere Partner Gateway Hub and not for WebSphere Partner Gateway Application DB. 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.sh/bat. 3) In the Product Selection window provide the DMGR installed location as the value for Directory Path. 4) In the Maintenance Operation Selection window select Install maintenance package. 5) In the Maintenance Package Directory Selection window provide the Fix Pack (pak file to be installed) location. 6) In the Available Maintenance Package to Install window ensure that the check box for Fix Pack pak file is checked. Note that when using the IBM Update Installer for WebSphere Partner Gateway, only one pak file should be selected for installation. Else it may give unexpected results. 7) Installation Summary window will list the details about the pak file to be installed on selected location. 8) After this the installation will start and once it is complete the appropriate message i.e., Success or Failed will be displayed. Please verify the logs present under /logs/update/<6.1 FP3 pak name.install> for more information on the fixpack installation. 9) These steps should be performed in all machines where WPG components are installed. ================================================== Uninstalling WebSphere partner Gateway 6.1 Fixpack 3 IBM WebSphere Partner Gateway Version 6.1 Fixpack 3 can be uninstalled using IBM® Update Installer for WebSphere Software (7.0.0.1 and above). Note: Uninstallation of the Fix Pack 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 WPG 6.1 fix pack 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 (excluding Database changes) Note: In Case of uninstalling the Fix pack on WPG distributed mode installations ( Simple distributed and Fully Distributed) , the fix pack .pak file needs to be removed using update installer on all machines that host following WPG components in the specified order: a. WebSphere Partner Gateway Application DB. b. WebSphere Partner Gateway Hub, c. WebSphere Partner Gateway Deployment Manager, In case of uninstalling the Fix pack on WPG simple mode installation, the fix pack .pak file needs to be removed using update installer providing the product location as corresponding to the WPG component locations of: a. WebSphere Partner Gateway Application DB. b. WebSphere Partner Gateway Hub. On Unix machines for Simple mode uninstallation, UPDI is required to be run as WPGUser. This is ONLY applicable for removing WPG 6.1 FP3 pak file using UPDI at the WebSphere Partner Gateway Hub and not for WebSphere Partner Gateway Application DB. 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.sh/bat. 3) Provide the Directory Path in the Product Selection window as the DMGR installed location. 4) In the Maintenance Operation Selection window select Uninstall maintenance package. 5) Select the maintenance package to uninstall, here the Fix Pack pak file. Note that when using the IBM Update Installer for WebSphere Partner Gateway, only one pak file should be selected for uninstallation. Else it may give unexpected results. 6) Uninstallation Summary window will list the details about the pak file to be uninstalled on which location. 7) After this the uninstallation will start and once it is complete the appropriate message i.e., Success or Failed will be displayed. Please verify the logs <.updateconfig.log> present under /logs/update/<6.1 FP3 pak name.uninstall> for more information on the fixpack uninstallation. 8) These steps should be performed in all machines where WPG components are installed. Step B - Restoring the Application Database 9) Once the uninstallation is successfully complete, restore the database using the backup taken before applying the Fix Pack. ================================================== List of Fixes in WebSphere Partner Gateway 6.1.0.3 Component name: Archiver Apar: JR27370 Description: Instead of pointing to the correct DB2 drivers, the BCGArchive script was pointing to an incorrect classpath. It did not have the correct path to DB2 drivers. The path of DB2 Jar files are corrected in this fix pack. Apar: JR28224 Description: While calling AR_PURGEHEADERS stored procedures, WebSphere Partner Gateway returned SQL0532N error. Example: call AR_PURGE_HEADERS('2007-08-15') SQL0532N A parent row cannot be deleted because the relationship "BCGUSER.LG_A ACTIVITY_DTL.FK_ACTIVITY_DTL_1" restricts the deletion.SQLSTATE=23504 In this fix pack, the keyword "EXISTS" in the procedure is replaced with the keyword "IN". Apar: JR28302 Description: The BcgMaintenanceNonRepMaintenance.bat was not purging data from LG_MSG_ARCHIVE table. Component name: Console Apar: JR27408 Description: Every time a document associated to a parent document was routed, the document viewer redundantly listed the parent document. Apar: JR27877 Description: If the profile of a Trading Partner was updated and any of the business IDs of this trading partner was used in channel-attribute, then whenever the partner profile was updated, the value of this attribute was getting reset.Description: Apar: JR27938 Description: Some of the events were not getting excluded while using event exclusion property, and these were displayed in event viewer. Now, with this fix pack, all the routing/runtime events can be excluded. Apar: JR29417 Description: The Partner Interface Process (PIP) Codes were missing in the RNIF interactions display. Apar: JR32420 Description: The maximum allowed length for RETRY INTERVAL and RETRY COUNT fields on the FTP Scripting Gateway configuration screen of the console was not consistent with the same fields on other gateway configuration screens. This has been corrected and these field lengths have been increased to 5 characters each. Apar: JR32429 Description: In "System Administration > DocMgr Administration > Event Engine > External Events" page of the WebSphere Partner Gateway console, Password was shown in readable text. From this fix pack onwards, the password does not appear as readable text. Apar: JR32434 Description: In the FTP Gateway configuration page, the value for the attribute, "Use Unique File Name" was not getting saved properly. Apar: JR32538 Description: New Zealand has extended Daylight Saving Time (DST) effective from September 2007. See the New Zealand Department of Internal Affairs official announcement link - http://www.dia.govt.nz/diawebsite.nsf/wpg_URL/Services-Daylight-Saving-Index?OpenDocument.ICU4J v3.6 takes into consideration these daylight savings. Component name: Console/EDI Apar: JR30160 Description: When you import from an EIF using the EIF Import Wizard, all the translation tables were not getting imported. Translation table entries were missing after the import. This was not an expected functionality while using the DIS client import. EIF Import Wizard was corrected in this fix pack. Component name: Console/Security Apar: JR28425 Description: The resend capability of the console was not available for users of hubadmin group. Apar: JR28653 Description: If you provide an invalid user name and password in the LDAP configuration page of the console, you will be directed to a "Login Failed" error page. Subsequently, the login page was failing to show up unless you close and reopen the browser. Apar: JR32609 Description: In some circumstances, it is possible for an intruder to inject SQL queries by trapping the WPG HTTP request. These SQL injected scripts may get executed and might result in an additional inference on the Database. You can avoid this intrusion by using this Fix. Component name: Database Apar: JR27932 Description: From this fix pack onwards, Huge Maps of more than 1MB size can be imported into WebSphere Partner Gateway. Apar: JR30341 Description: When a duplicate insert was done to the LG_AS_HDR table, it resulted in an incorrect error message. The message, "LG_AS_HDRI_ah1 failed with error code = 2. Error msg = RAN SUCCESSFULLY!” was logged in the System.out file. In this fix pack, this is corrected to display - "LG_AS_HDRI_ah1 failed with error code = 2. Error msg = DUP_VAL_ON_INDEX in LG_AS_DTL". Apar: JR32416 Description: The "java.sql.SQLException: ORA-01873: the leading precision of the interval is too small" error that occurred during resend was fixed in this fix pack. Apar: JR32428 Description: DB2 v8.1 FP16 will be supported from WPG 610 FP3 onwards. Apar: JR32435 Description: In case of FTP Scripting Gateway, the MetaData.sql had two configuration point ID entries for the gateway preprocess handler. When the available handlers were loaded in the Scripting Gateway configuration screen, it displayed erratic behavior. Component name: Destination/FTP Apar: JR32424 Description: Earlier, when the ftp server of the partner became unavailable unexpectedly, the FTP Gateway did not change its state to offline. Component name: Destination/JMS Apar: JR30466 Description: If there were no transport headers attached to the response document, Custom destination PostProcess handler failed to introduce the response document into the webSphere Partner Gateway flow. Apar: JR32436 Description: When you envelope transformed EDI Enveloped documents, it was not delivered to a JMS destination. Component name: Document manager Apar: JR27328 Description: When common file system was full, system went to an inconsistent state. WebSphere Partner Gateway was not able to recover from this error in spite of adequate available space. Apar: JR27482 Description: The 'isSecureTransportRequired' element in the delivery header of the RNIF message was not carrying appropriate values based on the transport type used. Apar: JR28004 Description: In WebSphere Business Integration Connect 4.2.2, the Content type for outbound XML was set as "TEXT/XML". Whereas, in WebSphere Partner Gateway 6.1 it was set as "APPLICATION/XML". This fix pack allows you to set the desired content type for the outbound message. Apar: JR28188 Description: The Event error BCG210033 "Message store failed" occurred for inbound FA 997. Apar: JR28238 Description: In certain SSL transactions, even after receiving HTTP 200 OK, the socket was not closed. Also, in the WebSphere Partner Gateway console, the document remained in "In Process" state. This has been corrected by creating a tunneled Socket with “autoclose” set to "true". Apar: JR28711 Description: In the previous fix pack version, the Server restart was required whenever there was any update to the Validation map. In this fix pack, the validation map is dynamically updated with the latest changes without server restart. Apar:JR29628 Description: Generally, WebSphere Partner Gateway 6.1 queues messages that are not delivered to trading partner due to failed network connection. Earlier, when such queued messages were resent to the trading partners, the messages failed with a "Message Array Index out of range" error. Apar:JR30414 Description: For a signed document, the payload content type did not contain any information about the payload encoding. This caused the UTF-8 data to be saved as ASCII resulting in corruption of data for partners, who use non - WebSphere Partner Gateway software to receive AS Message. In this fix pack, a channel attribute is provided, which can be used to set the encoding on the channel that sets it on the payload. Apar: JR32118 Description: The reprocessDbLogging script is not successful if the ws_runtime.jar is not found in “\deploytool\itp\plugins\com.ibm.websphere. " directory. However, while applying WebSphere Application Server FixPacks, the part changes causing the batch file to fail. As a part of this fix, if the script fails, a warning will be displayed, so that you can change the ws_runtime.jar location. Apar: JR32418 Description:The Common Base Events generated by WebSphere Partner Gateway did not contain the Document ID attribute of the transactions. Apar: JR32431 Description: Generally, if the thread for polling FTP gateway folder is running and FTPScripting gateway is disabled, it will cause the scheduler to stop the polling of FTP Gateway from delivering documents. Earlier, this did not change to normal even after you re enable the FTP scripting gateway. Component name: Document manager/Alert engine Apar: JR28000 Description: In Oracle database, duplicate alert notifications were happening in the case of a multiple node setup. When all the nodes queried the DB for the notification generator, all of them generated alerts. Component name: Document manager/AS protocol Apar: JR27426 Description: In earlier fix packs, "OutOfMemoryException" used to occur while routing several 8 MB documents simultaneously over AS2. This has been rectified to route even several 16 MB documents together. Apar: JR27897 Description: When a binary payload was received, Document Viewer was not showing the DocIDs of the processed documents that were successfully delivered to the trading partner. Apar: JR32421 Description: In case of backend integration with AS Channel, if a blank value was specified for x-aux-process-instance-id, the outbound AS2 message had a blank MessageID. From this fix pack onwards, during such instances, WebSphere Partner Gateway will generate a MessageID. Component name: Archiver Apar: JR32430 Description: Even though the Websphere Partner Gateway received a signed MDN that failed in signature verification, the AS Viewer displayed the MDN as passed. Component name: Document manager/EBMS protocol Apar: JR27671 Description: If the document failed at the gateway, ebMS retries did not work at the ebMS protocol level. Apar: JR27878 Description: When an ebMS PONG message contained the element, , the WebSphere Partner Gateway generated a "Missing SyncCheck Handler" error. Component name: Document manager/EDI Apar: JR27279 Description: If only a handler using the EDISOURCEVALIDATIONFACTORY step was configured for an EDI to EDI interaction, without transformation, then the count of the specified transaction segments in the output was incorrect. Apar: JR27312 Description: This problem has two parts: 1. How to fill User Defined Search Fields in WebSphere Partner Gateway using DIS Transformation maps? (This is not documented) 2. The expectation is that the fields set within the map can be searched using Console document viewer filter. This fix uses DIS Client. You need to set the target properties from UserSeachField1 through UserSeachField10 to search user defined search fields. They can set the fields using the setProperty() command present in DIS Client. For the first input for setProperty, use the values from SearchField1-SearchField10. For example, if you have to set the first User Defined Search Field, set it as setProperty("SearchField1","ABC"). For the 2nd User Defined Search Field, set it as setProperty("SearchField2","DEF") and so on. WebSphere Partner Gateway will read these values and populate them in the database accordingly. Apar: JR28235 Description: The ROD serializer failed during an XML to ROD transformation when the definition of the output ROD document did not have a record ID. Apar: JR28650 Description: Earlier, when the Inbound EDI transactions requested for functional Acknowledgement, the Functional Acknowledgement was not enveloped. Apar: JR29103 Description: The error “SQLException causes BCG310012 event code: Error in removing the transactions from the envelope queue” occurred when the enveloper attempted to envelope the already enveloped and delivered transactions. Apar: JR30859 Description: When map functions ROUND and TRUNCATE were used in transformation maps, it did not result in a correct output. Apar: JR32427 Description: Earlier, the UCI04 Element with value 8 in an inbound EDIFACT FA had a reject status. From this fix pack onwards, it will have an accept status. Apar: JR32432 Description: When locale is Chinese, the error “ArrayIndexOutOfBounds” occurred during transformation. This was not witnessed when locale is en_us. Component name: Document manager/FTP Scripting gateway Apar: JR32446 Description: The FTP error events were lost due to unhandled exceptions and were not displayed. Component name: Document manager/Gateway Apar: JR28474 Description: In a WebSphere partner gateway setup, where the DNS Server was used to resolve Partner IP information, it generated "UnknownHostException errors". This has been corrected such that the hostname to IP resolution is not attempted in WebSphere partner gateway. Component name: Document manager/RNIF protocol Apar: JR27443 Description: Inappropriate 0A1 was generated while routing messages from the backend (RNSC) to RNIF. Here, both sides of the flow (RNSC and RNIF) were trading partners (external partner to external partner). Consider the scenario where the backend trading partner (not a Hub Biz ID) sends RNSC to the router, and the router sends RN to the receiving trading partner. In this case, if the receiving trading partner does not send an acknowledgement before the time limit to perform, the router generates an A1. Instead of directing the 0A1 to the RN trading partner, it directed it to the RNSC trading partner. Also, instead of sending a 900 XML event, generated by the router, to the RNSC trading partner, it sent to the RN trading partner. This was occurring in case of both one way and two way PIPS. Apar: JR28473 Description: When the content validation of the incoming RNIF document is enabled and if the document is invalid, two acks got generated. Removed the generation of the extra acknowledgement in this fix pack. Apar: JR28706 Description: When WebSphere Partner Gateway received an RNIF document with quoted values in the Mime Header, "Content-Location", the document failed. Apar: JR29305 Description: While routing a valid v2.00 RN document, validation error was generated because PIP v2.00 was not in accordance with its corresponding message guideline. Apar: JR32425 Description: RosettaNet Viewer Page displayed the business ID of the source partner instead of a label. Component name: Infrastructure Apar: JR32950 Description: When you restart any application without restarting the server, it will throw a java.lang.UnsatisfiedLinkError. This is because the native libraries were associated with the application. In this FixPack, it is associated at the Server level. Component name: Partner Migration Apar: JR30823 Description: While using BCGMigration import utility, Null pointer exceptions were seen in processConnectionList attribute. These exceptions were seen due to an error in code, as imported enveloper profile names were not looked up properly in later references. Apar: JR31511 Description: While exporting routing objects, the partner migration utility used to fail w ith the exception, "Exception in getRoutingObjectListXML():com.ibm.bcg.shared.VCBaseException". Component name: Receiver Apar: JR30357 Description: DB connections were left open during Receiver startup. This happened when there were a number of Receivers of different transport types. Also, most of these receivers had custom handlers defined for them. Component name: Receiver/File receiver Apar: JR28847 Description: The files that were not picked up by the receiver from file directory were renamed to .tmp files. In spite of that, the receiver was not able to pick them up. This issue was seen on AIX intermittently due to some file latency issues. Component name:Receiver/FTP scripting receiver Apar: JR32417 Description: When Calendar Scheduling option was used, FTP Scripting Target failed to schedule the task on the scheduled days. From this fix pack onwards, there will not be any problems with respect to calendar scheduling options. Component name: Receiver/JMS Apar: JR27826 Description: JMS receiver lost messages when either the common file system was full or MAS DB was not able to persist the business document. In this fix pack, during such scenarios, the JMS Message is rolled back to the MQ Server. Apar: JR32433 Description: When the trace level for the Receiver application was in debug mode, the logs displayed the passwords, defined in a JMS receiver, as plain text. Component name: Security Apar: JR28721 Description: When uploading a certificate in the Console set for UTC time, the certificate expiration time got incorrectly recorded in the database table. It added the UTC time difference to the value in the certificate "valid from" field. Apar: JR29959 Description: When using FTPS receiver, transaction failed during certPath validation, with event error BCG240024. This indicates that the revocation status of the certificate could not be determined. This error occurred regardless of the "false" or "true" value set for attributes:bcg.build_complete_certpath and bcg.checkRevocationStatus. This error happened because the Receiver server was not able to access these attributes. The properties are now added as Common properties, so that both Docmgr and Receiver can access them. ===================================================================== Notices and trademarks: http://www.ibm.com/legal/copytrade.shtml Terms of use: http://www.ibm.com/legal/us/en/