After you configure or reconfigure the console, you can also update cluster nodes by downloading a configuration archive from the <pf_install>/pingfederate/server/default/data/drop-in-deployer directory on each cluster node or provisioning-failover server.screen and then deploying it (either manually or via a scripted process) to the
A configuration archive contains the same information sent during the configuration push from the administrative console described in the previous section. However, this option provides for scheduling and scripting cluster synchronization.
Runtime state-management services
If you have configured one of the following runtime state-management services on the engine nodes, you must migrate the configuration files (located in the <pf_install>/pingfederate/server/default/conf directory) to the engine nodes manually.
|RPC-based service implementation
|Account Locking Service
|Artifact-Message Persistence and Retrieval Service
|Assertion Replay Prevention Service
|IdP Session Registry Service
|Inter-Request State-Management (IRSM) Service
|Back-Channel Session Revocation Service
|SP Session Registry Service