Skip to main content
Version: 2.8

Database requirements

Databases store metadata and information for the different systems.

D1, for example, needs a database to store information about a document getting checked out, the name of the document or its history. This information goes into the database. Similar principle applies to the Conversion Service. In addition, the system databases are used for storing user information, sessions, locks, and so on. A relational database can handle this quite well - therefore it is used.

It is possible to share databases in the configurations described in the following table:

Shared databaseImportant information
System database for D1 and Conversion ServiceUsers, sessions, and other system data is shared between D1 and Conversion Service in this setup.
Single database for Conversion system and access dataThis setup is possible provided you don't need to back up your conversion system data. In practice it means that you can share the database provided you don't have any special conversion users.
Single database for Conversion access data and D1 Cache dataThis setup is possible but not recommended. Conversion access data is transient; D1 cache data is also a kind of transient, but it is really time consuming to recreate - it requires regular backups.

D1 database requirements

For D1, you need to have the following databases:

  • One SQL database for system-related data (such as sessions, user accounts or repository configuration):
  • An SQL databases for each repository;
  • Cache abd content databases for tribefire repository;
  • Cache database for external repositories (e.g. Documentum, CMIS).
UsageDescriptionBackupType
System databasecontains user information, repository configuration, user sessions, locking information, leadership informationPriority 1shared between all D1 nodes, optionally shared with Conversion Service and/or Messaging
Cache databasecontains cache/representations of content - can be recreated in a time consuming processPriority 2shared between all D1
Content databasecontains business dataPriority 1shared between all D1

PostgreSQL database requirements

Version requirement

The version of PostgreSQL database must be 11 or newer.

The following table describes size requirements for the PostgreSQL database:

RequirementsParameterDescription
ConnectionPool size User Session - minUSER_SESSIONS_DB.minPoolSize*0
ConnectionPool size User Session - maxUSER_SESSIONS_DB.maxPoolSize*20
ConnectionPool size User Statistics- minUSER_SESSION_STATISTICS_DB.minPoolSize*0
ConnectionPool size User Statistics - max USER_SESSION_STATISTICS_DB.maxPoolSize*10
ConnectionPool size Authorization - minAUTH_DB.minPoolSize*0
ConnectionPool size Authorization - max AUTH_DB.maxPoolSize*10
ConnectionPool size Locking - minLOCKING_DB.minPoolSize*0
ConnectionPool size Locking - maxLOCKING_DB.maxPoolSize*5
ConnectionPool size LEADERSHIP_DB - minLEADERSHIP_DB.minPoolSize*0
ConnectionPool size LEADERSHIP_DB - maxLEADERSHIP_DB.maxPoolSize*5

*or the default configuration of DEFAULT_DB - the sum of the maximum connections of each connection pool is the required number of connections from the database

Oracle database requirements

Version requirement

The version of Oracle database must be 11 or newer.

The following table describes the size requirements for the Oracle database:

RequirementsParameterDescription
Version---11 or newer
ConnectionPool size User Session - minUSER_SESSIONS_DB.minPoolSize*0
ConnectionPool size User Session - maxUSER_SESSIONS_DB.maxPoolSize*20
ConnectionPool size User Statistics - minUSER_SESSION_STATISTICS_DB.minPoolSize*0
ConnectionPool size User Statistics - max USER_SESSION_STATISTICS_DB.maxPoolSize*10
ConnectionPool size Authorization - minAUTH_DB.minPoolSize*0
ConnectionPool size Authorization - max AUTH_DB.maxPoolSize*10
ConnectionPool size Locking - minLOCKING_DB.minPoolSize*0
ConnectionPool size Locking - maxLOCKING_DB.maxPoolSize*5
ConnectionPool size LEADERSHIP_DB - minLEADERSHIP_DB.minPoolSize*0
ConnectionPool size LEADERSHIP_DB - maxLEADERSHIP_DB.maxPoolSize*5

*or the default configuration of DEFAULT_DB - the sum of the maximum connections of each connection pool is the required number of connections from the database.

MSSQL database requirements

Version requirement

The version of MSSQL database must be 12 or newer.

The following table describes size requirements for the MSSQL database:

RequirementsParameterDescription
ConnectionPool size User Session - min USER_SESSIONS_DB.minPoolSize*0
ConnectionPool size User Session - maxUSER_SESSIONS_DB.maxPoolSize*10
ConnectionPool size User Statistics - minUSER_SESSION_STATISTICS_DB.minPoolSize*0
ConnectionPool size User Statistics - max USER_SESSION_STATISTICS_DB.maxPoolSize*10
ConnectionPool size Authorization - minAUTH_DB.minPoolSize*0
ConnectionPool size Authorization - max AUTH_DB.maxPoolSize*10
ConnectionPool size Locking - minLOCKING_DB.minPoolSize*0
ConnectionPool size Locking - maxLOCKING_DB.maxPoolSize*5
ConnectionPool size LEADERSHIP_DB - minLEADERSHIP_DB.minPoolSize*0
ConnectionPool size LEADERSHIP_DB - maxLEADERSHIP_DB.maxPoolSize*5

