Help Center/ ROMA Connect/ User Guide/ Instances/ Restoring/Migrating Integration Assets/ Service Interconnection Adaptation and Verification
Updated on 2022-09-02 GMT+08:00
View PDF

Service Interconnection Adaptation and Verification

Overview

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.

Service Interconnection Adaptation

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

Category

Service Scenario

Configuration Data

Service integration

Calling an API
  • API calling address (required only in asset migration scenarios)
  • API authentication information, including the keys, secrets, AppCodes, and AK/SK of integration applications/clients
  • Key and secret of backend signature keys

Message integration

Sending and receiving messages
  • Topic connection address (required only in asset migration scenarios)
  • Key and secret used when SASL authentication is enabled.

Device integration

Reporting messages and delivering commands
  • Device connection address (required only in asset migration scenarios)
  • Access authentication information of devices, including client IDs, usernames, and passwords

Service Verification

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.