Upgrade from 12.8.06 to 12.9 for Policy Server, Policy Store, and XPSSweeper usage
Article ID: 401585
Updated On:
Products
Issue/Introduction
Planning to upgrade SiteMinder Policy Server from 12.8SP6a to 12.9, can the Policy Server be upgraded only to run XPSSweeper to check for and fix any integrity issues?
Resolution
Depending on whether it's possible to sacrifice 1 Policy Server for the environment to do that. Installing a new Policy Server of the targeted version is recommended.
To illustrate:
Suppose running 2 Policy Servers 12.8SP6a in Production.
Upgrade one first, and run the XPSSweeper.
Important problems are found in the Policy Store data.
Then, the upgrade of Policy Server 12.9 in Production can't be done.
And there's only 1 Policy Server 12.8SP6a to correct the data manually.
That would put at risk the Production.
This is the reason it's suggested to install a brand new Policy Server 12.9 as standalone, only for the execution of XPSSweeper.
It's strongly suggested to correct the data on a "copy of the existing policy store." (1).
Policy Server 12.9 is supported on RedHat 8 (2).
Often, the errors are missing link objects (3), and they're unpredictable.
They can be of any type of data corruption.
"Plug" the Policy Server 12.9 to any Policy Store 12.8SP61 instance to run XPSSweeper for analysis (1).
Note that to fix the Policy Store data from 12.8SP6a version, try first to use the AdminUI 12.8SP6a.
Then, if the correction needs the XPS Tools, use the XPSSweeper, and XPSImport version 12.9 (4).
If XPSExplorer needs to be used, run it from the Policy Server 12.8SP6a.
Additional Information
Feedback
