Add each Oracle Database Firewall as follows:
1. Display the Oracle Database Firewall Management Server Administration Console.
This must be the primary Oracle Database Firewall Management Server if a resilient pair of Oracle Database Firewall Management Servers is used.
Note: You can determine which Oracle Database Firewall
Management Server is the primary from the Status field in the High Availability section of the System Status page.
Also, the secondary Management Server has a red bar on its user interface, which identifies it as secondary.
Step 3: Complete the Final Database Firewall Management Server Tasks
2. Click the Appliances tab.
3. Click Add in the Appliances menu.
4. Enter a name for Oracle Database Firewall in the first field, and its IP address in the second.
5. Click Save.
If there is a message that indicates that there is a problem with the certificate, check that the date and time are set consistently across both the Oracle Database Firewall and the Management Server.
6. Click the link on the name of the appliance to go to the Administration Console for that managed Database Firewall, and specify the following settings for that appliance.
■ Click Date and Time in the System menu, then click the Change button:
Set the time (to the time that you want the traffic to be logged. Typically, you set it to the local time. Set the Time Offset if you are using NTP time
synchronization.
Enable NTP Time Synchronization: Select the check box to synchronize this Database Firewall’s time with the specified NTP servers.
Synchronize Time After Save: Select the check box to apply the NTP server time after you save and exit this page.
WARNING: In DPE (blocking) mode, Synchronize Time After Save causes all enforcement points to restart, thereby dropping existing connections to protected databases. This would cause a temporary traffic disruption.
Click Save when finished with Date and Time.
■ Click Services in the System menu, and then click the Change button:
For the DNS Server 1, DNS Server 2, and DNS Server 3 fields, enter the IP addresses of up to three DNS servers on the network. Oracle Database Firewall uses these addresses to resolve any network names that may be used at the Oracle Database Firewall Management Server. Keep the fields blank if there is no DNS server, otherwise system performance may be impaired.
Web Access: If you want to allow only selected computers to access the Oracle Database Firewall Management Server Administration Console, enter their IP addresses in the box. Using the default of all enables access from any
computer on your site.
Terminal Access: You can specify a list of IP addresses that are allowed to access the Oracle Database Firewall Management Server from a remote console. Entering all allows access from any computer on your site. The default of disabled prevents console access from any computer.
SNMP Access: Specifies a list of IP addresses that are allowed to access the Oracle Database Firewall Management Server's network configuration through SNMP (settings as per Terminal Access). The SNMP community string is gT8@fq+E.
Secure Log Access (Reporting): Specifies a list of IP addresses that are allowed to access the log data held on the Oracle Database Firewall
Step 3: Complete the Final Database Firewall Management Server Tasks
Management Server, for example, to report using external reporting systems (settings as per Terminal Access). If you complete this setting, then ensure that you complete "Step 3: Enable Secure Log Access in the Standalone Database Firewall" on page 2-5.
Traffic Log Access (Analyzer): Specifies a list of IP addresses of computers running the Analyzer software that are allowed to access the traffic log on the Oracle Database Firewall Management Server (settings as per Terminal Access).
Click Save.
■ Click Syslog in the Connectors menu:
Syslog Destinations (UDP): Use this box if you are using a User Datagram Protocol (UDP) to communicate syslog messages (for example, disk full) from the Oracle Database Firewall Management Server. Enter the IP address of each machine that is permitted to receive the syslog messages.
Syslog Destinations (TCP): Use this box if you are using Transmission Control Protocol (TCP) to communicate syslog messages from the Oracle Database Firewall Management Server. Enter the IP address and port number of each server that is permitted to receive the syslog messages.
Syslog Categories: Select from the following types of syslog messages to generate:
– System: System messages generated by Oracle Database Firewall or other software, which have a syslog priority level of at least "INFO".
– Alerts: Oracle Database Firewall and F5 alerts (Oracle Database Firewall syslog message IDs 7, 9, 10, 11 and 12).
This category is not present on the Management Server.
– Info: General Oracle Database Firewall messages and property changes (Oracle Database Firewall syslog message IDs 1, 4 and 8).
– Debug: Engineering debug messages (for Oracle Database Firewall use only).
– Heartbeat: Oracle Database Firewall heartbeat message and current statistics (Oracle Database Firewall syslog message ID 3).
This category is not present on the Management Server.
Maximum Syslog Message Length (bytes): Enter the maximum number of character bytes for each syslog message. The accepted range of values is 1024 to 1048576. The default is 1024.
Click Apply when finished with the Syslog settings.
■ Click Network in the System menu, and configure the network settings as
described in "Changing the Network Configuration" on page 13-11.
7. Repeat the procedure for each Oracle Database Firewall that the Oracle Database Firewall Management Server manages, including the second Oracle Database Firewall of a resilient pair.