Migrating cluster discovery settings
To simplify future upgrades, you should migrate the cluster discovery settings in the tcp.xml
file to the jgroups.properties
file.
About this task
When you upgrade, PingFederate can set the default configuration of any new features in the supported discovery protocols. Because of this, you should use the <pf_install>/pingfederate/bin/jgroups.properties
file to enable and configure cluster discovery settings. For example, if NATIVE_S3_PING
gets a new discovery protocol configuration, a PingFederate upgrade could automatically add the following line to jgroups.properties
as a reasonable default, letting you take advantage of the new configuration:
pf.cluster.NATIVE_S3_PING.new_configuration=reasonable-default-configuration-value
For more information, see Dynamic cluster discovery.
The
|
The examples in the following table compare the syntax of cluster discovery settings in the tcp.xml
file and the jgroups.properties
file.
Examples intcp.xml | Examples injgroups.properties |
---|---|
<TCPPING initial_hosts="${pf.cluster.tcp.discovery.initial.hosts}" return_entire_cache="true" port_range="0"/> |
pf.cluster.TCPPING.initial_hosts=${pf.cluster.tcp.discovery.initial.hosts} pf.cluster.TCPPING.return_entire_cache=true pf.cluster.TCPPING.port_range=0 |
<org.jgroups.aws.s3.NATIVE_S3_PING region_name="us-east-1" bucket_name="[...]" endpoint="[...]" remove_all_data_on_view_change="true" write_data_on_find="true"/> |
pf.cluster.NATIVE_S3_PING.region_name=us-east-1 pf.cluster.NATIVE_S3_PING.bucket_name= pf.cluster.NATIVE_S3_PING.endpoint= pf.cluster.NATIVE_S3_PING.remove_all_data_on_view_change=true pf.cluster.NATIVE_S3_PING.write_data_on_find=true |
<dns.DNS_PING dns_query="[service name].default.svc.cluster.local" /> |
pf.cluster.DNS_PING.dns_query=[service name].default.svc.cluster.local |
To migrate the cluster discovery settings from the tcp.xml
file to the jgroups.properties
file:
Steps
-
Open the
<pf_install>/pingfederate/bin/jgroups.properties
file and the<pf_install>/pingfederate/
server/default/conf/tcp.xml
file in a text editor. -
In the
jgroups.properties
file:-
Specify the cluster discovery protocol.
For example:
pf.cluster.discovery.protocol=NATIVE_S3_PING
-
Specify the values for the cluster discovery protocol parameters that correspond with the values in the
tcp.xml
file.For example:
pf.cluster.NATIVE_S3_PING.region_name=us-east-1 pf.cluster.NATIVE_S3_PING.bucket_name= pf.cluster.NATIVE_S3_PING.endpoint= pf.cluster.NATIVE_S3_PING.remove_all_data_on_view_change=true pf.cluster.NATIVE_S3_PING.write_data_on_find=true
-
-
In the
tcp.xml
file, insert the${DISCOVERY_TAG}
and remove the cluster discovery protocol settings.Do not remove other settings from the
tcp.xml
file. -
Repeat these steps for the other PingFederate nodes in the cluster.