Restoring/Migrating Instance Assets

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. For details on how to import and export assets, see Importing and Exporting 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.

  You are advised to periodically export asset files (for example, on a monthly basis) for data backup and 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.

Restoration/Migration Process

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

Preparations

Before you restore or migrate integration assets, make the following preparations:

• Prepare an integration asset package.

  Obtain the integration asset package you want to import.

• Obtain configuration information of the source instance to which an asset package belongs. This information is required only in asset migration scenarios.

  The configuration information includes the security group configuration, instance configuration parameters, and data dictionary information of instances.

• Obtain interconnection information of peripheral systems. The information is required only in asset migration scenarios.

  System	Item	Purpose
  Data Source	IP address, username, and password for accessing a data source	Used for ROMA Connect to connect to the data source
  Service application	Network segment of a service application	Used for ROMA Connect to connect to the service application

Modifying Instance Configurations

Before you import integration assets, modify the parameter configurations of the instance to which you want to import integration assets, including the security groups, routes, instance configuration parameters, and data dictionaries.

In asset migration scenarios, the instance configuration parameters must be the same as those of the source instance to which the asset package belongs. Otherwise, the assets cannot be imported.

1. Log in to the ROMA Connect console. In the navigation pane on the left, choose Resource. On the displayed page, click the instance to access its console.
2. Modify the security group configuration. This step is performed only in asset migration scenarios. Otherwise, skip this step.
   1. On the Basic Information tab page of the Instance Information page, click the security group name.
   2. On the security group configuration page, modify the security group rule based on the source instance information obtained in Preparations and the actual networking requirements of the new instance.
3. (Optional) Modify instance routes. Mandatory only in asset migration scenarios.

   On the basic information tab page, modify the route information.

4. Modify instance configuration parameters. This step is performed only in asset migration scenarios. Otherwise, skip this step.

   On the Instance Information page, click the Configuration Parameters tab and modify the configuration parameters based on the source instance information obtained in Preparations.

5. Add data dictionaries.

   On the Instance Information page, click the Data Dictionaries tab and add data dictionaries based on the source instance information obtained in Preparations.

   For details about how to create a data dictionary, see Creating a Data Dictionary.

Importing Integration Assets

You can use the asset import function to quickly import an integration asset package to the ROMA Connect instance.

1. On the Instances page, click Import Asset in the upper right.
2. In the Import Asset dialog box, select Append or Overwrite based on the site requirements.
   • In asset restoration scenarios, select Overwrite.
   • In asset migration scenarios, select Append.
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 a 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.

Modifying Integration Application Configurations

User authorization information of integration applications is non-asset data, which must be reconfigured after you import integration assets.

• In asset restoration scenarios, you need to configure the imported integration applications.
• In asset migration scenarios, you can configure the integration applications based on the site requirements.

1. On the Integration Applications page of the ROMA Connect instance console, click Application Authorization Management on the right of an integration application.
2. In the dialog box displayed, configure authorization information for the application.

   For details about how to configure authorization information, see Configuring Integration Application Authorization.

3. Click OK.

Modifying Data Source Configurations

Data source connection information includes the connection address, account, and password, which is non-asset data. After you complete importing integration assets, you must reconfigure the data source connection information.

1. On the Data Sources page of the ROMA Connect console, click Edit on the right of the target data source.
2. On the Edit Data Source page, modify connection information about the data source.
   • In asset restoration scenarios, change the password.
   • In asset migration scenarios, change the IP address, username, and password of the data source.

   For details about the data source parameters, see Overview.

3. After the modification is complete, click Check Connectivity to verify the connectivity between ROMA Connect and the data source.
4. Click Save.

Modifying API Configurations

The environment information, control policy information, secret information, blacklist and whitelist for API authorization, and APIs that are not published in the RELEASE environment are not asset data. You need to reconfigure this information after importing integration assets.

• Environment information includes the independent domain names, environment variables, cloud server information of load balance channels, and non-default environments.
• Control policy information includes request throttling policies, access control policies, client access control policies, and client quota policies.
• Secret information includes clients' AppCodes and custom backends' configurations of the password or certificate type.

Configuring Environment Information

1. Bind an independent domain name.
   1. On the instance console, choose API Connect > API Groups. Click the name of an API group to view details.
   2. Choose Group Information and click Bind Independent Domain Name in the Independent Domain Names area to bind an independent domain name to the API group.

      For details about the parameters, see Binding a Domain Name to an API Group.

   3. Click OK.
2. Create an environment.
   1. On the instance console, choose API Connect > API Policies, and click the Environments tab.
   2. Click Create and create an environment for publishing APIs.
   3. Click OK.
