The customer will be able to download the Hotfix from the TIBCO Support Customer Portal Web UI using their username and password for the TIBCO Support Web page. Once logged on they can find the Hotfix under the Download Menu :

AvailableDownloads/BusinessConnect/ebXML/6.3.0/hotfix-01

For instructions on how can TIBCO customers download / access all GA hotfixes , Refer to Article 000022290 :  https://support.tibco.com/s/article/hotfix.

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

================================================================================
Closed issues in bcebxml_6.3.0_HF-001 (This Release)

EBMS-1836 
Message sent to private process contains duplicate payload in both 'request' and 
'binaryRequest' fields.

To control the behavior, define a new protocol property by following the below 
steps:            
    1. Logon to Tibco Administrator
    2. Go to BusinessConnect >> System Settings >>
                Activated Protocol Plug-ins and Properties >> ebXML
    3. Click Add
    4. Set the below values for the new property
            Property Name : bc.protocol.ebxml.binaryEnabled 
            Property Type : boolean
            Description : Allow binary fields to be used to carry business documents
            in private process communication.
    5. Click Save
    6. Click Save
    7. Click Done

EBMS-1842
Configuration problem after upgrade.

After upgrading to BC 7.2 from 6.3, ebMS3 transactions failed with ERROR status, COMPLETED_WITH_ERROR 
state and 'http://docs.oasis-open.org/wss/oasis-wss-SwAProfile-1.1#Attachment-Content-Signature-Transform 
algorithm and DOM mechanism not available' error.

EBMS-1844
EBMS3SAML2AssertionException when performing EBMS3 "One-way push Message" transaction with ATO setup.

EBMS-1846
Failure to send AS4 messages from host to a particular participant

The SOAP body element of encrypted outbound AS4 messages sent by Tibco BusinessConnect was not empty
and that caused processing failures at specific trading partner systems which expect empty SOAP body
as per ENTSOG AS4 profile.

To allow empty soap body in outbound messages, define a new protocol property by following the below 
steps:            
    1. Logon to Tibco Administrator
    2. Go to BusinessConnect >> System Settings >>
                Activated Protocol Plug-ins and Properties >> ebXML
    3. Click Add
    4. Set the below values for the new property
            Property Name : ebms3.empty.soap.body
            Property Type : boolean
            Description   : Allow empty SOAP body in outbound messages
    5. Click Save
    6. Click Save
    7. Click Done

EBMS-1863
NullPointerException followed by unable to get 'include message into log' flag.

TIBCO BusinessConnect failed to read 'include message into log' system property intermittently
and then the incoming messages were no longer logged in BC_MESSAGES_BIN table.

A new protocol property is introduced to read 'include message into log' property value from cache 
instead of database.

To define the new protocol property, follow the below steps:            
    1. Logon to Tibco Administrator
    2. Go to BusinessConnect >> System Settings >>
                Activated Protocol Plug-ins and Properties >> ebXML
    3. Click Add
    4. Set the below values for the new property
            Property Name : ebxml.includeMessageInBin.flag.cached 
            Property Type : boolean
            Description   : Read 'include message into log' property value from cache instead of database
    5. Click Save
    6. Click Save
    7. Click Done

all platforms

TIBCO BusinessConnect™ ebXML Protocol 6.3.0 hotfix 1 is now available.