You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the documentation I cannot answer the following questions regarding port numbers:
Micro Integrator Ports
What is the port number of the Micro Integrator Dashboard?
What is the port number for the Micro Integrator? What does "The port of the HTTPS Passthrough transport." mean? Is this the port number I need to expose on the load balancer to access the Micro Integrator?
API-M ports
Which port is responsible for handling the incoming API requests?
Which ports belong to the control plane, traffic manager and gateway if I run them separately?
Is the management console, publisher and developer portal exposed on the same port - 9443?
Traffic Manager
... No ports documented (or, mentioned clearly) ...
Control Plane
... No ports documented (or, mentioned clearly) ...
What will be helpful is a diagram showing which port numbers are used to connect the various components internally (used for internal communication between all components) and which ports expose functionality externally - meaning those ports that I should open on the load balancer to handle incoming traffic.
The text was updated successfully, but these errors were encountered:
Location : https://apim.docs.wso2.com/en/latest/install-and-setup/setup/reference/default-product-ports/
From the documentation I cannot answer the following questions regarding port numbers:
Micro Integrator Ports
API-M ports
Traffic Manager
... No ports documented (or, mentioned clearly) ...
Control Plane
... No ports documented (or, mentioned clearly) ...
What will be helpful is a diagram showing which port numbers are used to connect the various components internally (used for internal communication between all components) and which ports expose functionality externally - meaning those ports that I should open on the load balancer to handle incoming traffic.
The text was updated successfully, but these errors were encountered: