Default Product Ports¶

This page describes the default ports used by WSO2 Micro Integrator.

Note

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

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

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.