- Preinstallation and preupgrade tasks
- Configure permissions for the service account
- Set an environment variable for the Java location
- Configuring connections for the BlackBerry UEM database
- Backing up the databases
- Creating or upgrading a BlackBerry UEM database using CreateDB
- Performing a test upgrade of the BlackBerry UEM database
- BlackBerry UEM Readiness Tool
- Steps to install BlackBerry UEM
- Supported upgrade environments
- Steps to upgrade BlackBerry UEM version 12.18 or later to UEM version 12.20
- Installing or upgrading the BlackBerry UEM software
- Install a new BlackBerry UEM instance
- Check the ports assigned by the BlackBerry UEM setup application
- Install an additional BlackBerry UEM instance
- Upgrade BlackBerry UEM version 12.18 and later to BlackBerry UEM version 12.20
- Upgrade a domain that consists of multiple instances of BlackBerry UEM
- Install or upgrade BlackBerry UEM using the command prompt window
- Install the BlackBerry UEM components on separate computers using the command prompt window
- Installing BlackBerry UEM in a DMZ
- Installing or upgrading BlackBerry UEM in a dark site environment
- Post-upgrade checklist
- Creating server groups and installing BlackBerry Connectivity Node instances
- Create a server group
- Change the default settings for BlackBerry Connectivity Node instances
- Prerequisites: Install a BlackBerry Connectivity Node instance
- Install a BlackBerry Connectivity Node instance
- Activate a BlackBerry Connectivity Node instance
- Configure proxy settings for a BlackBerry Connectivity Node instance
- Manage server groups
- Install a standalone BlackBerry Router
- Logging in to BlackBerry UEM for the first time
- Removing the BlackBerry UEM software
- Rebuilding a BlackBerry UEM server instance
- Removing the BlackBerry Connectivity Node software
- Rebuilding a BlackBerry Connectivity Node instance
- Troubleshooting BlackBerry UEM installation or upgrade
- Best practices for running BlackBerry UEM
- BlackBerry UEM Configuration Tool
- Configuring BlackBerry UEM for disaster recovery
Servers and services
When the main network is running properly, the disaster recovery servers are powered on, but their services are stopped. This configuration allows for server maintenance such as security patches. Because the services are off, TCP connections are quickly rejected if there is an attempt to connect to one of the disaster recovery servers.
In a disaster recovery event, the primary servers go offline. An administrator must manually start the services on the disaster recovery servers after the failover of the databases is complete.
The high availability configuration for all clusters is at least n + 1 (the number of servers you require plus one or more servers for high availability).