Install and configure the Connect service cluster

Disaster recovery is not supported for BlackBerry Connect using Cisco Jabber because BEMS only stores one set of global configurations.
Before adding a Connect service instance for disaster recovery, complete the following actions:
  • If your environment has separate Front End Pools or additional Trusted Application Pools, make sure that you add the correct permissions. Note: The Presence service and Connect service can use the same Trusted Application Pool for disaster recovery.
  • Make sure that the appropriate network ports are open to allow the servers that host the Connect service in your secondary site to communicate with the database, Skype for Business Server or Skype for Business database, and BlackBerry Proxy servers in your secondary and primary site.
  1. Install BEMS on each server that hosts the Connect service at the primary site. Select the Connect option in each case. Use a new database to create a new cluster that is dedicated to the Connect service.
  2. Install BEMS on each server that will host the Connect service at the secondary site. Select the Connect option in each case. Add the servers to the same database that you used in step 1.
  3. At the primary site, complete the following tasks:
    1. In the BEMS dashboard for the Connect service (BlackBerry Services Configuration > Connect > BlackBerry Dynamics), add the BlackBerry Proxy for the primary site. Repeat this step for each Connect service instance in the primary site.
    2. In the BEMS dashboard (BEMS System Settings > BlackBerry Configuration > BlackBerry Dynamics), configure one or more BlackBerry Proxy servers from one or more clusters in the primary site. This list is used only for startup. Clear the 'Apply to other nodes in this BEMS cluster' check box. Repeat this step for each Connect service instance in the primary site.
  4. At the secondary site, complete the following tasks:
    1. In the BEMS dashboard for the BEMS-Connect (BlackBerry Services Configuration > Connect > BlackBerry Dynamics), add the BlackBerry Proxy for the secondary site. Repeat this step for each Connect service instance in the secondary site.
    2. In the BEMS dashboard (BEMS System Settings > BlackBerry Configuration > BlackBerry Dynamics), configure one or more BlackBerry Proxy servers from one or more clusters in the secondary site. This list is used only for startup. Clear the 'Apply to other nodes in this BEMS cluster' check box. Repeat this step for each Connect service instance in the secondary site.
  5. Configure the appropriate instant messaging (for example, Skype for Business) and Active Directory settings (for example, the front-end pool).
  6. Stop the services on the servers at the secondary site to prevent the disaster recovery nodes from contributing to normal cluster operations (for example, send instant messages).
  7. In the BlackBerry UEM management console, in the BlackBerry Dynamics connectivity profiles that are assigned to users, do the following. Depending on your environment configuration, additional server-side services might be required. For more information about BEMS services and server-side bindings, see the Additional information.
    1. Under App servers for BlackBerry Connect, for each of the server that hosts the Connect service at the primary site, set the Priority to PRIMARY and set the Primary BlackBerry Proxy cluster to BPCluster1.
    2. Under App servers for BlackBerry Connect, for each of the server that hosts the Connect at the secondary site, set the Priority to SECONDARY or TERTIARY and set the Primary BlackBerry Proxy cluster to BPCluster2.