MySQL by Shell Job

This section explains how DFM discovers the MySQL server:

1. The MySQL by Shell job connects to the remote host using Shell credentials.

2. The job checks for the existence of the path of the MySQL configuration file by executing the following command:

   mysqld --verbose --help
   

3. If the job cannot find the configuration file with this command, it assumes the file is located in the default configuration file path:

   • UNIX or Linux: /etc/my.cnf

   • Windows: ../my.ini

4. The job tries to retrieve the attribute values from the configuration file. The job either reads the attribute values from the command line, or reads the configuration file to find the values of the attributes that were not found in the command line.

   Example of command line with attribute values:

   mysqld-nt.exe --defaults-file=C:\hp\UCMDB\DataFlowProbe\MySQL\my.ini DDM_Probe_DB
   

5. If the job does not find any attribute values, it takes the default values from the MySQL documentation.

   For details of the MySQL attributes, see MySQL by Shell Job.

6. The job creates the MySQL CIs with appropriate attribute values and relationships.

7. The job now checks if this MySQL instance is a replica. If it is a replica, the job attempts to discover a master host and master user. The version of the MySQL engine is taken from the mysqld --version command output.

8. The job creates the MySQL replication CI with appropriate attribute values and relationships.

• MySQL

  • server_id. The server ID is used in the replication job and must be unique for each server.

  • database_datadir. Path to the database root (datadir in the configuration file).

  • database_max_connections. The maximum number of concurrent sessions allowed by the MySQL server (max_connections in the my.ini file).

  • database_dbsid. The unique identifier for running the MySQL instance-process port. The format is MySQL on port ####.

• MySQL Replication

  • master_user. A user name used when connecting to the master server.

  • master_connect_retry. The number of seconds that the slave thread sleeps before trying to reconnect to the master, if the master goes down or the connection is lost.

• Input Query

• Triggered CI Data

  Name	Value
  Protocol	${SHELL.root_class}
  credentialsId	${SHELL.credentials_id}
  dbport	${SOURCE.database_dbport}
  dbsid	${SOURCE.database_dbsid}
  ip_address	${SHELL.application_ip}
  processParams	${PROCESS.process_parameters}
  processPath	${PROCESS.process_path}

To view discovered CITs, select a specific adapter in the Resources pane.

• ClientServer

• Composition

• ConfigurationDocument

• Containment

• IpAddress

• IpServiceEndpoint

• MySQL

• MySQL Replication

• Node