Description:
TIBCO BusinessConnect ebXML Protocol 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/ebXML/5.0.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.0.0_hotfix02 (This Release)

CR_ID: 1-ACIN11
BusinessConnect ebXML50 was not properly cleaning the outbound temp files in
the working share folder. This has been fixed.
        
CR_ID: 1-9LTY63
The  "type" attribute for "PartyId" was missing in a message if the
participant's domain type was specified as "uri". This has been fixed.
        
CR_ID: 1-9N1X3A
There was an invalid UTF-8 sequence error when processing a business ducument
with national characters. This has been fixed.  

CR_ID: 1-AEMYMF
No information was sent to the private process when TIBCO BusinessConnect
ebXML 5.0 finished with retries to the trading partner and the accumulated
retries duration was greater than the persistent duration.
This has been fixed.
        
CR_ID: 1-9LJ8TI
The"Validate Incoming Document" checkbox was missing for Notify type
operations. This has been fixed.

CR_ID: 1-9N1X3A

Two new fields are introduced in the INITIATOR.REQUEST and RESPONDER.REQUEST RV messages that carry the raw bytes of the payload, “binaryRequest” and “binaryResponse” respectively.  If the customer doesn’t want this feature, they have to explicitly set the value of these new fields in the tra file:

“java.property.bc.protocol.ebxml.binaryEnabled” to be “false”; the default value is “true” if this property doesn’t exist in the tra file.

TIBCO BusinessConnect ebXML Protocol hotfix 2 has been released.

Product: TIBCO BusinessConnect ebXML Protocol Version: 5.0.0 OS: All --------------------