Log in as
ssgconfig
and open a privileged command shell from the
API Gateway
 main menu.
At the command prompt, type:
rpm  -q ssg
The installed version of the
API Gateway
 is displayed.

At the command prompt, type:

pkginfo -l L7TECHssg

You should see something similar to the following:

PKGINST: L7TECHssg
NAME: CA API Gateway XML Networking Gateway
CATEGORY: JAVAAPPS,application,ssg
ARCH: all
VERSION: 8.4.00
BASEDIR: /
VENDOR: CA Technologies Inc.
DESC: CA API Gateway Gateway Software Package
PSTAMP: 20150828
INSTDATE: Aug 18 2015 15:47
HOTLINE: 888.681.9377
EMAIL: support@ca.com
STATUS: completely installed
FILES: 2580 installed pathnames
       63 directories
       16 executables
       651625 blocks used (approx)

(Optional, but recommended)
Back up the database.
Stop the
API Gateway
.
Ensure that a Java SE Development Kit (JDK) has been installed.
Download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 8 from the Oracle web site. Unzip the files and then copy them to the following directory (assuming the JDK 1.8 was installed to the default directory
/usr/j2se/
):
# cp UnlimitedJCEPolicy/* /usr/j2se/jdk1.8.0_
xx
/jre/lib/security/
Stop the slave in MySQL on all nodes in the cluster.
Set the permissions and upload the relevant patch files to the
API Gateway
. These files are available from the CA Support download site.
# chmod 755 /opt/SecureSpan/Controller/*.L7P
# /opt/SecureSpan/Controller/bin/patch.sh upload /opt/SecureSpan/Controller/<patchFileName>.L7P
Install each uploaded patch file. Unless noted otherwise, the patch files may be installed in any order.
# /opt/SecureSpan/Controller/bin/patch.sh install <patchFileName>
Open
my.cnf
for editing:
# edit my.cnf
Add the following property to
my.cnf
:
log_bin_trust_function_creators=1
The following property may also need to be added; contact your system administrator if it is required for your installation:
slave_exec_mode=IDEMPOTENT
The properties should be added to this section:
# Uncommment log-bin and log-slave-update if a clustered
# db server
log-bin=/var/lib/mysql/ssgbin-log
log_bin_trust_function_creators=1
log-slave-update	
# uncomment the next item on 1st db master server
server-id=1
# uncomment the next item on 2nd db master servers
#server-id=2
relay-log = /var/lib/mysql/ssgrelay-bin
relay-log-index = /var/lib/mysql/ssgrelay-bin.index
relay-log-info-file = /var/lib/mysql/ssgrelay-bin.info

# Slave reliability items:
slave-skip-errors=126,1053,1105,1129,1158,1159,1160,1161
slave_compressed_protocol=1
slave-net-timeout=30
slave_exec_mode=IDEMPOTENT
Restart the MySQL service on all nodes in the cluster.
Restart the
API Gateway
.
Upgrade the
API Gateway
 database on one node.
Tip:
To do this, use option
1
("Upgrade the Layer 7 Gateway database") on the Gateway Main Menu (Software).
Start the
API Gateway
. The databases on the other nodes will be replicated from the primary database.

Stop the
API Gateway
 service with this command:
# /opt/SecureSpan/Gateway/runtime/bin/gateway.sh stop
Back up the previous embedded database by copying this directory to your local directory:
/opt/SecureSpan/Gateway/node/default/var/db
Remove this directory:
/opt/SecureSpan
Reboot the computer.
Install the
API Gateway
 software with this command:
# rpm -Uvh ssg-<version>.noarch.rpm
where
"<version>"
is the version number of the new
API Gateway
.
Run the following to configure the
API Gateway
:
# /opt/SecureSpan/Gateway/runtime/bin/setup.sh
The
API Gateway
 main menu appears.
Select option
2
(Configure the Gateway).
Select option
1
(Java VM) and verify that the Java VM settings are correct.
Select option
2
(Database Connection) and then configure the
API Gateway
 to use the embedded database.
Exit the
API Gateway
 main menu and reboot the computer.
