Description:
================================================================================
NOTE: See attached Readme document for installation instructions and list of issues resolved in this hotfix.
================================================================================

The TIBCO® API Exchange 2.1.0 Hotfix 004 can be downloaded from the TIBCO Product Support file transfer server, mft.tibco.com, using your username and password for the TIBCO Support Central website. Please note you should use an FTP or SFTP client or command-line FTP.
TIBCO employees must use a secure protocol.

Server name: mft.tibco.com
Credentials: use your TSC (TIBCO Support Central website) login.
Browser:  https://mft.tibco.com
FTP: port 21
SFTP: port 22

Once logged on you can find the hotfix under:

AvailableDownloads/_Additional_Products/APIExchange/2.1.0/TIB_api-exchange-manager_2.1.0_hotfix04
AvailableDownloads/_Additional_Products/APIExchange/2.1.0/TIB_api-exchange-gateway_2.1.0_hotfix04

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

TIBCO® API Exchange Gateway
=================================================================================
Introduction

Hotfixes are cumulative. This hotfix includes all previous generally available
hotfixes for TIBCO API Exchange Gateway product.
See the section "Closed Issues in 2.1.0_HF-004" to check the resolved issues in
this hotfix.

=================================================================================
Closed Issues in 2.1.0_HF-004 (This Release)

ASG-5227
TIBCO API Exchange Gateway now logs the client IP address, host, SOAPAction, and
ServiceURI fields of the incoming request message when the detail level logging
is enabled.

ASG-5207
TIBCO API Exchange Gateway now includes CORS filter in web.xml file of
OAuthWebapp archive.

ASG-5175
TIBCO API Exchange Gateway now generates a token when the owner information is
stored in the LDAP server for OAuth authencation.

ASG-5150
The Gateway User Interface no longer throws an error when the user
is authenticated against LDAP server in search mode.

ASG-5121
The Gateway core engine now interprets the request URL correctly if the query
string contains the "#" character.

ASG-4990
The Gateway core engine now publishes only the error transactions to the
central logger. For more information, refer to TIBCO API Exchange Gateway
Addendum, tib_apix_2.1.0-HF-004_addendum.pdf, provided with this
hotfix.

ASG-4984
The Gateway core engine now returns correct HTTP status code (429) for the error
response message as "Too Many Requests".

ASG-4966
The Gateway core engine no longer adds the asynchronous response into the context
header of the requests sent over JMS transport.

ASG-4954
TIBCO API Exchange Gateway now encodes the query parameters containing non-ascii
characters in the URL of the request sent over http transport.

ASG-4951
The Gateway Configuration User Interface now displays the 'isAsync' flag for
SOAPJMS channel.

ASG-4889
TIBCO API Exchange Gateway now supports the TargetOperation in authorization
policy. This allows the end users to apply the policies on TargetOperations
using a single policy file or at least a fewer files.

ASG-4880
The Gateway User Interface now allows the end users to disable the validation
on specific fields (for example, Timeout under Target Operation,
destination name for SOAPJMS and ESB channels) which can be defined with
the global variables in the ASG_CONFIG_HOME/asg.properties file.

ASG-4868
TIBCO API Exchange Gateway now allows you to set the default content-type
header for the HTTP request if the request does not contain any content-type
header. You can set the default content-type using the following global
variable in ASG_CONFIG_HOME/asg.properties file:
- tibco.clientVar.ASG/Response/DefaultContentType
For example, the value of DefaultContentType can be "application/xml",
"text/xml","application/json".

ASG-4864
TIBCO API Exchange Gateway now refers to the value of deliveryMode set
using tibco.clientVar.ASG/SharedResources/JMS/deliveryMode=<delivery_mode_number>
global variable in the ASG_CONFIG_HOME/asg.properties file for the southbound
requests sent through SOAPJMS channel.

ASG-4860
TIBCO API Exchange Gateway now supports a function to parse xmlstring in the
response of the JMS message. This function allows you to set the data in the HTTP
headers of the response message.

ASG-4850
TIBCO API Exchange Gateway now supports the plain text passwords for file based
authentication. Users can enter the plain text password with empty salt in the
XML file. TIBCO API Exchange Gateway generates the encrypted password,  updates
the password and salt in the XML file after processing the XML file.

ASG-4836
TIBCO API Exchange Gateway no longer sends some duplicate headers when
the "Headers To Forward" is set as "*" for a target operation configuration.

ASG-4832
TIBCO API Exchange Gateway no longer reports an error in FacadeResponse.rule
when the <TIBCO_HOME>\asg\2.1\projects\ASG_DefaultImplementation project is
imported using TIBCO API Exchange Gateway Studio.

ASG-4817
The performance of Gateway User Interface is extremely slow when there are
large number of entries stored in the configuration (CFG) files under
ASG_CONFIG_HOME for a project configuration.

ASG-4800
TIBCO API Exchange Gateway no longer shows the "PartnerOperation Timeout"
messages for the ERROR level logging in the gateway core engine log file.

ASG-4766
The Gateway core engine no longer throws the
"java.lang.ArrayIndexOutOfBoundsException" when the detail level
logging is enabled for the central logger and large number of requests are
sent from multiple users concurrently.

ASG-4698
TIBCO API Exchange Gateway now provides a function to encode and decode
entities in a XML document sent as a response by the target service.

ASG-4061
The Gateway core engine no longer depends on TIBCO Hawk when the gateway
core engine is started as a windows service. To start the gateway core
engine as a windows service, you must comment the HAWK_HOME variable in
the ASG_HOME/bin/asg-engine.tra file as follows:
#tibco.env.HAWK_HOME=

ASG-661
TIBCO API Exchange Gateway now supports an asynchronous mode on the
TargetOperation for the request sent over SOAPJMS transport.

ASG-554
TIBCO API Exchange Gateway now allows the users to set the non-standard JMS
header fields such as "Host", "Content-Type", "Content-Length" from the
HTTP headers of the request message. For more information, refer to
TIBCO API Exchange Gateway Addendum, tib_apix_2.1.0-HF-004_addendum.pdf,
provided with this hotfix.


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

TIBCO® API Exchange Manager
==================================================================================
Introduction

Hotfixes are cumulative. This hotfix includes all previous generally available
hotfixes for TIBCO API Exchange Manager product.
See the section "Closed Issues in 2.1.0_HF-004" to check the resolved issues in
this hotfix.

==================================================================================
Closed Issues in 2.1.0_HF-004 (This Release)

ASG-4781
TIBCO API Exchange Manager now displays appropriate error messages when it
fails to publish the message to TIBCO API Exchange Gateway.

ASG-4728
TIBCO API Exchange Manager now displays the detailed error description for
the errors returned from TIBCO API Exchange Gateway for the host admin users.

ASG-4712
The performance of some of the pages such as "Global Configuration" and
"Users Manager" on the administrator site is now improved when the site has
more than 1000 registered users.
To improve the performance, make sure to disable the following fields under
"API Manager Configuration and Email Templates" by setting the value as "No":

- Show Permissions
- Show Text Filters.
================================================================================

TIBCO® API Exchange (Gateway and Manager) 2.1.0 Hotfix 04 is now available.

This hotfix applies to the following products and versions: - TIBCO® API Exchange Gateway 2.1.0 - TIBCO® API Exchange Manager 2.1.0

TIB_api-exchange-gateway_2.1.0_HF-004_readme.txt, TIB_api-exchange-manager_2.1.0_HF-004_readme.txt, tib_apix_2.1.0-HF-004_addendum.pdf, tib_asg_migration200To210.pdf