There is a newly written Portalman to help increase with some of the performance of on-prem API Portal.
If you aren't on CR3 or above, after you upgrade to one of these, you have to enable the new portalman to use JDBC instead (it’s not the default).
1. Login to your API Gateway via Policy Manager
2. Create a JDBC connection with the following details:
Connection Name: Local
Driver Class: com.l7tech.jdbc.mysql.MySQLDriver
JDBC URL: jdbc:mysql://<Primary DB Server Hostname-OR-IPaddy>,<Secondary DB Server Hostname-OR-IPaddy>:3306/ssg
Password: <gateway user password set during initial setup>
3. Click “Test” button to ensure your configuration is valid
4. Open line 355 of the portalman policy (Perform JDBC Query Assertion) and set the drop down to:
JDBC Connection = Local
5. Save and Activate the policy.
6. Go to "Manage Cluster-Wide Properties" and create a new cluster-wide property named:
and set the value to: true
***Note: make sure there isn't any white space in the cluster-wide property name or value***
7. Test the API Portal by going to Dashboard > APIs and ensure that you're getting a list of APIs returned.