Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry Enterprise Mobility Server 3.1
  3. BEMS Installation Guide
  4. Prerequisites: Installing and configuring BEMS
  5. Core requirements
  6. System and network requirements

System and network requirements

Verify that your environment and the servers that host 
BEMS
 meet the following system and network requirements. 
Item
Requirement
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. 
Operating system
Verify that your server is running an operating system that supports 
BEMS
. For information about the supported operating systems, see the BEMS Compatibility Matrix.
Supported browsers
Verify that the servers that host and access the 
BEMS
 Dashboard have a supported browser installed.
Administration rights
  • The user that performs the installation must have local administrative privileges on the host machine. The user that performs the installation must also have db_owner permissions to all the 
    BEMS
     databases. For more information, visit support.blackberry.com/community to read article 42661. 
  • The 
    BEMS
     service account must have "Log on as a service" right.
  • Disable antivirus software before you install or upgrade the 
    BEMS
     software.
  • Exclude the 
    BEMS
     directory from virus scanning.
  • The local 
    Windows
     firewall must be disabled.
A Group Firewall Policy will cause the installer to fail its prerequisite checks, even if the local firewall is disabled.
Inbound TCP Ports 
The following ports must be open and ready for 
BEMS
 and not blocked by any firewall:
  • 49555 from 
    Microsoft Lync Server
     for the 
    Connect
     service
  • 49555 from the on-premises 
    Skype for Business
     server (for 
    BlackBerry Connect
    ) when the 
    Connect
     service is trusted by 
    Skype for Business
  • 49777 from the 
    Microsoft Lync Server
     or 
    Skype for Business
     for the 
    Presence
     service
  • 61616 TCP port to and from 
    BEMS
     servers in the same cluster (bidirectional)
  • 61617 TCP (SSL) to and from 
    BEMS
     servers in the same cluster (bidirectional)
To support clustering, 
BEMS
 employs ActiveMQ's enterprise features. By design, network port 61616 and 61617 (SSL) are used for inter-
BEMS
 communication. Any firewall between 
BEMS
 nodes in the same cluster should have rules allowing bi-directional communication between 
BEMS
 nodes over port 61616 and/or 61617 (SSL).
Outbound TCP Ports
Verify that the following ports are open and ready for 
BEMS
 and not blocked by any firewall:
  • 443 to 
    BlackBerry Dynamics NOC
     (gdweb.good.com)
  • 443 to 
    Microsoft Exchange
  • 443 to 
    Firebase Cloud Messaging
     (FCM)for 
    Android
     Push Notification
  • 443 or 80 to 
    Microsoft SharePoint
  • 443 to 
    Microsoft Office Web Apps
     Server (OWAS)
  • In a 
    Skype for Business Online
     environment, 443 to the following:
    • login.microsoftonline.com
    • lyncdiscover.EMAIL-DOMAIN
    • *.online.lync.com
  • 5061 (for 
    BlackBerry Connect
    ) to the 
    Microsoft Lync Server
     or on-premises 
    Skype for Business
     server configured as trusted mode 
  • 1433 to the 
    Microsoft SQL Server
     (default)
  • 1434 UDP to the 
    Microsoft
    Lync
     database (for initial setup only)
  • 8443 to the Presence Web Service (CIMP server)
  • 5222 to the Presence Web Service (CIMP server)
  • 8083 to the 
    Cisco
     IM and Presence Service 
  • 49152 – 57500 TCP: Random port in this range to the Lync database (for initial setup only)
  • 61616 TCP port to and from 
    BEMS
     servers in the same cluster (bidirectional)
  • 61617 TCP (SSL) to and from 
    BEMS
     servers in the same cluster (bidirectional)
  • In a 
    SharePoint Online
     environment, 433 to the following:
    • login.microsoftonline.com
    • *.sharepoint.com
  • In an 
    Azure
     Information Protection environment, 443 to the following:
    • login.microsoftonline.com
    • graph.microsoft.com
    • *.aadrm.com 
  • In a 
    Box
     environment, 443 to *.box.com
For installing 
Connect
 for 
Microsoft Lync Server
 or or 
Skype for Business
, if the 
Microsoft Lync Server
 or 
Skype for Business
 database server is using a static port then open that port. The range of ports is necessary only when the 
Microsoft Lync Server
 or 
Skype for Business
 database server is using dynamic ports.
Devices must be able to connect to the 
Apple
 (APNS) and cloud messaging servers to receive push notifications from 
BEMS
. If your 
Wi-Fi
 network restricts outbound access, make sure that the proper outbound ports are open for your devices.
Internal ports
The following ports are used by 
BEMS
:
  • 8080 or 8082 for use by the 
    BlackBerry Connect
     service
  • 8101 for SSH connectivity to 
    BEMS
  • 8443 for 
    Push Notifications
     and 
    Presence
  • 8099 for use by the .NET Component Manager
  • 8060 for use by the Lync Presence Provider (LPP)
  • 6379 for use by 
    Lync
    Presence
     Provider (LPP) in a 
    Microsoft Lync
     or 
    Skype for Business
     environment and 
    BEMS-Core
     in a 
    Cisco Unified Communications Manager
     IM and Presence environments to read and write to the Redis service database.
TCP/IP port access to the database
  • 1433 to the 
    Microsoft SQL Server
     default
Upload 
BEMS
 statistics
For 
BEMS
 to upload the 
BEMS
 statistics to the 
BlackBerry Dynamics NOC
, 
BEMS-Core
 must be able to access the following:
  • https://gwmonitor.good.com
  • TCP port 443 
For more information, visit support.blackberry.com/community to read article 43542 and 36470.
Upload log files
For 
BEMS
 to be able to upload logs, it must have access to the following:
  • https://login.good.com
  • https://gwupload.good.com
  • TCP port 443 
For more information, visit support.blackberry.com/community to read article 43542 and 36470.
1
 A plus sign (+) indicates support for service packs and updates released subsequent to the core version.