3 Complete the Post-Migration Steps

Learn how to complete the migration.

Topics:

• Fix Apiary Links

• Register Gateway Nodes

• Test the Migrated Instance

Fix Apiary Links

Re-establish links between the APIs and Apiary projects.

The Oracle API Platform Cloud Service instance on Oracle Cloud Infrastructure uses a different Apiary OAuth client than the original Oracle API Platform Cloud Service Classic instance on Oracle Cloud Infrastructure Classic. You must re-establish links between APIs to Apiary projects in the new instance, through a REST API call. You can use the REST API to look up the credentials in the database and change them to the correct credentials.

As an alternative, you can use the API Platform Cloud Service console. See Link an Oracle Apiary Specification in Using Oracle API Platform Cloud Service.

To fix the Apiary links:

1. If you don't have jq, enter the following command as the command prompt.

   sudo yum install jq

2. Identify your client_id, client_secret, account_id, and instance_id.
   See Find Your Client ID and Client Secret in Using Oracle API Platform Cloud Service.
3. Obtain an access token from Oracle Identity Cloud Service.

   export TOKEN=(curl -u <client_id>:<client_secret> -X POST https://idcs-<account_id>.identity.oraclecloud.com/oauth2/v1/token -H 'cache-control: no-cache' -d 'grant_type=password&scope=https://<instance_id>.apiplatform.ocp.oraclecloud.com:443.apiplatform&username=<username>&password=<password>'| jq -r ".access_token")

4. Use the following REST endpoint to fix the Apiary links.
   Use the same Apiary credentials you use when you connect to Apiary from the Management Portal.

   curl -k -i -X POST -H "Authorization: Bearer ${TOKEN}"-H "Content-Type: application/json" -d '{"username":"<username>","password":"<password>"}' <service-url>/apiplatform/mtmigration/apiary

Register Gateway Nodes

Create a new gateway node and register it with the logical gateway created during migration.

Logical gateways are created for the Oracle API Platform Cloud Service instance on Oracle Cloud Infrastructure as part of the data migration process, but it's not possible to migrate attached gateway nodes. You must create new gateway nodes and register them with the new logical gateways. You can't attach an existing node that was attached to a logical gateway on Oracle API Platform Cloud Service Classic to a new logical gateway for an Oracle API Platform Cloud Service instance.

Complete the following general steps:

1. Open the Management Portal and locate the logical gateways created during the migration process.
2. Create new gateway nodes.
   See Install a Gateway Node in Using Oracle API Platform Cloud Service.
3. Register the new gateway nodes with the logical gateways created during the migration process.
   See Register a Node to a Logical Gateway in Using Oracle API Platform Cloud Service.
4. Change each gateway node's network routing so that API invocations go to the new nodes.
   See Manage Gateways in Using Oracle API Platform Cloud Service.

For more information on gateway management, see Manage Gateways in Using Oracle API Platform Cloud Service.

Test the Migrated Instance

After you have fixed Apiary links and registered new gateway nodes, test the migrated instance.

To test your migrated API Platform Cloud Service instance, use the following guidelines:

1. In the Management Portal, perform the following tasks:
   1. Log in as the Administrator user, step through all main pages (APIs, Applications, Plans, Services, Service Accounts, Gateways), and check whether the object lists you see are correct.
   2. Log in from a restricted user account to ensure that grants have been transferred correctly, and that the restricted user can view only what is allowed to a restricted user.
   3. From each main page, open an object and check the validity of the details. Preform the following specific checks on the individual pages:

      APIs

      • If you have APIs with Apiary specification, open those APIs and verify the Apiary information.
      • Check if API analytics data appears correctly. You will see only analytics data that was collected in your your original system before you exported your database dump.

      Services, Service Accounts

      • If you have associated credentials, use the REST API to check that the credentials are correct. Do this in order to verify that the CSF key transfer was successful.

      Gateways

      • Check that gateway analytics data appear correctly.
      • Verify that the gateway nodes you created and registered are alive, they are polling as expected, and new analytics data are flowing in from them.
2. In the Developer Portal perform the following tasks:
   1. Perform the same checks you performed in the Management Portal for APIs, Applications, and Plans.
   2. For applications, review the application analytics and verify the content is accurate.

The migration process is complete.