Switching INUBIT Monitoring Database

In the H2 database which is included in the delivery, the monitoring tables are limited to 50'000 entries. At least one database entry is written for every workflow execution. If 110 workflows are executed every day, then these are each visible for about one year. The oldest entries are removed from the file system and transferred to a log file for archiving as soon as a maximum of 50'000 entries has been reached.

The decision which scenario will initiate a switch to another database depends on how many workflow executions take place during what timeframe and for how long the entries are to remain visible on the monitor.

If many workflows are executed simultaneously, or one workflow is executed more frequently, then the maximum number of entries in the H2 database may be reached quickly. By means of the enclosed configuration files it is then possible to switch to a database such as MSSQL, MySQL, or Oracle, for example.

Proceed as follows

Install the JDBC driver which is appropriate for your selected database system.

Refer to Managing Libraries
In your database system create a schema.
Stop the INUBIT Process Engine.
Rename the configuration file of the H2 database, for example from logsDBConfig.xml to logsDBConfig.xml.h2. The configuration files are located in the directory <inubit-installdir>/inubit/server/ibis_root/conf/.
Remove the configuration file ending you want to switch to, thus naming the file logsDBConfig.xml.

In the logsDBConfig.xml file adjust the values of the elements url, user and password, according to your database and work environment.

The maximum number of entries in a database is each specified in the configuration file; e.g. <maximumLimit>41000</maximumLimit> for the system log in a MySQL database. If increasing the number limit, please note the comment about the element! The comment contains a reference to the maximum number.

Restart the INUBIT Process Engine.