Skip Navigation

BlackBerry UEM
 listening ports

The following is a list of the default ports that the 
BlackBerry UEM
 setup application tries to use when you install the first 
BlackBerry UEM
 instance in your organization’s domain. If a default port is not available, the setup application assigns a port from the range of 12000 to 12999. Some listening ports require the default port and cannot be assigned a different port value (see notes in the table below).
To check the minimum ports that must be open between 
BlackBerry UEM
 instances, or any assigned listening port, see Check the ports assigned by the BlackBerry UEM setup application.
BlackBerry UEM
 uses port 8889 for identity management for 
BlackBerry 10
 devices and to handle SCEP requests for 
BlackBerry Secure Connect Plus
BlackBerry UEM
 must be able to access this port to support devices running 
BlackBerry 10
 OS version 10.3 or later.
Default port
Name in database
Purpose
1610
mdm.snmp.monitoring.udpport
The 
BlackBerry UEM Core
 uses this port to provide SNMP monitoring data.
1611
com.rim.p2e.snmp.monitoring.udpport
SNMP clients can use this port to query monitoring data for 
BlackBerry Secure Connect Plus
.
1612
com.rim.asp.snmp.monitoring.udpport
This is the default port that is used for SNMP monitoring for the 
BlackBerry Secure Gateway
. This port can be changed in the management console.
1613
com.rim.platform.mdm.zed.snmp.monitoring.udpport
This is the default port that is used for SNMP monitoring for the 
BlackBerry Cloud Connector
.
1620
mdm.snmp.eventing.ipv4.udpport
The 
BlackBerry UEM Core
 uses this port to send SNMP notifications in an IPv4 environment.
3202
ec.gme.common.rcp.internal.port
The active 
BlackBerry Affinity Manager
 listens for RCP connections from the 
BlackBerry Dispatcher
 on this port.
3203
ec.gme.common.bipp.bippe.port
The 
BlackBerry Dispatcher
 listens for BIPPe connections from the 
BlackBerry MDS Connection Service
 on this port.
8000
443
ui.port.ssp
ui.port.admin
BlackBerry UEM Self-Service
 and the management console listen for HTTPS connections on this port.
If 443 is not available, the setup application tries to use port 8008. If port 8008 is not available, the setup application assigns a port from the range of 12000 to 12999.
8085
ec.gme.affinityManager.notification.port
The active 
BlackBerry Affinity Manager
 listens on for REST notifications on this port.
8087
com.rim.asp.proxy.listenPort
The primary 
BlackBerry UEM
 components and any 
BlackBerry Connectivity Node
 instances send 
BlackBerry Secure Gateway
 traffic to this port.
8095
tomcat.public.https.port
This port is reserved for secure REST communication between external systems and 
BlackBerry UEM
 plug-ins.
8100
ui.port.healthcheck
The 
BlackBerry UEM Core
 uses this port to check the status of the 
UEM
 management console.
8102
com.rim.p2e.monitoringservice.listenerPort
The 
BlackBerry UEM Core
 uses this port to check the status of 
BlackBerry Secure Connect Plus
.
8103
com.rim.asp.monitoringservice.listenPort
The 
BlackBerry UEM Core
 uses this port to obtain the status of the 
BlackBerry Secure Gateway
. The status is displayed in the management console.
8182
bcs.mgmt.port
The 
BlackBerry UEM Core
 uses this port to obtain the status of the 
BlackBerry Collaboration Service
.
8448
ui.port.internal-api
The 
BlackBerry UEM Core
 and the management console and 
BlackBerry UEM Self-Service
 use this port for internal communication.
8543
The 
BlackBerry UEM
 management console uses this port when an administrator or user logs in to the management console or 
BlackBerry UEM Self-Service
 using certificate-based authentication.
8881
tomcat.bdmi.certicom.https.port
The 
BlackBerry UEM Core
 uses this port to receive management requests for 
BlackBerry 10
 devices. The connection uses mutual authentication with ECC certificates.
8882
tomcat.enrol.http.port
The 
BlackBerry UEM Core
 uses this port to receive enrolment requests for 
BlackBerry 10
 devices.
8883
tomcat.enrol.https.port
The 
BlackBerry UEM Core
 uses this port to receive enrolment requests for 
iOS
Android
, and 
Windows Phone
 devices.
8884
tomcat.bdmi.bouncycastle.https.port
The 
BlackBerry UEM Core
 uses this port to receive management requests for 
iOS
Android
, and 
Windows Phone
 devices. The connection uses mutual authentication with 
RSA
 certificates.
8885
tomcat.applemdm.https.port
The 
BlackBerry UEM Core
 uses this additional port to receive management requests for 
iOS
 devices. The connection uses mutual authentication with 
RSA
 certificates.
8887
tomcat.ipc.https.port
The 
BlackBerry UEM Core
 and the management console use this port for authenticated connections to check the status of 
