Runtime Manager 1.3.x Release Notes

1.3.1

Anypoint Runtime Manager version 1.3.1 is a minor release that includes performance enhancements, bug fixes, and native support for Splunk’s http event collector in our handler.

Hardware and Software Requirements

No change.

Compatibility

Agent plugins integrations is compatible with the following runtime versions:

Mule

3.6.x and above

Availability

Cloud only

API GateWay

2.x and above for API Analytics

Runtime Manager Agent

1.1.0 and above. However it is recommended that you use the latest version of Agent. Click here for the latest version of Agent.

The Runtime Manager version that is bundled as part of the Anypoint Platform Private Cloud Edition is Version 1.2.

Features and Functionality

  • Splunk handler enhancement: Added support for Splunk’s TCP and HTTP Event Collector, so Splunk users can easily and securely send events from MuleSoft’s platform into Splunk.

  • JMX handler enhancements.

Deprecated Features or Functionality

None.

Resolved Issues

Includes usability, performance enhancements, and bug fixes.

  • CHHYBRID-591: Applications in “Failed” state can now be started

  • CHHYBRID-963: User can no longer create Server Groups or Clusters if servers have different agent versions

  • CHHYBRID-1107: Behavioral improvements while redeploying of domains in the Runtime Manager Agent

  • CHHYBRID-1135: Server deletion enhancements.

  • CHHYBRID-1176: Users with no permission to see the “Servers” page will now be re-directed.

  • CHHYBRID-1180: Ability to upload large applications without affecting performance.

  • CHHYBRID-1198: Memory optimization while deploying an app

  • CHHYBRID-1209: Fixed ability to configure Plugins when Event Tracking Level is None.

  • CHHYBRID-1218: Fixed error when a user wants to perform an action in the deployment

  • CHHYBRID-1223: Fixed enabling the agent plugin for Runtime Manager Agent versions that are greater than 1.2.0

  • CHHYBRID-1226: Clusters created in 1.2.0 cannot be deleted in 1.3.0

  • CHHYBRID-1233: Correct positioning of Failed message when an application fails

Migration Guidance

No migration required.

1.3.0

The Anypoint Runtime Manager, V1.3, release features usability enhancements on clustering support, backend improvements to enhance performance and functionality for the upcoming releases, and bug fixes. Including, but not limited to the mule connection manager.

This release is only available for the cloud version of the Runtime Manager, accesible online through the Anypoint Platform. It’s not yet available for the On Premises version of the Runtime Manager.

Hardware and Software Requirements

No change.

Compatibility

Agent plugins integrations is compatible with the following runtime versions:

Mule

3.6.x and above

Availability

Cloud only

API GateWay

2.x and above for API Analytics

Runtime Manager Agent

1.1.0 and above. However it is recommended that you use the latest version of Agent. Click here for the latest version of Agent.

The Runtime Manager version that is bundled as part of the Anypoint Platform Private Cloud Edition is Version 1.2.0.

Features and Functionality

Usability Enhancements for Clustering: this release includes improvements in clustering support in ARM

  • Visibility among nodes: Users now have the ability to view any communication issues between nodes in a cluster.

  • Master node: Identifies the master node in a cluster.

  • The IP of the nodes are now visible.

  • Cluster deployment changes: When a node is removed from a cluster the applications will be undeployed, avoiding unexpected behaviors.

RDBMS support (Beta)

Agent modules for Mule Runtime event tracking and API Gateway analytics, available on request. Support for MySQL, MSSQL and Oracle.

Deprecated Features or Functionality

None.

Resolved Issues

  • SE-2861: Cannot delete disconnected servers with applications

  • CHHYBRID-962: User should not be able to create cluster and server groups if servers have different agent versions

  • CHHYBRID-1104: Cluster nodes are restarted multiple times during creation

  • CHHYBRID-1106: Configuration not synchronizing on server startup for groups and clusters

  • CHHYBRID-1113: Duplicated server name in Application panel

Migration Guidance

No migration required from older versions

Support

No change.

Was this article helpful?

💙 Thanks for your feedback!