.com.zerog.registry.xml file update

Article Id: 142183

Status: Published

Updated On: 20-12-2019 16:19

Products:

CA Single Sign On Secure Proxy Server (SiteMinder) , AXIOMATICS POLICY SERVER , CA Single Sign On Agents (SiteMinder) , CA Single Sign On Policy Server (SiteMinder) , CA Single Sign On Federation (SiteMinder) , CA Single Sign On SOA Security Manager (SiteMinder) , SITEMINDER

Issue/Introduction:

We'd like to know how to the "ideal recomended way to update a
.com.zerog.registry.xml file." ?

Environment:

Policy Server 12.8SP2 on RedHat 6

Resolution:

At first glance, the .com.zerog.registry.xml is handled by the
installer and configurator and the file should not be modified
manually.

The problem of the .com.zerog.registry.xml is that this one has only
upgraded version as product value and the upgraded version doesn't
exist anymore.

To avoid this issue :

- Always uninstall the product to get a clean .com.zerog.registry.xml
file;
- If you restore from a backup, restore also the
.com.zerog.registry.xml file along.

Accoding to the following KD, a possible work around is to get the
.com.zerog.registry.xml to the correct version, by installing again
the current version in place.

When upgrading the AdminUI, I'm not asked to do an upgrade
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=7605

So before upgrading, we suggest you to do a backup of the installation
and keep a copy of this file. If you roll back, roll back also this
file to keep the content in sync with the installation.