If you use OpenAPI Explorer to create resources such as topics and groups in Message Queue for MQTT V2.X.X, OpenAPI Explorer may malfunction after you upgrade Message Queue for MQTT to V3.X.X. In this case, you must migrate OpenAPI Explorer to a new trace to initialize resources. The Message Queue for MQTT broker ensures that the Message Queue for MQTT version is upgraded after the code for OpenAPI Explorer is modified.

Procedure

Perform the following steps to upgrade Message Queue for MQTT from V2.X.X to V3.X.X:

  1. Evaluate the use scenarios and trace of OpenAPI Explorer.
  2. contact ApsaraMQ for MQTT technical support. The service provider provides a migration solution based on your business requirements.
  3. In most cases, you must modify your code based on the instruction in the migration solution before you can call the new version of OpenAPI Explorer.
  4. After you modify the code for OpenAPI Explorer, contact the service provider to schedule the upgrade of Message Queue for MQTT.
  5. The service provider completes the upgrade of Message Queue for MQTT from V2.X.X to V3.X.X.
  6. You must confirm whether to delete previous API calls in OpenAPI Explorer and existing resources based on your business needs.
Note To ensure compatibility, make sure that the names of the resources that you create by using OpenAPI Explorer in Message Queue for MQTT V2.X.X and Message Queue for MQTT V3.X.X are the same during dual writes. This helps prevent messaging errors in production environments.