Description:
The closed issues section of the readme has been updated to include the omitted defect that was addressed in this hotfix. Kindly, download the updated readme file attached to this LBN :

===================================================================
Closed Issues in 2.1.1_HF-002 (This Release)

ASG-6471
TIBCO API Exchange Gateway did not support the authentication for validation
API provided by OAuth Server.
To use the "/access_token" validation API, users must send the Authorization header
in the HTTP header of access token request. The username and password for the
Authorization header must match the username and password specified in the
ASG_HOME/mm/config/users.pwd file.

ASG-6451
TIBCO API Exchange Gateway did not include the special characters in the parameter
values of the query string for a facade operation request. 

To pass-through the special characters in the parameter values of the query string, 
set the following properties in the ASG_CONFIG_HOME/asg.properties file:

- com.tibco.asg.runtime.http_client.default_uri_format=false
- tibco.clientVar.ASG/Operation/RequiresQueryDecoding=false

ASG-6432
TIBCO API Exchange Gateway did not support a property to set the timeout value
for HTTP native transport when the target service took more than one minute to
send the response to client.
Use the following properties in ASG_CONFIG_HOME/asg.properties to set the
connection timeout value for HTTP, HTTPS, OAuth HTTP, and OAUth HTTPS transports:

tibco.clientVar.DefaultImplementation/Connections/HTTP/FacadeHTTPConnection/
ConnectionTimeout=60000
tibco.clientVar.DefaultImplementation/Connections/HTTP/FacadeHTTPSSLConnection/
ConnectionTimeout=60000
tibco.clientVar.DefaultImplementation/Connections/HTTP/OAuthWebappsConnection/
ConnectionTimeout=60000
tibco.clientVar.DefaultImplementation/Connections/HTTP/OAuthWebappsSSLConnection/
ConnectionTimeout=60000

ASG-6431
TIBCO API Exchange Gateway did not set the Content-Length header when the client
sent a HTTP request with 1.0 or 0.9 protocol version.

ASG-6414
TIBCO API Exchange Gateway did not provide a script to purge the log data for
Microsoft SQL Server database.

ASG-6407
TIBCO API Exchange Gateway did not forward the "Authorization" header name to
the target service when the "Headers To Forward" field of the request contained
the "Authorization" header name.

ASG-6392
TIBCO API Exchange returned a misleading "Operation Not Found" error message
when a request with an invalid or missing API Key was sent to the gateway.

ASG-6391
TIBCO API Exchange did not export the data from Spotfire analytics dashboard
to PDF, CSV and PPT formats correctly.

ASG-6276
TIBCO API Exchange Gateway returned an error response when the client sent a
request with no user name and password in HTTP header for HTTP basic
authentication using non-preemptive mode.

ASG-6234
The purge database script for MySQL shipped with TIBCO API Exchange Gateway
may throw a foreign key constraint error.

ASG-6226
The value set in  the "items per page" field under Pagination of Config UI
did not work as expected.
For example, the page entries only displayed 10 entries per page irrespective
of the value set in the "items per page" field.

ASG-6221
Kerberos SPNEGO authentication did not work correctly in TIBCO API Exchange Gateway.

ASG-1193
TIBCO API Exchange Manager displayed an alert error for Linked Data Report
when the report was opened with TIBCO Spotfire. The error report referred to
invalid column in the ASG_TRANSACTION_MESSAGES  table of Central Logger database.

ASG-1103
The Central Logger of TIBCO API Exchange Gateway threw a null pointer exception when
it was deployed in cluster mode.

=================================================================================
Closed Issues in 2.1.1_HF-001

ASG-6243
TIBCO API Exchange Gateway did not handle the responses correctly when content-type
was multipart or mixed.

ASG-6217
TIBCO API Exchange Gateway did not provide the properties on the Config UI to support
SSL V3 for native HTTP channel.

ASG-6215
When AS channels were enabled, TIBCO API Exchange Gateway did not use the
asg.properties file specified with -p parameter of asg-engine command to start
Core Engine, and it searched for ASG_CONFIG_HOME/asg.properties file.

ASG-6195
An error "WSS AuthN Failure - Request is not authenticated with username token"
was thrown by TIBCO API Exchange Gateway if the multiple requests were
processed for WSS authentication.

ASG-6156
TIBCO API Exchange Gateway did not correctly encode the query parameters in the facade
operation URL of northbound request.

ASG-6137
TIBCO API Exchange Gateway did not provide the properties in the
ASG_CONFIG_HOME/asg.properties file to enable the SSLv3 support for the northbound
request received through the native HTTP channel.

To enable SSLV3, set the following property in the ASG_CONFIG_HOME/asg.properties
file:
tibco.clientVar.DefaultImplementation/Connections/HTTP/FacadeHTTPSSLConnection/
SSLServerProtocols=SSLv3,SSLv2,SSLv2Hello

ASG-6114
TIBCO API Exchange Gateway did not log the Client IP, Host, SOAPAction, and
ServiceURI headers of the incoming request at the INFO level.

ASG-6107
The REST serializer of TIBCO API Exchange Gateway used the payload as NULL if the
"Transfer-Encoding: Chunked" header was set instead of the "Content-Length" header.

ASG-6106
When the token API was used to retrieve an access token details, the status of the
access token was shown "Active" in the response message for an expired token.

ASG-5422
TIBCO API Exchange Gateway returned different response messages to clients
when the request was sent to the gateway using the facade HTTP channel instead of
being sent using the Apache module.

ASG-5264
Using the Config UI, when the new target operations are added and saved on
"Target Operation Groups" tab, they were not shown in the "Target Operation Groups"
tab.

Omission in "Closed Issues" section of the hotfix readme in TIBCO API Exchange Gateway(R) 2.1.1 Hotfix-002 whose released was announced via Late Breaking News Article,#43778.

TIB_api-exchange-gateway_2.1.1_HF-002_addendum_readme.txt