Operating Systems

The following operating systems are supported:

• Linux Debian-based (e.g. Debian, Ubuntu)
• Red Hat (RHEL, CentOS)

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

Java

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

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

Firewall Software Configuration

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

Petals ESB Hazelcast Registry hardware requirements

Only x86 hardware and 64-bit derivatives of x86 hardware are supported with Petals ESB Hazelcast Registry. Server load depends primarily on the number of deployed service endpoints. Petals ESB Hazelcast 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 Hazelcast Registry nodes perform a lot of exchanges with other nodes. The network is therefore highly solicited.

Petals ESB Hazelcast Registry requires few disk space.

Petals ESB Hazelcast 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 re-installation.

See System configuration for Petals ESB Hazelcast Registry to adjust your system to get the best of Petals ESB Hazelcast Registry.