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 001 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_hotfix01
AvailableDownloads/_Additional_Products/APIExchange/2.1.0/TIB_api-exchange-gateway_2.1.0_hotfix01

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

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

Hotfixes are cumulative. This is the first hotfix for TIBCO API Exchange Gateway
product. See the section "Closed Issues in 2.1.0_HF-001" to check the resolved
issues in this hotfix.

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

ASG-4829
The Central Logger of TIBCO API Exchange Gateway should not write empty rows to
the ASG_THROTTLE_USAGE table.

ASG-4826
When the target service is SSL enabled and Authentication policies are enforced,
TIBCO API Exchange Gateway core engine throws the error during authentication as
the CLASSPATH specified in <ASG_HOME>/bin/asg-engine.tra file does not include
<TIBCO_HOME>/tools/lib directory. Make sure that you update the CLASSPATH to
include <TIBCO_HOME>/tools/lib directory.

ASG-4810
The BookQueryBE example throws a fatal error because the XML file it uses
contains invalid characters.

ASG-4814
TIBCO API Exchange Gateway does not remove the "chunked" encoding header from
the response message received from the backend services.

ASG-4798
TIBCO API Exchange Gateway core engine throws unsupported encoding exception when
it processes a northbound response message containing the encoding in double
qoutes specified in the Content-Type header.

ASG-4790
TIBCO API Exchange Gateway core engine does not handle the request correctly when
both WS-Security and HTTP basic headers are present in the request message. The
security headers are not stripped from the request message before the request
is sent to the target application.

ASG-4779
The Mapper of the TIBCO API Exchange Gateway does not handle the nesting of
<payload> element inside <payload-xml> elements of the request properly
when isBinary attribute on payload is enabled.

ASG-4767
The property used to disable the BSP compliance check in WSS properties file
does not work. Add the following property to WSS property file to disable BSP
compliance:
     com.tibco.trinity.runtime.core.provider.authn.wss.wssBspCompliant=false
    
Note: The default value of above property is true as BSP compliance is
      enabled by default. Restart the TIBCO API Exchange Gateway core engine
      after the property is added/edited.

ASG-4758
TIBCO API Exchange Gateway core engine throws a SSL socket error when the
certificate and identity url are configured for HTTP(s) channel for a request.
Notes:
------
     1. You must use the following property in <ASG_CONFIG_HOME>/asg.properties file  
        for facade HTTPS Channel:
     - tibco.clientVar.DefaultImplementation/Connections/HTTP/FacadeHTTPSSLConnection
       /IdentityFilePassword
     2. The following property in <ASG_CONFIG_HOME>/asg.properties file for
        facade HTTPS Channel is not applicable:
     - tibco.clientVar.DefaultImplementation/Connections/HTTP/FacadeHTTPSSLConnection
       /KeyPassword

Setup Information:
--------------------
   Ensure to perform following steps to complete the system setup.

   Windows platform:
   --------------------
   1. Download the "tcnative-1.dll" library from Apache Tomcat website.
         For example, you can download from the following url:
         http://tomcat.apache.org/download-native.cgi
   2. Copy the "tcnative-1.dll" to <TIBCO_HOME>\tibcojre64\1.7.0\lib directory.

   Linux platform:
   ------------------
   1. Install Apache Portable Runtime (APR) and OpenSSL (if not already installed
      on the system).
      1.1 For Dedian based Linux, execute the following command:
       - apt-get install build-essential libapr1-dev libssl-dev

      1.2 For Redhat Linux, perform the following steps:
          1.2.1 Download the source for APR from
             http://apr.apache.org/download.cgi (download the .tar.gz file)
          1.2.2 Execute the following command to extract the package:
             tar xvzf apr-1.5.0.tar.gz
          1.2.3 Execute following commands at the command prompt in sequence:
             cd apr-1.5.0
             ./configure
             make
             make install
             
          Note: Note down the path shown at the end of "make install" command. The
                directory at this path should contain"apr-1-config". The "apr-1-config"
                is required while building tomcat native library as mentioned in
                "Build Tomcat native library" section.

   2. Build Tomcat native library
      2.1 Download the "tomcat-native.tar.gz" archive to a temporary location such as,
       "/home/user/tomnative". The "tomcat-native.tar.gz" archive is located under
       $CATALINA_HOME/bin.
      2.2 Navigate to the temporary location directory "/home/user/tomnative".
      2.3 Extract the "tomcat-native.tar.gz" archive in the "/home/user/tomnative" location.
      2.4 Change to the "/home/user/tomnative/tomcat-native-1.1.27-src/ini/native" directory.
   2.5 Execute following commands at the command prompt in sequence:
       2.5.1 ./configure -with-apr=</usr/bin/apr-1-config>
             -with-java-home=</usr/tools/jdk_1.7.0_45>
             -with-ssl=yes -prefix=<path to destination directory>
 
             where <path to destination directory> is the directory where the libraries are
             created. Modify the full path to "apr-1-config" (as specified with -with-apr argument)
             and the full path to JDK (as specified with -with-java-home parameter) as per your
             system setup.
       2.5.2 make
       2.5.3 make install
       Note: Verify that the destination directory contains around 5 new files with extensions
             such as .so, .la,.a etc after the successful installation.

   3. Set up the LIBRARY PATH
      3.1 Navigate to the <ASG_HOME>/bin/directory
      3.2 Edit the asg-engine.tra file.
      3.3 Set the LD_LIBRARY_PATH to the destination directory where the libraries were created.
          The destination directory is indicated by the -prefix parameter as specified
          in 2.5.1 step. Set the library path as below:
       
          LD_LIBRARY_PATH=<path to destination directory>
          export LD_LIBRARY_PATH
      3.4 Save the asg-engine.tra file.

