Description:
 TIBCO BusinessConnect ebXML Protocol 6.1.0 hotfix 2 has been released.

You can download this Hot Fix from the TIBCO Product Support website using your TIBCO Support username (email address) and password under “Downloads” and then “Hotfixes”

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

           /AvailableDownloads/BusinessConnect/ebXML/6.1.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 6.1.0_HF-002 (This Release)
The following issues are closed in this release:

CR: EBMS-1658
Hibernation entries were not deleted for ebXML.

This issue is fixed.

CR: EBMS-1659
There was an issue with SAML token synchronization across engines when not using the 
shared directory and the RV connection. Also, the current configstore-based token store 
threw the "BCObjectLockException: Item checked out (locked) by another user" error 
when automatic update of tokens was turned on.

With this hotfix, SAML token is stored in the configstore or the runtime datastore. 
A new boolean property must be defined in ebXML protocol plug-in properties to determine 
the target store.
    
        To define ebXML protocol plug-in property:
        a. Login to BC administrator.
        b. Navigate to Business Connect > System Settings > Activated Protocol Plug-ins and 
           Properties > ebXML.
        c. Click Add.
        d. Enter the following values:
            Property Name = ebxml.samlToken.storeInRuntime
            Property Type = boolean
            Description = <optional> Property to save and manage SAML token in BC runtime store
        e. Click Save.
        f. Click Done.

This issue is fixed.

CR: EBMS-1663
The request URL was missing when the outbound HTTP/S URL did not contain any "/".

This issue is fixed.

================================================================================================

Closed Issues in 6.1.0_HF-001

CR: EBMS-1606
When SOAP Fault with "EBMS:0006 EmptyMessagePartitionChannel" error message was 
received as a Pull response from ATO/SBR2 service, BusinessConnect ebXML protocol
didn't continue the pulling, but just forwarded the error message as a response 
to back-office system. 

This issue is fixed. 

BusinessConnect ebXML Protocol keeps pulling the response when it
receives this error message. The error message is forwarded to 
back-office system only when all the pulling attempts are exhausted. 

CR: EBMS-1607  
In ATO/SBR use case when the client side used a "One-Way/Push" operation 
followed by a "One-Way/Pull" operation to simulate a "Two-Way/Push-and-pull" 
transaction, the pulled response cannot be processed correctly since 
BusinessConnect used the operation definition of the "One-Way/Push" operation
to process the pulled response, as this "One-Way/Push" operation have the 
same "Service/Action" value as the "One-Way/Pull" operation, as required by
ATO/SBR2 services.

This issue is fixed.

Customer needs to add a "Two-Way/Push-and-pull" operation in the "Partner Can
Initiate" operation list in BusinessAgreement operation binding, with the same 
"Service/Action" values. BusinessConnect will look to the definitions in this 
"Two-Way/Push and Pull" operations to process the pulled response. This is in 
addition to the "One-Way/Push" and "One-Way/Pull" operations defined in the 
"Host can Initiate" operation list. 

CR: EBMS-1608  
For EBMS3/AS4 standard, Non-repudiation(signature) of received receipts was not 
checked against the local receipt configurations.

This issue is fixed.

CR: EBMS-1610  
For EBMS3/AS4 Standard, Consistency check between "Required Non-repudiation of 
Request/Response" and "Required Non-repudiation of Receipt" during configuration 
was forced, which conflicted with the current status of ATO/SBR2 service where 
the generated receipt might not be signed even the submitted request/response 
was signed.

This issue is fixed. 

The consistency check between "Required Non-repudiation of Request/Response"
and "Required Non-repudiation of Receipt" in configuration UI was removed.

CR: EBMS-1611  
When there's no MPC value provided from private process, BusinessConnect ebXML 
Protocol packaged a "mpc=""" string in the outbound Pull Request, which cannot 
be handled by ATO/SBR2 service. 

This issue is fixed.

CR: EBMS-1621 
When BusinessConnect ebXML Protocol was deployed in Load Balance mode, outbound 
request for ATO/SBR2 services couldn't be signed with error "Couldn't find the 
AUSKey Certificate".

This issue is fixed.

CR: EBMS-1622
SOAP Fault replied from ATO/SBR2 services couldn't be processed successfully
because there was a ATO/SBR2 proprietary fault code value in the SOAP Fault 
message which doesn't comply with the OASIS SOAP schema.

This issue is fixed.
 
CR: EBMS-1632: 
For ebMS3 standard, the signature generated by BusinessConnect 
in outbound messages contains an optional 
"CanonicalizationMethod/InclusiveNamespaces" element which couldnot be processed 
by some other ebMS3 implementation.

This issue is fixed by turning off this.

CR: EBMS-1634
When responses pulled back from SBR2 service contains an empty 
PartInfo/Schema/@Location attribute, it cannot be processed well by 
BusinessConnect while it sends the response message to private process.

This issue is fixed.