This topic describes common scenarios in which you can migrate the resources of an IoT Platform instance and the corresponding processes.
Scenario 1
Business scenario
Devices are connected to IoT Platform by using the unique-certificate-per-device verification method and the endpoint of a public instance.
Devices submit data by using custom topics. The data is forwarded to cloud services by using the message forwarding feature and sent to the corresponding business server.
The business server calls the Pub operation to send messages to the devices.
Process
You do not need to modify the configuration of devices.
You can use phased migration to verify a small number of devices at a time.
During phased migration, the system automatically migrates products and the configuration information that is forwarded by the message forwarding feature to cloud services or the configuration information of an Advanced Message Queuing Protocol (AMQP) server-side subscription. We recommend that you use AMQP server-side subscriptions because Enterprise Edition instances do not support Message Service (MNS) server-side subscriptions.
Check whether the devices are connected to IoT Platform and submit data as expected.
Check whether the Pub operation returns an expected result and whether business runs as expected.
You can specify an Enterprise Edition instance ID when you call the Pub operation. This reduces workloads required to modify the configuration of the business server. If you want to specify an Enterprise Edition instance ID when you call the Pub operation, submit a ticket.
Use phased migration or full migration to migrate existing devices.
Scenario 2
Business scenario
Devices are connected to IoT Platform by using the unique-certificate-per-device verification method and the endpoint of a public instance.
Specific devices are connected to IoT Platform by using gateways.
Devices submit data by using custom topics. The data is forwarded to cloud services by using the message forwarding feature and sent to the corresponding business server.
The business server calls the Pub operation to send messages to the devices.
Process
You do not need to modify the configuration of devices. Specific devices are connected to IoT Platform by using gateways. Make sure that topologies between the devices and the corresponding gateways remain unchanged.
Use phased migration to verify a small number of devices at a time.
During phased migration, the system automatically migrates products and the configuration information that is forwarded by the message forwarding feature to cloud services or the configuration information of an AMQP server-side subscription. We recommend that you use AMQP server-side subscriptions because Enterprise Edition instances do not support MNS server-side subscriptions. For more information, see Configure an AMQP server-side subscription.
Check whether the devices are connected to IoT Platform and submit data as expected.
Check whether the Pub operation returns an expected result and whether business runs as expected.
You can specify an Enterprise Edition instance ID when you call the Pub operation. This reduces workloads that you must perform to modify the configuration of the business server. If you want to specify an Enterprise Edition instance ID when you call the Pub operation, submit a ticket.
Use phased migration, verify the result based on Step 2, Step 3, Step 4, and Step 5 in Scenario 1, and verify the devices of the corresponding gateways.
Use phased migration or full migration to migrate existing devices.
Scenario 3
Business scenario
Devices are connected to IoT Platform by using the pre-registration unique-certificate-per-product verification method and the endpoint of a public instance.
Devices submit data by using custom topics. The data is sent to the business server by an AMQP server-side subscription to the corresponding business server.
The business server calls the Pub operation to send messages to the devices.
Process
You do not need to modify the configuration of devices.
You can use phased migration to verify device information.
During phased migration, the system automatically migrates products and generates new AMQP server-side subscription consumers. You must modify the configuration of the corresponding business server and verify the result.
Check whether the devices are connected to IoT Platform and submit data as expected.
Checks whether the Pub operation returns an expected result, the AMQP server-side subscription works as expected, and business runs as expected.
You can specify an Enterprise Edition instance ID when you call the Pub operation. This reduces workloads that you must perform to modify the configuration of the business server. If you want to specify an Enterprise Edition instance ID when you call the Pub operation, submit a ticket.
If new devices are added to the source public instance after phased verification is complete, you can create devices on the destination Enterprise Edition instance and check whether business runs as expected.
Use phased migration or full migration to migrate existing devices.
Scenario 4
Business scenario
TSL models are defined for products. Devices are connected to IoT Platform by using the unique-certificate-per-device verification method and the endpoint of a public instance.
The devices submit data by using topics whose data conforms to the Alink protocol. The data is forwarded to cloud services by using the message forwarding feature and sent to the corresponding business server.
The business server calls the InvokeThingService operation to invoke services of devices.
Process
You do not need to modify the configuration of devices.
Use phased migration to migrate a small number of devices at a time.
During phased migration, the system automatically migrates products and the configuration information that is forwarded by the message forwarding feature to cloud services or the configuration information of an AMQP server-side subscription. We recommend that you use AMQP server-side subscriptions because Enterprise Edition instances do not support MNS server-side subscriptions.
Check whether the devices are connected to IoT Platform and submit data as expected.
Check whether the InvokeThingService operation returns an expected result and whether business runs as expected.
You can specify an Enterprise Edition instance ID when you call the InvokeThingService operation. This reduces workloads that you must perform to modify the configuration of the business server. If you want to specify an Enterprise Edition instance ID when you call the InvokeThingService operation, submit a ticket.
If you want to migrate the historical data of TSL properties, events, and services, enable the data synchronization feature and wait for 7 to 30 days.
You can use phased migration or full migration to migrate existing devices 7 to 30 days after you enable the data synchronization feature. This way, historical data of the previous 7 to 30 days for the devices that are migrated to an Enterprise Edition instance exists on the instance.