Windows: Discover database instances

The instance discovery agent runs once per day, by default. It reports new database instances, listener, and port information to the Guardium® system. It does not update the inspection engine configurations.

Instance discovery uploads its findings to the Discovered Instances report of the associated Guardium system.. You can add datasources and inspection engines to Guardium by using the Actions menu in the report.
You can modify the discovery frequency in the UI, by modifying the parameter Discovery interval in the S-TAP Control: Details page, or the DISCOVERY_INTERVALparameter in the guard_tap.ini . For more information, see Protocol 7 Discovery parameters or Protocol 8 Discovery parameters.

You can run the database instance discovery manually in the S-TAP Control page by clicking Send, and selecting Run Database Instance Discovery. If you start a manual discovery while a scheduled discovery is running, the new request is ignored. To avoid an instance where S-TAP discovery does not open the Informix database, it is recommended to start Informix databases by using the full path to the executable.

Important: Do not check Replace Inspection Engines unless you want to overwrite the existing inspection engine configurations.

You can define rules to manage inspection engine creation on discovered database instances. For more information, see Database discovered instances rules. This configuration is used when you run the Send command in the S-TAP Control page. Do not check Replace Inspection Engines when using the rules.

Instance discovery is configured and run independently of auto discovery. For more information, see Windows: Auto discovery of database instances during installation and upgrade.