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-05.

================================================================================
Minimum Requirements

TIBCO(R) Enterprise Administrator 2.3.0_HF-002 and later.
================================================================================

Closed Issues in 6.4.2_HF-005 (This Release)

AMBW-31570
Swagger 2.0 definitions that had other files in related directories
could not be imported to TIBCO ActiveMatrix Businessworks.
Note : When you import the swagger file, first generate the XSD schema.
Right click the swagger json file, and click Refactor > Generate XSD Schema
to generate the XSD schema.
Create the service using the top-down approach, and change the schema element
in the Input Editor tab of the generated Reply activity.

AMBW-31527
The Invoke REST Reference displayed the error,  
"java.lang.IllegalArgumentException: prefix cannot be null when creating a QName"
under heavy load of concurrent REST requests, or during load testing.

AMBW-31406
The "String index out of range: -1" error was generated with the Microsoft SQL
data direct driver, when the driver was used with the server instance name
instead of a port number in the JDBC shared resource.

AMBW-31353
Messages with duplicate prolog could not be parsed in the Parse Xml activity.
To avoid producing an XML declaration in the Transform Xml activity output,
the following property must be added in the AppNode or AppSpace config.ini
file:  

bw.palette.xml.transform.omitXMLDeclaration=true

From TIBCO Business Studio, add the VM argument

-D bw.palette.xml.transform.omitXMLDeclaration=true.

If the property is not present or has a value false,
it produces an XML declaration in the Transform Xml activity output.

AMBW-31346
Due to the missing name attribute in a process, the argument cannot be null
error was displayed when the process was opened after migration.

AMBW-31345
Closing and restarting TIBCO Business Studio caused the previously added
components to disappear.

AMBW-31342
When module properties were added to the shared module and the application
project was imported, the properties of the application were not updated after
import.
The following error was displayed: "Application configuration error.
A set of module properties included in the BW application are not in sync
with the module properties configured for the module. Re-include module in
the application".
This has been fixed, and now TIBCO Business Studio includes or updates the
missing properties of the application when the application is included
in the workspace.

AMBW-31322
When logging a large validation exception resulted in the out of heap space
condition.

AMBW-31261
Mappings in the End activity were not migrated.

AMBW-31240
When using the XML Transform activity, the EmptyStackException error was
displayed during XSLT transformation.

AMBW-31239
When creating a concrete WSDL, TIBCO Business Studio displayed a Null Pointer
Exception, when schemas that imported other schemas with no target
namespace for a SOAP service.

AMBW-31160
During migration, process loading failed with the out of memory issue leading
to the Java heap space error.

AMBW-31064
httpVersion, statusCode, and reasonPhrase data elements of the statusLine data
element were not populated in the fault output of the Send HTTP Request activity
when the HTTP server returned the 500 HTTP response.

AMBW-30993
When creating a concrete WSDL, TIBCO Business Studio displayed the
Null Pointer Exception, when schemas included other schemas with no target
namespace for a SOAP service.

AMBW-30932
BWAGENT REST API role management failed to grant read access rights to all
the browse REST APIs.

AMBW-30864
The information added in the Summary field in TIBCO Business Studio
did not appear in the Swagger file on deployment when the top-down process
workflow was used.

AMBW-30715
The Get Context activity could not fetch Security Context Certificate values, when
the Expose Security Context check box was selected in the SOAP service binding.

AMBW-30261
The MTOM attachment style did not support SOAP 1.1 specification at the server
side.
This has been fixed, and now the MTOM attachment style supports both SOAP 1.1,
and SOAP 1.2 specification.

AMBW-29315
When an XSD defined inside a WSDL was used in the REST service, the
JSON validation error occurred when invoking the service.

AMBW-28549
The error, "No matching ns9:property" was reported when
Refactor > Repair BusinessWorks Projects was used with the option,
Recover Activity IDs.
This is now fixed and the error is no longer reported.
With this fix the Recover Activity IDs option in the Refactoring Wizard
has been replaced with the Quick Fix option.
To apply Quick Fix, perform the following steps:
1.Navigate to Windows > Preference > BusinessWorks > Validation and change
the preference for Recover Activity ID and Recreate Activity ID
from Warning to Error.

2.Right click on the errors related to Recover Activity Id,
Recreate Activity ID, and select the Quick Fix option.
 
AMBW-26871
Incorrect schemas were generated when composition was used in two Java
classes and both the Java classes were used in the Java To XML activities in the
same application module.

AMBW-25310
Importing the XSD file from a shared module now directly adds the shared module
in the dependency list.


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