Mobile Studio Installation

Installing Mobile Studio involves the following steps:

Log in as escenic on your assembly-host.
Download the Mobile Studio 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/[l-engine-version]/mobile-studio-1.1.2.178688.zip          
```
Otherwise, download it to some temporary location of your choice.
If the folder /opt/escenic/engine/plugins does not already exist, create it:
```
$ mkdir /opt/escenic/engine/plugins
```
Unpack the Mobile Studio distribution file:
```
$ cd /opt/escenic/engine/plugins
$ unzip /mnt/download/mobile-studio-1.1.2.178688.zip          
```
This will result in the creation of an /opt/escenic/engine/plugins/mobile-studio folder.
Mobile Studio communicates with the Content Engine via a different web service from Content Studio, called mobile-webservice. You have to create this web service by copying the standard engine-webservice delivered with the Content Engine:
```
$ cd /opt/escenic/engine/webapps
$ cp engine-webservice.war mobile-webservice.war
```
The copied web service must be called mobile-webservice.war, or Mobile Studio will not work.
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.
If you have a single-host installation, then skip this step.

On each engine-host on which you wish to run the Mobile Studio 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 Mobile Studio plug-in on editorial hosts.
On each engine-host on which you wish to run the Mobile Studio 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 Mobile Studio plug-in on editorial hosts.