Architecture: BEMS
BEMS
From this high-level architectural view, the diagram does not show how the
BlackBerry Work
application connects to Microsoft Exchange
Server
for accessing email. It shows how each BEMS
service is accessed by BlackBerry Work
on devices, which is BEMS
role, to expose secure device-facing services used by BlackBerry Work
and make them available to other BlackBerry
Dynamics
-powered apps. These services currently include BlackBerry
Push Registration, BlackBerry
Follow Me, BlackBerry Presence
, BlackBerry Directory Lookup
, and BlackBerry Docs
.Communicating using the protocols shown, the feature modules of
BEMS
integrate with your backend systems of record using a shared Microsoft SQL
Server
running multiple databases for Core/Mail
, Connect
, and Docs
.For high availability,
BEMS
is deployed as a cluster, with all of its device-facing services provided by all instances of BEMS
in the cluster and made available to client devices through the BlackBerry
Dynamics
infrastructure. Each BlackBerry
Dynamics
-powered client app connects through a Good Proxy
cluster deployed on-premise. Entitlement to use BEMS
services is managed through Good Control
.A slightly different view looks like this again at a high level:
It is important to note in the diagram above that the
BlackBerry
Mail
service utilizes the same database server as Good Control
. The database server can be local to Good Control
or remote.Some necessary supporting infrastructure is required to support enterprise network operations. Such components include:
- Microsoft Exchange Server
- Skype for Business
- Cisco Unified Communications Managerfor IM and Presence
- Microsoft Active Directory
- Good Control
- Good Proxy
For more information about the
BEMS
architecture in a BlackBerry UEM
environment, see the BlackBerry UEM
Architecture and Data Flow Reference content.