Dashboard > AutoFocus Server 4.0 documentation > ... > Administration Manual > 01. Installation
Added by Herko ter Horst , last edited by Alex Alishevskikh on 2008-07-14  (view change)
Labels: 
(None)

This document explains how to perform a basic installation of AutoFocus Server.

Prerequisites

Hardware requirements

We recommend a Pentium 4 class CPU, 512 MB of main memory and 1 GB of free disk space as the minimum specifications to run AutoFocus Server. For larger deployments, main memory is the most important asset for increased scale. 64-bit hardware (and software) is required for deployments that need more than 4 GB of memory (or 2 GB on some operating systems).

Software requirements

AutoFocus Server is written in Java, a platform-neutral language. This means it can be deployed unchanged on Windows, Linux and Mac OS platforms, or indeed any platform for which a suitable Java VM is available (see below).

AutoFocus Server consists of two standards-compliant Java web applications (WAR files). This means the software can be deployed on any Java-compatible platform that meets the following specifications:

  • Java Standard Edition 5 or higher.
    We recommend Sun JDK 5 (1.5.0_14). A free copy can be downloaded from Sun's Java SE download page.
  • Java Enterprise Edition application server that supports the Servlet 2.4 and JSP 2.0 standards.
    We recommend Apache Tomcat 5.5.26. A free copy can be downloaded from the Apache Tomcat download page.

AutoFocus Server performs best when it has access to a large amount of main memory. Therefor, make sure to allocate an ample amount of heap space to the Application Server for AutoFocus Server. We recommend no less than 256 MB for small scale deployments. Large scale deployments may need several gigabytes of memory. In that case, 64-bit hardware and software (including a 64 bit version of Java) is required.

Installing AutoFocus Server

The AutoFocus Server distribution contains two WAR files (autofocus.war and autofocus-metadata.war). These contain standard Java web applications that can be deployed on any compatible Application Server. Please consult your application server's manual to learn how to deploy web applications on that particular server.

Installing AutoFocus Server on Apache Tomcat

When using Apache Tomcat in its default configuration, it is sufficient to place the two war files in Tomcat's webapps directory.

Upgrading from previous versions

Before upgrading, remove old AutoFocus Server WAR files as well as autofocus and autofocus-metadata directories from Application Server deployment directory (webapps in the case of Tomcat).

AutoFocus Server 4.0 does not provide backward data compatibility with older versions. It is recommended to remove existing autofocus-server and autofocus-metadata data directories before installation. The actual path to these directories depends on your platform:

  • Windows Vista
    C:\Users\<USERNAME>\AppData\Roaming\Aduna
  • Windows 2000, 2003, XP
    C:\Documents and Settings\<USERNAME>\Application Data\Aduna
  • Mac OS
    /Users/<USERNAME>/.aduna
  • Linux
    /home/<USERNAME>/.aduna

Basic authorization

The administration interface of AutoFocus Server is pre-configured to allow access to anyone in the autofocus-admin role. To make use of AutoFocus Server, at least one user needs to be setup in your Application Server configuration. Once again, please refer to the documentation for your Application Server to learn how to setup users and assign roles to them.

User configuration on Apache Tomcat

When using Apache Tomcat in its default configuration, add the following line to the tomcat-users.xml found in Tomcat's conf directory:

<user username="admin" password="secret" roles="autofocus-admin"/>
Obviously, change the password to something more secure. Alternatively, add the role autofocus-admin to the (comma-separated) list of roles of a user already configured in the tomcat-users.xml file.

You will need to restart Tomcat for these changes to take effect.

Please note that AutoFocus Server uses HTTP Basic authentication by default, in which the username and password are transmitted in plain text. For secure operation, only use Basic authentication over an encrypted channel, i.e. HTTPS.

Powered by a free Atlassian Confluence Open Source Project License granted to Aduna Open Source. Evaluate Confluence today.
Powered by Atlassian Confluence 2.7, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators