Decision Insight 20210301 (Latest) Save PDF Selected topic Selected topic and subtopics All content For the list of all supported Decision Insight downloads and releases, see the Downloads page. Activate HA/DR on existing nodes If you have a standalone or a Primary/Replica cluster, you can activate high availability (HA) / disaster recovery (DR) by following the steps below. We assume that you already know how to install and upgrade Axway Decision Insight (DI) on one node or more. If you do not, start by reading Installation. 1. Stop the cluster All the nodes of the cluster must be stopped in order to be reconfigured. 2. Migrate the nodes to a release supporting the feature The HA cluster functionality is available from release 20190722 onward. Installers can be downloaded from Axway Support Portal or from Decision Insight supported downloads and releases. For more information about how to upgrade a cluster, see Upgrade clusters. 3. Install a backup node First, retrieve the encryption key of your main node. Then install a node of type Replica and make sure the node configuration matches the main node and uses the same encryption key(number of partition, cluster id, ...). Once you have installed your replica node, turn your replica node into a backup node by updating the platform.properties with the following settings. com.systar.electron.type HA Activates the HA feature. com.systar.electron.host Host / IP of the local host Used to open the internode communication. com.systar.electron.ha.host Host / IP of the remote main host Used to connect to main node. com.systar.electron.ha.token Password of your choice Access token used to secure the cluster manager API. Once started, the backup node will automatically download the latest checkpoint from the main node. If you also want to backup locked checkpoints, you will have to manually copy them from the main node to the backup node. 4. Reconfigure main node Configure your STANDALONE or PRIMARY node and specify the following settings in the platform.properties file. com.systar.electron.type HA Activates the HA feature. com.systar.electron.host Host / IP of the local host Used to open the internode communication. com.systar.electron.ha.host Host / IP of the remote backup host Not used by main node, but mandatory since main and backup nodes can switch their roles. com.systar.electron.ha.token Password of your choice Access token used to secure the cluster manager API.It is recommanded to use the same token for all HA nodes. 5. Restart all nodes 6. Switch main node A HA node always starts as backup. Use the Switch backup to main procedure on main node. Related Links
For the list of all supported Decision Insight downloads and releases, see the Downloads page. Activate HA/DR on existing nodes If you have a standalone or a Primary/Replica cluster, you can activate high availability (HA) / disaster recovery (DR) by following the steps below. We assume that you already know how to install and upgrade Axway Decision Insight (DI) on one node or more. If you do not, start by reading Installation. 1. Stop the cluster All the nodes of the cluster must be stopped in order to be reconfigured. 2. Migrate the nodes to a release supporting the feature The HA cluster functionality is available from release 20190722 onward. Installers can be downloaded from Axway Support Portal or from Decision Insight supported downloads and releases. For more information about how to upgrade a cluster, see Upgrade clusters. 3. Install a backup node First, retrieve the encryption key of your main node. Then install a node of type Replica and make sure the node configuration matches the main node and uses the same encryption key(number of partition, cluster id, ...). Once you have installed your replica node, turn your replica node into a backup node by updating the platform.properties with the following settings. com.systar.electron.type HA Activates the HA feature. com.systar.electron.host Host / IP of the local host Used to open the internode communication. com.systar.electron.ha.host Host / IP of the remote main host Used to connect to main node. com.systar.electron.ha.token Password of your choice Access token used to secure the cluster manager API. Once started, the backup node will automatically download the latest checkpoint from the main node. If you also want to backup locked checkpoints, you will have to manually copy them from the main node to the backup node. 4. Reconfigure main node Configure your STANDALONE or PRIMARY node and specify the following settings in the platform.properties file. com.systar.electron.type HA Activates the HA feature. com.systar.electron.host Host / IP of the local host Used to open the internode communication. com.systar.electron.ha.host Host / IP of the remote backup host Not used by main node, but mandatory since main and backup nodes can switch their roles. com.systar.electron.ha.token Password of your choice Access token used to secure the cluster manager API.It is recommanded to use the same token for all HA nodes. 5. Restart all nodes 6. Switch main node A HA node always starts as backup. Use the Switch backup to main procedure on main node.