Identity Portal in High Availability
search cancel

Identity Portal in High Availability

book

Article ID: 15868

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal

Issue/Introduction

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

Environment

Release: 14.X
Component: SIGMA / Identity Portal

Resolution

  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:  

Additional Information

There should be only twice as many entries in JGROUPSPING table as there are Identity Portal nodes in the cluster.

Attachments

1558717919835000015868_sktwi1f5rjvs16uqj.jpeg get_app