CA AG : Upgrading from R12.8

Document ID : KB000113662
Last Modified Date : 17/09/2018
Show Technical Document Details
Introduction:
Customer has installed two instances (installs) of fresh R12.8 CA AG on same box. We do not see any ..com.zerog.registry.xml file under the install user's home directory. We do see a folder called CA created under the user's home directory, with the following content.

/home/admin/CA/install-info cat ca-install-history.log ########################## # DO NOT DELETE THIS FILE! # ########################## -------------------------------------------------------------------------------------- Product Name=CA Access Gateway Location=/test/abc/ca-ag/int-ag1/secure-proxy FullVersion=12.80.0.1761 -------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------- Product Name=CA Access Gateway Location=/test/abc/ca-ag/int-ag2/secure-proxy FullVersion=12.80.0.1761 --------------------------------------------------------------------------------------
Question:
We know this is a very futuristic question to ask, but here is what spawned the discussion at Customer location. The question we have is, do the new installers refer this location / file for upgrades going forward. If NOT, how does the installer detect an upgrade? Is it by manually specifying the actual absolute path to existing install home?
Environment:
AG R12.8, PS R12.8
Both on Linux
Answer:
For Unix Hosts 
============ 

From 12.8 onwards 
---------------------------- 
CA Access Gateway (AG) has a special installation procedure as we can install multiple instances of CA Access Gateway on a single host machine. While installing AG, there is a screen asking for registry location. One needs to provide the same location in this screen for every installation. AG maintains the list of all installed instances on that box under this location and, during upgrade, one needs to provide this same location in that screen for all the instances. Subsequently, CA Access Gateway detects all instances available on that machine by reading contents from that location. It displays a screen with the list of all instances and their versions available on that machine, asking for user input on which instance to upgrade. 

Note: If one provides different locations for different instances in that registry screen during installation, AG will not be able to determine all instances installed on that machine and one has to perform manual steps for detecting all instances on that machine during upgrade or has to provide same exact path provided during installation (which will show only that instance or those instances information present under that location provided). 

Until 12.7 
------------ 
CA Access Gateway maintains this information under /opt/etc. Non root user installation should give write permissions to this location before installation. Else, installation will succeed; however, upgrade will not detect those instances' directories.

The procedure for upgrade is outlined here:
https://docops.ca.com/ca-single-sign-on/12-7/en/upgrading/in-place-upgrade/upgrade-ca-access-gateway/ 

For Windows Hosts
===============
CA Access Gateway maintains all instances information in the Windows registry; and, during upgrade, the upgrade process fetches information from the registry.