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-003 (This Release)
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.