This chapter contains step-by-step instructions for installing the Content Store on a single host computer or on a cluster of several host computers. The instructions use the host names listed in Identifying Host Machines to indicate where you should carry out various steps. If some of your hosts are "multi-purpose" (if for example, your database server is installed on the same host as your editorial Content Store installation), then carry out all appropriate steps on that machine (for example, all database-host steps and all editorial-host steps).
Some of the steps are not required for single-host deployment. These steps are clearly marked.
The following placeholders are used in paths specified in the instructions:
There are a number of preparatory tasks that you need to carry out, described in Preparation. The main installation procedure is described in Installation. Post-installation tasks (assembling and deploying an EAR file containing the supplied CUE web applications, checking that everything is installed correctly and so on) are described in Finishing Up.
The CUE Content Store and all related applications (plug-ins, the CUE editor, CUE Print, CUE Front and so on) are released on a synchronized schedule where all product versions in a given release are known to work well together. Only these approved version combinations are supported. Each set of compatible product versions is identified by a code name, and during installation you can use this code name instead of the individual product's version number, thereby simplifying the installation process.
In the case of the
and other Linux applications installed on Ubuntu using
apt, the code name is actually the name of a repository
containing compatible versions of all products. This means that in order
to ensure version compatibility, all you need to do is add the name of the
required repository to your
/etc/apt/sources.list.d/escenic.list file. Once you
have done this you do not need to specify any version numbers when
installing individual packages -
apt will just install
the latest maintenance release from that repository.
Note that code names cannot be used in this way on CentOS/Red Hat installations, where the application packages to be installed must still be identified by their version numbers.
The code name for