Hippo CMS and DX 11 System Requirements

This document describes the generic system requirements for Hippo CMS and Hippo DX 11 to provide a guideline for infrastructure decisions. Hippo requires customers to consult the Hippo Quality Assurance Team for final sign-off if the installation is not based on the preferred system prerequisites to ensure that the individual combination of software versions employed is both eligible for Hippo Support and also facilitates best possible performance and stability.

In all cases, Hippo only supports system components that are actively and regularly supported by the respective vendors to support optimal business continuity.

Hardware Recommendations

Hippo recommends a minimum of two cluster nodes in any production environment for Backend and Frontend Servers as depicted in the graphic below. Hippo does not differentiate hardware recommendations between Backend or Frontend Servers.

Hippo products utilize a shared Database Server, therefore Hippo advises to consult your DBA as hardware recommendations are largely depending on which Database Server is in place.

Furthermore, disk space requirements are directly related to content stored in Hippo CMS and DX and the capacity needed for frontend servers is depending on the complexity of the website implementation and generated traffic.

For further information on the Hippo architecture as well as horizontal scaling to accommodate high-load environments, please refer to the Hippo Technical Whitepaper and “High Performance Content Delivery” which can be downloaded from our website onehippo.com. A sizing and dimensioning guide for On Premise installations can be provided by your account manager.

The Hippo DX Relevance module requires additional nodes for Elasticsearch. Hippo advises to run a clustered Elasticsearch setup.

Hippo Server Software Prerequisites

Hippo CMS Community edition stack

Hippo DX stack

Hippo DX (previously known as the Hippo Enterprise Edition) supports several different stacks, i.e. combinations of operating system, database and application server. Hippo has a preferred stack as mentioned below. In case your environment differs from the preferred stack look at options mentioned in the DX stack options. Please contact Hippo Sales for final sign-off to ensure that the individual combination of software versions employed is both eligible for Hippo support and also facilitates best possible performance and stability.

Hippo DX stack options

Hippo Client Software Prerequisites

The Hippo CMS and Hippo DX User Interface is fully web based and requires no prerequisites to be installed. As such, Hippo is expected to run in any standard browser environment. Hippo cannot guarantee browser plug-ins, tools or any kind of modifications to the browser to work with Hippo CMS or Hippo DX.