Blueprint Developer Manual / Version 2412.0
Table Of ContentsThe following tables show the database users that are required for CoreMedia applications and features. For MySQL and Microsoft SQL Server you will find scripts in the workspace creating these users.
Table 7.20, “ Application-Specific Database Users ” refers to the central, application-specific database users. Along with that come database users bound to certain features like Editorial Comments as shown in Table 7.21, “ Feature-Specific Database Users ”. Unlike the application-specific database users, these may be accessed by several applications in parallel. Note, that these database users (thus, especially their respective names, passwords) must be configured in all bound applications.
| Application | Username | Description |
|---|---|---|
|
Content Management Server |
cm_management |
This database user will manage the content of the Content Management Server. This database will require most of the space, since content is versioned. |
|
Master Live Server |
cm_master |
This database user will manage the content of the Master Live Server. Up to two versions of each published content will be stored. |
|
Replication Live Server |
cm_replication |
This database user will manage the content of the Replication Live Server. Up to two version of each published content will be stored. |
|
CAE Feeder for preview |
cm_mcaefeeder |
This database user will persist data for the CAE Feeder working in the management environment. Content is not versioned. |
|
CAE Feeder for live site |
cm_caefeeder |
This database user will persist data for the delivery environment. Content is not versioned. |
Table 7.20. Application-Specific Database Users
| Username | Description | Applications(s) |
|---|---|---|
|
cm_caplist |
This database user will persist data for the features My Edited Content and Workflow Lists if SQL persistence is enabled for CapLists. For details see Section 4.2.4, “SQL Replacement for MongoDB-Based Editorial Services”. |
Studio Server; User Changes Application; Workflow Server |
|
cm_editorial_comments |
This database user will persist data for the feature Editorial Comments. |
Studio Server |
|
cm_notifications |
This database user will persist data for the Notifications based on SQL persistence layer. For details see Section 4.2.4, “SQL Replacement for MongoDB-Based Editorial Services”. |
Studio Server; User Changes Application |
|
cm_projects |
This database user will persist data for the Projects/To-Dos based on SQL persistence layer. For details see Section 4.2.4, “SQL Replacement for MongoDB-Based Editorial Services”. |
Studio Server |
Table 7.21. Feature-Specific Database Users