Restore the database by copying the backup made to this directory:
/opt/SecureSpan/Gateway/node/default/var/
Change the ownership and permissions back for the database directory and all of its subdirectories/files
Change the owner of database directory (in the previous step) from
root
to
gateway
.
Change the permissions of database directory to
rwxrwxr-x
Change the permissions of the following directory and all its subdirectories to
rwxrwxr-x
/opt/SecureSpan/Gateway/node/default/var/db/ssgdb
Change the permissions of all files within the "ssgdb" directory (from above) to
rw-rw-r- -
Change the permissions of the subdirectories within the "ssgdb" directory (from above) to
rwxrwxr-x
Change the permissions of the following log file to
rw-rw-r- -
/opt/SecureSpan/Gateway/node/default/var/db/derby.log
Start the
API Gateway
with this command:
# /opt/SecureSpan/Gateway/runtime/bin/gateway.sh start
The upgrade is now complete.

On the Solaris
API Gateway
 server, install the JDK for Solaris and note the installation path. This JDK is available from
java.sun.com/javase/downloads/index.jsp
.
Download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 8 from the Oracle web site. Unzip the files to the following directory (assuming JDK 1.8 was installed to the default directory
/usr/j2se/
):
cp UnlimitedJCEPolicy/* /usr/j2se/jdk1.8.0_
xx
/jre/lib/security/
If you have previously upgraded the MySQL software but not yet run "mysql_upgrade", navigate to the MySQL directory and run:
# mysql_upgrade --skip-write-binlog
Next, do the following to upgrade the
API Gateway
 software:
Stop the slave in MySQL on all nodes in the cluster.
Run the following command to remove the old installation:
# pkgrm L7TECHssg
Copy the new
API Gateway
 software package
L7TECHssg
-
<version>
.pkg
to the host machine.
Run the following command to install the
API Gateway
 software:
# pkgadd -d L7TECHssg-<version>.pkg
Select the package(s) to process.
Open
my.cnf
for editing:
# edit my.cnf
Add the following properties to
my.cnf
:
log_bin_trust_function_creators=1
slave_exec_mode=IDEMPOTENT
Restart the MySQL service on all nodes in the cluster.
Run the following to configure the
API Gateway
:
/opt/SecureSpan/Gateway/runtime/bin/setup.sh
The
API Gateway
 main menu appears .
Select option
2
(Configure the Gateway).
Select option
1
(Java VM) and verify that the Java VM settings are correct.
Select option
2
(Database Connection) and then verify that the database connection settings are correct. The settings from the previous version of the
API Gateway
 should be displayed as the default for each setting. Press [
Enter
] to use the existing value from the previous installation. You will need to enter the password of the database from the previous installation.
You will see an error stating ‘Database version mismatch’. This is expected because you have just updated the Gateway software. The database will be updated in the next step.
Select option
1
(Upgrade the Gateway database) and follow the prompts to upgrade the database.
Start the
API Gateway
:

/opt/SecureSpan/Gateway/runtime/bin/gateway.sh start

Stop the
API Gateway
 service with this command:
/opt/SecureSpan/Gateway/runtime/bin/gateway.sh stop
Back up the previous embedded database by copying this directory to your local directory:
/opt/SecureSpan/Gateway/node/default/var/db
Remove the old installation with this command:
# pkgrm L7TECHssg-<version>
Remove this directory:
/opt/SecureSpan
Reboot the computer.
Copy the new
API Gateway
software package
L7TECHssg-<version>.pkg
to the host machine.
Install the
API Gateway
 software with this command:
# pkgadd -d L7TECHssg-<version>.pkg
Enter
Y
when prompted whether to install the conflicting files, then enter
Y
to confirm installing <L7TECHssg>.
Run the following to configure the
API Gateway
:
# /opt/SecureSpan/Gateway/runtime/bin/setup.sh
The
API Gateway
main menu appears.
Select option
2
(Configure the Gateway).
Select option
1
(Java VM) and verify that the Java VM settings are correct.
Select option
2
(Database Connection) and then configure the
API Gateway
 to use the embedded database.
Exit the Gateway main menu and reboot the computer.
Restore the database by copying the backup to this directory:
/opt/SecureSpan/Gateway/node/default/var/
Change the ownership and permissions back for the database directory and all of its subdirectories/files:
Change the owner of database directory (in the previous step) from
root
to
gateway
.
Change the permissions of database directory to
rwxrwxr-x
Change the permissions of the following directory and all its subdirectories to
rwxrwxr-x
/opt/SecureSpan/Gateway/node/default/var/db/ssgdb
Change the permissions of all files within the "ssgdb" directory (from above) and all its subdirectories to
rw-rw-r- -
Change the permissions of the following log file to
rw-rw-r- -
/opt/SecureSpan/Gateway/node/default/var/db/derby.log
Start the
API Gateway
 with this command:

/opt/SecureSpan/Gateway/runtime/bin/gateway.sh start