Hippo

Technical Specifications

Hippo CMS server is completely platform-independent (100% Java and XML). We have extensive experience with Windows 2000, Linux (RedHat, Suse) and Unix (HP‑UX).

The editing environment runs under Windows by default, but a Linux / Apple version is also available.

Hippo CMS server works well with Apache HTTPD, Microsoft IIS, SQUID, or standalone (without a web server) and supports the following application servers:

  • Tomcat
  • IBM Websphere
  • BEA Weblogic

The relational/XML-enabled databases supported by Hippo CMS, are:

  • X-Hive
  • Tamino
  • MS SQL
  • MySQL
  • ORACLE
  • PostgreSQL
  • standard ODBC or JDBC databases

An important component of Hippo CMS is a publishing infrastructure called Apache Cocoon 2.

There are various ways in which the XML content stored in the CMS can be used as a source for other systems: via a web interface (over HTTP or SOAP); via a database connection; using XML documents on the file system. Hippo CMS makes (automatic) integration of external XML content possible. This is done with Apache Cocoon, which is one of the basic components of the system. Cocoon is a publishing system that enables the user to split the development of a project up into three different layers: content, design and layout. Cocoon makes XML documents on the web available in different formats by applying 'on the fly' XSL stylesheets. The administrator can indicate which XML documents are available by linking them to URLs; for each URL, he can state which XSLT stylesheets are to be applied. This makes Hippo CMS the ideal content management system for distributing content to each of the available output formats (e.g. HTML, XML, SVG, Rich Text Format, WML, XML Forms and PDF).

Hardware requirements for Hippo CMS

The minimum hardware/server specifications are: single Pentium III 800MHz, 512MB RAM, 256MB hard disk space. We recommend a dual Pentium IV 1.4GHz with at least 1GB hard disk space.