Description:
TIBCO BusinessConnect ebXML Protocol hotfix 3 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-03/

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_hotfix03 (This Release)

CR_ID: EBMS-665
The temporary directories named  "ebxmlmime_&lttp>/&ltdate>", which are under
shared directory and used for storing outbound temporary files, have not been
removed even when all the files underneath have been cleaned up.

This has been fixed. The periodic clean-up logic is triggered every 5 minutes.
In hotfix03 (this release), the  temporary directories have been  renamed
from "&lttp>/&ltdate>" to "ebxmlmime_&lttp>/&ltdate>" to better handle these periodic
cleanups.

CR_ID: EBMS-668
When the "responseOnly" synchronous reply mode is chosen, the temporary
outbound response files under the directories
"&ltshared_dir>/ebxmlmime_&lttp>/&ltdate>" on the responder side have not been
cleaned up after the responses have been sent back.

This has been fixed.

CR_ID: EBMS-669
When the synchronous reply mode "none" is chosen and  when only the  
Receipt Acknowledgement Signal but not the MSH Acknowledgement Signal was
requested, the temporary outbound Receipt Acknowledgement Signal files  
under the directories "&ltshared_dir>/ebxmlmime_&lttp>/&ltdate>" on the sending
side have not been cleaned up after the receipts were sent out.

This has been fixed.

CR_ID: EBMS-666
The Outbound jobs starting from the checkpoint have been blocked by the
duplication detection  mechanism. This occurred when the engine restarted,
or when the master engine switched to the standby engine in the fault-
tolerant deployment.

This has been fixed.

CR_ID: EBMS-670
This issue was introduced in a fix of CR 1-9N1X3A in 5.0.0_hotfix02 where,
in addition to  the original text based "request" or "response" field,  a
binary field was introduced in the request and response messages sent to
the private process. However, this behavior is by default, which is not
backward compatible.

This has been fixed. Users need to explicitly set the property
"bc.protocol.ebxml.binaryEnabled=true" to enable this feature.

The fix of 1-9N1X3A in hotfix02 is also incomplete in the sense that it
does not include the detailed description, which is as follows:

In addition to the original text based "request" or "response" fields, the
binary fields were introduced in request and response messages that are
sent to the private  process.  These binary fields are named "binaryRequest"
and "binaryResponse" respectively and  contain raw bytes of the payload
received from the inbound transport. This is useful in cases when the private
process is using an RV encoding different from the  encoding used by the
TIBCO BusinessConnect engine (always UTF-8 after the release 5.0).
Customer's private process is responsible to decode the byte sequence into
text messages.

For outbound, customers can also populate the "binaryRequest" or
"binaryResponse" field in the messages sent from private process to the TIBCO
BusinessConnect engine; the byte sequence will be sent to trading partner as
a payload without any changes.

Both the inbound and outbound features are enabled by specifying the property
in the TIBCO BusinessConnect engine TRA file:

"java.property.bc.protocol.ebxml.binaryEnabled=true".

CR_ID: EBMS-671
The Notify operation’ audit log was not correct when the Notify operation was
picked up from the checkpoint by a standby TIBCO BusinessConnect engine;
however, a new audit log post was generated  with "NOTIFICATION_FROM_PP" as  
the last state, and no information would show that  it was coming  from the
checkpoint.

This has been fixed.

CR_ID: EBMS-674
Non-repudiation audit log occurs when it is dis-allowed on ebXML protocol
binding.

This has been fixed.

TIBCO BusinessConnect ebXML Protocol hotfix 3 has been released.

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