How to manually upgrade a Gateway install

Document ID : KB000009888
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

After performing an application upgrade it appears the gateway is not upgraded and rpm output shows the prior version and you can't attempt a db upgrade 

Background:

When upgrading CA API Gateway appliances, you first upload and install the platform patch. After that is installed, reboot the server. When the server comes up, we than install the application patch. Once we reboot the gateway appliance, the application version should have changed. So if we upgraded from 9.0 to 9.1, the application patch should have changed the version number to 9.1 

 

 

Environment:
CA API GATEWAY 8.x, 9.x In our example we performed an upgrade from 9.0 to 9.1
Instructions:

After performing an application upgrade it appears the gateway is not upgraded and rpm shows the prior version and you can't attempt a db upgrade 

 

1) The L7P file is a zip archive. After copying the 9.1.00 Application L7P file to the /home/ssgconfig directory, the first step is to unzip the archive to a temporary directory; # unzip -d /tmp/l7p /home/ssgconfig/Layer7_v9.1.00.L7P 

 

2) Change to the directory containing the rpm files \\example ... 

# cd /tmp/l7p/

3) Make certain the ssg service is stopped # service ssg stop 

4) Manually update the rpm files. 

# /bin/rpm -Uvh ssg-9.1.00*.rpm ssg-appliance-9.1.00*.x86_64.rpm 

5) Reboot the server 

6) Check to see if the rpms are now correctly reflected as being 9.1.00 # rpm -qa | grep ssg 

7) If all looks good then proceed to login to the ssgconfig menu and attempt a database upgrade to 9.1.00