Configuring Databases

For INUBIT, you need databases for the following data:

The cache database contains mostly workflow data, module data, and configuration data. The cache database must fit the following requirements:
- For a highly available INUBIT, the database must be highly available.
- The database must be able to process the accruing data.
- The database must be configured so that the data are automatically committed (autocommit=true).
Repository
Logging

Configuring database connection retry mechanisms in case the database is temporary not available

To prevent data loss if the cache database or the monitoring is temporary not available, you can use several parameters to configure how often the INUBIT Process Engine tries to reconnect to the database if it is disconnected.

Additionally, you can use the tolerance parameters to configure a leaky bucket mechanism.

Refer to

Prerequisites

All databases are created in the same databases management system.

The database driver is installed in the <inubit-installdir>/server/process_engine/lib directory.

Install the database driver only once in the <inubit-installdir>/server/process_engine/lib directory. Installing a wrong driver or multiple drivers can cause the Process Engine not to start up.

MySQL, MariaDB

The MySQL/MariaDB database was started with the parameter --max_allowed_packet and a value appropriate for your environment, for example:

mysqld --max_allowed_packet=32M

Refer to Switching the Repository to a Database

For productive use, you need to replace the H2 databases – installed by default and intended for testing purposes only – by one of the supported databases, refer to Software Requirements.

If you want to specify the database user and/or his password on an encrypted basis, you can encrypt the information with the INUBIT CLI. Then set the attribute encrypted="true" for the respective parameter.

Configuring Cache Database

Proceed as follows

Rename the file matching your database <inubit‑installdir>/server/ibis_root/conf/ibis.xml.<Database> to ibis.xml.

Open the file <inubit‑installdir>/server/ibis_root/conf/ibis.xml and adjust the following values to the common database, such as:

<Property name="jdbcUrl">jdbc:oracle:thin:@Oracle-Host:1521:inubitDatabase</Property>
<Property name="user">DatabaseUserName</Property>
<Property name="password">DatabaseUserPassword</Property>

Refer to Configuring the Database in the ibis.xml File

Configuring Logging Database

Proceed as follows

Rename the <inubit-installdir>/server/ibis_root/conf/logsDBConfig.xml.<database> file matching your database to logsDBConfig.xml.
Open the file <inubit‑installdir>/server/ibis_root/conf/logsDBConfig.xml and adjust the following values to the common database, such as:
```
<url>jdbc:oracle:thin:@Oracle-Host:1521:INUBITDatabase</url>
<user>DatabaseUserName</user>
<password>DatabaseUserPassword</password>
```

Refer to Configuring the Logging Database Connection in the logsDBConfig.xml File.

Configuring Repository Database

Proceed as follows

Rename one of the following files matching your operating mode and your database to repository.xml: <inubit-installdir>/server/ibis_root/conf/repository.xml.<database>.{SINGLE|CLUSTER}
Copy the driver for your database into the following directory:

<inubit-installdir>/server/process_engine/lib

Configuring the Database Connection Encryption for Oracle-Based INUBIT Databases

Prerequisites

You have not yet started the INUBIT Process Engine for the first time.
You have configured an Oracle database as INUBIT database for cache, monitoring, and repository.

Proceed as follows

Navigate to the <inubit-installdir>/server/ibis_root/conf directory.
Open the ibis.xml file for editing to configure the connection for the cache and the repository database.

Search for the following line:

<Property name="driverProperties" type="Map"/>

Replace this line with the following lines:

<Property name="driverProperties" type="Map">
  <Property name="oracle.net.encryption_client">REQUIRED</Property>
  <Property name="oracle.net.encryption_types_client">( AES256,AES192 )</Property>
  <Property name="oracle.net.crypto_checksum_client">REQUIRED</Property>
  <Property name="oracle.net.crypto_checksum_types_client">( SHA1 )</Property>
</Property>

Save the changes.
Open the logsDBConfig.xml file based on the logsDBConfig.xml.Oracle template for editing to configure the connection for the monitoring database.

Search for the following line:

<connectionProperties connectionEncrypted="false">

Replace the string connectionEncrypted="false" with connectionEncrypted="true".
Save the changes.