During a Guardium deployment planning meeting, a database administrator indicated that the mission critical databases were clustered. How should the Guardium administrator handle S-TAP installation…

Question

Options

• AInstall S-TAP agents on all active nodes. Set ALL_CAN_CONTROL=1 to failover the S-TAP
• BInstall S-TAP agents on all active nodes. Set WAIT_FOR_DB_EXEC=-1 to set the agent
• CInstall S-TAP agents on all active and passive nodes. Set ALL_CAN_CONTROL=0 to disable
• DInstall S-TAP agents on all active and passive nodes: Set WAIT_FOR_DB_EXEC>0 on all

• A
  79% (30)
• B
  13% (5)
• C
  5% (2)
• D
  3% (1)

Explanation

To properly support load balancing, the Guardium S-TAP agents must be configured properly. Add, uncomment, or modify the settings on your S-TAP Configuration to look like the following See the Guardium product documentation on how and where to adjust the S-TAP configuration file, as well as for updated guidance from IBM. * Sqlguard_ip = <Your BIG-IP Virtual Server IP address/hostname> For example: Sqlguard_ip = * Participate_load_balancing = 3 * All_can_control = 1 Sqlguard_ip is the address you will define on BIG-IP LTM during the Virtual Server configuration. Participate in Load balancing allows the S-TAP to send session information on every failover to All Can Control allows the S-TAP to be able to edit S-TAP configurations through GUI. Note: all_can_control . 0=S-TAP can be controlled only from the primary Guardium system. 1=S-TAP can be controlled from any Guardium system.

No community discussion yet for this question.