Welcome to Kofax RPA > Management Console > Management Console Configuration and User Interface > Settings > General > RoboServer log database

RoboServer log database

On this tab, you can configure the logging database used by Management Console to store schedule runs, schedule messages, robot runs, robot messages, robot tags, Desktop Automation Service messages as well as all RoboServers belonging to clusters where database logging has been enabled in the cluster settings.

Note To use a database for logging, you need to prepare your database server by either creating a new database (schema), or simply making sure an existing database is available. You need to obtain a user name and password with rights to create tables, drop tables, create indexes, drop indexes, select, insert, update, and delete in the database.

Both Management Console and RoboServer create the log tables automatically when they are started (if the tables do not already exist). However, you may also create them using the Scripts for creating database tables.

Select Log to database and configure the logging database.

Property Description
Host

Host name of the database server, which can be an IP address, the fully qualified domain name (myhost.kofax.com), or a work computer name (PC1X1XXX).

Port Port of the database server.
Schema Name of the database schema (or catalog).
Type Type of database, such as Oracle. The different types of databases are configured in Management Console and are provided automatically when Design Studio is started.
User name User name for the database.
Password Password for the database.
To test the current configuration, click Test.
Note This action only tests the connection to the database. It does not test whether you have the proper permissions in the database.
Click Save when finished.

The following cleanup thresholds can be configured for the RoboServer log database.

Property

Description

Keep robot and schedule statistics for (day)

Specify the number of days to keep the robot and schedule statistics. According to the cleanup settings you define, the old data is deleted on a daily basis.

Max messages in robot run

Specifies the maximum number of messages in a single robot run. The robot message logging stops for the specific run when the number of robot messages exceeds this threshold.

The cleanup deletes the oldest robot runs and the messages for the deleted runs. If you experience performance problems with the log database, you can lower this threshold. To store more historic messages, you can increase this threshold.