Enterasys Security Information and Event Manager, Configuration Manual

Page: 155 / 426

Configuring DSMs
IBM Proventia Management SiteProtector 139
Database
Instance If you select MSDE as the Database Type and you have multiple
SQL server instances on one server, define the instance to which
you want to connect.
Note: If you use a non-standard port in your database
configuration, or have blocked access to port 1434 for SQL
database resolution, you must leave the Database Instance
parameter blank in your SIEM configuration.
Table Name Type the name of the table or view that includes the event records.
The default table name is
SensorData1.
The table name can be up to 255 alphanumeric characters in
length. Also, the table name may include the following special
characters: dollar sign ($), number sign (#), underscore (_), en
dash (-), and period(.).
Select List Type
*
for all fields from the table or view.
You may use a comma-separated list to define specific fields from
tables or views, if required for your configuration. The list must
contain the field defined in the Compare Field parameter. The
comma-separated list can be up to 255 alphanumeric characters in
length. Also, the list may include the following special characters:
dollar sign ($), number sign (#), underscore (_), en dash (-), and
period(.).
Compare Field Type
SensorDataRowID
to identify new events added between
queries to the table.
The compare field can be up to 255 alphanumeric characters in
length. Also, the list may include the following special characters:
dollar sign ($), number sign (#), underscore (_), en dash (-), and
period(.).
Start Date and
Time Optional. Configure the start date and time for database polling.
The Start Date and Time parameter must be formatted as
yyyy-MM-dd HH:mm with HH specified using a 24 hour clock. If the
start date or time is clear, polling begins immediately and repeats
at the specified polling interval.
Use Prepared
Statements Select the check box to use prepared statements, which allows the
JDBC protocol source to setup the SQL statement once, and then
execute the SQL statement many times with different parameters.
For security and performance reasons, we recommend that you
use prepared statements.
Clear this check box to use an alternative method of querying that
does not use pre-compiled statements.
Table 31-4 JDBC Parameters (continued)
Parameter Description