Unpack Content Engine Components

If you are installing everything on a single host or if you created a shared file system as described in Create Shared File System, then you should have direct access to the Content Engine packages you downloaded earlier (see Download Content Engine). If not, you will need to copy it to some temporary location on the assembly-host. The following instructions assume that you have downloaded the packages to the shared folder /mnt/download.

On your assembly-host, while logged in as root:

Create a folder for the Content Engine under /opt:

# mkdir /opt/escenic
# chown -R escenic:escenic /opt/escenic

Change user to escenic and unpack the Content Engine package as follows:

# su - escenic
$ cd /opt/escenic/
$ unzip /mnt/download/engine-5.3.10.154952.zip

Create a symbolic link from /opt/escenic/engine to the Content Engine folder, so that it will be easier to upgrade to new versions when necessary.
```
$ ln -s engine-5.3.10.154952 engine
```

Create a folder and symbolic link for the assembly tool, then unpack the assembly tool into the folder:

$ mkdir assemblytool-2.0.2
$ ln -s assemblytool-2.0.2 assemblytool
$ cd assemblytool/
$ jar xf /mnt/download/assemblytool-2.0.2.zip

Note that the jar command shown above is part of the JDK, and is located in the bin directory of the Java distribution. Some Linux distributions ship with a GNU jar command which has a different syntax and does not support all the same options. Make sure you use the JDK's jar command.