هذه الصفحة غير متوفرة حاليًا بلغتك المحلية. نحن نعمل جاهدين على إضافة المزيد من اللغات. شاكرين تفهمك ودعمك المستمر لنا.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Configuring MQS for Device Data Forwarding

Updated on 2024-07-17 GMT+08:00

Overview

ROMA Connect does not directly store data reported by devices. You must configure data forwarding rules to forward device data to other services for storage. In this practice, device data is forwarded to ROMA Connect's MQS for integration.

Procedure

  1. Create a message topic for storing device data.
    1. In the navigation pane on the left, choose Message Queue Service > Topic Management. On the page displayed, click Create Topic in the upper right corner.
    2. In the Create Topic dialog box, set topic parameters and click OK.
      Table 1 Topic configuration

      Parameter

      Description

      Topic Name

      Enter the topic name, which is user-defined.

      Integration Application

      Select the integration application created in Registering a Device on ROMA Connect.

      Permission

      Select the topic permission for the integration application to which the topic belongs. In this example, select Publish/Subscribe, which indicates that the topic can be used to produce and consume messages.

      Partitions

      The appropriate number of partitions can improve the concurrent performance of message creation and retrieval.

      Replicas

      ROMA Connect automatically backs up data on each replica. If one replica is faulty, data will still be available. The reliability increases with the number of replicas of a topic.

      Aging Time (h)

      After the aging time expires, messages stored in the topic are deleted.

      Synchronous Replication

      Whether to copy messages to all replicas before returning responses to the message client when the client produces messages to the topic. This parameter is not enabled here.

      Synchronous Flushing

      Whether to write each message produced by the message client to the topic to the disk immediately. This parameter is not enabled here.

      Tag

      A tag can be added for a topic to facilitate topic search.

      Sensitive Word

      Enter values to filter out topic messages containing these values. In this practice, sensitive fields are not required.

      Description

      Enter a brief description of the topic.

  2. Configure data forwarding rules.
    1. In the navigation pane on the left, choose LINK > Rule Engine. On the page displayed, click Create Rule in the upper right corner.
    2. In the Create Rule dialog box, set rule parameters and click OK.
      Table 2 Rule configuration

      Parameter

      Description

      Integration application

      Select the integration application created in Registering a Device on ROMA Connect.

      Rule Name

      Enter the rule name, which is user-defined.

      Description

      Enter a brief description of the rule.

      Status

      This parameter specifies whether to enable the rule. Retain the default value Enabled.

    3. In the rule list, click the name of the rule created in 2.b to access the rule details page.
    4. In the Source area, click Create Source, set related parameters, and click Save.
      Table 3 Source configuration

      Parameter

      Description

      Product Name

      Select the product created in Registering a Device on ROMA Connect.

      Device Name

      Select All devices.

      Topic Name

      Select the topic used by the device to send messages. The format is {Product ID}/out/+.

      Topic Level

      Select a topic level. The value is automatically adapted based on the value of Device Name. If you do not specify Device Name, Topic Level is Product-level. If you select a specific device from the Device Name drop-down list box, Topic Level is Device-level.

      Base64 Encoding

      This parameter specifies whether Base64 encoding is performed on the forwarded device data. This function is disabled here.

      Include Device Data

      Specifies whether the forwarded data includes device data. To facilitate subsequent identification of the device to which the forwarded data belongs, enable this option.

    5. In the Destination area, click Create Destination, set related parameters and click Save.
      Table 4 Destination configuration

      Parameter

      Description

      Destination

      In this practice, data is forwarded to the MQS of ROMA Connect. Therefore, select ROMA MQS.

      Connection Address

      Select the MQS intranet address of the current ROMA Connect instance. You can view the address on the Instance Information page of the ROMA Connect console.

      Topic Name

      Select the message topic created in 1.

      Username

      This parameter is mandatory only if MQS SASL_SSL is enabled for the ROMA Connect instance.

      Enter the key of the integration application to which the topic defined in Topic Name belongs.

      Password

      This parameter is mandatory only if MQS SASL_SSL is enabled for the ROMA Connect instance.

      Enter the secret of the integration application to which the topic defined in Topic Name belongs.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback