Connecting to target databases : Adding (or modifying) a target connection
 
Adding (or modifying) a target connection
1. Go to Target Database Server > Targets.
2. Do one of the following:
To create a target, click Add.
To modify a target, click the name of a target database.
3. On the General tab, complete the following settings:
Name
Do not use spaces in the name.
Type
If you select Oracle, complete the settings on the SSH tab.
If you select DB2, on the DB2 Options tab, do one of the following:
Select SSH, and then complete the settings on the SSH tab.
For more information on SSH tab settings, see “Configuring SSH connections to Oracle and DB2 databases”.
Select an option other than SSH. For more information on these settings, see “Configuring DB2 options”.
DB Host Name/IP
Enter the DB host name or IP address of the computer where the target database is located.
Port
Enter the number of the port the database uses; the default port is 1521
Connect At
Displayed for Microsoft SQL Server or Sybase only.
Select Database Level or Server Level.
Select Server Level to exclude the databases specified by the MSSQL Server Level Exclusions or Sybase Server Level Exclusions global properties.
Additional JDBC Settings
By default, the target uses the additional JDBC settings values that you set in the Target global properties. For more information on these properties, see “Target properties”.
To use different values, enter one or more key-value pairs separated by a semicolon.
For Microsoft SQL Server or Sybase databases only, you can also do the following:
Microsoft SQL Server — To support an SSL-encrypted connection, in SQL Server, set ForceEncryption to Yes. Then, for Additional JDBC Settings, enter SSL=require.
(To connect without encryption, in SQL server, set ForceEncryption to No.)
If you use NTLM version 2 authentication, enter useNTLMv2=true.
Sybase — To support an SSL-encrypted connection, enter SYBSOCKET_FACTORY=com.fortinet.fortidb.target.internal.connection.SybaseSSLSQL
Note: Database activity monitoring (DAM) using the TCP/IP sniffer is not available when FortiDB connects to Sybase using SSL.
DB Activity Monitoring
Select to monitor this database.
4. (Optional) Enter information on the Classification and Contact Info tabs.
You can use this information to filter the list of targets when you search the list of targets or create target groups.
5. To test your connection, select Test Connection.
6. Click Save.
See also
Managing targets
Configuring DB2 options
Configuring SSH connections to Oracle and DB2 databases
SSH environment requirements (software-only version)
Enabling operating system vulnerability assessment (OSVA) for Solaris and AIX
Auto-discovery