The PPaaS membership scheme is a Carbon membership scheme. It is implemented to discover the Hazelcast cluster of a Carbon server via the topology.
How it works
Once a Carbon server starts it waits for the topology to initialize via the message broker. Next, it queries and gets the the member IP addresses of the given cluster, in the topology. Thereafter the Hazelcast network configuration is initialized for the queried IP addresses. As a result the above Hazelcast instance connects all the members in the cluster. Additionally, when a new member is added to the cluster all the other members are conceded to the new member.
Follow the steps given below to install the PPaaS Membership Scheme:
kernel patch0012Carbon patch. The patch includes a modification in the Carbon Core component, allowing it to add third party membership schemes.
For more information, see WSO2 patch application process.
Copy the following
JARfiles to the /
dropinsdirectory of the Carbon server:
<PPAAS_HOME>/repository/conf/axis2.xmlfile with the following configurations:
The cluster ID parameter needs to contain the cluster ID of the relevant carbon server cluster:
When using Private PaaS with the
private-paasmembership scheme, the
localMemberPortproperty in the
axis2.xmlfile should be updated, because the
private-paasmembership scheme uses the default port, which is 4000.
Update the JNDI configuration of the product to include the message broker configuration for the PPaaS Membership Scheme to connect to. Point the java.naming.provider to the AMQP port of the message broker.