Silk

Deployment
The deployed Silk tool is the latest stable version 2.5.3 (from March 6, 2012), directly downloaded from. Documentation for the tool can be found on the developer’s wiki at.

The software was deployed on a Tomcat 7 web container configured to run with the options JAVA_OPTS="-Djava.awt.headless=true -Xms2048m -Xmx8192m -XX:PermSize=1024m -XX:MaxPermSize=1024m" , that is, a maximum use of 8GB of RAM. Depending on the use of the machine, the maximum amount of allocated RAM can still be raised lateron, seeing the total of 16GB installed.

Deploying the latest release as is resulted in two drawbacks. Firstly, the working directory is called .silk (and thus hidden on Unix/Linux systems) and situated in the home directory of the user which in this case is the user that also runs the server. Subsequently, the working directory is situated at /usr/share/tomcat7/.silk. Secondly, the integration into the DM2E’s Single Sign On cannot be completed without changes being made to the software itself. As Silk has no user management, a mechanism for logging in is not implemented, but would be necessary for that. However, the Silk service is integrated into the Single Sign On with the exception that there is no possibility of logging out of the system while visiting Silk.