Linux-UNIX: Editing the S-TAP configuration parameters
You can modify the S-TAP® configuration after it is installed using GIM, the UI, or for advanced users, the configuration file on the database.
You can some modify parameters in the GUI. See Linux-UNIX: Configuring S-TAP in the S-TAP Control page.
GIM is an easy method for modifying parameters, if the S-TAP bundle was installed with GIM. See Set up by Client.
Configuration Change Alerting: When the S-TAP sends an
updated configuration to the collector, the collector checks the new configuration against the last
stored configuration on the collector and an alert is generated detailing what has changed. This
alert appears in the S-TAP event log. If a
section is added or removed, the parameters of that section are listed. If a section parameter is
changed, it displays the section name, parameter name, old value, and new value. If a parameter is
added or removed from a section, the section name, parameter name, and value are displayed. For
example:UTAP 'rh7-docker1' configuration changed, differences: Section 'TAP' parameter
'discovery_debug' changed from '0' to '1' Section 'TAP' parameter 'stap_statistic' changed from '1'
to '0' Section 'SQLGuard_1' added Section 'SQLGuard_1' parameter 'connection_pool_size'='0' added
Section 'SQLGuard_1' parameter 'num_main_thread'='1' added Section 'SQLGuard_1' parameter
'primary'='2' added Section 'SQLGuard_1' parameter 'sqlguard_ip'='gibm39' added Section 'SQLGuard_1'
parameter 'sqlguard_port'='16016' added
If it is necessary to modify the configuration file from the database server, follow the procedure described in this section. The guard_tap.ini file contains comments that explain many of the parameters.
The S-TAP needs restarting after you modify the guard_tap.ini file. Either restart it in the S-TAP Control page with the Send command or using one of: Linux-UNIX: Start and stop S-TAP and GIM processes for various OS types/versions, Linux-UNIX: Using guard-config-update to start, restart, and stop S-TAP, and view status.
The guard_tap.ini file has a [Proxy] section that is only used for the Guardium External S-TAP containers. Do not modify any parameters in this section.
- Log on to the database server system using the root account.
- Stop the S-TAP.
- Make a backup copy of the configuration file: guard_tap.ini. The default file locations is /usr/local/guardium/guard_stap/guard_tap.ini
- Open the configuration file in a text editor.
- Edit the file as necessary.
- Save the file.
- Restart the S-TAP and verify that your change has been incorporated.