7.1 General considerations when upgrading MySQL Enterprise Monitor

This section describes how to perform an update for the MySQL Enterprise Service Manager or the MySQL Enterprise Monitor Agent.

You cannot use the update installers to change to a different operating system or chip architecture. For example, you cannot update a 32-bit Linux installation to a 64-bit version using an update installer. You must perform a fresh installation instead.

You cannot update 2.2 to 3.0. Users of 2.2 must upgrade to 2.3 before proceeding with the upgrade process.

You also cannot use the upgrader if you installed the MySQL server for the MySQL Enterprise Service Manager instance outside the MySQL Enterprise Service Manager installation directory.

Customizations to setenv.sh are lost, as this file is replaced and optimized for MySQL Enterprise Monitor 3.0 during an upgrade.

The installation and configuration of MySQL Enterprise Monitor Agent must be standard before you start the installation. The update installer cannot upgrade agents where you have changed or modified the filenames or directory layout of the installed agent, configuration files, or the startup files.


The upgrade installer overwrites items-mysql-monitor.xml. On Windows, this file is in the C:\Program Files\MySQL\Enterprise\Agent\share\mysql-monitor-agent directory and on Unix, in the /opt/mysql/enterprise/agent/share/mysql-monitor-agent directory. Back this file up if you have made any changes to it.


The Upgrade installer for MySQL Enterprise Service Manager overwrites any changes made to the my.cnf in your MySQL Enterprise Service Manager installation. Backup the existing my.cnf file before starting the upgrade installer.

SSL Considerations

The Upgrade installer for MySQL Enterprise Service Manager overwrites any changes made to the CA certificate files within your MySQL Enterprise Service Manager installation. This includes cacerts for the bundled JRE, and myKeystore for the bundled Tomcat web server. These files are replaced with the bundled CA certificate files, so if custom changes exist, such as an LDAP server with a self-signed certificate, you must manually re-import the custom changes. These files are backed up during the upgrade, and the locations are logged within the configuration_report.txt log file.

The following example imports one root CA from the backed up file, and uses the default password for keystores in Java which is "changeit". The alias names and path locations may also be different.

$ pwd

$ ./keytool -importkeystore \
  -srckeystore /opt/mysql/enterprise/monitor/backup/java/lib/security/cacerts \
  -destkeystore /opt/mysql/enterprise/monitor/java/lib/security/cacerts \
  -srcstorepass changeit \
  -deststorepass changeit \
  -srcalias myorigrootca \
  -destalias myrootca

The following are the options:

  • -srckeystore: the location of the source keystore (the backed up keystore), which contains the certificate you want to import.

  • -destkeystore: the location of the destination keystore. The certificate is imported to this location.

  • -srcstorepass: password of the source keystore. The default password is changeit. If you changed the password, enter it here.

  • -deststorepass: password of the destination keystore. The default password is changeit. If you changed the password, enter it here.

  • -srcalias: the alias of the certificate in the source keystore. If you have multiple certficates in the keystore, run the following command for a list of all certificates and their aliases in the source keystore:

    keytool -list -v -keystore /Applications/mysql/enterprise/monitor/backup/java/lib/security/cacerts

    If source alias is not provided, all entries in the source keystore are imported and stored in the destination keystore with their original aliases.

  • -destalias: the alias to use in the new keystore.


The command is the same if you are using mykeystore, except for the paths, which must be changed to reflect the different location.

Running the Update Installer

The name of the update file varies, but it shows the target operating system, the version the update applies to, and the component name. (There are separate update installers for the Service Manager and the Agent.) For example, a file named mysqlenterprisemanager-3.0.0-windows-update-installer.exe updates MySQL Enterprise Service Manager on Windows to version 3.0.0.

You install an update in the same way that you initially installed the Service Manager or the Agent; in win32 or unattended mode on Windows; in gtk, text, xwindow, or unattended mode on Unix; and in osx, text , or unattended mode on OS X.

Run the installation file and choose the directory of your current installation and whether or not you wish to back up your current installation. The time required to complete the process varies depending upon the nature of the update.

You can run an unattended upgrade, the same way you run an unattended install. To see all the options you can specify during the upgrade process, run the update installer with the --help option.