Architecture: High availability for BlackBerry UEM
BlackBerry UEM
The following diagram shows a high availability domain with two
BlackBerry UEM
instances. You can install any number of BlackBerry UEM
instances. This topic explains how specific components are involved in a high availability configuration. For more information about the BlackBerry UEM
architecture and components, see the Architecture content.
Components |
Description |
---|---|
BlackBerry UEM database |
Each BlackBerry UEM instance connects to the BlackBerry UEM database to access user and device data. |
Management console and BlackBerry UEM Core |
You can use any management console to manage the domain’s user accounts and devices. The BlackBerry UEM Core associated with that console carries out the management tasks.You can configure a round-robin DNS pool that connects to each console. If there is a problem with a console, the pool connects to a working console. Each instance manages enterprise connectivity for the BlackBerry 10 devices that are assigned to it by the BlackBerry Affinity Manager . Any healthy instance can process device management tasks for all device types. |
BlackBerry MDS Connection Service and BlackBerry Dispatcher |
These components allow BlackBerry 10 devices to connect to and use work resources. |
BlackBerry Affinity Manager |
The BlackBerry Affinity Manager is responsible for:
Only one BlackBerry Affinity Manager is active (the others are on standby). If the active instance finds a problem with enterprise connectivity, it reassigns BlackBerry 10 users to the healthy BlackBerry UEM instances.Each standby BlackBerry Affinity Manager monitors the active BlackBerry Affinity Manager . If there is a problem with the active BlackBerry Affinity Manager , a failover occurs and one of the standby instances becomes active. |