

Changing the Default Ports¶

When you run multiple WSO2 Micro Integrator instances or a cluster of instances on a single server or virtual machine (VM), you must change the default ports to avoid port conflicts.

Micro Integrator ports¶

Default 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).

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

Changing default MI ports¶

There are two ways to manually offset the default ports.

Tip

The internal offset of 10 is overriden by this manual offset. That is, if the manual offset is 3, the default ports will change as follows:
- 8290 -> 8283 (8290 - 10 + 3)
- 8253 -> 8246 (8253 - 10 + 3)
- 9164 -> 9157 (9164 - 10 + 3)
Note that if you manually set an offset of 10 using the following method, you will get the same default ports.

Pass the port offset to the server during startup.
On MacOS/Linux/Centos
```
./micro-integrator.sh -DportOffset=3
```
On Windows
```
micro-integrator.bat -DportOffset=3
```
Open the deployment.toml file (stored in the MI_HOME/conf folder) and add the port offset as follows:
```
[server]
offset = 3
```

EI Analytics ports¶

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

Default Port	Description
`9645`	The port of the EI Analytics Portal.
`9091`	The HTTP port of the management API of EI Analytics.
`9444`	The HTTPS port of the management API of EI Analytics.
`7712`	Thrift SSL port (for the secure transport) on which the client is authenticated when accessing EI Analytics.
`7612`	Thrift TCP port on which EI Analytics receives events from clients

Changing default EI Analytics ports¶

If required, you can manually change the HTTP/HTTPS ports in the deployment.yaml file (stored in EI_ANALYTICS_HOME/conf/server folder) as shown below.

Note

With the default internal port offset, the effective port will be https_port + 1.

HTTPS Port

wso2.transport.http:            
listenerConfigurations:
-
    id: "msf4j-https"
    host: "0.0.0.0"
    port: https_port
    scheme: https

HTTP Port

wso2.transport.http:
listenerConfigurations:
-
  id: "default"
  host: "0.0.0.0"
  port: http_port

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 during 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 <MI_HOME>/conf/log4j2.properties file.

Top