Accessing the WSO2 Service

In a VM setup the VM instances will be fronted by a Load Balancer in PPaaS. Whereas, in Kubernetes the Docker instances will be fronted by a proxy service, which is created for each service cluster. When the Load Balancer or the Proxy service receive application traffic, it will route the traffic to the members (worker nodes) in the respective clusters, based on their resource availability.

When using Kubernetes, you need to define the Kubernetes proxy service port range as 30000 - 32767 in the Kubernetes cluster definition, as there are different service port types with different port ranges in Kubernetes. Therefore, when using Kubernetes, the first proxy service that gets created will be assigned to port 30000, and the subsequent proxy services that get created will be assigned port values in order incrementally. Port ranges are not applicable when using PPaaS on Virtual Machines.

Follow the instructions below to access the WSO2 service:

Prerequisites

Define port mapping.
When creating the dependent artifacts that are needed to deploy an application, you need to define port mapping, in the cartridge definition JSON, for each port that will be used with the WSO2 product cartridge.
The following examples illustrate how unique proxy ports can be set for ports that are used with the cartridge.

Identify the Load Balancer IP and the hostname of the each of the clusters that are available in the deployed application.
For more information, see Getting the Runtime Topology of an Application.
Map the cluster hostname with one of the Load Balancer IPs.
Each Load Balancer IP refers to the IP of a node.
1. Open the /etc/hosts/ file.
  Example:
  If you are using Vim, which is a text editor, you can open the file in the terminal as follows:
```
vim /etc/hosts/
```
2. Define mapping for all the hostnames against the available LB IPs in the /etc/hosts/ file and save the file.
  <LB_IP> <HOSTNAME>
  Example:
```
172.17.8.103 wso2as-521-application.mgt.as.wso2.org
```
  Each LB IP can have more than one hostname mappings. However, these mappings need to be defined separately in the /etc/hosts/ file.
Use the following URL format to access the WSO2 service (e.g., the ESB service):

- <LOAD_BALANCER_IP> - This will refer to the Load Balancer IP to which the cluster hostname was mapped to as explained in step 2.
- <LB_PROXY_PORT> - The LB proxy port to which the port was mapped to as explained in Prerequisites.