Create a cluster

Platform Manager can create a MiVoice Business SDS and call control cluster.

Note the following limitations:

A call control and SDS clusters is created when the Platform Blueprint is configured with two MiVoice Business (MiVB)-type resource blueprints, when the cluster option is enabled.
The Platform Manager clustering process assumes that the golden databases contain of all the required configuration data for clustering. These databases must be part of the resource blueprints used in the platform blueprint. See the Oria Engineering Guidelines for guidance for configuring the resource database.
When describing the MiVoice Business resources (in the Resource Details section of the platform blueprint), you must specify which resource is the SDS master.
MiVoice Business Express: Clustering with an external MiVoice Business is not supported, so you cannot create resilient configurations with MiVoice Business Express using Platform Manager. You can, however, add MiVoice Business controllers manually later to support resiliency.

Example Platform Blueprint

The screen image below shows a sample Platform Blueprint that will generate a platform instance with the following inclusions and characteristics:

Blueprint name: Reference_SP_v102
A pair of MiVoice Business tenants configured as a resilient cluster
A MiCollab Multi-Tenant enterprise tenant
50 UCC Entry SB user licenses (# 54006169).
It contains two resources, both MiVoice Business tenants.
Resource 1 is built from the Resource Blueprint primary_20160606 and ARID blueprint mivbmi_sp_sub_base. This tenant will be the SDS Master and the primary controller in the Cluster.
Resource 2 is built from the same ARID Blueprint (which describes a base part), but a different Resource Blueprint, secondary_20160531. The secondary blueprint is similar to the primary blueprint except that it contains a different golden database–one suitable for the secondary controller in the resilisent pair of MiVoice Business tenants. The secondary blueprint also specifies a different pool of MiVoice Business Multi-Instance servers, to ensure high availability in the event of a MiVoice Business Multi-Instance server failure.
A single AMC group part, 54006169, is specified. User parts from this bundle will be allocated to the MiCollab Multi-Tenant server and to resource 1; the primary controller. In this example, there are no user parts allocated to the secondary MiVoice Business.
The MiCollab Multi-Tenant server used to create the new Customer will come from a pool called “RealServers”. (Configuration > MiCollab-MT Pools)