Cluster considerations

• A cluster can have up to five Avaya Breeze® platform servers, with the exception of the Core Platform cluster profile, which supports up to 10.

• An enterprise can have up to 35 Avaya Breeze® platform instances.

• To install snap-ins, an Avaya Breeze® platform server must belong to only one cluster.

• Snap-ins are installed at the cluster level, and all servers in a cluster have the same snap-ins.

Cluster profiles

A cluster profile is a preloaded template that contains fixed and variable cluster attributes.

A set of cluster profiles are preloaded on Element Manager. Each cluster profile contains a set of required snap-ins. Ensure that the required snap-ins are loaded. Some cluster profiles might have optional snap-ins that you might choose to install.

• General Purpose cluster profile: Enables you to install a snap-in or service. This profile must have at least one server.

• Customer Engagement cluster profile: Supports Avaya contact center snap-ins. Use when instructed by appropriate Avaya product installation guides.

• General Purpose Large cluster profile: Supports mainly the Engagement Call Control solution.

• Core Platform cluster profile: Supports up to 10 Avaya Breeze® platform servers. You can install snap-ins such as Presence Services and Call Park and Page Snap-in.

• Product-specific cluster profiles: Includes a specified list of snap-ins. If these snap-ins are not installed, cluster creation fails. For example, Context Store.

Clustering functionalities

Use the clustering functionalities to:

• Create a new cluster and assign a cluster profile to the cluster.

• Edit a cluster and the cluster attributes.

• Delete a cluster.

• Add or remove servers from a cluster.

• Install or remove snap-ins in a cluster.

• Manage resources for logging.

• Create the cluster database.

• Back up and restore the cluster database.

• Select product-specific cluster profiles, such as Context Store.

Data grid for clusters

Avaya Breeze® platform supports the data grid configuration on a cluster. A Lookup service is required when a server needs access to the data of other servers in the cluster. The Lookup service is hosted on two designated Lookup servers in a cluster.