Install Menu Editor

In the following description, escenic-home refers to the server folder in which the Content Engine is installed.

Installing Menu Editor on the server involves the following steps:

Make sure there is a plug-in folder: If the folder escenic-home/plugins does not already exist on your server, create it. If for some reason you need to create the plug-in folder in some other location, edit the escenic-home/assemblytool/assemble.properties file and set the plugins property accordingly. For example:
```
plugins=escenic-home/my/plugin/folder
```
This folder will be referred to as plugin-home in the rest of this manual.
Unpack the Menu Editor distribution: Unpack the Menu Editor distribution file to plugin-home. This will result in the creation of a plugin-home/menu-editor folder.
Rebuild the Content Engine: Build the Escenic enterprise archive by entering the following commands:
```
cd escenic-home/assemblytool
ant ear
```
The assembly tool will then add the Menu Editor plug-in to the Content Engine's classpath, including default configuration files and any required web application components.
Deploy the Content Engine: Deploy the new EAR file. For general instructions on how to deploy the EAR file on different application servers, see the Escenic Content Engine Installation Guide.
Verify the plug-in installation: See Verify The Installation for details of how to verify plug-in installations.

If the application server does not support EAR-based deployment, then all the JAR files located in the plugin-home/menu-editor/lib folder must be added to the application server's classpath. All the WAR files that have been rebuilt with the assembly tool should be redeployed.