Update Gateway 11.0 cr3 to Gateway 11.1.2 tedious and error prone

Products

• CA API Gateway

Issue/Introduction

Gateway Appliance (OVA) upgrade requires 6 L7P files to be uploaded/installed requiring reboots.  Looking for improved upgrade procedure 

The procedure is repeated 100’s of times between the different environments containing clusters with 10 to 25 nodes in each. Looking to remove human error for this repeated procedure

 

Environment

Gateway 11.X

Resolution

Recommend creating an upgrade package that contains all  L7P (patches folder) for a particular upgrade, with scripts numbered sequentially (ie 1.sh , 2.sh, 3.sh …..).

Tested package upgrade, gzipped complete package, then copy to all gateways nodes allowing simpler upgrade

The script calls the documented command line script patchs.sh to upload and install 

Doc link for “Patching Using the Command Line”

Example script: 

1.sh

 

#!/bin/bash

# find the Patches in the same directory as this script

SCRIPT_DIR=`dirname "$0"`

echo "Stop Gateway application from SSGCONFIG Menu first - option 2 -> option 7 -> 1 (STOP)"

sleep 10  # Waits 10 seconds

# do the upload of the patch

echo "Doing upload patch"

/opt/SecureSpan/PatchManagement/bin/patch.sh upload /home/ssgconfig/patches/Layer7_API_PlatformUpdate_v11.1.00-Debian-17707.L7P

# do the install of patch

echo "Doing install patch"

/opt/SecureSpan/PatchManagement/bin/patch.sh INSTALL Layer7_API_PlatformUpdate_v11.1.00-Debian-17707

# Reset owner patch logs

echo "Reset owner for patch logs"

chown patcher:patcher  /opt/SecureSpan/PatchManagement/var/logs/*

# Reboot image SSGCONFIG Menu

echo "Reboot image"