Hippo CMS and BloomReach Experience 12 System Requirements

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

In all cases, BloomReach only supports system components that are actively and regularly supported by the respective vendors.

Hardware Recommendations

BloomReach recommends a minimum of two cluster nodes in any production environment for backend and frontend servers as depicted in the graphic below. BloomReach does not differentiate hardware recommendations between backend or frontend servers.

//onehippo-prod.global.ssl.fastly.net/binaries/ninecolumn/content/gallery/connect/library/deployment/sys-reqs-hardware.png

BloomReach Experience products utilize a shared database server, therefore BloomReach 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 BloomReach Experience and Hippo CMS and the capacity needed for frontend servers is depending on the complexity of the website implementation and generated traffic.

Server – per cluster node

Minimum

Recommended

Processor

4 cores

4 cores

RAM

4 GB

8 GB

Disk Space

25 GB

25 GB

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

The BloomReach Experience Relevance module requires additional nodes for Elasticsearch. BloomReach advises to run a clustered Elasticsearch setup.

Server Software Prerequisites

Hippo CMS stack

Preferred Community edition Stack

JVM

Oracle JVM 8

Operating System

Ubuntu Server 16.04

Application Server

Tomcat 8.5

Database Servers

MySQL 5.6

BloomReach Experience stack

BloomReach Experience supports several different stacks, i.e. combinations of operating system, database, and application server. BloomReach Experience has a preferred stack as mentioned below. To provide flexibility we do of course offer additional ‘’stack options’’ (listed below) if your environment differs from the preferred stack. Please contact BloomReach sales for final sign-off to ensure that the individual combination of software versions employed is both eligible for BloomReach support and also facilitates best possible performance/stability.

Preferred BloomReach Experience stack

JVM

Oracle JVM 8

Operating System

Ubuntu Server 16.04 (preferred)

Application Server

Tomcat 8.5

Database Servers

MySQL 5.6 or Oracle 12

Relevance module requirement

Elasticsearch 5.5

BloomReach Experience stack options

JVMs

Oracle JVM 8

Operating Systems1

Ubuntu Server 14.04, 16.04

RedHat Enterprise Linux (RHEL) 6, 7.3, or corresponding CentOS versions

Debian Wheezy (7) and Jessie (8)

Windows Server 2008 R22, 2012, 2012 R2

Application Servers

Tomcat 8.0, 8.5 (preferred)

CMS Database Servers

MySQL 5.6

Amazon RDS (using MySQL 5.6 or Oracle RDS 12c)

Oracle 12

MS SQL Server 2016

PostgreSQL 9 (Please also note the relevance module requirements)

Proxy servers

Apache HTTP Server 2.4

Relevance Module: additional software requirements

Elasticsearch 5.5

Additional database:

MySQL 5.6

Amazon RDS (using MySQL 5.6 or Oracle RDS 12c)

Oracle 12

PostgreSQL 9.5

LDAP Directories

OpenLDAP

Microsoft Active Directory

ApacheDS

Client Software Prerequisites

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

Operating Systems3

Microsoft Windows 8.1 and 10

Apple Mac OS X 10.1/10.12 and higher

Ubuntu 14.4 and higher

Browsers4

Google Chrome: latest stable version supported

Mozilla Firefox: latest stable version supported

Apple Safari: latest stable version supported (Mac OS X only)

Edge latest stable version supported (on W10 and higher)

Various

The system requires cookies to be activated for the domain it runs in.

Browser support for the website is determined by the website implementation.

The CMS will look best when used with a screen resolution of 1280 x 720 or higher.

__________________________

1 Running the 64 bit version of the OS, on x64 bit Intel (or compatible) processor.

2 Please note that from the next minor release (V12.1) support on Windows Server 2008 R2 will end.

3 Note: whilst a number of BloomReach customers run the CMS User Interface through Citrix solutions, BloomReach does not support Citrix environments via the regular support agreement. Customers looking to employ Citrix are advised to bring this to the attention of BloomReach support or their respective account managers for further investigation.

4 Note: In case of a Beta release, only Chrome (latest version) is supported. For GA and succeeding release, the other browsers mentioned are supported as well.