Protocol 8 Discovery parameters

The discovery parameters define the behavior of the auto-discovery feature, for discovering database instances and sending the results to the current active S-TAP.

These parameters are stored in the [TAP] section of the S-TAP® properties file. For a full description of the feature, see Windows: Discover database instances.

Attention: These are advanced parameters and should be modified only by IBM Technical Support.
Attention: If a parameter is available through both the Guardium installation manager (GIM) and the command line interface (CLI), then the GIM parameter, including any defaults, always overwrites any value that is available from WINSTAP_CMD_LINE.
GIM guard_tap.ini Default value Description
WINSTAP_AUTO_DISCOVERY AUTO_DISCOVERY 0 Enables auto discovery of database instances, populates inspection engines, and updates guard_tap.ini at S-TAP start. Auto discovery runs once at the time of S-TAP installation and does not automatically repeat. The parameter value is 1 upon a fresh install and changes to 0 after the initial discovery. When set to 1, auto-discovery overwrites user modifications to the inspection engines configurations. Use with caution. Valid values:
  • 0: disabled
  • 1: enabled
Dynamic parameter. When you modify the value in the guard_tap.ini, the S-TAP does not need restarting for the updated values to take effect.
WINSTAP_DISCOVERY_INTERVAL DISCOVERY_INTERVAL 24 The time interval, in hours, at which the S-TAP reports its discovered DB instances to collector. Valid values:
  • 0: disabled
  • negative integer: interval in minutes in the range -5 through -1440 (5 - 1440 minutes)
  • positive integer: interval in hours. Maximum value is 24 (24 hours)
Dynamic parameter. When you modify the value in the guard_tap.ini, the S-TAP does not need restarting for the updated values to take effect.
WINSTAP_DISCOVERY_PORT DISCOVERY_PORT 8443 S-TAP uses this port to connect to the Guardium system. Valid values: 10244-65535.
Dynamic parameter. When you modify the value in the guard_tap.ini, the S-TAP does not need restarting for the updated value to take effect.