Runtime Manager Agent 1.12.x Release Notes
1.12.2
May 3, 2019
This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 1.12.2.
1.12.1
February 19, 2019
This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 1.12.1.
Changes in This Release
-
The API now returns the root cause when an application fails to deploy.
-
Application properties are now stored in the application’s
ymldescriptor instead of in themule-agent.yml. -
For APCE environments, trusted certificates are always used from the JKS file instead of the JVM.
1.12.0
January 28, 2018
This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 1.12.0.
Changes in This Release
-
This version of Runtime Manager Agent uses a new Publicly Certified certificate and connects to two new endpoints in Anypoint Runtime Manager.
-
Now, when enabling a service that has a null log configuration, the Mule Agent API returns a bad request (400) instead of an internal server error (500).
Upgrade Requirements
When you upgrade the agent two new endpoints for communicating with Anypoint Runtime Manager are created.
Before performing the upgrade, ensure there are no networking constraints for accessing the FQDNs on port 443. For more information, see Ports, IP Addresses, and Hostnames to Allowlist.
| United States | EU |
|---|---|
|
|