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 the download the hotfix by selecting the “Downloads” -> “Hotfixes” option. Then go to the AvailableDownloads/BusinessWorks/6.4.2/hotfix-16.

================================================================================
Closed Issues in 6.4.2_HF-016 (This Release)        

AMBW-40628
The Signature verification failed exception was displayed when calling the BW SOAP endpoint
with the Integrity policy and the protected token was not set.

AMBW-40088
The null error was generated in the AppNode logs with a custom TeraData JDBC Driver
and when the connection idle timeout had passed.

AMBW-39928
Now you can capture the details of query parameters sent as a part of the incoming request to
a REST service.
Set the following logger in the logback.xml file :

<logger name="com.tibco.bw.binding.rest">
    <level value="DEBUG"/>
</logger>

AMBW-39926
Logs for the Invoke REST API activity now also display the response body information.
Set the following logger in the logback.xml file:

<logger name="com.tibco.bw.palette.restjson.runtime.RestInvoke">
<level value="DEBUG"/>
</logger>


AMBW-39565
The Parse JSON activity could not parse a JSON key having a value of Array type with length
more than 512 characters.

AMBW-39089
Now you are able to log input XML and output JSON for the Render JSON activity
when schemaType is XSD by enabling Debug level logs.

Set the following logger in the logback.xml file :

<logger name="com.tibco.bw.palette.restjson">
<level value="DEBUG"/>
</logger>

AMBW-38589
Now you are able to log input JSON and the output XML for the Parse JSON activity
when schemaType is XSD by enabling Debug level logs.

Set the following logger in the logback.xml file :

<logger name="com.tibco.bw.palette.restjson">
<level value="DEBUG"/>
</logger>

AMBW-38473
No method was not available in the Method drop-down list on the General tab of the Java Invoke
activity.

AMBW-28785
The performance of JDBC palette activities is improved.

Set the following VM arguments :

-Dbw.application.jdbc.validateConnection.frequency=55
The frequency means how often to check connection validity when inside the pool.
This value must not be above the Connection Idle Timeout property in the
JDBC Connection shared resource.

-Dbw.application.jdbc.validateConnection=false
Check whether to validate the connection prior to send it to the activities.

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