Identity Portal in High Availability

Document ID : KB000015868
Last Modified Date : 14/02/2018
Show Technical Document Details

What additional steps are needed for Clustering Identity Portal between 2 nodes? 

  1. Identity Portal nodes use the JGroups messaging protocol to communicate internally.
  2. On any 14.x release of Identity Portal, as long as the Identity Portal nodes are configured to use the same database – the cluster should work out of the box with no additional steps.
    This is achieved by a JGROUPSPING table on the Identity Portal database which manages the node list automatically (e.g. when a node is powered on – it is able to both register itself and detect the other cluster members).
    Each node registers itself twice, for both a “portal” and “hibernate” cluster group name:  

  3. For further reading - I recommend that you review the following Tech note which details a cluster validation procedure and shows the expected configurations in standalone.xml.
    (Please disregard the known issue described in the article – it does not apply to your system as it is related to older version of the Portal - 1.6.2)

**External Links are subject to change and can't be controlled by CA**