Importing and Exporting Custom Backends

Prerequisites

• Supplement the Swagger extended definitions for custom backends in the API file to import.
• Before importing a custom backend, ensure that there is sufficient custom backend quota.
• When importing a custom backend, the maximum size of a target API definition file is 3 MB.
• When exporting a custom backend, the maximum size of a target API definition file is 50 MB. If the size of the target API definition file exceeds 50 MB, the excess part will not be exported.

Importing Custom Backends

1. Log in to the ROMA Connect console. On the Instances page, click View Console next to a specific instance.
2. In the navigation pane on the left, choose API Connect > Custom Backends. On the Backends tab page, click Import above the backend list.
3. On the Import Backend page, configure backend import information.

   Table 1 Parameters for importing custom backends

   Parameter	Description
   Basic Definition Overwrite	Specifies whether to overwrite the existing backends when the imported backends conflict with the existing ones.
   Extended Definition Overwrite	Specifies whether to overwrite the existing extended information, such as the request throttling policy and access control policy, when there is a conflict between the imported custom backends and ROMA Connect. Enable: The existing extended information is overwritten with that defined in the imported file. Disable: The existing extended information is used, rather than that in the imported file.
   Swagger	Click Select and select a local YAML or JSON file that complies with Swagger specifications. After the file is imported, you can preview and modify the file online.

4. Click OK.

   The import result is displayed in the right pane. The success field contains the backends that are successfully imported, and the failure field contains the failed backends and their error codes and error description.

   

   After importing a custom backend in non-overwrite mode, its status defaults to "Developing."

Exporting Custom Backends

1. Log in to the ROMA Connect console. On the Instances page, click View Console next to a specific instance.
2. In the navigation pane on the left, choose API Connect > Custom Backends. On the Backends tab, click Export above the backend list.

   Only backends in the Developing state can be exported.

3. On the Export Backend page, configure backend export information.

   Table 2 Parameters for exporting backends

   Parameter	Description
   Scope	Specify the scope of custom backends to be exported. All: All custom backends are exported. Only a random one of the custom backends with the same request path among different integration applications can be exported. Current application: Custom backends of an integration application are exported.
   Integration Application	Mandatory for Scope set to Current application. Select the integration application to which the custom backends to export belong.
   API Definition	Specify the type of API definition to be exported. Only Full is supported, indicating that all requests and service information of backends are exported.
   Format	Select the format of the exported API file. Options: YAML or JSON

4. Click Export to export the API file to a local directory. The content of the exported file is displayed in the right pane.