Serving Static Data Using Trifork Application Server

Trifork Application Server supplied with Fiona can not only be used for serving the Java Server Pages of the HTML user interface but also for static web pages. This means that the files exported by the Template Engine can be displayed without using a webserver. Proceed as follows to configure the Trifork server correspondingly:

First, create a new web application directory named Export:

cd instance/myInstance/webapps
mkdir Export
cd Export
mkdir WEB-INF
mkdir META-INF

In the WEB-INF directory create the file web.xml and place the following content into it:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"

Into the META-INF directory, place the file trifork-app-conf.xml containing the following:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE trifork-app-conf PUBLIC '-//Trifork Technologies//DTD
    Trifork Application Descriptor1.0//EN'
  <role-mapping />

Furthermore, place the file containing the following into the current directory NPS~/instance/default/webapps/Export:

<?xml version="1.0"?>
<jar name="NPSExport.war">
  <dir path="WEB-INF"
  <dir path="META-INF"
  <dir path=""
    from="/opt/Infopark/NPS/instance/default/export/online/docs" />

If you did not install Fiona into the /opt/Infopark/NPS directory, please adapt the paths in the file above.

Then execute the following command in a shell to make the files in the Export directory available as a web application (the following two lines are one command line, not two):

TriforkInstallDir/domains/default/bin/trifork archive deploy
  -uadministrator -padminPassword -inplace default

The default password of the Trifork administrator is trifork. After the command has been executed successfully, you can access your exported content using the following URL:


Instead of my.npsserver provide your CMS host name. If the page index.html can not be found, please make sure that the Template Engine has been integrated properly and that the user runnig the Trifork server has read access to the export directory of the Template Engine.