How to determine which node of a WildFly cluster should be designated as the Systems Operation Node (SON) in RSA Identity Governance & Lifecycle
Originally Published: 2020-04-01
Article Number
Applies To
RSA Version/Condition: 7.1.x, 7.1.x, 7.2.x
Platform/Application Server: WildFly
Issue
Resolution
This is best illustrated with an example. The following example illustrates this concept with a two-node cluster:
Scenario 1: The SON is on the domain controller.
Node 1: Domain controller and SON.
Node 2: General node.
Node 2: General node.
If Node 1 goes down, the entire application becomes unavailable because a cluster cannot operate without a domain controller.
If Node 2 goes down, Node 1 will stay fully functional because it is the SON.
If Node 2 goes down, Node 1 will stay fully functional because it is the SON.
Scenario 2: The SON is on a general node.
Node 1: Domain controller.
Node 2: General node and SON.
Node 2: General node and SON.
If Node 1 goes down, the entire application becomes unavailable because a cluster cannot operate without a domain controller.
If Node 2 goes down, Node 1 will stay functional but with limited functionality since the SON will be gone. No data collections or AFX requests will process.
If Node 2 goes down, Node 1 will stay functional but with limited functionality since the SON will be gone. No data collections or AFX requests will process.
Related Articles
Unable to delete Object while connected to the HOST node in a cluster setup in RSA Governance & Lifecycle 6Number of Views Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle 518Number of Views What is the Change Request Pending Submission State in RSA Identity Governance & Lifecycle 193Number of Views The RSA Authentication Manager 8.x RSA RADIUS Server Operations Console Service Stops with a FAILED State. 516Number of Views Approval workflow slow or stuck in decision node in RSA Governance & Lifecycle 391Number of Views
Don't see what you're looking for?