- About this guide
- What is BEMS?
- Preinstallation checklists
- Installation and upgrade
- Supported installation and upgrade paths
- Best practices: Preparing to upgrade
- Steps to install BEMS
- BEMS setup application modes
- Steps to upgrade BEMS
- Steps to upgrade BEMS and change to an alternate JRE
- Steps to upgrade BEMS and change the instant messaging service
- Steps to install BEMS instances into a cluster
- Prerequisites: Installing and configuring BEMS
- Core requirements
- Configure the Java Runtime Environment
- Prerequisites: Connect for Microsoft Lync Server and Skype for Business
- Preparing the computer that hosts BEMS for use with Microsoft Lync Server 2013 or Skype for Business
- BlackBerry Connect service database requirements
- Preparing the Microsoft Lync Server and Skype for Business topology for BEMS
- SSL certificate requirements for Microsoft Lync Server and 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
- 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: Microsoft Lync Server and Skype for Business
- Prerequisites: BlackBerry Push Notifications service
- Prerequisites: Cisco Unified Communications Manager IM and Presence Service requirements for Presence
- Prerequisites: Docs service
- Prerequisites: BlackBerry Directory Lookup, BlackBerry Follow-Me, and BlackBerry Certificate Lookup services
- Installing or upgrading the BEMS software
- Removing the BEMS software
- Troubleshooting BEMS installation or upgrade
- 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
- Architecture: BEMS notification flow using the Microsoft Graph API
- Architecture: BEMS
- Appendix: AlwaysOn Availability support for SQL Server
- BlackBerry Docs
- BlackBerry Enterprise Mobility Server 3.5
- BEMS Installation Guide
- Appendices
- Appendix: AlwaysOn Availability support for SQL Server
Appendix: AlwaysOn Availability support for SQL Server
SQL Server
The AlwaysOn Availability Groups feature is a high-availability and disaster-recovery solution that provide an enterprise-level alternative to database mirroring. Introduced in
SQL Server
2012, AlwaysOn Availability Groups maximize the availability of a set of user databases for an enterprise that is running SQL Server 2012, 2014, 2016, or 2017. An availability group supports a failover environment for a discrete set of user databases, known as availability databases, that fail over together. A read-scale availability group is a group of databases that perform read-only work and are copied from other SQL Server
instances. An availability group supports a set of read-write primary databases and one to eight sets of corresponding secondary databases. Optionally, secondary databases can be made available for read-only access and some backup operations.
For more information about AlwaysOn availability, visit docs.microsoft.com to read Overview of Always On Availabilty Groups.
Section:
Appendices
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