Runtime Manager Agent 2.2.0 Release Notes
January 28, 2018
This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 2.2.0.
This release contains the following new features or enhancements:
Added Java 11 OpenJDK Support
This version of Runtime Manager Agent enables connection to the new Runtime Manager Publicly Certified endpoints for Mule Manager and Auth Proxy.
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).
This release contains the following fixed issue:
The issue that caused an NPE when processing
ExceptionNotificationfrom the implicit error handler is fixed.
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.|
mule-agent.ymlfile, configure the following URLs in the appropriate section.
United States EU
wsprotocol, change the
ws://runtime-manager.anypoint.mulesoft.comlike in the following example:
websocket.transport: enabled: true consoleUri: ws://runtime-manager.anypoint.mulesoft.com
For the HTTPS protocol, change
https://data-authenticator.anypoint.mulesoft.comlike in the following example:
authenticationProxy: endpoint: https://data-authenticator.anypoint.mulesoft.com
Restart the Mule runtime engine.