loading table of contents...

3.5.3.2. Starting the Editorial Components

Starting the Preview CAE

Next, you can start the preview CAE. That is the CAE which will be used by the editors for checking their written content. 

$ cd $CM_BLUEPRINT_HOME/modules/cae/cae-preview-webapp
$ mvn tomcat7:run -Pdevelopment-ports

When the web application is up and running browse to http://preview-corporate.localhost:40081/ to see the Blueprint demo web application. If the URL cannot be resolved, you have probably not added the fake domains to your /etc/hosts file, see Section 3.3.4, “Configuring Vagrant Based Setup” for the list of required host mappings. If the page looks broken, your browser is possibly configured too restrictive with an anti-scripting plugin. Trust CoreMedia, and grant the Blueprint web application all required permissions. You should be able to click through the whole web application, register yourself, login to rate and comment on various content.

In a production deployment the Preview CAE and Studio run in the same Tomcat instance and thus have the same AJP and HTTP ports. If you use the tomcat7 Maven plugin however, each web application runs in a separate Tomcat instance, so you would encounter a port clash between the Preview CAE and Studio. The development-ports profile overrides the ports for the preview CAE and prevents a port clash.

Starting CoreMedia User Changes Web Application

After the Content Management Server is running, you can start the User Changes web application.

Start CoreMedia User Changes web application with the Tomcat plugin: 

$ cd $CM_BLUEPRINT_HOME/modules/server/user-changes-webapp
$ mvn tomcat7:run

When Tomcat is running, look into user-changes-webapp/target/logs/user-changes.log. If the logfile shows no errors and it contains 

Initializing user-change-listener
Attach user-change-listener to content repository with timestamp

the User Changes web application is running.

Starting CoreMedia Studio

Now, the Content Management Server, the Workflow Server and the Preview CAE are running.

If you skipped the Master Live Server before, you should start it now, because the next application to start is CoreMedia Studio, and without the Master Live Server you would not be able to publish content.

Start CoreMedia Studio with the Tomcat plugin: 

$ cd $CM_BLUEPRINT_HOME/modules/studio/studio-webapp
$ mvn tomcat7:run -Pdevelopment-ports

After the Tomcat server started up, you can browse to http://localhost:40080/ to open CoreMedia Studio. Login as user "admin" with password "admin".

Starting the WebDAV Server

The WebDAV Server is an optional web application for editing content via the WebDAV protocol. You can start it using the Tomcat plugin as follows: 

$ cd $CM_BLUEPRINT_HOME/modules/editor-components/webdav-webapp
$ mvn tomcat7:run-war

WebDAV clients can now connect to https://localhost:8086/webdav. Open the URL with your browser, login as admin/admin, and you can browse through the repository and find some documents, especially pictures. With Microsoft Windows 7 enter the following command to create a network drive that is connected to the WebDAV Server: 

$ net use * https://localhost:8086/webdav/ * /user:admin /persistent:no
Starting the Site Manager

For user management and special content editing tasks which are not yet covered by CoreMedia Studio you can use the Site Manager (formerly known as CoreMedia Editor).

[Note]Note

Note, that the Site Manager is only supported with a 32bit Java. You can set the used Java in the bin/pre-config.jpif file with the JAVA_HOME property. By default, it is set to your local JAVA_HOME environment variable. 

$ cd $CM_BLUEPRINT_HOME/modules/editor-components/editor/target/editor
$ bin/cm editor
Prev Up Next
 Home