{section}
{column}

This page lists the system requirements to run Petals ESB Registry.
This list is related to the Petals ESB Registry node.

{column}
{column:width=350px}
{panel:title=Table of contents}{toc}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}

h1. Operating Systems

The following operating systems are supported:
* Linux Debian-based (e.g. Debian, Ubuntu)
* Red Hat (RHEL, CentOS)

Although Petals ESB Registry runs on Windows and MacOS, these operating systems are neither recommended nor supported in production environments.

h1. Java

You must have installed a Java Runtime Environment (JRE) headless on your operating system before before proceeding with a Petals ESB Registry installation.

OpenJDK 1.7 is the only JRE supported (no specific version).

h1. Firewall Software Configuration

All the ports declared within the *cluster.xml* file must be opened between Petals ESB Registry nodes and Petals ESB containers.
In addition, JMX ports must be accessible for administrators machines.

h1. Petals ESB Registry hardware requirements

Only x86 hardware and 64-bit derivatives of x86 hardware are supported with Petals ESB Regsitry. Server load depends primarily on the number of deployed service endpoints. Petals ESB Registry runs over virtualized environments.

*Production use, light to medium server load :*
* 2 GHz\+ CPU Xeon or equivalent
* 1 GB of RAM for Petals
* 1.000 Mbits/s network interface
* 50 MB of disk for Petals

*Production use, heavy load :*
* Dual 2GHz\+ CPU Xeon or equivalent
* 2 GB of RAM for Petals
* 1.000 to 10.000 Mbits/s network interface
* 50 MB of disk for Petals

Notice that in a distributed mode, Petals ESB Registry nodes perform a lot of exchanges with other nodes. The network is therefore highly solicited.

Petals ESB Registry requires few disk space.

Petals ESB Registry does not require to back up any data. If a node crashes, you can simply reinstall it over another machine (with the same network configuration).
However, to minimize the impact of a crash, you can use a RAID configuration. This solution avoids a full reinstallation.