ASG-4755
TIBCO API Exchange Gateway User Interface throws error if the version number is set to
a value greater than 128 for a project configuration.

ASG-4753
TIBCO API Exchange Gateway User Interface had some usability issues such as follows:
   - Some screens scroll past right margin and do not provide scroll bars.
   - The right side of the user interface goes past right margin and does not
     provide any scroll bars to scroll.  

ASG-4751
TIBCO API Exchange Gateway does not provide the migration tool(asg-tools) for the
configuration migration from 2.0.0 release to 2.1.0 release.

ASG-4742
TIBCO API Exchange Gateway does not identify the partner as an authenticated user from
the request as the gateway saves the authenticated user incorrectly. This causes
gateway to identify partner incorrectly as "anon".

ASG-4739
The HTTP to JMS SOAP transport bridging of TIBCO API Exchange Gateway does not handle
the request/response message with content-type as multipart/related correctly.

ASG-4735
The <override-header> tag of the mapping transformation (XSLT) does not work. For
example, TIBCO API Exchange Gateway core engine does not replace the value of
Content-Type header as specified in the <override-header> element of the
transformation.

ASG-4725
TIBCO API Exchange Gateway core engine throws a java.lang.NullPointerException if the
transport is configured as blank.

ASG-4724
TIBCO API Exchange Gateway does not support XML file based authentication.

ASG-4723
TIBCO API Exchange Gateway does not check into the Group principle for role if it
cannot find any roles in SAML used with Authorization action.

ASG-4722
TIBCO API Exchange Gateway does not support roles in SAML to be used with XML file
based authentication.

ASG-4721
TIBCO API Exchange Gateway does not support caching for username/password for XML
file based authentication.

ASG-4720
TIBCO API Exchange Gateway does not support a utility that generates hashes for
passwords.

ASG-4719
TIBCO API Exchange Gateway does not support plain text passwords in the configuration
file used with XML file based Authentication.

ASG-4717
The error Mapper of TIBCO API Exchange Gateway does not return the data to the client
correctly when the Apache module is used and AsgBodyBinary is enabled.

ASG-4478
TIBCO API Exchange Gateway does not add HTTP headers to the façade response received
from a SOAP target service for a HTTP request from the client.

ASG-4622
LDAP Authentication login module of TIBCO API Exchange Gateway sends the wrong query
for subgroups when group Has Users.

ASG-4035
When TIBCO API exchange gateway is configured as a pass through proxy for REST
requests, the gateway does not handle the errors from the backend services.
TIBCO API exchange gateway allows you to disable the gateway error handling so
that the errors from the backend services are simply passed through. You should
add “Proxy” in the operation feature of an operation to simply pass the backend
service error to the client.

ASG-4006
TIBCO API exchange gateway does not support mutual SSL authentication for HTTPS
transport when the path specified for the truststore contains the resource
outside of a BusinessEvents project.

ASG-3021
The Central Logger fails to commit the transactions to the database when large
number of requests from multiple users are processed with the detail level
logging being enabled.

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

TIBCO® API Exchange Manager
==================================================================================
Closed Issues in 2.1.0_HF-001 (This Release)

ASG-4676
TIBCO API Exchange Manager portal engine does not support any special character
(such as $) in the URI path required to add an operation.

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

TIBCO® API Exchange (Gateway and Manager) 2.1.0 Hotfix 01 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-001_readme.txt, TIB_api-exchange-manager_2.1.0_HF-001_readme.txt