Contact Free trial Login

Anypoint Platform Private Cloud Edition 2.1.1 Release Notes

August 31, 2020

New Features and Enhancements

This version of Anypoint Platform Private Cloud Edition (Anypoint Platform for PCE) contains the following features and enhancements:

  • Anypoint Platform for PCE features and enhancements

    • Reliability enhancements provided for install, upgrade, and backup operations.

  • Anypoint Access Management features

    • Certificate validation is displayed in the UI for an incorrect certificate chain or mismatching DNS.

    • More detailed feedback is provided during new certificate configuration.

    • Rate limiting on the internal endpoint is now disabled to avoid random failures.

Installing

Contact MuleSoft professional services prior to installing. MuleSoft professional services must be involved with your installation procedure.

Upgrade to Anypoint Platform PCE Version 2.1

Contact MuleSoft professional services prior to upgrading. MuleSoft professional services must be involved with your upgrade procedure.

Software Compatibility

Compatible with Version

Mule runtime engine

3.7.x , 3.8.x, 3.9.x, 4.0.x, 4.1.x, 4.2.x, 4.3.0

API Gateway Runtime

2.1.x - 2.2.x

Anypoint Runtime Manager Agent

1.7 - 1.9.x, 2.1.x

Anypoint Studio

6, 7.4

Infrastructure providers

  • VMWare

  • Bare metal

  • AWS

Upgrade Paths

Upgrades from the following PCE versions are supported:

  • PCE 2.0.x

  • PCE 2.1.x

Fixed Issues

Description

In Runtime Manager, deployment properties are now synched to a node in a cluster if properties are introduced when the corresponding node is down.

In Runtime Manager, component memory limits are configured to avoid out of memory errors.

In Access Management, you can now upgrade with a client management configuration.

In Access Management, the correct UI version is now displayed when a DNS contains "anypoint".

In Access Management, the SMTP credentials can now be configured to "".

In Access Management, the cron job that removes unnecessary roles is now working as expected.

In API Console, when you use a security schema with client credentials, the Client ID and Client Secret fields are now displayed.

After an upgrade is complete, the DNS setting does not need to be reconfigured.

During the backup process, all files are now backed up correctly.

Known Issues

Description Workaround

Some parts of the UI request fonts from external domains.

No workaround. These requests can be ignored.

Some containers run as root (AOP-2077).

No workaround.

Log forwarding settings are not preserved during 2.1.0 upgrade.

Reconfigure the log forwarding settings after the upgrade.

Was this article helpful?

💙 Thanks for your feedback!