RoboServer Log Database

This is the logging database used by all RoboServers belonging to clusters where database logging has been enabled in the cluster settings. The database is configured in the same way as the cluster databases.

Cleanup thresholds can be configured for the RoboServer log database in the same way as for the Schedule Log.

Property

Description

Robot message count threshold

The log will automatically clean up the database when the number of robot messages in the database exceeds this threshold. The cleanup will delete 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. If you wish to store more historic messages you can increase this threshold.

Robot run count threshold

The log will automatically clean up the database when the number of robot runs in the database exceeds this threshold. The cleanup will delete 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. If you wish to store more historic messages you can increase this threshold.

Server message count threshold

The log will automatically clean up the database when the number of server messages in the database exceeds this threshold. The cleanup will delete the oldest server messages. If you experience performance problems with the log database you can lower this threshold. If you wish to store more historic messages you can increase this threshold.

RoboServer Log Database Cleanup


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

Both the Management Console and RoboServer will create the log tables automatically when they are started (if the tables do not already exist). However you may also create them using the following scripts

Database

Create Tables

Drop Tables

IBM DB2

create

drop

Derby

create

drop

MySQL

create

drop

Oracle

create

drop

Microsoft SQL Server

create

drop

Sybase

create

drop

SQL scripts for log tables (right click and chose save as)


If you are upgrading from version 7.2, and want to use the logging tables already created, you will have to modify the ROBOT_RUN table, since a new column has been added. You must add a column named PROJECTNAME of type VARCHAR(255) to the ROBOT_RUN table (NVARCHAR2 on Oracle, NVARCHAR on Sybase and Microsoft SQL server).

If you are upgrading from version 8.1 or earlier, and want to use the logging tables already created, you will have to modify the ROBOT_MESSAGE table, since a new column has been added. You must a a column named PROJECTNAME of type VARCHAR(255) to the ROBOT_MESSAGE table (NVARCHAR2 on Oracle, NVARCHAR on Sybase and Microsoft SQL server).