TIBCO® API Exchange (Gateway and Manager) 2.1.1 Hotfix 001 is now available.

TIBCO® API Exchange (Gateway and Manager) 2.1.1 Hotfix 001 is now available.

book

Article ID: KB0102782

calendar_today

Updated On:

Products Versions
TIBCO API Exchange -
Not Applicable -

Description

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

The TIBCO® API Exchange 2.1.1 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.1/TIB_api-exchange-manager_2.1.1_hotfix01
AvailableDownloads/_Additional_Products/APIExchange/2.1.1/TIB_api-exchange-gateway_2.1.1_hotfix01

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

TIBCO API Exchange Gateway(R)
=================================================================================
Introduction

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

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

ASG-6243
TIBCO API Exchange Gateway did not handle the responses correctly when content-type
is multipart/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 was searching 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 are
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.

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

TIBCO API Exchange Manager(R)
==================================================================================
Closed Issues in 2.1.1_HF-001 (This Release)

ASG-6230
The value of Partner Timeout in Facade Access tab was reset to 25 seconds when the
timeout value was updated using the Config UI from TIBCO API Exchange Manager.

ASG-5902
TIBCO API Exchange Manager threw the
"Data truncation: Data too long for column 'content' at  row 1" error for mysql
database when the portal functions were updated.

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

Issue/Introduction

TIBCO® API Exchange (Gateway and Manager) 2.1.1 Hotfix 001 is now available.

Environment

This hotfix applies to the following products and versions: - TIBCO API Exchange Gateway(R) 2.1.1 - TIBCO API Exchange Manager(R) 2.1.1

Additional Information

TIB_api-exchange-gateway_2.1.1_HF-001_readme.txt, TIB_api-exchange-manager_2.1.1_HF-001_readme.txt

Attachments

TIBCO® API Exchange (Gateway and Manager) 2.1.1 Hotfix 001 is now available. get_app
TIBCO® API Exchange (Gateway and Manager) 2.1.1 Hotfix 001 is now available. get_app