Hello all., about the failover capability of AAC or Federation- when primary master fails, I read that AAC, Federation and secondary master would detect that failure and cluster is dynamically reconfigured to promote the secondary master to a primary master for the runtime database cluster service. Does this mean secondary is automatically promoted to primary - like an automatic failover as in DSC or we have to manually configured? 
And one other question - when a federation runtime is restarted is there going to be any user/application impact via webseal authentication?

Thank you!
-Raj

------------------------------
Rajkumar
------------------------------

Raj,

If the primary master fails the read-only copy of the runtime database which resides on the secondary master becomes read-write and nodes within the cluster will automatically failover to this new database server.  When the primary master recovers everything switches back to the database server on the primary master (after the contents of the database on the secondary have been automatically synced back to the master).

Please note however that IBM does not recommend using the embedded runtime database in a production environment.

When the federation runtime is restarted there should be minimal impact on federated SSO flows.

I hope that this helps.

------------------------------
Scott Exton
IBM
Gold Coast
------------------------------

I couldn't get much clarity on this from the knowledge center wording. you finally clarified! Thank you so much!

------------------------------
Rajkumar
------------------------------

Original Message:
Sent: Mon August 17, 2020 01:49 AM
From: Scott Exton
Subject: very basic question on AAC and Federation failure

Raj,

If the primary master fails the read-only copy of the runtime database which resides on the secondary master becomes read-write and nodes within the cluster will automatically failover to this new database server.  When the primary master recovers everything switches back to the database server on the primary master (after the contents of the database on the secondary have been automatically synced back to the master).

Please note however that IBM does not recommend using the embedded runtime database in a production environment.

When the federation runtime is restarted there should be minimal impact on federated SSO flows.

I hope that this helps.

------------------------------
Scott Exton
IBM
Gold Coast
------------------------------