CoreMedia Digital Experience Platform 8 Developer Manual, Version 7.5.45-10
3.5.3. Locally Starting the Components | 3.5.3.1. Starting Management Components

Starting the Search Engine

The Content Management Server needs the Search Engine to index all documents for full text search within CoreMedia Studio.

$ cd $CM_BLUEPRINT_HOME/modules/search/solr-webapp
$ mvn tomcat7:run-war

When you read the message that Tomcat server is up and running, simply test the Search Engine by browsing to its administration page at http://localhost:44080/solr. If you can see the administration page, everything is fine.

Starting the Content Servers

Now you start the Content Management Server, the backbone of a CoreMedia CMS.

$ cd $CM_BLUEPRINT_HOME/modules/server/content-management-server-webapp
$ mvn tomcat7:run-war

When you read the message that Tomcat server is up and running, check the IOR URL at http://localhost:41080/coremedia/ior. When you get an IOR like the following,

IOR:000000000000003849444c3a686f782f636f72656d2f636f7262612f4c6f676
96e536572766963655769746850726f746f636f6c56657273696f6e3a312e3000
000000010000000000000082000102000000000a3132372e302e302e3100be2b00
000031afabcb00000000207ba1b4de00000001000000000000000100000008526f
6f74504f4100000000080000000300000000140000000000000200000001000000
200000000000010001000000020501000100010020000101090000000100010100
00000026000000020002

the Content Management Server is running.

	Note
	If the Content Management Server fails to start up, you probably did not provide a valid license or you haven't configured it yet. See the section called “Configuring the licenses” and apply the necessary configuration.

You can start the Master Live Server the same way and check its IOR at port 42080. (However, this is no prerequisite for the Preview CAE, and you can also do it later.)

$ cd $CM_BLUEPRINT_HOME/modules/server/master-live-server-webapp
$ mvn tomcat7:run-war

Importing the Blueprint contents

In order to be able to explore the Blueprint features, CoreMedia provides sample content, which you can import into the Content Management Server. During the build of the workspace the sample content and the users of all activated extensions are collected into one Zip file. Take the file boxes/target/shared/content/content-users.zip and unzip it into a folder. Now, import the content with the following command, replace $PATH_TO_CONTENT with the path to the unzipped content <PathToUnzippedFile>/content:

$ cd $CM_BLUEPRINT_HOME/modules/cmd-tools/cms-tools-application/target/cms-tools
$ ./bin/cm serverimport -u admin -p admin -r $PATH_TO_CONTENT

or, when you are using a 64-bit Windows

$ ./bin/cm64 serverimport -u admin -p admin -r $PATH_TO_CONTENT

This will import all the XML files you can find under the content folder.

Importing the Blueprint users

CoreMedia provides users for the demo content, which you can import to the Content Management Server. The users are also part of the Zip file content-users.zip for the demo content. You might find several XML files for several extensions. Replace $PATH_TO_CONTENT with the path to the demo user file, that is <PathToUnzippedFile>/users/<filename>.xml:

$ cd $CM_BLUEPRINT_HOME/modules/cmd-tools/cms-tools-application/target/cms-tools
$ ./bin/cm restoreusers -u admin -p admin -f $PATH_TO_USERS

or, when you are using a 64-bit Windows

$ ./bin/cm64 restoreusers -u admin -p admin -f $PATH_TO_USERS

This will import all the users defined in the XML file. Import the other user files in the users folder similarly.

Starting the Content Feeder

Now that the Content Management Server and the Search Engine are up and running, you can start the Content Feeder.

$ cd $CM_BLUEPRINT_HOME/modules/search/content-feeder-webapp
$ mvn tomcat7:run

Afterwards you can check the Content Feeder's administration page at http://localhost:39080/feeder/admin. The Content Feeder feeds content (documents) to the Search Engine and will immediately start feeding. To check it, browse to the Solr administration page at http://localhost:44080/solr and search for id:coremedia*. This query searches for all index entries whose id starts with coremedia. If Solr finds some, the Content Feeder works properly.

Starting the Preview CAE Feeder

Like the Content Feeder the CAE Feeder depends on the Content Management Server and the Search Engine to be running. The CAE Feeder feeds content beans to the Search Engine.

$ cd $CM_BLUEPRINT_HOME/modules/search/caefeeder-preview-webapp
$ mvn tomcat7:run

Afterwards take a look into the CAE Feeder's logfile at caefeeder-preview-webapp/target/logs/caefeeder.log. The CAE Feeder should start feeding all the content beans based upon the content you have just imported into the Content Management Server. To check it, browse to the Solr administration page at http://localhost:44080/solr and search for id:contentbean*. This query searches for all index entries whose id starts with contentbean. If Solr finds some, the CAE Feeder works properly

Starting the Workflow Server

The next component to start is the Workflow Server.

$ cd $CM_BLUEPRINT_HOME/modules/server/workflow-server-webapp
$ mvn tomcat7:run-war

When Tomcat is running, look into workflow-server-webapp/target/logs/workflow.log. If the logfile shows no errors and ends with

Server - Server: started (Workflow Server Starter)

the Workflow Server is running.