- About this guide
- What is BEMS?
- Preinstallation checklists
- Installation and upgrade
- Prerequisites: Installing and configuring BEMS
- Core requirements
- Configure the Java Runtime Environment
- Prerequisites: Connect for Skype for Business
- Preparing the computer that hosts BEMS for use with Skype for Business
- BlackBerry Connect service database requirements
- 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
- 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
- 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
Creating an additional trusted application pool
One
BlackBerry Connect
instance can be associated with only one Trusted Application Pool. In a high availability or
disaster recovery scenario, it is recommended that you create an additional trusted application
pool in your Front-End high availability and disaster recovery pool for your Connect
high availability and
disastery recovery instances.The steps for creating an additional trusted application pool are the same as
creating your first trusted application pool for
Connect
with the exception that
trusted application pool names must be unique. Therefore, if you named your first trusted
application pool "pool1_bems.example.com", then your second trusted application pool name must be
different. For example, "pool2_bems.example.com".