/
Default Product Ports
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links' is unknown.

Default Product Ports

Dec 15, 2017

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

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.

Common ports

The following ports are common to all WSO2 products that provide the given feature. Some features are bundled in the WSO2 Carbon platform itself and therefore are available in all WSO2 products by default.

1 Common portsPipe2 Management console portsPipe3 LDAP server portsPipe4 KDC portsPipe5 JMX monitoring portsPipe6 Clustering portsPipe7 Random ports

Management console ports

WSO2 products that provide a management console use the following servlet transport ports:

WSO2 Enterprise Integrator (WSO2 EI) uses the following ports to access the management console:

  • 9443 - HTTPS servlet transport for the ESB runtime (the default URL of the management console is https://localhost:9443/carbon)

  • 9445 - HTTPS servlet transport for the EI-Business Process runtime (the default URL of the management console is https://localhost:9445/carbon)

  • 9444 - Used for the EI-Analytics management console

LDAP server ports

Provided by default in the WSO2 Carbon platform.

  • 10389 - Used in WSO2 products that provide an embedded LDAP server

KDC ports

  • 8000 - Used to expose the Kerberos key distribution center server

JMX monitoring ports

WSO2 Carbon platform uses TCP ports to monitor a running Carbon instance using a JMX client such as JConsole. By default, JMX is enabled in all products. You can disable it using <PRODUCT_HOME>/repository/conf/etc/jmx.xml file.

  • 11111 - RMIRegistry port. Used to monitor Carbon remotely

  • 9999 - RMIServer port. Used along with the RMIRegistry port when Carbon is monitored from a JMX client that is behind a firewall

Clustering ports

To cluster any running Carbon instance, either one of the following ports must be opened.

  • 45564 - Opened if the membership scheme is multicast

  • 4000 - Opened if the membership scheme is wka

Random ports

Certain ports are randomly opened during server startup. This is due to specific properties and configurations that become effective when the product is started. Note that the IDs of these random ports will change every time the server is started.

  • A random TCP port will open at server startup because of the -Dcom.sun.management.jmxremote property set in the server startup script. This property is used for the JMX monitoring facility in JVM.

  • A random UDP port is opened at server startup due to the log4j appender (SyslogAppender), which is configured in the <PRODUCT_HOME>/repository/conf/log4j.properties file.

Product-specific ports

Some products open additional ports. 

1 API ManagerPipe2 BPSPipe3 Data Analytics ServerPipe4 Complex Event ProcessorPipe5 Elastic Load BalancerPipe6 ESBPipe7 Enterprise IntegratorPipe8 Identity ServerPipe9 Message BrokerPipe10 Machine LearnerPipe11 Storage ServerPipe12 Enterprise Mobility ManagerPipe13 IoT Server
API Manager

  • 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.

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.

BPS

  • 2199 - RMI registry port (datasources provider port)

Data Analytics Server

Given below are the specific ports used by WSO2 DAS.

Ports inherited from WSO2 BAM

WSO2 DAS inherits the following port configurations used in its predecessor, WSO2 Business Activity Monitor (BAM).

  • 7711 - Thrift SSL port for secure transport, where the client is authenticated to use WSO2 DAS.

  • 7611 - Thrift TCP port where WSO2 DAS receives events from clients.

Ports used by the Spark Analytics Engine

The Spark Analytics engine is used in 3 separate modes in WSO2 DAS as follows.

  • Local mode

  • Cluster mode

  • Client mode

Default port configurations for these modes are as follows.

For more information on these ports, go to Apache Spark Documentation.

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

  • Ports available for the cluster mode 
    The following ports are available only for the cluster mode.

Complex Event Processor

  • 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

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.