Blueprint Developer Manual / Version 2412.0
Table Of ContentsRelational Database Setup
You need to create different databases and users used by the various CoreMedia
CMS
components (see Section 3.1, “Prerequisites”). In the
workspace-configuration/database
folder of the Blueprint workspace you will
find SQL scripts for creating and dropping all database entities needed for the relational
database.
The scripts are suitable for a local MySQL instance in a developer environment. You can easily
adapt them for other databases or remote users. There are also Bash scripts and Windows batch
files to apply the SQL scripts. If the MySQL server is running and the
mysql command line client is executable via the PATH
variable, you only need to execute the following in order to prepare the databases for
CoreMedia Content Cloud.
Windows:
> cd $CM_BLUEPRINT_HOME\workspace-configuration\database\mysql\
createDB.bat
Linux:
$ cd $CM_BLUEPRINT_HOME/workspace-configuration/database/mysql
./createDB.sh
The command was successful if the following databases have been created:
| Database | User | Password | Description |
|---|---|---|---|
| cm_management | cm_management | cm_management | Database for the Content Management Server |
| cm_master | cm_master | cm_master | Database for the Master Live Server |
| cm_replication | cm_replication | cm_replication | Database for the Replication Live Server |
| cm_mcaefeeder | cm_mcaefeeder | cm_mcaefeeder | Database for the CAE Feeder connected to the Content Management Server |
| cm_caefeeder | cm_caefeeder | cm_caefeeder | Database for the CAE Feeder connected to the Master Live Server |
| cm_editorial_comments | cm_editorial_comments | cm_editorial_comments | Database for the Studio Server that runs the feature Editorial Comments |
| cm_notifications | cm_notifications | cm_notifications |
Database for the Notifications based on SQL persistence layer. For details see Section 4.2.4, “SQL Replacement for MongoDB-Based Editorial Services”. |
| cm_projects | cm_projects | cm_projects |
Database for the Projects/To-Dos based on SQL persistence layer. For details see Section 4.2.4, “SQL Replacement for MongoDB-Based Editorial Services”. |
| cm_caplist | cm_caplist | cm_caplist |
Database for the CapLists based on SQL persistence layer. Relevant for the features My Edited Content and Workflow Lists. For details see Section 4.2.4, “SQL Replacement for MongoDB-Based Editorial Services”. |
Table 4.5. Database Settings
MongoDB Database Setup
Several CoreMedia core features like My Edited Content and Workflow Lists (backed by CapLists), Notifications, and Projects/To-Dos by default use MongoDB as a persistence layer. A default local MongoDB installation is sufficient, because the CoreMedia components connect through the default port with no user credentials, by default. If required, see Section 4.5, “Collaborative Components” in Operations Basics for more MongoDB configuration.
For details, how to switch the persistence layer for these features to SQL, see Section 4.2.4, “SQL Replacement for MongoDB-Based Editorial Services”.
