Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Minor change.

...

Tip
  • In this guide, the IP of the first Message Broker (MB) node is referred to as https://xxx.xxx.xxx.xx1 and the IP of the second MB node is referred to as https://xxx.xxx.xxx.xx2.
  • If you want to test out clustering in a development environment using the same server, you need to port offset one of your ESB nodes.


    Follow the step given below:
    Specify the port offset value in the <EI_HOME>/conf/carbon.xml file.

    Note

    This is not recommended for production environments. Change all ports used in your configurations based on the offset value if you are setting a port offset for the specific node.

    For more information on the default ports of WSO2 Enterprise Integrator, see the WSO2 administration guide.

    Expand
    titleClick here for more information on configuring the port offset.

    When you run multiple products/clusters or multiple instances of the same product on the same server or virtual machines (VMs), change their default ports with an offset value to avoid port conflicts. An offset defines the number by which all ports in the runtime (e.g., HTTP(S) ports) are increased. For example, if the default HTTP port is 9763 and the offset is 1, the effective HTTP port will change to 9764. For each additional product instance, set the port offset to a unique value. The offset of the default ports is zero.

    The port value will automatically increase as shown in the Port Value column in the following table, allowing all five WSO2 product instances or servers to run on the same machine.

    WSO2 product instance

    Port Offset

    Port Value

    WSO2 server 1

    0

    9443

    WSO2 server 2

    1

    9444

    WSO2 server 3

    2

    9445

    WSO2 server 4

    3

    9446

    WSO2 server 5

    4

    9447

    Example:

    Code Block
    languagexml
    <Ports>
    	...
    	<Offset>5</Offset>
    	...
    </Ports>

...