Installer Does Not Offer Upgrade Option for AdminUI (WamUI)

Products

• CA Single Sign On Secure Proxy Server (SiteMinder)
• CA Single Sign On SOA Security Manager (SiteMinder)
• CA Single Sign-On
• SITEMINDER

Issue/Introduction

When attempting to upgrade the SiteMinder Administrative UI (AdminUI), the installer fails to detect the existing installation. Instead of prompting for an upgrade, the installer proceeds directly to a fresh installation path.

This behavior occurs even if the AdminUI is currently installed and running on the system.

Cause

This issue typically occurs when the ZeroG Registry file is missing, corrupted, or does not contain the required entries for the AdminUI and its prerequisites.

The SiteMinder installer queries the following file to determine if a version is already present:

/var/.com.zerog.registry.xml

If the entries for the AdminUI prerequisites (e.g., the embedded JBoss/Wildfly components) or the AdminUI application itself are missing from this XML registry, the installer assumes no previous version exists.

Resolution

To resolve this and restore the upgrade path, you must ensure the registry correctly reflects the installed state.

1. Re-install the current version: Re-run the installer for your currently installed version for both the AdminUI prerequisites and the AdminUI (1).
   
   Note: This "over-install" repairs the registry entries without needing to uninstall first.
   
   
2. Verify the Registry: After the re-installation, confirm that the entries for both components now exist in:
   
   /var/.com.zerog.registry.xml
   
   
3. Perform the Upgrade: Run the installer for the new version. It should now detect the existing installation and offer the "Upgrade" option (2).
4. Re-registration: Once the upgrade is complete, you may need to re-register the AdminUI with the Policy Server using the XPSRegClient utility (3).

Additional Information

1. Install the Administrative UI
   
   
2. Upgrade an Administrative UI
      
3. Re-register Administrative UI
       

Note: Ensure you select the correct version (e.g., 12.8.x or 12.9) in the TechDocs dropdown menu to match your specific environment.