Description:
You can download this HotFix from the TIBCO Product Support FTP server using your eSupport username and password, at

ftp://support-ftp.tibco.com

Once you have successfully logged into the server, you will find the hotfix packages under

available_downloads/ActiveMatrix/ActiveMatrixServiceGateway/1.2.0/TIB_asg_1.2.0_hotfix005/

Listed below is a summary of updates included. Please refer to the hot fix readme document for any additional information.
================================================================================
Closed Issues in 1.2.0_HF-005 (This Release)

ASG-1598
ActiveMatrix Service Gateway core engine failed to override the target service
to route the request, in case the target is specified in the
"override-targetServiceId" tag of full mapper of the facade operation.

ASG-1945
ActiveMatrix Service Gateway core engine  was treating all 2xx response codes
other than 200 as FAILED. The gateway core engine returns SUCCESS for all 2xx
response codes.

ASG-1970
ActiveMatrix Service Gateway did not xml-encode the query string which is added
to the context xml document.

ASG-1971
ActiveMatrix Service Gateway did not append the query-string and sub-uri to
the southbound service URI configuration.You must include {query_string} and
{uri_suffix} parameters in headerstoForward field for the target services
configuration using the ActiveMatrix Service Gateway user interface.

ASG-1982
ActiveMatrix Service Gateway did not return any response data to the client for
the binary response when the response was sent from  Apache server. The
Content-Length header field was not set correctly in the HTTP headers.

ASG-1995
ActiveMatrix Service Gateway did not match the most specific URI path of the
operation configuration with the URI of an incoming request to identify an
operation.

ASG-2032
ActiveMatrix Service Gateway core engine was throwing a NullPointer Exception
when a HTTP enabled southbound service returns HTTP 503 error.

ASG-2033
ActiveMatrix Service Gateway core engine did not return the response headers
in the northbound response message to the client. The response headers are added
by the southbound service.

ASG-2489
ActiveMatrix Service Gateway did not allow empty HTTP Headers in the request.

ASG-3185
ActiveMatrix Service Gateway core engine did not pass the transformation name when
RV type of mapping is selected for the mapper.

================================================================================
Closed Issues in 1.2.0_HF-004

ASG-1114
ActiveMatrix Service Gateway User Interface was throwing an error when the
Routing Key is defined only for Service Group instead of Service Name.
The user interface did not allow blank Service Name for a Routing Key in case
when the Routing Key is defined for Service Group.

ASG-1115
Service Group routing was not working when the Routing Key is defined and
saved using the ActiveMatrix Service Gateway User Interface.

ASG-1154
The Apache module of the ActiveMatrix Service Gateway did not support RVSD/RVSRD
connections for secure deployments.

ASG-1179
ActiveMatrix Service Gateway was throwing a java.lang.NullPointerException
exception when a message is received on the ESB northbound Channel.

ASG-1195
refreshConfig on the ActiveMatrix Service Gateway User Interface was not
working correctly in all cases.

ASG-1208
The Internet Browser did not receive any response to the ping operation requests
when Internet Explorer is used.

ASG-1209
ActiveMatrix Service Gateway did not support the customization of the default
error messages returned from the Apache module. This issue is now resolved for
firefox browser only.

ASG-1210
ActiveMatrix Service Gateway did not get a response from a HTTPS service When
"isAnonymous=true" is set in services.cfg.

ASG-1219
ActiveMatrix Service Gateway User Interface did not provide an option to logout
and Invalidate Session (Session Timeout) to meet the security requirements.

ASG-1224
ActiveMatrix Service Gateway User Interface was slow in responding to browsing
the tabs when there are large number of entries (e.g 600+) configured.

ASG-1233
ActiveMatrix Service Gateway User Interface was not using LDAP to authenticate
and authorize a user.

ASG-1307
There was a performance impact to the ActiveMatrix Service Gateway engine when
schema validation is enabled.

================================================================================
Closed Issues in 1.2.0_HF-003

ASG-1170
ActiveMatrix Service Gateway core engine could not handle non-ASCII characters
in the payloads of the incoming request which was sent to the HTTP transport
based backend service.

ASG-1180
ActiveMatrix Service Gateway did not generate a valid context document when a
SOAP message is received over JMS transport.

================================================================================
Closed Issues in 1.2.0_HF-002

ASG-824
ActiveMatrix Service Gateway did not support the complete pattern for correlation
of reply and request message on the northbound side.

ASG-835
TIBCO ActiveMatrix Service Gateway UI did not support both absolute and relative
paths when the file locations field were configured on the UI.

ASG-836
TIBCO ActiveMatrix Service Gateway UI was saving the value of "Is Anonymous"
field on the Services tab incorrectly in services.cfg file.

ASG-863
TIBCO ActiveMatrix Service Gateway Studio and TIBCO ActiveMatrix Service Gateway
Engine did not show the latest build version.

ASG-903
When a relative path was specified for the location of files used by WSS
funtionality, TIBCO ActiveMatrix Service Gateway was using a different
root path than ASG_CONFIG_HOME.

ASG-943
When SOAP/JMS transport was used for request operations, the gateway engine did
not send the response message on the reply queue.

ASG-994
ActiveMatrix Service Gateway Studio gave errors in windows environment when a
new EAR file was generated for the ASG_DefaultImplementation project after
adding custom extensions.

ASG-996
Out of the box, asg_cl.cdd was not enabled for Central Logger component in a
cluster mode.

ASG-1070
The core engine was throwing a NullPointerException when the mappings are
used to create headers for the response message.

================================================================================
Closed Issues in 1.2.0_HF-001

ASG-701
TIBCO ActiveMatrix Service Gateway UI saved the destination name incorrectly
for services of SOAP JMS transport type.

ASG-702
Parse XSLT based on PartnerId did not overwrite the partner for a transaction.

ASG-719
Multiple parameters in Query String were incorrectly stored in context XML.

ASG-603
The client connection information was not available in the request context to
the ActiveMatrix Service Gateway engine.

ASG-710
ActiveMatrix Service Gateway Engine allows to change the error processing behavior
of an individual service call using route override with full override.

ASG-310
ASG can act as a client to SOAPJMS servers which ignore the received
JMSCorrelationID and instead return the request's JMSMessageID as the
JMSCorrelationID in the response message.

ASG-783    
WS-Security based authentication for LDAP with User Has Groups configuration is
supported by ActiveMatrix Service Gateway Engine.

ASG-833
ActiveMatrix Service Gateway Engine supports HTTPs transport for the southbound
services.

ASG-786
Encrypted password in the services.cfg file for http transport type are supported by
ActiveMatrix Service Gateway Engine.

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