Description:
TIBCO BusinessConnect Protocol 5.2.0 hotfix 2 has been released.

You can download this Hot Fix from the TIBCO Product Support FTP server using your eSupport username and password, at

           ftp://support-ftp.tibco.com

Once you have successfully logged into the server, you will find the hotfix packages under

           available_downloads/ActiveExchange/BusinessConnect/5.2.0/hotfix-02/

Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.

Closed Issues in 5.2.0 Hotfix 2 (This Release)

CR: 1-8LX1HM
On migration from version 5.1.3 to version 5.2.0, BusinessConnect failed to detect the existence of audit/nr/runtime tables upon new installation creation against a database that contains existing audit/nr/runtime data specifically from version 5.1.3 and caused the tables to be dropped and recreated. All the existing data were removed inadvertently. This issue is fixed in bcwebadmin.war administrator plugin that requires uploading to the administrator domain (see installation instructions below).

CR: 1-8HSR0H
For tibXML private process messages, the tracking information in the RV AEMsg was not interpreted and published. This created a backward compatibility issue with legacy private processes that rely on the tracking information for back office integration. The tracking information is now processed and published in the "^tracking^" RV message field for all tibXML private process messages.

CR: 1-8ME915
For tibXML RESPONDER.ACK message to the private process, the aeClass path under the "^prefixList^" RV message field was incorrectly output for EZComm instead of tibXML. This caused an java ClassNotFoundException on the custom subscribing application for back office integration developed on SDK. This issue is fixed.

Closed Issues in 5.2.0 Hotfix 1

CR: 1-8HSQYI
For outbound EZComm email and AS1 notify request, BusinessConnect 5.2 always dynamically generates the email subject based on the operation and the transaction ID. This created a backward compatibility issue with request generated from BusinessConnect 5.1 where user can specify any subject and is sent to trading partner as is. This issue is fixed by configuring the following boolean property to preserve the configured email subject that reverts back to the BusinessConnect 5.1 behavior:

ezcomm.notify.email.preserveSubject.

Add the property in TIBCO Administrator as follows:
1. Go to BusinessConnect-&gtSystem Settings
2. Select Installed Protocols | EZComm plugin
3. Add a boolean property: ezcomm.notify.email.preserveSubject

NOTE: This property will not be exported on configuration export (CSX).  It will have to be explicitly re-configured upon importing on new BusinessConnect installation.