BlackBerry UEM
 instances.
8889
tomcat.scep.https.port
The 
BlackBerry UEM Core
 uses this port for identity management for 
BlackBerry 10
 devices and to handle SCEP requests for 
BlackBerry Secure Connect Plus
 (the 
BlackBerry UEM Core
 acts as the CA).
BlackBerry UEM
 must be able to access port 8889 to support devices running 
BlackBerry 10
 OS version 10.3 or later.
8890
tomcat.e2c.https.port
When 
BlackBerry Secure Connect Plus
 and the 
BlackBerry Gatekeeping Service
 are installed remotely as part of a 
BlackBerry Connectivity Node
, these components use this port to obtain configuration and authorization data and certificates. The 
BlackBerry Gatekeeping Service
 also uses this port for gatekeeping operations.
8891
tomcat.i2c.https.port
Certain 
BlackBerry Infrastructure
 services use this mutually authenticated port to connect with 
BlackBerry UEM
.
8892
tomcat.e2c.local.https.port
When 
BlackBerry Secure Connect Plus
 and the 
BlackBerry Gatekeeping Service
 are installed with the primary 
BlackBerry UEM
 components, they use this port to obtain configuration and authorization data and certificates. The 
BlackBerry Gatekeeping Service
 also uses this port for gatekeeping operations.
8893
tomcat.bb2fa.local.http.port
This port supports connections to the 
BlackBerry UEM Core
 from the 
BlackBerry 2FA
 app on 
BlackBerry 10
 devices (10.3.2 or earlier).
8894
tomcat.core.health.check.http.port
 The 
BlackBerry UEM Core
 health can be collected on this port. This functionality is available only for deployments of 
BlackBerry UEM Cloud
.
8895
tomcat.i2c.basic.https.port
The 
BlackBerry UEM Core
 uses this port is to receive requests from external services such as 
BEMS
BlackBerry Connect
, and 
BlackBerry Workspaces
8896
tomcat.dynamics.apps.https.port 
BlackBerry UEM
 listens on this port for REST requests from 
BlackBerry Dynamics
 apps. This port uses GDAuthToken-based authentication.
8897
tomcat.bdmi.wp8.https.port
BlackBerry UEM
 listens on this port when you are upgrading 
BlackBerry UEM
 so that it can communicate with 
Windows Phone
 8 devices. For more information, visit support.blackberry.com/community to read article 48098.
8900
winservice.bgs.https.port
The 
BlackBerry Gatekeeping Service
 listens on this secure SSL port.
10080
ec.gme.mdscs.web.server.listenport
The 
BlackBerry MDS Connection Service
 listens for enterprise push data on this HTTP port.
10443
ec.gme.mdscs.web.server.listensslport
The 
BlackBerry MDS Connection Service
 listens for enterprise push data on this HTTPS port. This port is used when you turn on push encryption.
11001
com.rim.p2e.endpoint.listenerPort
BlackBerry Secure Connect Plus
 uses this port to listen for signaling requests from the 
BlackBerry Infrastructure
.
17080
good.proxy.appservers.http.listening.port
BlackBerry Proxy
 listens on this port for connections from application servers.
The default port must be used. The setup application does not assign an alternate port if the default port is not available.
17317
good.control.container.management.listening.port
BlackBerry UEM
 listens on this port for 
BlackBerry Dynamics
 container management data.
The default port must be used. The setup application does not assign an alternate port if the default port is not available.
17433
good.proxy.appservers.ssl.listening.port
BlackBerry Proxy
 listens on this port for SSL connections from application servers.
The default port must be used. The setup application does not assign an alternate port if the default port is not available.
17533
good.proxy.container.ssl.listening.port
BlackBerry Proxy
 listens on this port for SSL connections.
The default port must be used. The setup application does not assign an alternate port if the default port is not available.
18084
tomcat.bws.port
Applications can use this port to send data to the 
BlackBerry Web Services
.
38082
com.rim.platform.mdm.core.proxy.adam.endpoint.port
The 
BlackBerry UEM Core
 listens on this port to route email notification traffic through the 
BlackBerry Infrastructure
 to the APNs for 
iOS
 devices.
38083
com.rim.platform.mdm.core.proxy.direct.endpoint.port
The 
BlackBerry UEM Core
 listens on this port for migration requests when you move devices from 
BES10
 to 
BlackBerry UEM
.
38086
com.rim.platform.mdm.core.proxy.apns.endpoint.port
Your organization’s TCP proxy server or the 
BlackBerry Router
 listens on this port for data that 
BlackBerry UEM
 sends to the APNs.
38087
com.rim.platform.mdm.core.proxy.cirr.endpoint.port
The 
BlackBerry UEM Core
 listens on this port to route traffic for 
BlackBerry Enterprise Identity
 through the 
BlackBerry Infrastructure
.