Overview

Scenarios

ROMA Connect allows you to export applications and tasks of an instance as an asset file and import an asset file to restore or migrate integration assets.

Asset restoration: You can export integration assets from a ROMA Connect instance for data backup. In the event of a faulty instance or data loss, you can import the backup asset file to the instance for restoration.
Asset migration: You can import an integration asset file that was exported from existing ROMA Connect instances into a new instance to quickly deploy and reuse existing integration assets.

Only integration asset data can be imported, excluding asset-related instance configuration data. After integration asset import, you need to reconfigure asset-related instance data.

**Table 1** Instance configurations
Category	Item	Description	Processing Method
Public instance information	Integration application secret	The secrets of integration applications are non-asset data.	After assets are imported, ROMA Connect automatically generates new secrets. Notify interworking service applications to update the secrets accordingly.
Public instance information	Integration application authorization information	The authorization information of integration applications is non-asset data.	Reconfigure user authorization after assets are imported.
Data integration	Data source connection information	Includes the addresses, accounts, and passwords, which are non-asset data.	Configure connection information for the corresponding data sources after assets are imported.
Service integration	APIs that have not been published in the RELEASE environment	Include APIs that have not been published and APIs that have been published in a non-RELEASE environment. These APIs are non-asset data.	Re-create and publish APIs as required after assets are imported.
	Environment information of APIs	Includes the independent domain names, environment variables, cloud server information of load balance channels, and non-default environments. This information is non-asset data.	Reconfigure environment information after assets are imported.
	Control policy information of APIs	Includes request throttling policies, access control policies, client access control policies, and client quota policies. This information is non-asset data.	Reconfigure control policy information after assets are imported.
	Secret information of APIs	Includes signature keys, client's AppCodes, and custom backends' configurations of the password or certificate type. This information is non-asset data.	After asset import: ROMA Connect automatically generates new keys and secrets for signature keys. Notify backend services to update the keys and secrets accordingly. Reconfigure the client's AppCode. Reconfigure the configurations of the password or certificate type for the custom backends.
	Blacklist and whitelist specific to API authorization	The blacklist and whitelist specific to API authorization is non-asset data.	Reconfigure blacklist and whitelist information after assets are imported.
Device integration	Device information	The device information is non-asset data.	Re-create devices after assets are imported.
Device integration	Device rule information	The device rule information is non-asset data.	Re-create device rules after assets are imported.

Restoration/Migration Process

The following table describes the restoration/migration process of integration assets.

**Table 2** Service process
No.	Operation	Description
1	Preparations	Obtain an integration asset package and collect information about interconnection with peripheral systems (such as data sources, backend services, and service applications).
2	Modifying Instance Configurations	Modify the security group and configuration parameters of the instance you want to restore or a new instance.
3	Importing Integration Assets	Import the integration asset package to the instance you want to restore or a new instance.
4	Modifying Integration Application Configurations	Modify the authorization configurations of integration applications.
5	Modifying Data Source Configurations	Modify the connection configuration of data sources.
6	Modifying API Configurations	Modify the environment, control policy, secret, and blacklist/whitelist configurations of APIs.
7	Modifying Device Configurations	Create devices and rules in batches.
8	Service Interconnection Adaptation and Verification	Interconnect with peripheral systems and verify services.