Bloomreach Experience Manager 14 and 15 System Requirements - Bloomreach Experience Manager (PaaS/Self-Hosted) - The Fast and Flexible Headless CMS
13-04-2022

Bloomreach Experience Manager 14 and 15 System Requirements

These system requirements apply to on-premise Bloomreach Experience Manager deployments.
When deploying in Bloomreach Cloud, assume the standard stack as described below. Contact Bloomreach Cloud support for details.

This document describes the generic system requirements for brXM and the developer edition 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 support and also facilitates best possible performance/stability. 

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

Server software prerequisites

Developer Edition stack

Developer Edition Stack

Java

Java 8 for brXM 14; Java 11 for brXM 151

Operating System

Ubuntu Server (by Canonical supported active LTS versions)

Application Server

Tomcat 8.5, 9.02

Database Servers

MySQL 5.7, 8

Docker3 Docker Engine 18.03 to 19.03

brXM stack

brXM supports several different stacks, i.e. combinations of operating system, database and application server. 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. In all cases, Bloomreach only supports system components that are actively and regularly supported by the respective third party vendors. Also note that support on third party products depends on the stack options you have licensed. 

brXM standard stack

Java

Java 8 for brXM 14; Java 11 for brXM 151

Operating System

Ubuntu Server (by Canonical supported LTS versions) (preferred)

RedHat Enterprise Linux (RHEL, supported LTS versions)

Application Server

Tomcat 8.5, 9.0

Database Servers

MySQL 5.7, 8 

Relevance module requirement

Elasticsearch 7.16.2

brXM extended stack options

JVMs

We support standard OpenJDK builds, including Oracle's official build, alternative builds such as AdoptOpenJDK, and builds shipped with Linux distributions such as Red Hat Enterprise. All with current CPU (Critical Patch Update) and Hotspot that is actively supported by its vendor.

Operating systems4

Ubuntu Server (by Canonical supported active LTS versions)  

CentOS versions corresponding to RedHat Enterprise Linux (RHEL, supported LTS versions)

Debian stable

Windows Server 2016

Application servers

Tomcat 8.5, 9

CMS database servers

MySQL 5.7, 8 

PostgreSQL 9.5/9.6, 10, 12.4

Oracle 12c or 19c (12c R2 or 19c is required when using Projects feature)

MS SQL Server 2016 (can not be used for relevance data, see Relevance Module requirements below)

Amazon RDS (using any DB type and version listed above)

Relevance Module: additional software requirements

Elasticsearch 6.0-6.8.22, 7.9, or 7.16.2; ES 8.1 is also supported with brXM 15.0.0 or higher

Additional database:

     MySQL 5.7, 8

     PostgreSQL 9.5/9.6, 10, 12.4

     Oracle 12c, 12c R2, or 19c

     Amazon RDS (using any DB type and version listed above)

Proxy servers

Apache HTTP Server 2.4

LDAP directories

OpenLDAP

Microsoft Active Directory

ApacheDS

Upcoming versions

We try to support newer versions of supported stack options as soon as possible. If the supported stack changes we'll update this page.

Client software prerequisites

The brXM 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 brXM. 

Operating systems5

Microsoft Windows 10

Apple Mac OS X 10.11/10.12/10.13/10.14 and higher

Actively supported (by Canonical) versions of Ubuntu

Browsers6,7

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 - based on Chromium - 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 We support standard OpenJDK builds, including Oracle's official build, alternative builds such as AdoptOpenJDK, and builds shipped with Linux distributions such as Red Hat Enterprise. All with current CPU (Critical Patch Update) and Hotspot that is actively supported by its vendor.

2 Bloomreach does not plan to support Tomcat 10.

3 Using Docker is optional. Other Docker versions may work, however it's not advisable to use versions out of the specified range.

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

5 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.

6 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.

7 Please note that brX and brSM only support the latest stable version of Google Chrome.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?