*or the default configuration of DEFAULT_DB - the sum of the maximum connections of each connection pool is the required number of connections from the database.

Conversion Service database requirements

The Conversion Service needs the following databases:

  • One SQL database for system-related data (such as sessions or user accounts).
  • One SQL database for storing the job information.

In addition, a proprietary database is used on all nodes. This database holds the configuration of the Conversion Service.

TypeDescriptionBackupType
System databasecontains user information, repository configuration, user sessions, locking information, leadership informationPriority 1shared between all Conversion Service nodes, optionally shared with D1 and/or Messaging
Conversion databasecontains transient dataPriority 4shared between all Conversion Service nodes
Note

If CONV_STORAGE_TYPE=db then the conversion files will be stored in database. This needs to be considered in case of sizing/caching configuration of the database.

PostgreSQL database requirements

Version requirement

The version of PostgreSQL database must be 11 or newer.

The following table describes size requirements for the PostgreSQL database:

RequirementsParameterDescription
ConnectionPool size User Session - minUSER_SESSIONS_DB.minPoolSize*0
ConnectionPool size User Session - maxUSER_SESSIONS_DB.maxPoolSize*20
ConnectionPool size User Statistics - minUSER_SESSION_STATISTICS_DB.minPoolSize*0
ConnectionPool size User Statistics - max USER_SESSION_STATISTICS_DB.maxPoolSize*10
ConnectionPool size Authorization - minAUTH_DB.minPoolSize*0
ConnectionPool size Authorization - max AUTH_DB.maxPoolSize*10
ConnectionPool size Locking - minLOCKING_DB.minPoolSize*0
ConnectionPool size Locking - maxLOCKING_DB.maxPoolSize*5
ConnectionPool size LEADERSHIP_DB - minLEADERSHIP_DB.minPoolSize*0
ConnectionPool size LEADERSHIP_DB - maxLEADERSHIP_DB.maxPoolSize*5

*or the default configuration of DEFAULT_DB - the sum of the maximum connections of each connection pool is the required number of connections from the database.

Oracle database requirements

Version requirement

The version of Oracle database must be 11g or newer.

The following table describes the size requirements for the Oracle database:

RequirementsParameterDescription
Version---11 or newer
ConnectionPool size User Session - minUSER_SESSIONS_DB.minPoolSize*0
ConnectionPool size User Session - maxUSER_SESSIONS_DB.maxPoolSize*20
ConnectionPool size User Statistics - minUSER_SESSION_STATISTICS_DB.minPoolSize*0
ConnectionPool size User Statistics - max USER_SESSION_STATISTICS_DB.maxPoolSize*10
ConnectionPool size Authorization - minAUTH_DB.minPoolSize*0
ConnectionPool size Authorization - max AUTH_DB.maxPoolSize*10
ConnectionPool size Locking - minLOCKING_DB.minPoolSize*0
ConnectionPool size Locking - maxLOCKING_DB.maxPoolSize*5
ConnectionPool size LEADERSHIP_DB - minLEADERSHIP_DB.minPoolSize*0
ConnectionPool size LEADERSHIP_DB - maxLEADERSHIP_DB.maxPoolSize*5

*or the default configuration of DEFAULT_DB - the sum of the maximum connections of each connection pool is the required number of connections from the database.

MSSQL database requirements

Version requirement

The version of MSSQL database must be 12 or newer.

The following table describes size requirements for the MSSQL database:

RequirementsParameterDescription
ConnectionPool size User Session - min USER_SESSIONS_DB.minPoolSize*0
ConnectionPool size User Session - maxUSER_SESSIONS_DB.maxPoolSize*20
ConnectionPool size User Statistics - minUSER_SESSION_STATISTICS_DB.minPoolSize*0
ConnectionPool size User Statistics - max USER_SESSION_STATISTICS_DB.maxPoolSize*10
ConnectionPool size Authorization - minAUTH_DB.minPoolSize*0
ConnectionPool size Authorization - max AUTH_DB.maxPoolSize*10
ConnectionPool size Locking - minLOCKING_DB.minPoolSize*0
ConnectionPool size Locking - maxLOCKING_DB.maxPoolSize*5
ConnectionPool size LEADERSHIP_DB - minLEADERSHIP_DB.minPoolSize*0
ConnectionPool size LEADERSHIP_DB - maxLEADERSHIP_DB.maxPoolSize*5

*or the default configuration of DEFAULT_DB - the sum of the maximum connections of each connection pool is the required number of connections from the database.