You can install one or more instances of the BlackBerry Connectivity Node to add additional instances of the device connectivity components to your organization’s domain. This includes BSCP traffic for enterprise connectivity and BlackBerry Dynamics traffic for BlackBerry Dynamics devices. Each BlackBerry Connectivity Node contains the following BlackBerry UEM components: BlackBerry Secure Connect Plus, the BlackBerry Gatekeeping Service, the BlackBerry Secure Gateway, BlackBerry Proxy, and the BlackBerry Cloud Connector.

Each BlackBerry Connectivity Node provides another active instance of these components to the BlackBerry UEM domain that can process and manage secure device connections. For information about installing a BlackBerry Connectivity Node, see the Installation and upgrade content.

You can also create server groups. A server group contains one or more instances of the BlackBerry Connectivity Node. When you create a server group, you specify the regional data path that you want the components to use to connect to the BlackBerry Infrastructure. For example, you can create a server group to direct device connections for BlackBerry Secure Connect Plus and the BlackBerry Secure Gateway to use the path for the United States to the BlackBerry Infrastructure. You can associate email and enterprise connectivity profiles with a server group. Any device that is assigned those profiles uses that server group’s regional connection to the BlackBerry Infrastructure when it uses any of the components of the BlackBerry Connectivity Node.

Optionally, you can designate each BlackBerry Connectivity Node in a server group to handle a single connection type: BlackBerry Secure Connect Plus only, BlackBerry Secure Gateway only, or BlackBerry Proxy only. This frees up server resources to allow fewer servers required for the same number of users or containers.

If a server group contains multiple instances of the BlackBerry Connectivity Node, devices can use any instance that is running. Device connections are load balanced across the available instances in the group. If no instances are available, devices cannot use those components for secure connections. At least one of the instances must be available.