Configuration-archive deployment
Uploading configuration archives is an alternate method of copying configurations to clustered PingFederate servers.
After you configure or reconfigure the console, you can also update cluster nodes by downloading a configuration archive from the System → Server → Configuration Archive window and then deploying it either manually or using a scripted process to the <pf_install>/pingfederate/server/default/data/drop-in-deployer directory on each cluster node or provisioning-failover server.
To enable automatic replication of a configuration data archive to server nodes, you must enable the replicate.after.drop.in.deploy attribute in the cluster-config-replication.conf file to true. Learn more in Upgrading configuration data.
|
If you use the drop-in deployment process:
|
A configuration archive contains the same information sent during the configuration push from the administrative console.
Runtime state-management services
If you have configured one of the following runtime state-management services on the engine nodes, you must manually migrate the configuration files to the engine nodes. The configuration files are locted at <pf_install>/pingfederate/server/default/conf
| Configuration file | RPC-based service implementation |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|