All installations of the Service Manager install the Tomcat and MySQL applications using the same basic set of parameters. Although the defaults provided by the installation process are designed not to interfere with existing installations of either product, check these parameters before installation to ensure that you do not experience any problems.
A value must be assigned to all settings that are defined in the
configuration file. This is different than passing these settings
into the command-line, which may default to
true when not passing in a value. Glib is used
for option handling, and specifically
g_key_file_get_boolean() to parse boolean
values. This means that
0 represent boolean
true. For example:
Passing a value to
config.properties may look
Or to the command-line, like either of these:
$ ./mysqlmonitor-installer.bin --log-use-syslog $ ./mysqlmonitor-installer.bin --log-use-syslog 1
The common parameters are divided into those applying to the location of the MySQL server, the Tomcat server, and the connection properties for the MySQL server (Repository Configuration):
Tomcat Server Port: This setting exists for MySQL Enterprise Monitor 2.3 compatability, as MySQL Enterprise Monitor 3.0+ requires SSL. This port will be redirected to the Tomcat SSL Port for connectors and web browsers, but 2.3 agents and aggregators cannot follow the redirect and, if applicatable, will use the non-SSL variant. The default value is 18080.
In other words, if you use MySQL Enterprise Monitor 2.3, then set this to the Tomcat Server Port that you used with it.
Tomcat SSL Port: The standard port used to connect to the Service Manager, which always uses Secure Sockets Layer (SSL) encrypted communication. The default value is 18443.
If you do not have a web server running on port 443, you
can use this well-known port rather than
18443. Since port
443 is the default SSL port for a web
server, you can then open the MySQL Enterprise Monitor User Interface without
specifying a port (but still remember to specify
MySQL Server selection
Using the bundled MySQL Server is preferred, but you may also choose to use your own MySQL Server to store repository data for the MySQL Enterprise Service Manager. The MySQL Server can be located on the same machine as the MySQL Enterprise Service Manager, or on a different machine. If you use your own MySQL Server, it must already be running when you start the installer.
Configuring the MySQL Enterprise Service Manager repository to use a database that you plan to monitor will be problematic, because the MySQL Enterprise Service Manager statistics will interfere with your setup. Using the same host will function normally, although some monitored statistics are host specific.
The requirements for the MySQL Server are:
MySQL 5.1.43 or higher.
It is not shared with a MySQL Enterprise Service Manager 2.x repository.
InnoDB Storage Engine enabled. MySQL Enterprise Monitor operation relies on the InnoDB-related configuration options being set high enough to handle the monitoring traffic. For example, the bundled MySQL server includes the settings:
innodb_buffer_pool_size = 512M innodb_log_file_size = 256M innodb_flush_log_at_trx_commit = 2 innodb_support_xa = 0 innodb_file_per_table innodb_max_dirty_pages_pct = 20 innodb_locks_unsafe_for_binlog = 1
Using too-low settings for the repository data could
result in errors such as
closed! in the Tomcat log file.
We can also make use of of compression within InnoDB, but this requires MySQL server 5.1 with the Plugin, or MySQL server 5.5+ with the following added to the configuration:
innodb_file_format = Barracuda
As of MySQL Server 5.5.7, the default value of
innodb_file_format is "Antelope",
while setting it to "Barraduca" is required for
utilizing table compression.
Configure the MySQL server with suitable credentials to
allow MySQL Enterprise Service Manager to create the database, tables and
other settings. The user should have
ALL privileges on the MySQL Enterprise Monitor
repository, which is stored within the database
mem, or you can provide full access to
all tables. Also, ensure you have the
OPTION. For example, you might create a suitable
user using the following
mysql> GRANT ALL PRIVILEGES ON *.* TO 'service_manager'@'localhost' -> IDENTIFIED BY '
password' WITH GRANT OPTION
Repository Configuration (MySQL Server)
Repository Username — if you are connecting to an
existing MySQL database, specify the username and password
that you configured with access to the MySQL Enterprise Monitor
repository. If you install the bundled MySQL database,
choose a username and password for the MySQL Enterprise Service Manager,
and that user is created automatically during
installation. In normal use, you do not need to access the
repository database directly, but it might be required to
resolve a service
request. The default value is
Repository User password — the password to use to connect to the MySQL database. Set it to a secure password so that the repository data is secure.
The Repository password is encrypted, you may use the
to change it.
Use SSL when connecting to the database — adds a
mysql.use_ssl=true to the
config.properties file. The
repository database must be configured for SSL
connections, as described in
Configuring MySQL for SSL. You can add this
line yourself to enable SSL connections after
installation. You can also manually add any of the
following items to
to customize the SSL connections to the repository
mysql.verify_server_cert (default is false) mysql.trust_cert_keystore_url (no default) mysql.trust_cert_keystore_type (no default) mysql.trust_cert_keystore_password (no default) mysql.client_cert_keystore_url (no default) mysql.client_cert_keystore_type (no default) mysql.client_cert_keystore_password (no default)
These items correspond to similarly-named JDBC connection properties that are described in Driver/Datasource Class Names, URL Syntax and Configuration Properties for Connector/J.
The information that you configure during installation is recorded
within the installation directory for the Service Manager, with
any passwords obscured. (Thus, be sure to record all passwords
that you specify during the installation process.)