====== Deployment in STAGE ======

  * Place the built tar.gz file (which can be found in the bee-workflowmanager/target directory after successfully building the project) into the bee home. E.g.: 
<code>/home/openbis/stage/bee/bee-1.0-SNAPSHOT-r266.tar.gz</code>

  * Extract the file. E.g.:
<code>
# ~/stage/bee> tar -zxvf bee-1.0-SNAPSHOT-r266.tar.gz
</code>

  * Copy the config files and the svn directory from the previous release into the ''etc'' folder:
<code>
# ~/stage/bee> cp bee-0.1.1/etc/* bee-0.2.0/etc/
# ~/stage/bee> cp -pr bee-0.1.1/etc/.svn bee-0.2.0/etc/
</code>
No need to do an SVN checkout / update

  * Do an svn status, and check what is there:
<code>
# ~/stage/bee/bee-0.2.0/etc> svn status
</code>
  * Remove unneeded skeleton files from the ''etc'' folder.

  * Commit new config changes

  * Point the ''current'' symlink to the new created directory. E.g.: 
<code>
# ~/stage/bee> rm current
# ~/stage/bee> ln -s bee-1.0-SNAPSHOT-r266 current
</code>

  * Start the daemon:
<code>
# ~/stage/bee/current> java -Dforce-accept-ssl-certificate=true -jar bee.jar 
</code>