Developer Portal 10.11 | Using Developer Portal | Configuring High Availability | Configuring High Availability | Configuring Ignite
 
Configuring Ignite
Developer Portal uses the embedded Ignite-core library to setup a cluster, without having to start any external runtime.
In Ignite terminology:
*a single Developer Portal with embedded ignite is an Ignite server node,
*together they form an Ignite cluster,
*and it is a stateless cluster as Developer Portal does not require persistence for its distributed caches.
Ignite cluster discovery
Each Ignite server node has to open a discovery port. Through this port, the nodes discover each other and form the cluster, and they detect the nodes that are added or removed from the cluster.
Each node in the cluster must be configured with a list of initial host names. These nodes will contact each other via the discovery port and form a cluster. Later more nodes can be added to the cluster, and even if their host names are not part of the initial host name list they can join the cluster by contacting one of the initial hosts, and then their host names will be communicated around the cluster.
Pre-requisites
Ensure that you have opened up the following ports:
*47500 - 47509. These ports enable the discovery of Ignite nodes.
*47100 - 47200. These ports enable communication between Ignite nodes.
If you have blocked the access of the port 47100 by any another application in the system, you need to open up the complete series. You can just open up the 47100 port. For more info refer https://ignite.apache.org/docs/latest/clustering/network-configuration.
*It is recommended that you do not open the following local ports when you system is behind firewall:
*10800. Enables communication between the thin client and the Ignite cluster.
*11211. Enables communication between the JDBC client and the Ignite database.
*47400. Enables node discovery via the UDP port.
Perform the following steps in all nodes of a cluster.
*To configure Ignite
1. Open the dpo_wrapper.conf file from the location, SAGInstallDir/profiles/CTP/configurations/.
2. Add the following entries:
wrapper.java.additional.310=-Dportal.server.cache.distributed.enabled=true
wrapper.java.additional.311=-Dportal.server.cache.distributed.cluster.peers.0=<devPortal1_hostname>:47500..47509
wrapper.java.additional.312=-Dportal.server.cache.distributed.cluster.peers.1=<devPortal2_hostname>:47500..47509
wrapper.java.additional.313=-Dportal.server.cache.distributed.cluster.peers.2=<devPortal3_hostname>:47500..47509
Note:
The values 311, 312, and 313 mentioned in the code block need not be the same. They are sample values only. You can specify numbers of your choice. As a recommended practice, find the biggest number in the dpo_wrapper.conf file and start incrementing the numbers for the next entries as and when you add them to the file. For example, if you see 2008 as the biggest value, then start assigning 2009, 2010 and so on to further entries.
3. Click Save.
The configuration is saved.
4. Start all Developer Portal nodes one after the other.