Mappings

Mappings describe the data flow from one topic to another, such as the data flow between devices and processing rules.

See also: Cybus::Mapping resource

Overview

Connections Overview

In the list, all mappings are displayed with the following information:

Service ID

• The unique identifier of the service that contains this mapping.

Name

• The name of the mapping.

Entries

• The number of entries for the mapping.

Agent

• The agent that is assigned to the mapping.

Status

• The current state of the mapping (e.g., enabled or enabling).

Mapping Details View

• To open the Mappings View for a specific service, click Services > Service Overview and select a service. In the Service Details view of the selected service, click the Mappings tab.

Mapping Details View

At the top of the Mapping Details View, the following information is displayed:

Mapping ID

• The unique identifier of the service that contains this mapping.

Service ID

• The unique identifier of the service that contains this mapping.

Entries

• The number of entries for the mapping.

Agent

• The agent that is assigned to the mapping.

Status

• The current state of the mapping (e.g., enabled or enabling).

Resources of Mappings

Each mapping has resources itself.

• To open the resources of mappings, click a mapping in the Mappings View.

See also: Mappings in the service commissioning file

For reliable operation, MQTT shared subscriptions are not supported in the Entries tab, as they could interfere with other clients subscribed to the same topics.

Subscribe

• The resource that the mapping subscribes data from.

Subscribe Broker

• Indicates which message broker is used to receive the subscribed data (e.g., internal).

Publish

• The resource that the mapping publishes data to. You can click the entry to open the details view of the resource.

Publish Broker

• Indicates which message broker is used to publish the data (e.g., internal).

Rules

The Rules tab lists associated Rule Engine rules for the mapping. The rules define how data should be processed between subscribing and publishing. For more information, see Rule Engine.