Old-style Upgrade

You should only use this upgrade method if you have previously installed the Menu Editor plug-in as described in Old-style Installation. Otherwise you need to follow the method described in Package-based Upgrade.

To upgrade the Menu Editor plug-in to version 3.5.0-1:

Read the release notes for your planned upgrade. Make a note of any special tasks that need to be carried out in connection with the upgrades.
Log in as escenic on your assembly host.
Download the distribution file to a temporary location by entering:
```
$ cd /tmp/
$ wget http://user:password@maven.escenic.com/com/escenic/menu-editor/menu-editor/3.5.0-1/menu-editor-3.5.0-1.zip
```
where user and password are the user name and password you have received from Escenic.
Remove the old version of the Menu Editor plug-in from your Content Engine plugins folder.
```
$ mv /opt/escenic/engine/plugins/menu-editor/ /tmp/
```

Unpack the downloaded installation package into the plugins folder:

$ cd /opt/escenic/engine/plugins/
$ unzip /tmp/menu-editor-3.5.0-1.zip

Re-assemble the Content Engine by running the ece script:
```
$ ece assemble
```
If you are installing everything on one host, then skip this step.

Log in as escenic on each of your engine-hosts and 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:
```
$ ssh engine-host-ip-address
$ scp -r escenic@assembly-host-ip-address:/var/cache/escenic/engine.ear /var/cache/escenic/
```
where:

engine-host-ip-address

is the host name or IP address of one of your engine-hosts.

assembly-host-ip-address

is the host name or IP address of your assembly-host.
On each engine-host, deploy the EAR file by entering:
```
$ ece deploy
```
and then restart the Content Engine by entering:
```
$ ece restart
```
Carry out any required upgrade tasks.