Before deploying your own Hippo Portal with CMS integration, some external component applications have to be ready. As seen below, a Hippo Portal comprises of a repository, a CMS and a portal, interacting with the WebDav protocol (which is an extension to HTTP).

A Hippo Repository should be installed. It is designed to contain contents to show in the portal, like a site menu structure and the textual contents of portlets. To obtain a Hippo Repository, follow these instructions:
wrapper -c wrapper.conf
Note: the Hippo Repository uses a database to store the documents in. By default, this is a file based system but for a stable production environment, an RDBMS is preferred.
With Hippo CMS the content of repository documents can be managed, and therefore also the contents of a portlet. Installation instructions:
wrapper -c wrapper.conf
An application server is needed to run your portal on. Tomcat 5.5 is frequently used: you can download the "Core" binary distribution from tomcat.apache.org .
Note: because of a bug in the JAAS security Tomcat 5.5.25 cannot be used but newer
versions should have this fixed again.
Until then, best use Tomcat 5.5.23 which can be downloaded directly from
here
.
Add the following jar files to the <tomcat>/common/endorsed directory:
The first three jars can be downloaded directly using the links provided or from within
this zip file
at Apache
The database jdbc driver can be downloaded from mysql here
.
Choose the version that best matches your database installation (see below).
This documentation assumes a MySQL database to hold the portal data. Of course other databases like PostgreSQL, Oracle, DB2 etc. can be used too.
MySQL can freely be downloaded from mysql.com . Follow the installation instructions from mysql.
A named Hippo portal database should be created manually. For example, for the getting started track , enter the following on the command line (fill in your user/password information):
mysql -u<user> -p<password>
mysql> create database helloWorldPortal;