Blueprint Developer Manual / Version 2412.0
Table Of ContentsBefore you can start with development, you have to do some configurations, in part, depending on the Blueprint you want to work with.
Remove the Blueprints and modules that you do not want to use as described in Section 4.2.1, “Removing Optional Components”.
Adapt your Maven settings to the required repositories as described in Section 3.1, “Prerequisites”.
Adapt the workspace to your own project as described in Section 4.2.2, “Configuring the Workspace”. Configure, for example, groupId, version, deployment repositories and CoreMedia licenses.
If you want to use a local setup, then you have to do some database configuration and host mapping as described in Section 4.2.3, “Configuring Local Setup”.
Several CoreMedia core features like My Edited Content and Workflow Lists, Notifications, and Projects/To-Dos use MongoDB as a persistence layer.
This persistence layer can be and for a new installation should be replaced by the preferred SQL based persistence layer. See Section 4.2.4, “SQL Replacement for MongoDB-Based Editorial Services” for required adjustments.
Another persistence replacement option is the in-memory persistence layer, which is deprecated. Details how to enable this persistence layer can be found in Section 4.2.5, “In-Memory Replacement for MongoDB-Based Editorial Services (Deprecated)”.
