- Start here
- Planning tools
- BlackBerry UEM installation options
- Device management modes
- Designing a deployment plan for BlackBerry UEM
- Planning high availability for a BlackBerry UEM domain
- Architecture: High availability for BlackBerry UEM
- High availability and the BlackBerry UEM Core
- Configuring high availability for the management console
- High availability and the BlackBerry Connectivity Node
- Configuring database high availability using Microsoft SQL Server AlwaysOn
- Configuring database high availability using database mirroring
- Preinstallation and preupgrade requirements
- Hardware requirements
- Port requirements
- Server configuration
- Global IP ranges
- Mobile device configuration (Wi-Fi requirements)
- Reserved IP address ranges
- Outbound connections: BlackBerry UEM to the BlackBerry Infrastructure
- Outbound connections: BlackBerry UEM to the BlackBerry Dynamics NOC
- Outbound connections: Devices on a work Wi-Fi network
- Intranet connections
- How BlackBerry UEM selects listening ports during installation
- Supporting the deployment
- BlackBerry Docs
- BlackBerry UEM 12.17
- Planning and Architecture
- BlackBerry UEM and BEMS Planning Guide
- Planning high availability for a BlackBerry UEM domain
- Architecture: High availability for BlackBerry UEM
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. |