CoreMedia Digital Experience Platform 8 Developer Manual, Version 7.5.45-10
4.2.2. Deploying a System | 4.2.2.2. Deployment with Yum

This section covers the deployment process of the CoreMedia services using the rpm and yum utilities directly. It will not cover how to install and configure third-party RPM files such as MongoDB or MySQL.

Prerequisites

In order to proceed you need to make sure that you successfully meet the following prerequisites:

Creating a YUM repository

If you want to install the RPM files from a local RPM repository, make sure that you copied all RPM files to a directory and call createrepo on that path. If you are using a remote repository, you can skip this step.

Now you need to register a repository configuration in your /etc/yum.repos.d/. To do so create a file below that directory, for example /etc/yum.repos.d/cm8-repo, and add the following content.

[cm8]
name=CoreMedia 8 Repo
baseurl=file://PATH_TO_YOUR_REPO
gpgcheck=0
enable=1

If you are using a remote repository you need to specify the baseurl property accordingly.

Installing the RPMs

To install the RPMs, use the yum utility to install all selected packages at once, for example:

sudo yum install cm8-*
    

for all matching packages or specify a list of packages by calling

sudo yum install [PACKAGE_1] ... [PACKAGE_N]
    

Similar to the roles in Chef that group recipes such as packages to apply to your node, you can create groups within your YUM repository. This way, if there was a group bluepring-delivery, you could simply use

sudo yum groupinstall "blueprint-delivery"
    

to install a set of RPM files at once, without knowing the concrete packages included. To create groups use the yum-groups-manager utility.

After you have installed all RPM files and in case you are using the post-configuration approach, you need to adapt the default configuration defined in the property files below /etc/coremedia and reconfigure all services and tools. To skip this step you may provide the correct configuration files in advance. As a start you can use the default configuration files generated by the build and adapt them to your needs. You find these files below the boxes/target/shared/configuration-templates folder in your workspace.

To reconfigure the services and tools, you need to call sudo service [SERVICE NAME] reconfigure for each service and /opt/coremedia/[TOOL_NAME]/reconfigure-tool.sh for each tool.

Starting the Services

To start the services simply refer to the standard service utility. By default, all Tomcat based services created with the Blueprint workspace offer the following methods:

	Note
	The status method does not reflect the status of any of the contained web applications, it merely checks the presence of a process with a matching process id.

The order in which the services need to be started depends on many factors including customizations done in a project. Most CoreMedia applications can be started independently of each other but a safe order would look like the following:

To reload Apache, call service httpd restart