-r
switch to disable configuration replication on the
target version.
For more information on upgrading PingAccess, see Upgrade PingAccess.
Before beginning the upgrade process, make sure you have:
- Ensured PingAccess is running
- Downloaded the PingAccess distribution .zip file or the incremental update bundle and extracted it.
- The PingAccess license, if you are switching to a new license file
- Administrator credentials
- Basic Authentication enabled
Any warnings or errors encountered are recorded in log/upgrade.log, as well as on the screen while the utility is running. The upgrade uses an exit code of 0 to indicate a successful upgrade and an exit code of 1 to indicate failure.
If you are upgrading from version 4.3 or earlier, and your installation uses custom plugins, they will need to be rebuilt against the new (5.0) SDK. You will then run the upgrade utility manually with the new -i command-line option to specify a directory containing the custom plugin jars and only the custom plugin jars. To migrate your custom plugins, see the PingAccess Addon SDK for Java Migration Guide.
During the upgrade, it is important to not make any changes to the running PingAccess environment.
If PingAccess is running as a service, and you upgraded using the upgrade utility:
- In Linux, update PA_HOME in
/etc/systemd/system/pingaccess.service
to point to the new installation. - In Windows, remove the existing PingAccess service
(
<OLD_PA_HOME>\sbin\Windows\uninstall-service.bat
) and add the new service (<NEW_PA_HOME>\sbin\Windows\install-service.bat
).
After you have upgraded the administrative node, you can upgrade the replica admin node.