Components that support high availability failover
The following BlackBerry Enterprise Service 10 core components support high availability using a failover model. The table below describes the status of each component on the primary instance and on the standby instance. Note that when an automatic or manual failover occurs, the standby instance becomes the new primary instance, and what was previously the primary instance becomes the standby instance.
|
Component |
Associated with |
Status - primary |
Status - standby |
Description |
|---|---|---|---|---|
|
BlackBerry Controller |
BlackBerry Device Service |
Started |
Started |
Device service fails over from the primary instance to the standby instance. |
|
BlackBerry Dispatcher |
BlackBerry Device Service |
Started |
Started |
Device service fails over from the primary instance to the standby instance. |
|
BlackBerry MDS Connection Service |
BlackBerry Device Service |
Started |
Started |
Device service fails over from the primary instance to the standby instance. |
|
BlackBerry Secure Connect Service |
Universal Device Service |
Started |
Started |
Device service fails over from the primary instance to the standby instance. |
|
BlackBerry Web Services |
Universal Device Service |
Started if instance has the device management role Not started if instance does not have the device management role |
Not started |
The BlackBerry Web Services are started only on the primary instance with the device management role for Android devices and iOS devices. They are not started on other primary instances or standby instances. Device service fails over from the primary instance to the standby instance. The BlackBerry Web Services start automatically when device service fails over to the standby instance. |
|
BlackBerry Work Connect Notification Service |
Universal Device Service |
Started if instance has the device management role Not started if instance does not have the device management role |
Not started |
The BlackBerry Work Connect Notification Service is started only on the primary instance with the device management role for Android devices and iOS devices. It is not started on other primary instances or standby instances. Device service fails over from the primary instance to the standby instance. The BlackBerry Work Connect Notification Service starts automatically when device service fails over to the standby instance. |
|
Communication Module |
Universal Device Service |
N/A |
N/A |
Exists as a website in Microsoft IIS on both the primary instance and the standby instance. |
|
Core Module |
Universal Device Service |
N/A |
N/A |
Exists as a website in Microsoft IIS on both the primary instance and the standby instance. |
|
Enterprise Management Web Service |
BlackBerry Device Service |
Started |
Not started |
Device service fails over from the primary instance to the standby instance. The Enterprise Management Web Service starts automatically when device service fails over to the standby instance. |
|
Scheduler |
Universal Device Service |
Started |
Started |
On the primary instance, the Scheduler runs in primary mode. On the standby instance, the Scheduler runs in standby (or idle) mode. |