3. Add environment variables.
   1. On the instance console, choose API Connect > API Groups. Click the name of an API group to view details.
   2. Click the Group Information tab in the upper left corner. In the Environment Variables area, select the environment to which you want to add variables, and click Add Environment Variable.

      For details about the parameters, see Creating an Environment Variable.

   3. Click OK.
4. Modify a load balance channel server.
   1. On the instance console, choose API Connect > API Policies, and click the Load Balance Channels tab.
   2. Click Modify on the right of a load balance channel.
   3. Modify the server configuration.
      • For channels whose mode is set to Select cloud servers, click Add Cloud Server to add servers.
      • For channels whose mode is set to Specify IP addresses, modify the backend service addresses as required.

      For details about the parameters, see (Optional) Creating a Load Balance Channel.

   4. After the configuration is complete, click Finish.

Configuring Control Policy Information

1. Configure a request throttling policy.
   1. On the instance console, choose API Connect > API Policies, and click the Policies tab.
   2. Click Create Policy. On the Select Policy Type page, select Request Throttling in the Traditional Policies area.

      For details about the parameters, see Creating a Request Throttling Policy.

   3. Click OK.
   4. Bind the request throttling policy to the API, application, or tenant by following the procedure described in API Request Throttling.
2. Configure an access control policy.
   1. On the instance console, choose API Connect > API Policies, and click the Policies tab.
   2. Click Create Policy. On the Select Policy Type page, select Access Control in the Traditional Policies area.

      For details about the parameters, see Creating an Access Control Policy.

   3. Click OK.
   4. Bind an access control policy to the API by following the procedure described in API Access Control.
3. Configure a credential access control policy.
   1. On the instance console, choose API Connect > Credentials, and click the Credentials tab.
   2. Click Set Access Control on the right of a credential.

      For details about the parameters, see API Credential Access Control.

   3. Click OK.
4. Configure a credential quota policy.
   1. On the instance console, choose API Connect > Credentials, and click the Credential Quota Policies tab.
   2. Click Create Credential Quota Policy.

      For details about the parameters, see Creating a Credential Quota Policy.

   3. Click OK.
   4. Bind the quota policy to a credential by following the procedure described in API Credential Quotas.

Configuring Secret Information

1. Add a credential for simple authentication.
   1. On the instance console, choose API Connect > Credentials, and click the Credentials tab.
   2. Click the name of a credential.
   3. In the AppCode area, click Add AppCode to add an AppCode for the credential.
   4. Click OK.
2. Add the configurations of the password or certificate type for custom backends.
   1. On the instance console, choose API Connect > Custom Backends, and click the Configurations tab.
   2. Click Modify on the right of a configuration item.
      • For configuration of the password type, change the password.
      • For configuration of the certificate type, modify the certificate content and private key.
   3. Click OK.

Modifying Blacklist and Whitelist Configurations of API Authorization

Only APIs that are accessed using App authentication support authorization configuration.

1. On the instance console, choose API Connect > APIs. Choose More > Authorize Credentials of an API.
2. On the page displayed, click Enable Green Channel > Modify on the right of an authorized credential to modify the blacklist and whitelist.
3. Click OK.

Creating an API and Publishing It in a Non-RELEASE Environment

1. On the instance console, choose API Connect > APIs and click Create API.

   For details about the parameters, see Creating a RESTful API.

2. Publish the API to an environment other than RELEASE by following the procedure described in Publishing an API.

Modifying Device Configurations

Device and device rule information is not asset data. Reconfigure the information after importing integration assets. You can use the import function to restore or create devices and rules in batches.

1. (Optional) Prepare one device file and one rule file.

   Obtain the exported device file and rule file from the source instance to which the asset package belongs.

2. Create a device.
   1. On the ROMA Connect console, choose LINK > Device Management.
      • If you have obtained a device file, click Import to create a device by importing the file.
      • If you have not obtained a device file, click Create Device to manually create a device.

        For details about the parameters, see Creating a Device.

   2. After the import is successful, you can view the imported device in the device list.
3. Create a rule.
   1. On the ROMA Connect console, choose LINK > Rule Engine.
      • If you have obtained a rule file, click Import to create a rule by importing the file.
      • If you have not obtained a rule file, click Create Rule to manually create a rule.

        For details about the parameters, see Creating a Rule.

   2. After the import is successful, you can view the imported rule in the rule list.

Service Interconnection Adaptation and Verification

After you have restored or migrated integration assets in the ROMA Connect instance, notify the service applications interworking with ROMA Connect to update their interconnection configurations so that they can process services properly.

The following table describes the interconnection configurations to update on the service applications or devices connected to ROMA Connect.

After you update the interconnection configurations, check whether service applications can process services properly.

• Check whether a service application can call APIs.
• Check whether a service application can send messages to and receive messages from topics of ROMA Connect.
• Check whether a device can send data to and receive data from ROMA Connect and whether the rule engine can forward data.