Importing and Exporting Assets

Overview

ROMA Connect allows you to export application and task assets of an instance as files to a local PC or import local asset files to ROMA Connect to migrate assets in batches.

Prerequisites

• Only integration asset data can be imported, excluding asset-related instance configuration data. When you have imported integration assets, configure asset-related instance data. For details, see Restoring/Migrating Integration Assets.
• Ensure that the instance configurations during import and export are the same. Otherwise, the import may fail. For example, if app_route is not enabled on the exported instance but is enabled on the instance to be imported, the asset import may fail when the imported asset package contains APIs with conflict paths.
• Request throttling policies, access control policies, and signature keys of APIs cannot be imported or exported.
• If the imported assets contain APIs using FunctionGraph backends, ensure that the FunctionGraph version/alias of the current user is the same as that in the asset package.
• During asset import, if application A has a scheduled API task that calls application B's API, the import will fail. To resolve this, import application B's assets first, followed by application A's.

Importing Assets

1. On the Instance Information page of the console, click Import Asset in the upper right corner.
2. In the Import Asset dialog box, select Append or Overwrite based on the site requirements.

   The data source IDs of different instances must be different. If the data source IDs are the same, select Overwrite.

3. If you select Overwrite, set whether to override the environment configurations.
   • Override: The imported data source will overwrite the existing data source with the same name.
   • Not Override: The imported data source will not overwrite the existing data source with the same name.
4. Enter the prefix

   FDI tasks in the same instance must have different names. To import FDI tasks with same name, enter a prefix for each task before importing

5. In the dialog box displayed, select a local asset file and import it.
6. After the import is complete, click Close. You can view the imported assets in the instance.

• The custom authorizer name is globally unique. If a custom authorizer with the same name already exists in the instance when the asset is imported, random characters will be added to the end of the imported custom authorizer name to avoid duplicate names.
• If the following error information is displayed during asset import, contact technical support to upgrade the instance:

  "CipherEntry":{"reason":"{\"resourceType\":\"cipherEntries\",\"resourceId\":\"\",\"resourceName\":null,\"errorCode\":\"APIG.9999\",\"errorMsg\":\"System error\"}"}

Exporting Assets

1. On the Instance Information page of the console, click Export Asset in the upper right corner.
2. Export assets.
   • Exporting specified assets: Select the application or task assets to be exported and click Export Selected to export the asset files to the local PC.
   • Exporting all assets: Click Export All to export all asset files to a local directory.

   If you need to export all API asset information when exporting application assets, select Export all API assets in applications. All API asset information including self-created and authorized APIs will be exported. If you do not select this parameter, information about self-created and authorized APIs will be exported.

3. After the export is complete, click Close. You can view the exported assets in the local PC.