Re-assembling Applications

After installation, you may need to reassemble your web applications. You need you reassemble in the following cases:

  • You installed the Menu Editor plugin-in using the old-style installation method.

  • You installed the Menu Editor plugin-in using the package-based installation method and your installation includes any old-style JSP-based Escenic publications.

If you installed the Menu Editor plugin-in using the package-based installation method and all your publications are based on DPRES, the new decoupled presentation layer then you do not need to reassemble any applications.

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

  2. 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.

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

    On each engine-host, 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 escenic@assembly-host-ip-address:/var/cache/escenic/engine.ear /tmp/

    where assembly-host-ip-address is the host name or IP address of your assembly-host.

  4. On each engine-host, deploy the EAR file and restart the Content Engine by entering:

    $ ece stop deploy start --file /tmp/engine.ear
    $ ece restart