Page Comparison

In PPaaS, the backend members in the instances, such as in a Virtual Machine (VM) setup the VM instances and in a Kubernetes setup the Docker instances, are fronted by a Load Balancer with the use of proxies. The proxyPort property is used to define the port of the Load Balancer. When the Load Balancer receives application traffic, it will route the traffic to the members (worker nodes) in the respective clusters, based on their resource availability.

...

 "portMapping": [
        {
            "name": "mgt-http",
            "protocol": "http",
            "port": 9763,
            "proxyPort": 80
        },
        {
            "name": "mgt-https",
            "protocol": "https",
            "port": 9443,
            "proxyPort": 443
        }
    ],

 "portMapping": [
        {
            "name": "mgt-http",
            "protocol": "http",
            "port": 9763,
            "proxyPort": 0,
            "kubernetesPortType": "NodePort"
        },
        {
            "name": "mgt-https",
            "protocol": "https",
            "port": 9443,
            "proxyPort": 0,
            "kubernetesPortType": "NodePort"
        }
    ],

 "portRange": {
        "upper": "32767",
        "lower": "30000"
    },

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

2. Anchor
   step2 step2

   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:

      Code Block
      vim /etc/hosts/

   2. Define mapping for Map all the hostnames against the available LB IPs in the /etc/hosts/ file and save the file.
      <LB_IP> <HOSTNAME> 
      Example:

      Code Block
      172.17.8.103 wso2as-521-application.mgt.as.wso2.org

      Info
      Each LB IP can have more than one hostname mappings. However, these mappings need to be defined separately in the /etc/hosts/ file.

3. Optionally, add domain mapping if required.

   Expand
   title Click here for instructions...

   
    

   Include Page Adding Domain Mappings Adding Domain Mappings For more information, see Working with Domain Mappings.

4. Use the following URL format to access the WSO2 service (e.g., the ESB service):

   Localtabgroup

   Localtab active true title EC2 Panel Code Block http://<INSTANCE_HOSTNAME>:<LB_PROXY_PORT>/<CONTEXT_PATH> <LOAD<INSTANCE_BALANCER_IP> - This will refer to the Load Balancer IP to which the cluster hostname was mapped to as explained in step 2HOSTNAME> - The hostname of the cluster. <LB_PROXY_PORT> - The LB proxy port to which the port was mapped to as explained in Prerequisites. Example: Code Block  http://wso2as-521-application.mgt.as.wso2.org:80/index.php Localtab title Kubernetes Panel Code Block http://<LOAD<INSTANCE_BALANCER_IP>HOSTNAME>:<PROXY_SERVICE_PORT>/<CONTEXT_PATH> <LOAD <INSTANCE_ BALANCER_IP> - This will refer to the Load Balancer IP to which the cluster hostname was mapped to as explained in step 2 HOSTNAME> - The hostname of the cluster. <PROXY_SERVICE_PORT> - 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. Example: Code Block http://172.17.8.103wso2as-521-application.mgt.as.wso2.org:30000/index.php Info Currently, it is not possible to query auto generated Kubernetes proxy service ports via the Stratos API. However, they can be found on the PPaaS server log.