You are viewing an older version of this section. Click here to navigate to the latest version.

Persisting MMC Data On External Databases

Enterprise Edition

MMC Version 3.4.2 and Later

By default, the Mule Management Console stores its persistent data on an embedded database on the local host. In this scenario, a catastrophic failure of the host would cause the loss of all data. You can avoid this situation by configuring MMC to store data on an external database, which ideally would reside on a dedicated server.

MC version 3.4.2 introduced a new, simplified configuration for persisting data on external databases. This new configuration is valid for MMC versions 3.4.2 and later, and is detailed in this page. If you are looking for information about MMC 3.4.1, see [Persisting MMC Data On External Databases] on the Mule 3.4.x documentation. For earlier versions, see [Persisting Transaction Data] and [Persisting Environment Data] in the 3.3.x documentation.
This page and most of the pages linked here are intended for configuring data persistence on fresh MMC installations, i.e. installations that have not already been configured to persist data to an external database. If your MMC installation is already set up to persist data to an external database, and you are looking to upgrade to MMC 3.5.0, you will need to perform special steps, including some migration of old config data. To determine the exact procedure you need to follow in order to upgrade, see [Upgrading the Management Console].

There are two kinds of data that MMC can store on external databases:

  • Environment data, such as created alerts, deployments, dashboard portlets configuration

  • Transaction data (Business Events)

You can configure MMC to store its data on the following database servers:

  • [PostgreSQL]

  • [Oracle]

  • [MySQL]

  • [MS SQL Server]

Click the links above for details on setting up MMC to work with each of the listed database servers.