TIBCO ActiveMatrix Binding Type for REST 3.3.0. Hotfix 005 can be downloaded from TIBCO Support website

https://support.tibco.com

Log in using your username and password.,  Once logged on you can find the hotfix under the Downloads Menu:
/AvailableDownloads/BusinessWorks/BW_Service_Engine/5.11.0/TIB_amxrsbt_3.3.0_hotfix005

TIBCO ActiveMatrix Businessworks ServiceEngine 5.11.0 Hotfix, TIB_amxrsbt_3.3.0_hotfix005 is now available.

This hotfix applies to the following products and versions when installed in combination with TIBCO ActiveMatrix Binding Type for REST 3.3.0: - TIBCO ActiveMatrix Service Bus 3.3.0 - TIBCO ActiveMatrix Service Grid 3.3.0 - TIBCO ActiveMatrix BPM 2.2.0, 3.0.0, 3.1.0, 4.0.0, 4.1.0 - TIBCO Business Studio BPM Edition 3.6.0, 3.7.0, 3.8.0, 3.9.0, 4.0.0, 4.1.0 - TIBCO ActiveMatrix BusinessWorks Service Engine 5.11.0 + Hotfix 005 NOTE: TIBCO ActiveMatrix 3.3.0 Hotfix 013 or higher is required for this hotfix to function as expected.

================================================================================
Closed Issues in 3.3.0_hotfix005 (This Release)

RSBT-641
In a scenario where Mediation Implementation Type (IT) Component is wired to a
REST Binding Type (BT) Reference, and the Reference Binding receives a fault
message from an external service, the HTTP Status Code for which has not been
specified in the REST Resource Configuration (RRC) file, the exchange would
simply hang and the requesting client would not receive any response.
 
With this enhancement, the fault handling for REST Reference Bindings has been
enhanced to handle faults that are not listed in the RRC file. For example,
if the RRC file contains Error entries for HTTP status codes "401" and "402"
respectively, and the REST Reference Binding receives a fault with HTTP status
code "404", the fault will be propagated to the Mediation IT and subsequently,
the requesting client (depending on the Mediation IT implementation).

Note that at least one Declared Fault (Error with valid HTTP Status Code) must
be specified in the RRC file to achieve the expected behavior.

To enable this enhancement, set the property
"com.tibco.amf.runtime.bindingtype.rest.enableExtendedUndeclaredFaultSupport" to
'true' in the Runtime node. The value can be specified in the Runtime Node's TRA
file as follows:

java.property.com.tibco.amf.runtime.bindingtype.rest.enableExtendedUndeclaredFaultSupport=true   

and also using the TIBCO ActiveMatrix Administrator UI:
property=com.tibco.amf.runtime.bindingtype.rest.enableExtendedUndeclaredFaultSupport
value=true
 
The default value of this property is 'false'.

RSBT-656
In a DAA containing a REST Reference Binding, if the REST Resource Configuration (RRC)
file corresponding to the Binding contains an Error (Declared Fault) definition which
doesn't specify the HTTP Status Code, it resulted in deployment failure (NullPointerException)
in TIBCO ActiveMatrix Administrator. Since specifying HTTP Status Code is mandatory for
Error definitions, this fix addresses the NullPointerException by providing a more
meaningful exception.

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

You can also download the hotfix using the below link:

https://support.tibco.com/s/hotfixes?id=a011a000009RxYZAA0

TIB_amxrsbt_3.3.0_hotfix005_readme.txt 
TIB_rsbt_3.3.0_relnotes.pdf 
TIB_rsbt_3.3_binding_development.pdf