MySQL Enterprise Service Manager requires a repository to store its data. The installer optionally installs a local, clean repository for this purpose. However, you can choose not to install the bundled MySQL Server and use another repository instead. This repository can be installed on the same machine as MySQL Enterprise Service Manager, or on a remote machine.
It is strongly recommended that you use the bundled MySQL instance as MySQL Enterprise Monitor's repository. Only use an external repository if you have a compelling business reason for doing so.
The bundled MySQL instance has been comprehensively tested and tuned for use with MySQL Enterprise Service Manager
MySQL Enterprise Monitor upgrade installer can only upgrade a bundled MySQL, not an external one.
The various scripts delivered with MySQL Enterprise Service Manager only work with the bundled MySQL instance.
If you intend to use an alternative MySQL instance for your MySQL Enterprise Service Manager repository, the repository instance must be present before starting MySQL Enterprise Monitor installation.
It is strongly recommended you use a clean installation of MySQL Server as the Enterprise Service Manager repository and do not use this server for any other purpose.
You must make several configuration changes to enable it for use as the repository.
Ensure the following:
The MySQL Server version is 5.7.24, or higher, or 8.0.13, or higher.Note
It is not possible to use any MySQL 5.7 version preceding 5.7.24, or any MySQL 8.0 version preceding 8.0.13, as MySQL Enterprise Monitor repository. If you attempt to configure MySQL Enterprise Service Manager to use an earlier version, the installer displays an error and the installation cannot proceed.
The InnoDB storage engine is available. You must use InnoDB as the default storage engine.
SSL is enabled.
You must ensure the following in the MySQL Server configuration:
Query Cache must not be enabled.
innodb_file_format=Barracuda. This is not required if you are configuring MySQL 8 as the external repository.
On Linux/Unix hosts, ensure
innodb_flush_method=O_DIRECT, except on Solaris if ZFS is used. If using ZFS, comment out this parameter.
It is recommended to set
performance-schema-consumer-events-statements-history-long=ONmust be added to the repository's configuration file.
Define a Service Manager user to enable MySQL Enterprise Service Manager to connect to, and modify, the repository. This user must have the following privileges:
All privileges on
GRANT ALL PRIVILEGES ON `mem%`.* TO 'service_manager'@'127.0.0.1';
SELECTon all databases in the repository.
GRANT REPLICATION CLIENT, SUPER, PROCESS, SELECT ON *.* TO 'service_manager'@'127.0.0.1';
The Service Manager user's credentials are required by the MySQL Enterprise Service Manager installation process.
If you are using a MySQL Server repository other than the installation bundled with MySQL Enterprise Service Manager installation, the installer checks your MySQL Server for the following, minimum requirements:
MySQL Server version: versions older then MySQL 5.7.9 are not supported.
If you intend to use MySQL 8, it is not possible to use any version preceding MySQL 8.0.13. That is, it is not possible to use 8.0.0 to 8.0.4 as repository.
SSL: SSL must be enabled on the MySQL Server.
Solaris platforms: the Oracle Developer Studio 12.6 Runtime libraries must be installed.
For more information, see Installing MySQL on Solaris Using a Solaris PKG.
If any checks fail, the installer displays an error and cannot proceed until the configuration is corrected.
The upgrade process performs the same checks.
To check your repository for compatibility, before upgrading, use MySQL Enterprise Service Manager configuration utility. For more information, see Section 10.1, “Service Manager Configuration Utilities”.