Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added Traffic Manager related ports

This page describes the default ports that are used for each WSO2 product when the port offset is 0.

Warning

Note that it is recommended to disable the HTTP transport in an API Manager production setup. Using the Bearer token over HTTP is a violation of the OAuth specification and can lead to security vulnerabilities.

Table of Contents
maxLevel3
minLevel3

...

  • 5672 - Used by the internal Message Broker. 
  • 7611 - Authenticate data published when Thrift data publisher is used for throttling.
  • 7612 - Publish Analytics to the API Manager Analytics server.
  • 7711 - Port for secure transport when Thrift data publisher is used for throttling.
  • 7711 + Port offset of the APIM Analytics Server - Thrift SSL port for secure transport when publishing analytics to the API Manager Analytics server.
  • 8280, 8243 - NIO/PT transport ports.
  • 9611 - Publish data to the Traffic Manager. Required when binary data publisher for throttling.
  • 9711 - Authenticate data published to the Traffic Manager. Required when binary data publisher for throttling.
  • 10397 - Thrift client and server ports.
  • 9099 - Web Socket ports.
  • Traffic Manager related ports
    • 9160 - Cassandra port on which Thrift listens to clients
    • 7711 - Thrift SSL port for secure transport, where the client is authenticated to WSO2 CEP
    • 7611 - Thrift TCP port to receive events from clients to WSO2 CEP
    • 11224 - Thrift TCP port for HA management of WSO2 CEP
Note

If you change the default API Manager ports with a port offset, most of its ports will be changed automatically according to the offset except a few exceptions described in the APIM Manager documentation.

...

  • Ports available for all modes 
    The following ports are available for all three modes explained above. 

    DescriptionPort number
    spark.ui.port4040
    spark.history.ui.port18080
    spark.blockManager.port12000
    spark.broadcast.port12500
    spark.driver.port13000
    spark.executor.port13500
    spark.fileserver.port14000
    spark.replClassServer.port14500
  • Ports available for the cluster mode 
    The following ports are available only for the cluster mode.

    DescriptionPort number
    spark.master.port7077
    spark.master.rest.port6066
    spark.master.webui.port8081
    spark.worker.port11000
    spark.worker.webui.port11500
Complex Event Processor
Note

The following ports are also applicable when clustering and deploying the Traffic Manager in a distributed environment in WSO2 API Manager.

  • 9160 - Cassandra port on which Thrift listens to clients
  • 7711 - Thrift SSL port for secure transport, where the client is authenticated to CEP
  • 7611 - Thrift TCP port to receive events from clients to CEP
  • 11224 - Thrift TCP port for HA management of CEP

...

The following ports need to be opened for Android and iOS devices so that it can connect to Google Cloud Messaging (GCM)/Firebase Cloud Messaging (FCM) and APNS (Apple Push Notification Service) and enroll to WSO2 EMM.

Android:
The ports to open are 5228, 5229 and 5230. GCM/FCM typically only uses 5228, but it sometimes uses 5229 and 5230.
GCM/FCM does not provide specific IPs, so it is recommended to allow the firewall to accept outgoing connections to all IP addresses contained in the IP blocks listed in Google's ASN of 15169. 

iOS:

  • 5223 - TCP port used by devices to communicate to APNs servers
  • 2195 - TCP port used to send notifications to APNs
  • 2196 - TCP port  used by the APNs feedback service
  • 443 - TCP port used as a fallback on Wi-Fi, only when devices are unable to communicate to APNs on port 5223
    The APNs servers use load balancing. The devices will not always connect to the same public IP address for notifications. The entire 17.0.0.0/8 address block is assigned to Apple, so it is best to allow this range in the firewall settings. 

API Manager:

Info

The following WSO2 API Manager ports are only applicable to WSO2 EMM 1.1.0 onwards.

...