Please follow instructions below to download the hotfix: 
 ================================================ 
- Login to TIBCO Support Portal using your TIBCO Support Portal credentials.  
- After logging in select menu option “Downloads” -> “Hotfixes” , then navigate to /AvailableDownloads/BusinessEvents/EnterpriseEdition/6.2.2/hotfix-05 to download the Hotfix.
- Alternatively, you can use the direct portal link below to download 6.2.2 Hotfix-05. 
Direct Download Link

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

Closed Issues in 6.2.2_HF-005 (This Release)

BE-32307
For TEA Server deployment, Global Variables in GUI cannot be modified by editing
the profile.
The Global Variables are required to modify directly in the properties file in 
teagent/repo/<application> when needed.

BE-32298
In TIBCO BusinessEvents, Java version is upgraded to 11.0.21 to address the
below CVEs:

Oracle Critical Patch Update Advisory - January 2023:
CVE-2023-21835 
CVE-2023-21830 
CVE-2023-21843

Oracle Critical Patch Update Advisory - April 2023:
CVE-2023-21930 
CVE-2023-21967 
CVE-2023-21954 
CVE-2023-21939 
CVE-2023-21938 
CVE-2023-21968 
CVE-2023-21937

BE-32285
When the data is migrated from BE 5.X (TIBCO ActiveSpaces 2.x) to 
BE 6.2.2 (Apache Ignite), with the Legacy lookup enabled, scheduled events are  
not triggered in BE 6.2.2 even though the tuple counts are matching.

BE-32272
When the CacheAgent that acts as a manager node is stopped, the other CacheAgents
should proceed without any errors. But the CacheAgents generates an exception and 
the Ignite Cache Cluster is unavailable. This issue occurs for Persistence Type 
as Shared Nothing.

BE-32264
In TIBCO BusinessEvents, Apache Tomcat is upgraded to the version 9.0.83 to 
address the below Apache Tomcat CVE vulnerability:
CVE-2023-42795
CVE-2023-45648

BE-32249
The QueryCache rule function works properly with Active Spaces but fails for 
Apache Ignite. When running the query on Query.Metadata.getColumnCount, the 
column count sometimes returns 0 which is incorrect.

BE-32247
LDAP JMX authentication is not working properly.

The following JMX authentication properties are added for secure LDAP usage:
<property name="be.mm.auth.ldap.ssl.trustStore" value="<locationTrustStoreFile_jks>"/>
<property name="be.mm.auth.ldap.ssl.trustStoreType" value="JKS"/>
<property name="be.mm.auth.ldap.ssl.trustStorePassword" value="<trustStorePassword>"/>

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