Upgrade Gateway to 9.2
Upgrade your Tenant Gateway to version 9.2. Refer to the CA API Gateway documentation ("Upgrade the Gateway") for instructions.
Customers who have used CA API Gateway 9.0 at some point may still have an old ApiPortalIntegration.aar file. Ensure that Tenant Gateway does not have the file, as follows:
- Open a privileged shell on the Tenant Gateway.
- Navigate to
ApiPortalIntegration.aar if it exists.
Upgrade OTK to 3.4
Customers using an older version of CA API Management OAuth Toolkit (OTK) must upgrade to 3.4. Refer to the CA API Management OAuth Toolkit - 3.4 ("Upgrade and Uninstall") for instructions.
Note: Restart the Tenant Gateway after upgrading OTK. If you schedule the OTK upgrade well in advance of Portal migration, the following extra steps are required:
- Reset the Portal (CA SaaS Ops will co-ordinate with you before they perform this step)
- Re-enroll the Tenant Gateway (to be performed by you; refer to the "Re-enroll the Tenant Gateway" section in this document).
Before You Re-enroll the Tenant Gateway
- Remove "pssg" and "dssg" certificates:
- In the Gateway Policy Manager go to Tasks > Certificates, Keys and Secrets > Manage Certificates.
- Select the certificates that have "pssg" and "dssg" in their name, and click Remove.
- Click Close.
- Remove the portal.bundle.version cluster property:
- Go to Tasks > Global Settings > Manage Cluster-Wide Properties.
- Select the "portal.bundle.version" key and click Remove.
- Select the "portal.config.pssg.host" key and click Remove.
- Click Close.
- If you have SSO enabled:
- Save any customizations made to SSO Fragments.
- Remove the following SSO Policy and Fragments from the API Portal SSO folder: "API Portal SSO SAML Service", "API Portal SSO Configuration Fragment", "API Portal SSO SAML Request Service Fragment", and "API Portal SSO SAML Validation Service Fragment".
Re-enroll the Tenant Gateway
- Login to the Portal and copy the new enrollment URL:
- For SSO enabled tenants, log in to <portal tenant url>/admin/login, or retrieve it from the <tenant id>-enroll-urls.csv file provided by CA SaaS Ops.
- For multicluster tenants, retrieve it from the <tenant id>-enroll-urls.csv file provided by CA SaaS Ops. Note: Each URL is designated to be enrolled by a specific Tenant Gateway. The NODE_ID value from the file should match the Tenant Gateway's portal.config.node.id cluster property.
- Login to the Tenant Gateway using Policy Manager.
- Go to Tasks > Extensions and Add-Ons > Enroll with Portal in Policy Manager.
- Enroll the Portal using the URL from step 1.
- For SSO enabled tenants, re-apply the customizations to new SSO policy fragments if necessary.
- Restart the Tenant Gateway.
Verify Migration was Successful
- Log in as admin to the Tenant Portal using the same URL as before the migration.
- Verify that the Dashboard page appears after you log in.
- Go to Portal navigation menu > Settings > API Proxy, and:
- Check if there are 4 columns on the API Proxy page: "API Proxy Name", "API Proxy URL", "Proxy Version", and "Actions".
- Confirm that the proxy version for each enrolled Tenant Gateway is 9.2.
- Click View Details for each enrolled Tenant Gateway and confirm that the APIs, Apps and Account Plans are in sync.
- Go to Portal navigation menu > Analytics and verify that API Hits and Application Hits do not have a "NO DATA" message.
- Go to Portal navigation menu > Business Reports and verify that the report or graph has loaded.
- Go to Portal navigation menu > API Catalog:
- Retrieve the name of an API.
- Enter the API name in the Search box in the upper right corner.
- Verify that the search results list the API.
- Enter "Home" in the Search box from any page, and verify that the search results lists the Home page.
- Go to Portal navigation menu > Content Management and verify that the Adobe CQ5 page opens in a new tab.
- Go to Portal navigation menu > Portal APIs:
- Verify that the API Explorer page opens in a new tab.
- Click on the "Please select an API" box and verify two APIs are listed: "Portal API (<TenantName>)" and "Portal Metrics API (<TenantName>)", where <TenantName> represents the part of the Portal domain preceding ".dev.ca.com".
If you have managed to perform all the steps successfully, then your migration was successful.