Configure the Reaper Service Using the Shell Prompt

BTEventDBReaper gathers events from a collector (forwarded by endpoints) and writes the events to the database. BTCollector stores incoming events in a local, intermediate, database while BTEventDBReaper writes the events to the central SQL Server database.

BTEventDBReaper runs as a Windows service, but can be run from the command line to set up parameters for the service.

To view BTEventDBReaper arguments, execute the following command:

C:\Program Files\BeyondTrust\PBIS\Enterprise>BTEventDBReaper /?
Option Description
/? Display help.
/gui

Opens a GUI where you can set the database provider and connection string. Use as an alternative to command-line.

/d PROVIDER

Sets the database provider:

System.Data.SqlClient for SQL Server (default) or MySql.Data.MySqlClient for MySQL.

/c DBSTRING Sets the database connection string to connect to the BeyondTrust database.
/f NUMBER

Sets the earliest record id that should be copied when the agent runs. Use this parameter with caution.

The /f parameter is used to control the point at which the first event in the local collector database is written to the central AD Bridge Enterprise database. Under normal circumstances, it should not be necessary to set this parameter.

/r Refreshes the agent with new registry settings.
/s Shows the current status.
/debug Run as command line application with logging.

Any parameters set from the command line take effect the next time that BTEventDBReaper runs. To apply the settings immediately, run BTEventDBReaper with the /r argument.

The /s option is used to display the current configuration settings for the service:

C:\Program Files\BeyondTrust\PBIS\Enterprise>BTEventDBReaper /s

Current settings:
    Database provider:     System.Data.SqlClient
    Connection string:     Data Source=RVLN-BUILD;
                           Initial  Catalog=LikewiseEnterprise;
                           Integrated Security=True
    Record id last copied: 1794
    Records per period:    300
    Seconds in a period:   1200

Although the settings include records per period and seconds in a period, the parameters cannot be configured from the command-line. The default values can be changed using the Enterprise Database Management plug-in.