Installation

The following preconditions must be met before you can install Menu Editor 3.6.4-1:

  • A suitable version of the CUE Content Store and CUE assembly tool have been installed as described in the Escenic Content Engine Installation Guide and are in working order.

  • You have the credentials needed to access CCI Europe's SW repositories.

In a multi-host environment:

  • The Menu Editor plug-in must be installed on all hosts.

  • The CUE event mechanism must be working correctly.

Choosing an installation method

Until recently, all CUE-supplied components had to be installed by manually downloading and unpacking archive files. This is no longer the case. The Content Store itself, the assembly tool, the ece scripts and all plug-ins are now available as deb packages (for installing on Ubuntu/Debian systems) and as rpm packages (for installation on RedHat/CentOS systems). This is now the recommended method of installing CUE systems, although it is still possible to use the old method based on manually downloading and unpacking archives. Note, however, that when you are installing a plug-in on an existing Content Store installation, you should use the same installation method as you used for the Content Store itself.

Using the new package installation method offers many advantages over the old manual installation procedure:

  • It is faster and quicker

  • It is significantly less error-prone

  • It supports a fully automated upgrade process in which not only the installed packages themselves are upgraded, but also deployed EAR files. An upgrade script automatically checks the EAR files for copies of JAR files that have been updated, and replaces them with the new versions.

The old installation method will continue to be documented for the moment. Components installed using the new method are installed in /usr/share/escenic, whereas the old method recommends installation in /opt/escenic, and some other path components are slightly different. To cope with these differences, the following placeholders are used in some paths:

Placeholder NEW METHOD path OLD METHOD path

engine-installation

/usr/share/escenic/escenic-content-engine-engine-version

/opt/escenic/engine

assemblytool_installation

/usr/share/escenic/escenic-assemblytool

/opt/escenic/assemblytool

When installing the Menu Editor plug-in, you should use the same method as you used to install the CUE Content Store.

Note that if you are planning to install the CUE Content Store using the new package-based method, you can install the Menu Editor plug-in simultaneously by simply including the Menu Editor plug-in package name (escenic-menu-editor) in the apt-get installation command. You only need to follow this procedure if you have already installed the Content Store and now need to install the Menu Editor plug-in.

If you use CUE as your CUE editor, then in addition to installing the CUE Menu Editor plug-in, you must also activate CUE's Menu Editor plugin. For details, see CUE Plug-in Activation.