Default Product Ports

This page describes the default ports used by each runtime of WSO2 API Manager.

Note

If you change the default runtime ports, most of the runtime ports change automatically based on the offset.

API-M ports

Listed below are the ports used by the API-M runtime when the port offset is 0.

Info

See the instructions on changing the default API-I ports.

Default Port Description
9443 Port of the HTTPS servlet transport. The default HTTPS URL of the management console is https://localhost:9443/carbon.
9763 Port of the HTTP servlet transport. The default HTTP URL of the management console is http://localhost:9763/carbon.
10389 Port of the embedded LDAP server.
5672 Port of the internal Message Broker of the API-M runtime.
8280 Port of the Passthrough or NIO HTTP transport.
8243 Port of the Passthrough or NIO HTTPS transport.
9611 TCP port to receive throttling events. This is required when the binary data publisher is used for throttling.
9711 SSL port of the secure transport for receiving throttling events. This is required when the binary data publisher is used for throttling.
9099 Web Socket ports.
8000 Port exposing the Kerberos key distribution center server.
45564 Opened if the membership scheme is multicast.
4000 Opened if the membership scheme is WKA.
11111 The RMIRegistry port. Used to monitor Carbon remotely.
9999 The MIServer port. Used along with the RMIRegistry port when Carbon is monitored from a JMX client that is behind a firewall

Micro Integrator ports

By default, the Micro Integrator is internally configured with a port offset of 10. Listed below are the ports that are effective in the Micro Integrator by default (due to the internal port offset of 10).

Info

See the instructions on changing the default MI ports.

Default Port Description
8290 The port of the HTTP Passthrough transport.
8253 The port of the HTTPS Passthrough transport.
9201 The HTTP port of the Management API of WSO2 Micro Integrator.

Configuring the default HTTP port
If required, you can manually change the HTTP port in the deployment.toml file (stored in the MI_HOME/conf folder) as shown below.

[mediation]
internal_http_api_port = http_port

Note: With the default internal port offset, the effective port will be http_port + 10.
9164 The HTTPS port of the Management API of WSO2 Micro Integrator.

Configuring the default HTTPS port
If required, you can manually change the HTTPS port in the deployment.toml file (stored in the MI_HOME/conf folder) as shown below.

[mediation]
internal_https_api_port = https_port

Note: With the default internal port offset, the effective port will be https_port + 10.

Streaming Integrator Ports

Listed below are the default ports used by the Streaming Integrator runtime and the Streaming Integrator Tooling runtime. The defualt port offset in these runtimes are 0 and 3 respectively.

Info

See the instructions on changing the default SI ports.

  • Thrift and Binary ports:

    Default Port Description
    7611 Thrift TCP port to receive events from clients.
    7711 Thrift SSL port for the secure transport where the client is authenticated.
    9611 Binary TCP port to receive events from clients.
    9711 Binary SSL port for the secure transport where the client is authenticated.

  • Management ports:

    Streaming Integrator runtime

    Default Port Description
    9090 HTTP netty transport.
    9443 HTTPS netty transport.

    Streaming Integrator Tooling runtime:

    Default Port Description
    9390 HTTP netty transport.
    9743 HTTPS netty transport.

  • Streaming Integrator clustering ports:

    Minimum High Availability (HA) Deployment

    Default Port Description
    9090 HTTP netty transport.
    9090 The port of the node for the advertisedPort parameter in the liveSync section. The HTTP netty transport port is considered the default port.
    9443 HTTPS netty transport.

    Multi Datacenter High-Availability Deployment

    In addition to the ports used in clustering setups (i.e. a minimum HA deployment or a scalable cluster), the following port is required:

    Default Port Description
    9092 Ports of the two separate instances of the broker deployed in each data center (e.g., bootstrap.servers= 'host1:9092, host2:9092'. The default is9092` where the external kafka servers start.).

Random ports

Certain ports are randomly opened during server startup. This is due to the 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 the -Dcom.sun.management.jmxremote property is 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/log4j2.properties file.

Top