Contact Free trial Login

Runtime Manager Agent 1.12.0 Release Notes

January 28, 2018

This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 1.12.0.

New Features and Enhancements

This release contains no new features or enhancements.

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).

Fixed Issues

This release contains no fixed issues.

Known Limitations and Workarounds

There are no known limitations or workarounds in this release.

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.
  1. In the mule-agent.yml file, configure the following URLs in the appropriate section.

    United States EU



    For the ws protocol, change the websocket.transport URI to ws:// like in the following example:

        enabled: true
        consoleUri: ws://

    For the HTTPS protocol, change to like in the following example:

  2. Restart the Mule runtime engine.

Compatibility Notes

Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above


JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]


MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager