Unknown macro: {next_previous_link3}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Current »

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. The proxyPort property is used to define the port of the Load Balancer. When the Load Balancer receives traffic, it will route the traffic to the members (worker nodes) in the respective clusters, based on their resource availability.

PPaaS uses a Proxy Service for Kubernetes as there are different service port types with different port ranges. Therefore, when using Kubernetes, you need to set the proxyPort to zero in the Cartridge definition and define the Kubernetes proxy service port range as 30000 - 32767 using the portRange property in the Kubernetes cluster definition.

Follow the instructions below to access the WSO2 service:

The URL to access a service depends on the port mapping (VM) and port range (Docker) that you defined in the cartridge definition and the Kubernetes cluster definition respectively.

 Click here for more information...

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 is being used with the WSO2 product cartridge. 
The following examples illustrate how to set unique proxy ports for each port that is used with the cartridge.

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

  3. Optionally, add domain mapping if required.

     Click here for instructions...

    You can add domain mappings using the CLI tool or REST API as shown below:

    As the signup process takes place automatically when a single tenant application is deployed, domain mapping can be added straight after the application is deployed. However, if domain mapping is being added to a multi-tenant application, after the application is deployed, ensure to first carryout the application sign up process before adding the domain mappings.

     


    Sample domain mapping JSON

    {
      "domainMappings": [
        {
          "cartridgeAlias": "tomcat",
          "domainName": "abc.com",
          "contextPath": "/abc/app"
        }
      ]
    }

    For more information, see Working with Domain Mappings.

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

  • No labels