Assemble and Deploy

You may now need to assemble and deploy your web applications. You need to do this in the following cases:

You installed the Content Store using the old-style installation method.
You installed the Content Store using the package-based installation method and your installation includes one or more old-style JSP-based Escenic publications.

If you installed the Content Store 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 assemble and deploy.

Assembly and deployment consists of the following steps:

On your assembly-host, while logged in as escenic, run the ece script to assemble a set of Content Store applications:
```
$ ece assemble
```
This generates an enterprise archive (EAR file) which you can deploy on all your engine-hosts. The EAR file is called engine.ear, and is created in the /var/cache/escenic/ folder.
If you are installing everything on one host, 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 -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.
On each engine-host, deploy the EAR file by entering:
```
$ ece deploy
```