Pattern Goal

The goal of the MySQL RDBMS Database Detail pattern is to obtain the list of Databases being managed by the MySQL Server, and to obtain (optionally, and disabled by default) the list of Tables within these databases.

The information is then stored within the Atrium Discovery Model as DatabaseDetail Nodes. In Atrium Discovery 8.3 and later, the DatabaseDetail node has additional attributes added which permit easy mapping by the CMDB sync mechanism to the BMC_Database CIs in Atrium CMDB.
The pattern connects to the MySQL Server using a JDBC connection.

Configuration Required

The Database Detail Patterns require some additional configuration before they can be used.

Setting of Database Integration Point

• Set the Connection Parameters, including Username and Password.

Setting the port:

Atrium Discovery 8.0 and 8.1

The core TKU MySQL RDBMS Pattern will attempt to obtain the listening port for the database server dynamically. In case where it fails the Database Detail pattern will use the default port which is set in its configuration parameters. If the default port is likely to be different in your environment, the pattern configuration should be altered. Changing Pattern Configuration is detailed in Atrium Discovery Documentation .

Atrium Discovery 8.2 and later

The option to set the default port no longer exists in the MySQL Database Detail pattern.
The MySQL Database Detail pattern behavior is now as follows:

• If the core TKU MySQL RDBMS Pattern discovers the listening port, this is the port that will be used
• Alternatively, the MySQL Database Detail pattern will use the port that has been set in the database credentials by the user.
• If no port was retrieved and port DB listening port was not set by the user, the MySQL Database Detail pattern will not attempt to perform database queries.
  The reason for this change is to minimize the number of configuration steps required and prevent errors due to forgotten changes in pattern configuration.

Editing pattern configuration further

• Decide whether the pattern should attempt to retrieve tables or not, and whether any specific databases should be ignored

Database User Configuration

In order for Atrium Discovery to retrieve the Database details, it will need to be able to access the Database as a legitimate user, with privileges sufficient to execute the SQL Queries below.

SQL Queries Executed

The pattern executes the following SQL Queries.

• Obtaining a list of Databases being managed: SHOW DATABASES

• Obtaining a list of tables within a database: SELECT table_name FROM information_schema.tables WHERE table_schema = %db_name%