Sensor properties for the database sensor

book

Article ID: 179526

calendar_today

Updated On:

Products

Security Information Manager

Issue/Introduction

 

Resolution

Sensor properties for the database sensor

See About sensor properties for common sensor types.

Table: Database sensor properties

Sensor property

Description

JDBC Drivers Directory

Specify the path where the database driver is installed.

If the collector is installed on the Information Manager 4.6 appliance, the default directory is one of the following paths:

  • For Sybase, the path is as follows:

    /opt/Symantec/simserver/collectors/drivers/jConnect-6_0

  • For MS SQL Server, the paths are as follows:

    /opt/Symantec/simserver/collectors/drivers/mssqljdbc_2005/enu

    /opt/Symantec/simserver/collectors/drivers/mssqljdbc_2000/lib

  • For MySQL, the path is as follows:

    /opt/Symantec/simserver/collectors/drivers/mysql-connector-java-5.0.7

  • For PostgreSQL, the path is as follows:

    /opt/Symantec/simserver/collectors/drivers/postgresql-8.2-504

  • For IBM DB2, the path is as follows:

    /opt/Symantec/simserver/collectors/drivers/v9fp2_db2driver_for_jdbc_sqlj

Database URL

The collector includes a default database URL that can include any of the following items:

  • Type of database driver that is used

  • Instance name

  • Host name

  • TCP port

  • Database name

Example database URL formats are as follows:

  • If you use a Microsoft SQL Server database, the database URL format is as follows:

    jdbc:microsoft:​sqlserver://​host_name_or_​IP_address_of_​the_database_server:​1433;DatabaseName=​database_name

    For example, to connect to a Microsoft SQL Server database named MyDatabase on the localhost server, with the SQL Server listening for connections on the default port number 1433, you would use the following URL:

    jdbc:microsoft:sqlserver://192.168.255.234:1433;DatabaseName=MyDatabase

  • If you use a MySQL database, the database URL format is as follows:

    jdbc:mysql://ip_address:port_number/DatabaseName=database_name

    For example, to connect to a MySQL database named MyDatabase on the server at 192.168.255.234, with the MySQL server listening for connections on the default port number 3306, you would use the following URL:

    jdbc:mysql://192.168.255.234:3306/DatabaseName=MyDatabase

  • If you use a Sybase database, the database URL format is as follows:

    jdbc:sybase:Tds:host:port

    For example, to connect to a Sybase database on the server at 192.168.255.234, with the Sybase server listening for connections on the default port number 2638, you would use the following URL:

    jdbc:sybase:Tds:192.168.255.234:2638

  • If you use an Oracle database, the database URL format is as follows:

    jdbc:oracle:thin:@ip_address:1521:System_Identifier_(SID)

    For example, to connect to an Oracle database named MyDatabase on the server at 192.168.255.234, with the Oracle server listening for connections on the default port number 1521, you would use the following URL:

    jdbc:oracle:thin:@192.168.255.234:1521:MyDatabase

Note:
If you are not using the default port number, you must replace the default port number in the URL.

User Name

Specify the read-only database user account name for the database.

Password

Specify the password for the database user account name for the database.

Start Reading From

Specify from where to start reading the database upon restart of the collector as follows:

  • BEGINNING

    Specifies that the database is read from the beginning.

  • END

    Specifies that the database is read from the end. Only events that are written to the database after the collector starts are read.

Execution Time

Specify the scheduled time to send events to the Symantec Security Information Manager appliance, or leave this field blank if you want to collect events in real time.

Time is entered in 24-hour clock time. You can schedule the collector to send events on a specific day, every day at a specified time, every week, or on a specified number of weeks.

The time that is specified in the Execution Time field must use the same time zone and system clock as the collector computer.

If the first batch has not finished before the second batch needs to start, the second batch is skipped.

Execution Time syntax is as follows:

<Every day/Every n days/Every week/Every n weeks> 

On <Sun/Mon/Tue/Wed/Thu/Fri/Sat> at <n:n:n>,<n:n:n>, 

<Sun/Mon/Tue/Wed/Thu/Fri/Sat> at <n:n:n>,<n:n:n>

Examples are as follows:

  • 5:00:00

    Send events every day at 5:00 a.m.

  • 5:0:0,17:0:0

    Send events every day at 5:00 a.m. and 5:00 p.m.

  • Every day at 7:0:0,19:0:0

    Send events every day at 7:00 a.m. and 7:00 p.m.

  • Every 2 days at 0:0:0,12:0:0

    Send events every other day at midnight and noon.

    If a specified time has not passed, events are sent on the same day; if a specified time has already passed, events are sent in 2 days.

  • On Sun, Wed at 8:30:0,20:30:0

    Send events on Sunday and Wednesday at 8:30 a.m. and 8:30 p.m.

    (This value is the same as Every Week on Sun, Wed at 8:30,20:30.)

  • Every week on Mon, Fri at 7:0:0,14:0:0

    Send events on Monday and Friday at 7:00 a.m. and 2:00 p.m.

    (This value is the same as On Mon, Fri at 7:0:0,14:0:0.)

  • Every 2 weeks on Tue, Sat at 7:0:0,19:0:0

    Send events every 2 weeks on Tuesday and Saturday at 7:00 a.m. and 7:00 p.m.

  • Every 3 weeks on Thu at 7:0:0, Tue at 7:0:0,14:0:0

    Send events every 3 weeks on Thursday at 7:00 a.m. and on Tuesday at both 7:00 a.m. and 2:00 p.m.