BlackBerry Connect and BlackBerry Presence
BlackBerry Connect
and BlackBerry Presence
The following requirements apply when you need to configure servers to support
BEMS
with the BlackBerry Connect
and BlackBerry Presence
services. Complete | Requirement | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Registration | ||||||||||||||||
Request the BlackBerry Connect app from the Marketplace for Enterprise Software portal. | ||||||||||||||||
Log in to entitlements and confirm that you have the appropriate entitlements. For more information about entitlements, see the following:
| ||||||||||||||||
Network: Skype for Business | ||||||||||||||||
Verify that the following ports are open for BEMS :Inbound TCP Ports
Outbound TCP Ports
| ||||||||||||||||
If your environment uses Skype for Business using non-trusted application mode, verify that at least one DNS entry exists for lyncdiscoverinternal. For more information about DNS requirements for Skype for Business , see https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/network-requirements/dns. | ||||||||||||||||
If BEMS requires a proxy server for external access, record it here:
| ||||||||||||||||
Network: Cisco Unified Communications
Manager and Cisco IM and Presence | ||||||||||||||||
Verify that the following ports are open for BEMS :Inbound TCP Ports 8080 or 8082 from the BlackBerry Proxy or Good Proxy server (for BlackBerry Connect )
By default, SSL communication is enabled with a new BEMS 2.12.5.6 or later installation and is bound to port 8082. If you upgraded from BEMS 2.10 or earlier and SSL communication with the BlackBerry Connect app is not enabled, use port 8080. For more information on configuring BlackBerry Connect , see one of the following:
Outbound TCP Ports
| ||||||||||||||||
If BEMS requires a proxy server for external access, record it here:
| ||||||||||||||||
Microsoft Active
Directory : Skype for Business and Microsoft
Exchange | ||||||||||||||||
Create a Microsoft Active
Directory service account for the BEMS software (can be the same account used for BlackBerry Push Notifications . For example, BEMSAdmin). The service account must be in the same Microsoft Active
Directory domain as the BEMS . For more information, visit support.blackberry.com/community to read article 63703.For account and password considerations, see Creating a Microsoft Active
Directory account for the BEMS service account. | ||||||||||||||||
Create a mailbox for the BEMSAdmin account. | ||||||||||||||||
Grant Application Impersonation Permissions to the BEMSAdmin account in Microsoft
Exchange . For instructions, see Grant application impersonation permission to the service account.
You must mailbox-enable the BEMS-Connect service in Microsoft
Exchange to allow the BEMS-Connect service to properly write to the user's conversation history. For specific instructions, see the documentation for the Microsoft Exchange
Server version that you are using. | ||||||||||||||||
Verify that the BEMS service account has RTCUniversalReadOnlyAdmins permission during the BEMS installation. This permission is granted in the Microsoft Active
Directory . | ||||||||||||||||
If your environment uses multiple Skype for Business on-premises servers using trusted application mode or non-trusted application mode, have the Skype for Business servers load balanced with a load balance server. For more information about load balancing requirements, visit https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/network-requirements/load-balancing. | ||||||||||||||||
Microsoft Active
Directory : Cisco Unified Communications
Manager and Cisco IM and Presence | ||||||||||||||||
Create a Microsoft Active
Directory service account for the BEMS software. | ||||||||||||||||
BEMS : Skype for Business | ||||||||||||||||
Verify that your environment is running one of the following:
| ||||||||||||||||
Verify that you have a supported instant messaging server. | ||||||||||||||||
Make sure that the BEMS service account is a local administrator on the server. | ||||||||||||||||
Make sure that the BEMS service account has "Log on as a service" permission. | ||||||||||||||||
Verify that the servers that host and access the BEMS Dashboard have a supported browser installed. | ||||||||||||||||
Make sure that the server's date and time are set correctly. | ||||||||||||||||
Make sure that the server is joined to the domain. | ||||||||||||||||
Verify that the servers are running an operating system that supports the Connect service before you install or upgrade. | ||||||||||||||||
If your environment runs Skype for Business on-premises for Presence and plan to configure the Connect service as trusted by Skype for Business , make sure that Windows PowerShell (x86) is installed.Open “ Windows PowerShell (x86)” and run the following command to enable execution of remote signed scripts: Set-ExecutionPolicy -Scope CurrentUser RemoteSigned | ||||||||||||||||
If your environment includes Skype for Business on-premises and plan to configure the Connect service as trusted by Skype for Business , create a Trusted Application Pool, trusted application, and trusted application endpoint for BEMS in the Microsoft Lync Shell Console.The user creating the Trusted Application Pool must have RTCUniversalServerAdmins and Domain Admins permissions. For more information about preparing the first server hosting BEMS , see Prepare the initial computer hosting BEMS. | ||||||||||||||||
If your environment includes the following instant messaging server, verify the version of Microsoft .NET
Framework :Skype for Business on-premises and plan to configure the Connect service as non-trusted by Skype for Business . For more information, see Preparing the computer that hosts BEMS for use with Skype for Business. | ||||||||||||||||
If your environment runs Skype for Business on-premises for Presence and plan to configure the Connect service as trusted by Skype for Business , make sure that the required Microsoft Unified Communications Managed
API is installed.For more information, see Preparing the computer that hosts BEMS for use with Skype for Business. | ||||||||||||||||
If your environment runs Skype for Business on-premises for Presence and plan to configure the Connect service as trusted by Skype for Business , request and install an SSL certificate on BEMS .For more information, see SSL certificate requirements for Skype for Business. | ||||||||||||||||
Disable all antivirus programs and backup software before you install or upgrade the BEMS software. | ||||||||||||||||
Verify that you have installed JRE 8 on the servers where you will install BEMS and that you have an environment variable that points to its location. For instructions, see Configure the Java Runtime Environment. For information about the supported JRE versions, see the BEMS Compatibility Matrix. | ||||||||||||||||
BEMS - Cisco Unified Communications
Manager and Cisco IM and Presence | ||||||||||||||||
Verify that your environment is running one of the following:
| ||||||||||||||||
Make sure that the BEMS service account is a local administrator on the server. | ||||||||||||||||
Make sure that the BEMS service account has Logon As a Service permission. | ||||||||||||||||
Make sure that the server's date and time are correctly set. | ||||||||||||||||
Make sure that the server is joined to the domain. | ||||||||||||||||
Disable all antivirus programs and backup software before you install or upgrade the BEMS software. | ||||||||||||||||
Verify that you have installed JRE 8 on the servers where you will install BEMS and that you have an environment variable that points to its location. For instructions, see Configure the Java Runtime Environment. For information about the supported JRE versions, see the BEMS Compatibility Matrix. | ||||||||||||||||
Database | ||||||||||||||||
Verify your environment is running a supported database server. | ||||||||||||||||
Depending on the configuration of your environment (for example, all BEMS services on one server or on separate servers), you might need to create one or more SQL Server databases. The following table is an example of a small deployment that has all of the BEMS services installed on one server. For an example of a small deployment that has all of the BEMS services installed one server, see Example of a small BEMS deployment.
The following table is an example of a large deployment that has the BEMS services installed on separate servers. For an example of a large deployment that has the BEMS services installed on separate servers, see Example of a large BEMS deployment.
| ||||||||||||||||
Make sure that the BEMS service account has db_owner permission to the database. For more information, visit support.blackberry.com/community to read article 42661. |