- 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
- BEMS-Core database
BEMS-Core database
You can access the BEMS-Core database screen in the BlackBerry Enterprise Mobility Server Dashboard (BEMS System Settings > BEMS Database). It is prepopulated with the information that you entered during the BEMS software installation and requires a Microsoft SQL Server database that is available for BEMS. The information includes the SQL Server and database name, the authentication type used for BEMS to authenticate to the database, and any additional SQL properties that are required in your environment. By default, no changes are required on the Database Configuration screen. However, if you choose to make changes to the Database Configuration, consider the following:
- You must restart the Good Technology Common Services service for BEMS to update any changes.
- You can use the information to verify the database settings by clicking the Test button after you install the BEMS software.
- Important: If you use the database screen to update the SQL Server settings, and than upgrade your BEMS instance, the updated settings are reverted to the original settings that you specified during the BEMS installation. BlackBerry recommends that you update SQL Server settings using the Repair option in the Setup application. For more information on using the Repair mode, see 'BEMS setup application modes' in the BEMS Installation content'.