This topic describes how to use the features of IoT Platform after products and devices are migrated from a public instance to an Enterprise Edition instance.
Background information
For information about instance migration, see Usage notes.
For information about the features of IoT Platform, see Features.
Device connection
Feature | Description |
Link SDK | Devices are automatically connected to the Enterprise Edition instance. No manual operations are required. |
Device authentication | Unique-certificate-per-device verification and pre-registration unique-certificate-per-product verification are supported. |
NB-IoT device | Narrowband Internet of Things (NB-IoT) devices cannot be migrated. |
Device management
Feature | Description |
Thing Specification Language (TSL) models | You do not need to modify the data of products that are migrated to the Enterprise Edition instance. You can add or modify configurations based on your business requirements. Note When you migrate data between instances, the data is copied to the Enterprise Edition instance and the original data is retained on the public instance of the previous version. To prevent data loss due to misoperations, we recommend that you delete the data from the public instance after data migration is complete and your business runs as expected on the Enterprise Edition instance. |
Data parsing | |
Label | Tags cannot be migrated. You must re-add the tags to resources after data is migrated to the Enterprise Edition instance. |
Device grouping | Device groups cannot be migrated. After data is migrated to the Enterprise Edition instance, you must regroup the devices. Note The migrated devices are displayed in the device groups of the public instance. If you attempt to manage the device groups, errors are returned. We recommend that you delete the groups of migrated devices. |
Advanced search | You can retrieve data that is migrated to the Enterprise Edition instance. |
Device jobs | Device jobs cannot be migrated. You must recreate the jobs on the Enterprise Edition instance. |
Device shadows | After the migration is complete, you can continue using device shadows. |
File management | You can view the files that the devices uploaded on the Enterprise Edition instance. |
Network Time Protocol (NTP) service | After the migration is complete, you can use the NTP service on the Enterprise Edition instance to solve the issue that devices cannot obtain the server time in real time. |
Gateways and sub-devices | If the topological relationships remain unchanged during the migration, sub-devices can connect to IoT Platform after the migration. If the topological relationships are changed, an error is returned when a sub-device attempts to connect to IoT Platform after the migration. |
Device distribution | If devices are connected to IoT Platform by using a globally unique endpoint, the devices cannot connect to IoT Platform after a successful migration. |
Messaging
Feature | Description |
Server-side subscription | The server-side subscriptions and data forwarding rules can be migrated. You can use the subscriptions and rules after the migration is complete. You can add or modify server-side subscriptions and data forwarding rules based on your business requirements. Warning
For more information, see Developer guide. |
Data forwarding | |
Scene orchestration | Scene orchestration rules cannot be migrated. You must recreate the scene orchestration rules on the Enterprise Edition instance. |
RRPC communication | You must specify the ID of the Enterprise Edition instance to call operations such as RRpc and PubBroadcast after the migration. |
Broadcast communication |
Monitoring and O&M
Feature | Description |
Real-time monitoring | Metrics of devices, messages, TSL models, the rules engine, and other items are modified during the migration. You can monitor device connections and messaging in real time to ensure business continuity. When you migrate the data of a product from a source public instance to a destination Enterprise Edition instance, the amount of business data on the instances changes. The value of a metric for the source public instance decreases and the value of a metric for the destination Enterprise Edition instance increases. If a threshold-triggered alert rule is configured for the source public instance, an alert is triggered when the value of a metric is less than the specified threshold. In this case, you can disable or modify the alert rule based on your business requirements. For more information, see Configure alert rules. |
O&M dashboard | |
Online debugging | You must send commands to the migrated devices on the Enterprise Edition instance to debug the features of the devices. |
Device simulation | Before data migration is performed, you must disable the device simulator on the public instance. After the migration is complete, you must restart the simulator on the Enterprise Edition instance. |
Logging | You cannot query historical data of the public instance on the Enterprise Edition instance after the migration. |
Over-the-air (OTA) updates | To ensure successful OTA updates, you must recreate OTA update tasks on the Enterprise Edition instance after the migration. |
Remote configuration | You must perform remote configuration on the Enterprise Edition instance after the migration. |
Alerting center | You must reconfigure alerting for the Enterprise Edition instance after the migration. |
Secure tunnels | To ensure remote access to devices, you must recreate the secure tunnels for the migrated devices on the Enterprise Edition instance. |
Developer guide
Initiate API requests
When you send API requests after the migration, you must specify the ID of the Enterprise Edition instance.
When you call the Pub, RRpc, InvokeThingService, or SetDeviceProperty operation, you can specify an Enterprise Edition instance ID. To specify an Enterprise Edition instance ID when you call one of the preceding operations, submit a ticket. This reduces workloads that are required to modify the configuration of the corresponding business server.
WarningWhen you use IoT Platform SDKs for an Enterprise Edition instance, you must specify the ID of the Enterprise Edition instance to initiate API requests. Otherwise, the requests fail and business continuity is affected. For information about how to migrate data between instances, see Usage notes.
Connect an AMQP client to IoT Platform
If AMQP server-side subscriptions are configured or the rules engine forwards data to AMQP consumer groups on the public instance, you must copy the ID of the Enterprise Edition instance and the endpoint after the migration, configure a new AMQP client, and then connect the new client to IoT Platform by using an SDK. After the phased migration is complete, you must copy the new consumer group ID and start the new AMQP client.
WarningIf AMQP server-side subscriptions are configured before the migration is performed, you must start an AMQP client for the source public instance and another AMQP client for the destination Enterprise Edition instance. This way, the AMQP clients can receive data and prevent data loss.