CA API Portal 3.5 - CR patch fails if MySQL is set with a custom port

Products

• API SECURITY
• Portal

Issue/Introduction

The CR installation script tries to update the lrs and lrsdata database via default MySQL 3306 port. A custom port will break connection and the patch will fails.

Follow below instruction to specify a custom DB port. 

Environment

CA API Portal 3.5

Resolution

1. Edit CR patch installation script upgrade-v3.5.CR<number>.sh, for example:

# vi upgrade-v3.5.CR14.sh 

2. Search for the following entry: dbhost="-h $3"

3. Add custom port within the double quote, dbhost="-h $3 --port <custom_port>". For example:

dbhost="-h $3 --port 6809"

4. Save the file and run the patch as per instruction here:

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-api-management/api-portal-legacy/3-5/release-notes-3-5/upgrade-to-the-latest-cr-release.html

NOTE: as part of API Portal 3.5 CR application, there is a requirement to update Portal's Gateway integration kit.

Hence the Gateway's "metrics.properties" configuration file needs to be modified to reflect custom port as well

On the Gateway, edit /opt/SecureSpan/ApiPortal/metrics.properties and modify the JDBC destination Portal database's by adding correct custom port 

source.url=jdbc:mysql://localhost:3306/ssg 
source.username=gateway 
source.password=7layer 
dest.url=jdbc:mysql://<PORTAL_DB>:<CUSTOM_PORT>/lrsdata

For example:

dest.url=jdbc:mysql://apiportal35.domain.com:6809/lrsdata