Layer 7 API Developer Portal: Duplicate APIs published

Products

• CA API Developer Portal
• CA API Gateway

Issue/Introduction

When publishing an API through the developer portal, multiple duplicate APIs created on the Gateway may be observed.

Environment

This impacts all Portal versions.

Cause

There are two known causes:

• This occurs when a Gateway is enrolled with a 4.x Portal that was previously integrated with a 3.x or older API Portal Legacy.
• This can also be seen when a Portal was migrated from 3.x to 4.x.

Resolution

Some components from the previous portal are left behind on the Gateway that will need to be removed.

1. Log into the Gateway via ssh and locate the older assertions by running the commands below: ApiPortalIntegrationAssertion and ApiPortalDataLensAssertion 
   cd /opt/SecureSpan/Gateway/runtime/modules/assertions
   ls -al | grep -i Portal
   Example output:
   -r--r--r-- 1 layer7 layer7  1923558 May 30  2016 ApiPortalDataLensAssertion-8.4.00.aar
   -r--r--r-- 1 layer7 layer7   682431 May 30  2016 ApiPortalIntegrationAssertion-8.4.00.aar
2. Move the assertions out of this folder to another location (Note: only remove these two Portal assertions!):
   mv ApiPortalIntegrationAssertion-*.aar /home/ssgconfig
   mv ApiPortalDataLensAssertion-* /home/ssgconfig
3. Restart the Gateway service: service ssg restart

Additional Information

There are some instances where you will need to temporarily disable the API sync job on the Gateway and remove the API from the Portal as well as from the Gateway (duplicates and original). If removing the integration pieces alone does not address this, you will need to follow this process.