CoreMedia Studio's Server application needs to be connected with the Content Management Server to access the repository and with the preview CAE to show the preview of the opened form. If you use CoreMedia Blueprint, everything is already configured properly for your local workspace. If you use a distributed environment you can either use the local Spring profile and provide the installation.host property with the value of the host name where your CMS services and databases are running.

Connecting with the Content Server

When you start the Studio server Spring Boot application (apps/studio-server/spring-boot/studio-server-app) with mvn spring-boot:run during development, you may configure the CMS connection by configuring the installation.host property in the private Spring profile (src/main/resources/config/application-private.properties) as described in the documentation of how to start Blueprint applications.

Refer to the [Developer Manual] to learn about building deployable artifacts.

Connecting with the Editorial Comments Database

When running mvn spring-boot:run you can configure the properties editorial.comments.db.host=DB_HOST or editorial.comments.datasource.url=DATASOURCE_URL in the application-private.properties file to configure the Editorial Comments Database.

Connecting with the Preview CAE

When you start the Studio server application locally during development, you can configure the connection to the preview CAE in the application-private.properties file in the src/main/resources directory of studio-server-app. Simply change the value of the property studio.previewUrlPrefix to the URL prefix of your CAE.

The property studio.previewControllerPattern contains the configurable preview controller pattern. If it is empty or not defined, then Studio will use the default preview controller pattern preview?id={0}. If you want to use simple numeric IDs instead, then you can configure in the studio.properties file as follows: studio.previewControllerPattern=preview?id={1}. The placeholder 0 and 1 are representing the CoreMedia ID and the numeric ID, respectively.

Note that Elastic Social users and user comments do not have numeric IDs. Hence, you should configure preview?id={0}. However, when using preview?id={1}, the placeholder 1 is replaced with the non-numeric ID as well and the preview application has to handle this special case or will fail to deliver.