You can download this Hotfix from TIBCO Support Portal (https://support.tibco.com).  You will need to provide your TIBCO Support Portal credentials.  Once logged in you can download the hotfix by selecting the “Downloads” -> “Hotfixes” option, then go to /AvailableDownloads/BusinessEvents/Standard/5.3.0/hotfix-04 to download the Hotfix.

Alternatively, you can use the direct portal link to download Hotfix-04

https://support.tibco.com/s/hotfixes?id=a011a000008nR1vAAE
================================================================================
Closed Issues in 5.3.0_HF-004(This Release)
================================================================================

BE-25023
Server details were displayed in the response HTTP header in the native HTTP
channel.
This was fixed. Now, in the TIBCO BusinessEvents Studio, you can override the
server details, displayed in the response header, using the new channel
property: Server Header, under Channel > Advanced Tab. The default value is
"Apache-Coyote/1.1".
In the case of existing BusinessEvents projects, import them as existing
BusinessEvents project, and the migration process automatically adds this new
property to the existing HTTP channel with the default value. If required, you
can update the property value after import and build a new EAR.

BE-25018
An issue was encountered in hot-deployment when Key was defined in the Processing
Unit tab of the project CDD.

BE-24965
The catalog function Cluster.DataGrid.EvictCache() was deleting instances from
the object table in the database even when the property deleteFromPersistence
was set to false.

BE-24941
An exception was encountered while executing the Instance.updateInstanceFromXML()
function.

BE-24906
The JMS channel connection errors at BusinessEvents engine startup were needed
to be ignored and the connection to the TIBCO Enterprise Message Service servers
should be retried in the background.
This was fixed. Now, a new CDD property is added to ignore startup errors for
the JMS channels: be.jms.ignore.startup.error.channels=<comma separated list of
JMS channel URIs>. The default value is an empty string to retain existing
behavior. Set the value to an asterisk (*) to ignore startup errors for all JMS
channels. Also, set the property be.jms.reconnect.timeout=<value in seconds> to
retry the connection to Enterprise Message Service servers.

BE-24905
An exception was encountered when an event points to schema definitions in a
WSDL file.

BE-24614
The persistence policy of the worklist space was not updated as per the
application CDD.

 

TIBCO BusinessEvents 5.3.0 Hotfix-04 is available

All Supported Platforms

Please refer to attached readme file for installation instructions and list of fixes in this release

5.3.0 hf4, hotfix-04. hotfix04, HF04, HF4, hotfix4