CoreMedia Studio 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 have to adapt the following properties:
Connecting with the Content Server
When you start the Studio web application with mvn
tomcat7:run during development, you can configure the connection by supplying the
arguments -Dcontentserver.host=MYHOST and (optionally)
-Dcontentserver.port=MYPORT at the command line. Alternatively, you can configure
the connection in the application.properties file in the
src/main/webapp/WEB-INF directory. Use the contentserver.host and
contentserver.port properties for the host and port of your Content
Server , respectively.
Refer to the [CoreMedia DXP 8 Manual] to learn about building deployable artifacts.
Connecting with the Preview CAE
When you start the Studio web application with mvn
tomcat7:run during development, you can configure the connection to the preview
CAE in the override-web.xml file in the
CoreMedia Studio web application directory. Simply change the value
of the parameter ProxyTo to the URL of your
CAE. When you deploy
Studio in an application server like
Tomcat, you should change the application.properties in the
src/main/webapp/WEB-INF directory. The property
studio.previewUrlPrefix contains the path to the preview controller up to, but
not including the preview suffix.
If a different prefix is required for the final deployment, you have to add the
studio.properties file to the deploy workspace in the WEB-INF
directory and make the appropriate changes.
The property studio.previewControllerPattern contains the configurable preview
controller pattern. If it is empty or not defined, then the Studio
web application 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 as the following:
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.
 |  |  |
 |