CoreMedia Studio needs to know the URL of the Content Server to connect to and the URL of the preview server. To this end, adjust the repository.url property in WEB-INF/application.properties of the Studio web application and let it point to your Content Management Server.

repository.url=http://<Host>:<Port>/ior

Alternatively, you may configure the URL to connect to by modifying the contentserver.* properties in the same file.

contentserver.host=localhost
contentserver.port=44441

CoreMedia Studio also needs to know the URL of Apache Solr and the name of the index collection for searching the repository content. Configure the URL in the property solr.url and the name of the index collection in the property solr.content.collection in the same file.

solr.url=http://<Host>:<Port>/solr
solr.content.collection=studio

CoreMedia Studio needs an additional relational database connection to store editorial comments. The properties editorial.comments.datasource.url and editorial.comments.datasource.driver-class-name have to bet set according to the RDBMs to connect to. Furthermore, for each RDBMs there are differences in the configuration of the JDBC connection. For more details see Section 3.5, “Editorial Comments Database Configuration”.

CoreMedia Studio offers connectivity to the CoreMedia Workflow Server. Therefore, a Workflow Server has to run when starting CoreMedia Studio. If this is not desired, set the property repository.workflow in the file WEB-INF/application.properties to false.

repository.workflow=false

Studio supports "Simple Publication" and "Two Step Publication" publication workflows. To use these workflows, upload the workflow definitions studio-simple-publication.xml and studio-two-step-publication.xml to the Workflow Server with the cm upload tool. See section Section 5.6.1.2, “Predefined Publication Workflows” in Blueprint Developer Manual for more information on these workflows.