Content Server Manual / Version 2201
Table Of ContentsNote
Please read the Supported Operating Environments document on the CoreMedia Content Cloud documentation https://documentation.coremedia.com/cmcc-11 page in order to get the actually supported databases.
The general configuration of the database is described in Section 3.2.4, “Properties for the Connection to the Database” in Deployment Manual.
Vendor-specific configuration can be done in the database dependent
<DBName>.properties
files.
Note
Note: The required JDBC drivers are not part of the CoreMedia CMS distribution; they must be obtained from the corresponding database manufacturer.
The database must be accessible over the network and should be enabled for the Unicode character set. Each Content Server requires a different database user account. The database users must be able to create and delete tables and indexes in their schemas. (For Oracle, see Example 3.1, “Oracle: create DB User” and Example 3.3, “Oracle: delete DB User”)
Database Cluster
The Content Servers can be attached to a database cluster. While CoreMedia does not certify a specific cluster solution, clusters can be used as long as they use synchronous replication. That is, all transactions must be replicated to the other nodes before the end of the current transaction, so that all changes are visible even in case of a node failure. Otherwise, the memory state of the Content Server might differ from the database state after a failover.
For example, this might led to a database error, with "parent key not found" in the logs, if a blob is referenced from the Content Server memory but does not exist in the database.
Manual creation of tables is not necessary. A Content Server automatically creates tables, the first time it is started. The standard settings of the database or the standard values defined for the database user are used as default for the tables and indexes created, such as the initial reserved memory.
Note
Important: To guarantee high performance of the whole system, correct installation and regular database maintenance is necessary. In particular, the statistics data for tables and indexes must be updated daily according to the manufacturer's instructions.