Tissue Stack Installation

ATTENTION: This information is deprecated!

So far Tisssue Stack had to be installed by compiling its source code and configuration by hand.

Given that it consists of various parts written in C, Java and Java Script as well as its dependencies on an application server, web server and configuration database this task turns out to be more difficult than desired.

The steps to do so are detailed in README files in the individual component's respective folder.

HOWEVER, there is now a binary install which will facilitate the above described procedure considerably although a few manual steps are still required to achieve a successful installation.

Therefore, anybody who wants to merely install and use Tissue Stack, can do so by downloading the appropriate binary packages which can be found here:


There is an INSTALL text file which will guide you through the process.

Basically Tissue Stack was bundled into 2 parts:

(1) Image Server (C code) => made available as a 64 bit Debian package
(2) Tissue Stack Web and Configuration Services => downloadable as a *.tar.gz

Technically, either one can be installed without the other although this will result in limited functionality for (2). Essentially only manually pre-tiled and configured data sets can be displayed by (2) so it is recommended that you install both to take full advantage of the functionality available.

Part (2) is a fairly large file (~100MB), a consequence of achieving ease of installation at the cost of a larger download. The archive contains a java runtime and tomcat installation as well as the compiled Tissue Stack Web Application itself. These would have to be installed individually otherwise and the resulting downloads would actually result in a bigger download altogether since build tools would have to be installed as well (maven)

Potential Problems:
A) You do need super user privileges for some parts of the installation, e.g. debian package and postgresql database
B) Firewalls can prevent the installed system from working if they block ports 80 (apache), 5432 (postgresql) or 8080 (tomcat). Make sure you allow at least local access to the latter two, that's sufficient if access is proxied via the apache.
C) Configuration of the Apache Web Server: Make sure you have modules headers, proxy and proxy_http installed as well as the rules listed in the example configuration file that accompanies the installation archive.

No comments:

Post a Comment