Download binary distribution

• Download the latest build from [http://repository.hippocms.org/hippo-repository/v1.2.x/]
• Unzip the build into a folder on your harddisk, for example ~/hippo/hippo-repository-1.2.x
• Open a console (if you haven't already done)
• Type* cd ~/hippo/hippo-repository-1.2.x/bin (where 1.2.x is the version you downloaded)

The followinig step is only necessary if you are using linux.

• chmod u+x fortress.sh wrapper.bin libwrapper.so (give execute permissions)

• ./fortress.sh start (to start)
• ./fortress.sh stop (to stop)
• Open a webbrowser and navigate to [http://localhost:60000/default]
• You should get a popup asking for a username and password
• Enter the username "root" and password "password"
• Congratulations, your Hippo Repository is running!

Download and build from source

Download the source from SVN

See: Getting the Code

Build properties

For each deployment the repository needs to be rebuild. To tune the build to a certain environment create 'build.properties' files in 'slide' and 'openjms'.

OpenJMS settings

The settings for OpenJMS are very important. Somehow (probably because of IPv4 and IPv6 interactions) localhost does not resolve correctly under Linux:

• openjms.server.host should be set to the IP-address of the host.
• openjms.server.internhalhost should be set to localhost.

Slide settings

The main options in the Slide settings are the locations of the configuration files of Jetty and Slide. The configuration files for Jetty can be specified using the following properties:

• maven.jetty.useconfigpath must be set to true for maven.jetty.configpath to be used.
• maven.jetty.configpath is a path to a directory relative to the Fortress home directory.

The location of the Slide configuration can be set with the following property. If you specify an alternative location for the slide configuration make sure all paths in the configuration files are absolute. Relative paths will use Fortress home instead of the directory containing domain.xml as the base directory:

• repository.config.location is an absolute path, or a path relative to Fortress home to domain.xml. Please note that you cannot start with the parent directory symbol (..) in a relative path. If you have to use a directory above Fortress home specify an absolute directory.

Building

Run maven from the root of the hippo-repository project, with one of the following targets:

• Local development: maven build (default)
• Distribution: maven dist
• As a WAR file for deployment in application container: maven war

If you get a 'Provider org.apache.xalan.processor.TransformerFactoryImpl not found' error message you have place xalan-2.6.0.jar in the $MAVEN_HOME/lib/endorsed directory. Due to a Maven limitation (see MAVEN-156) the class name of the XSLT transformer factory has been hardcoded in the plugin. This solution works well with JDK 1.4, but fails with Java 5 that uses a different XSLT transformer.

Starting

• Start the repository with ./target/hippo-repository/bin/fortress.sh start
• Open a webbrowser and navigate to [http://localhost:60000/default]
• You should get a popup asking for a username and password
• Enter the username "root" and password "password"
• Congratulations, your Hippo Repository is running!

Building the repository as a WAR.

Because the deployment structure and selected components for deployment using WARs in application containers is different than for deployments using Jetty, a template with default configuration files and some skeleton directories is used. Instead of the configuration files in server/src/fortress/config the files from war-template/WEB-INF are used. The entire template directory is configurable by overriding maven.war.src in your build properties file and defaults to the directory war-template.

Deployment on Tomcat 5.5

Tomcat is a minimal application container, which does not include a number of essential services normally present in an application container, nor does it fully comply with the servlet specification. One of the missing required components is a JMS service. To add a JMS service you can add a JMS provider such as ActiveMQ to Tomcat (see http://activemq.apache.org/tomcat.html). An faster alternative, though servlet specification breaking one, is to enable the use of the embedded OpenJMS provider used in Jetty deployments. This is done using the following steps:

• from the top-level maven.xml file in the source tree, delete the line: <include name="geronimo-spec-jms-*.jar"/>;
• uncomment the openjms section in war-template/WEB-INF/components.xconf;
• create the directories war-template/WEB-INF/work and war-template/WEB-INF/work/openjms;
• and rebuild the WAR version of the repository.

Deploy the repository using the default Tomcat method, or just simply delete the contents of the webapps/ROOT directory, extract the WAR file into that directory and restart Tomcat.