Please follow instructions below to download the hotfix:
Login to TIBCO Support Portal ​using your TIBCO Support Portal credentials.  
Once logged in you can download the hotfix by selecting the “Downloads” -> “Hotfixes” option, then navigate to /AvailableDownloads/BusinessEvents/EnterpriseEdition/6.1.0/hotfix-01 to download the Hotfix.

Alternatively, you can use the direct portal link to download Hotfix-01. 
https://support.tibco.com/s/hotfixes?id=a012L00000QJsPYQA1

================================================================================
Closed Issues in 6.1.0_HF-001 (This Release)
================================================================================
BE-29599
When XPATH functions were used in decision tables,
heap usage and performance degradation was observed over a period of time.
As a fix, set the optional property
com.tibco.xpath.cache.disable to true (com.tibco.xpath.cache.disable=true) in 
the CDD file at the cluster level.
This disables the caching of the XPath expressions.
When not set, the property assumes the false value.

BE-29553
For the PostgreSQL database, the DBConcept importer converted numeric fields to 
String properties.

BE-29532
When using the JSON payload serialization, the namespace/type information was 
lost.
 
BE-29529 
The wal-store-path property was not working for the Apache Ignite cache. 

BE-29526
Support for the checkpointPageBufferSize parameter was not present for 
Apache Ignite.
The following properties were added to resolve this issue:
* data-region-checkpoint-page-buffer-size - Sets the amount of memory 
  allocated for the checkpoint temporary buffer. The buffer is used to 
  create temporary copies of pages that are being written to disk and 
  updating in parallel while the checkpoint is in progress.
* wall-archive-after-inactivity - Time in milliseconds to run 
  auto-archiving segment (even if incomplete) after the last record logging.
* checkpoint-threads - Sets the number of threads to use for checkpoint
  purposes.
* checkpoint-write-order - Sets the order (RANDOM/SEQUENTIAL) of writing pages 
  to the disk storage during the checkpoint.

BE-29523
Rule Management Server is now supported with TIBCO FTL as a cluster provider and
and TIBCO ActiveSpaces as the store provider in Store OM mode.
Supported TIBCO FTL Version: 6.5.0 and above
Supported TIBCO ActiveSpaces Version 4.5.0 and above
The new RMS_FTL.cdd file can be found at the location BE_HOME/RMS/bin.
Following are the steps to run RMS with TIBCO FTL as the cluster provider and TIBCO ActiveSpaces as the store provider:
#1. Generate TIBCO ActiveSpaces schema scripts for RMS using the following command:
cd BE_HOME/bin
./be-storedeploy -c BE_HOME/rms/bin/RMS_FTL.cdd -o BE_HOME/rms/bin/rms_as4 -s ACTIVESPACES BE_HOME/rms/bin/RMS.ear
Note: For more details about this command, 
refer to "Generating Deployment Scripts for a Store" in TIBCO BusinessEvents Developer’s Guide.
#2. Start the TIBCO FTL server and the TIBCO ActiveSpaces grid with the name "rms_grid" (or a name of your choice).
On this grid, run the following two scripts:
a) BE_HOME/bin/create_tables_as.tibdg
b) Script generated in step #1 above. 
E.g. BE_HOME/rms/bin/rms_as4.tibdg.
Note: Refer TIBCO FTL, TIBCO ActiveSpaces 4.x documentation for running the TIBCO FTL server and the TIBCO ActiveSpaces grid.
3. Start the RMS server using the RMS_FTL.cdd with the following command:
./be-rms -c RMS_FTL.cdd
Note: For customizing the FTL server or the ActiveSpaces url or grid name, 
configure GV values under the FTL_ActiveSpaces group in RMS_FTL.cdd cluster properties.

BE-29521
Unexpected behavior was observed when the state model handled out-of-order 
events (transition not triggered) and L1Cache was disabled (with single 
inference agent) or when multiple inference agents were started.

BE-29515
The studio JDBC schema export utility did not create CLOB or extended types when appropriate
options were selected.

BE-29468
An exception occurred when the statemachine was used in the TIBCO FTL cluster 
and Apache Ignite cache setup, and the be.engine.id.useLegacy property was set 
to "false" (default).

BE-29461
The option to enable the debug log level for Apache Ignite logs was not present.
Now, you can configure the log level for Apache Ignite logs independently of the engine log 
level using the module name as org.apache.ignite. For example, you can specify a level value 
"*:info org.apache.ignite:debug" for Apache Ignite. In this example, the log level is 
DEBUG while all engine log level is set to INFO.

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

Please refer to attached hotfix readme file for installation instructions, affected files and list of fixes in this release.