memoryoptions and upgrade
Upgrade paths behave differently when changes are executed based on the recommendations and execution of the memoryoptions
utility tool.
Depending upon the selected tool and whether the jvm-memory.options
file exists in the source installation, the expected behavior of the memoryoptions
utility differs. In general, the jvm-memory.options
file from the source installation is preserved without new recommended values.
You should not use the |
See the following table for information regarding expected behaviors.
Upgrade path | Expected behavior when thejvm-memory.optionsfile does not exist in the source installation |
---|---|
PingFederate installer for Windows |
|
PingFederate Upgrade Utility (upgrade.bat) |
The upgrade utility creates a new PingFederate installation based on the source installation and the PingFederate product distribution The default
|
PingFederate Upgrade Utility (upgrade.sh) |
The upgrade utility creates a new PingFederate installation based on the source installation and the PingFederate product distribution The default The JVM options set in the default The default JVM options are conservative. For most deployment scenarios using various physical or virtual resources, run the As a result of the execution of the |
Upgrade path | Expected behavior when thejvm-memory.optionsfile exists in the source installation | ||
---|---|---|---|
PingFederate installer for Windows |
|
||
PingFederate Upgrade Utility (upgrade.sh) |
|
||
PingFederate Upgrade Utility (upgrade.bat) |
The upgrade utility
creates a new PingFederate installation based on the source installation and copies the
|