Cxense Semantic Installation

Installing Cxense Semantic involves the following steps:

  1. Log in as escenic on your assembly-host.

  2. Download the Cxense Semantic distribution from the Escenic Technet web site (http://technet.escenic.com). If you have a multi-host installation with shared folders as described in the Escenic Content Engine Installation Guide, then it is a good idea to download the distribution to your shared /mnt/download folder:

    $ cd /mnt/download
    $ wget http://user:password@technet.escenic.com/downloads/release/5.7.unstable-VF-5970.161071/cxense-semantic-1.4.2.166554.zip          

    Otherwise, download it to some temporary location of your choice.

  3. If the folder /opt/escenic/engine/plugins does not already exist, create it:

    $ mkdir /opt/escenic/engine/plugins
  4. Unpack the Cxense Semantic distribution file:

    $ cd /opt/escenic/engine/plugins
    $ unzip /mnt/download/cxense-semantic-1.4.2.166554.zip          

    This will result in the creation of an /opt/escenic/engine/plugins/cxense-semantic folder.

  5. Log in as escenic on your assembly-host.

  6. Run the ece script to re-assemble your Content Engine applications.

    $ ece assemble

    This generates an EAR file (/var/cache/escenic/engine.ear) that you can deploy on all your engine-hosts.

  7. If you have a single-host installation, then skip this step.

    On each engine-host on which you wish to run the Cxense Semantic plug-in, copy /var/cache/escenic/engine.ear from the assembly-host. If you have installed an SSH server on the assembly-host and SSH clients on your engine-hosts, then you can do this as follows:

    $ scp -r escenic@assembly-host-ip-address:/var/cache/escenic/engine.ear /var/cache/escenic/          

    where assembly-host-ip-address is the host name or IP address of your assembly-host. It only really makes sense to run the Cxense Semantic plug-in on editorial hosts.

  8. On each engine-host on which you wish to run the Cxense Semantic plug-in, deploy the EAR file and restart the Content Engine by entering:

    $ ece stop
    $ ece deploy
    $ ece start

    It only really makes sense to run the Cxense Semantic plug-in on editorial hosts.