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.
You must perform the following steps in all nodes of a cluster.
To configure Ignite1. 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.311=-Dportal.server.cache.distributed.cluster.peers.1=<devPortal2_hostname>:47500..47509
wrapper.java.additional.311=-Dportal.server.cache.distributed.cluster.peers.2=<devPortal3_hostname>:47500..47509
3. Click Save.
The configuration is saved.
4. Start all Developer Portal nodes one after the other.