{info:title=Useful Information}
This setup instruction is mainly based on Windows (Vista) & Apache Tomcat (version 6.0.18).
You will find the complete "Installation & Deployment Guide" attatched to this page.
{info}

h2. Installation of Java

# You need a current installation of a Java Runtime Environment (JRE) on your machine; I used version 1.6.0_07-b06, which works well. You can get the Java binary from http://java.sun.com/javase.
# Your setup is successful, when you can afterwards open a commandline (-->start menu --> execute or search for "cmd.exe" ), issue a "java -version" command and see an output similar to the following:


h2. Installation of Apache Tomcat

# Download the current Apache Tomcat binary from http://tomcat.apache.org/download-60.cgi.
# The best option on the Windows Platform is the Windows Service Installer. Download it and execute the installer.
# You can follow the recommended install parameters: the only exception is the installation path: Tomcat recommends (along with MS-Windows settings) to be installed in c:\Program Files\Apache\... As this path includes spaces, some Java programs and configuration files have trouble starting files with path information (with spaces included): it is more safe (and better to keep the overview) to use an own folder high in the drive hierarchy without spaces. (e.g. take something like d:\tomcat_60)
# Tomcat recommends the port 8080 for development needs: however if port 80 is not used otherwise, you will have less trouble (e.g. related to firewall issues), when you use port 80 for your deployment.(Another reason for port 80 is that browsers by default use port 80, for any other port setting the user needs to be aware of the fact, as he/she has to include this in the URL.)
# Your setup is successful, when you can reach afterwards the following page:

{note:title=Be Careful}For all further examples I assume Tomcat to be installed in d:\tomcat_60.{note}

h2. Deployment of the ESME Application

* You can either build the current version directly from the source code repository (SVN)or setup the application from existing (but outdated) binary packages.

* Steps to deploy the current SVN version
*# Make sure, that you have a working installation of the Apache Maven tool (at [http://maven.apache.org/]). You can test this by issuing a "mvn --version" command on a command line.
*# Get the source of the ESME application with any subv ersion (SVN)-compatilbe client: [Wikipedia|http://en.wikipedia.org/wiki/Comparison_of_Subversion_clients] has a list with many clients and their features.
*# Issue a "svn checkout http://svn.apache.org/repos/asf/incubator/esme" command (preferably in an own directory).
*# Issue a "mvn install" in the directory, where you stored the SVN files. This creates a esme*.war file (most likely in the "target"-subdirectory).

* Steps to implement the precompiled binary packages 
*# Download the binary files from Google code page (at [http://code.google.com/p/esmeproject/downloads/list]).
*# You will see the following list:
*For hosting an ESME pilot or for the testing, the last three files are needed: Download them with a right mouse click to a temporary folder on your computer.
*# For deployment you need to the contents of the WAR-file and the two jar-files to the right locations. For this to work, you have to stop the Apache Tomcat service via the service console.
*# Create a directory called esme under d:\tomcat_60\webapps.(I recommend not to take over the naming of the WAR file - with the complete date, as this requires the later user to remember also the ESME build date)-
*# Extract the content of the WAR file to d:\tomcat_60\webapps\esme.
*# Now take the the two other Jar-files from your download (lift*.jar and scala*.jar) and put them to d:\tomcat_60\webapps\esme\WEB-INF\lib.

# You are now ready to start the tomcat server (via the service console) and to see your application running.
# Open your browser, and enter the following link: http://localhost:8080/esme.

Your setup was successful, when you can see a similar screen:
From now on you can enter the ESME world and try out everything.

h2. Further options for ESME deployment
As I also need to figure out further options for deployment, I just list my ideas here (knowing that these partly need further descriptions).
* Enabling HTTPS-Encryption on Tomcat (--> http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html) Even some intranets require this nowadays.