- What is BEMS?
- Configuring BlackBerry UEM Cloud email notifications and Cloud Docs service for BlackBerry Dynamics apps
- Preinstallation and preupgrade requirements for on-premises BEMS
- Set an environment variable for the Java location
- Setting up a Windows service account for BEMS
- Configuring connections for the BEMS databases
- Port requirements
- Prerequisites: BlackBerry Push Notifications service
- Docs prerequisites: CMIS Requirements
- Connect prerequisites: Skype for Business
- Preparing the computer that hosts BEMS for use with Skype for Business
- Preparing the Skype for Business topology for BEMS
- SSL certificate requirements for Skype for Business
- Mutual TLS (MTLS) certificates
- Steps to create a CA-signed certificate for the local computer account using a CSR for BEMS
- Steps to create a CA-signed for the local computer account using automatic enrollment for BEMS
- Create a CSR for the local computer account for BEMS
- Obtain a CA-signed certificate from the CA server
- Import the CA-signed certificate on the CSR requesting BEMS
- Create a Personal Certificate for the local computer account for BEMS
- Export the CA-signed certificate and private key from the Microsoft Management Console
- Import the CA-signed certificate and private key to additional BEMS instances
- Presence prerequisites: Skype for Business
- Presence Prerequisites: Cisco Unified Communications Manager IM and Presence Service
- Prerequisites: BlackBerry Directory Lookup, BlackBerry Follow-Me, and BlackBerry Certificate Lookup services
- Installing or upgrading the BEMS software
- Removing the BEMS software
- Configuring the BEMS services
- Appendices
- Appendix: AlwaysOn Availability support for SQL Server
- Steps to setup SQL Server for AlwaysOn availability
- Configure the BEMS services databases for AlwaysOn availability
- Enabling AlwaysOn availability group failover to subnets for the BEMS-Core and Mail services
- Enabling AlwaysOn availability group failover to subnets for the Connect service
- Enabling AlwaysOn availability group failover to subnets for the Docs service
- Data flow: BEMS notification flow using the Microsoft Graph API
- Configuring BlackBerry UEM Cloud to communicate with an on-premises BEMS
- Import the certificate to the BEMS Windows keystore
- Import the certificate into the Java keystore on BEMS
- Configure the BlackBerry Dynamics server in BEMS
- Configure BEMS connectivity with BlackBerry Dynamics
- Add an app server hosting the entitlement apps to a BlackBerry Dynamics connectivity profile
- Export the BlackBerry Proxy certificate to the local computer
- Appendix: AlwaysOn Availability support for SQL Server
- BlackBerry Docs
- BlackBerry Enterprise Mobility Server 3.8
- BEMS Installation Guide
- Appendices
- Appendix: AlwaysOn Availability support for SQL Server
- Configure the BEMS services databases for AlwaysOn availability
Configure the BEMS services databases for AlwaysOn availability
BEMS
services databases for AlwaysOn availabilityComplete this task if you installed
BEMS
in your environment without specifying the server and database for AlwaysOn during the installation. Complete these steps on each BEMS
instance in your environment.
If you manually specify the AlwaysOn Listener and database name in the
BEMS
dashboard, you must specify the updated server and database information when you perform future upgrades. For instructions on upgrading BEMS
, see Upgrade BEMS
.- To installBEMSservices connected to a database in AlwaysOn, the instance name must be set to the Listener in the AlwaysOn group, not the cluster name and not the host name of the host server in the cluster.
- The databases created forBEMSservices need to be added into the AlwaysOn group.
- In theBlackBerry Enterprise Mobility Server Dashboard, underBlackBerry Services Configuration, clickMail.
- ClickDatabase.
- In theServerfield, enter the FQDN of the AlwaysOn Listener.
- In theDatabasefield, enter the name of the database that is added to the AlwaysOn Availability Group.
- ClickTestto test the connection.
- ClickSave.
- Repeat the previous steps for theConnectandDocsservices.