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. See the following table for information regarding expected behaviors.
Upgrade path | Expected behavior when the jvm-memory.options file 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 .zip file.
The default
jvm-memory.options file becomes part of the new installation as the
upgrade utility extracts files from the PingFederate product distribution
.zipfile.
|
PingFederate Upgrade Utility (upgrade.sh) |
|
Upgrade path | Expected behavior when the jvm-memory.options file 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 jvm-memory.options file from the source installation to the new
installation.
|