• Documentation
  • Key Concepts

Key Concepts


This section shows the key concepts of EnOS Device Data Integration Service.

Integration Flow


An integration flow is a flow that you can design and build to deploy business processes as a series of steps via the Flow Designer in the EnOS Management Console. Each integration flow can only have one flow input node to start the flow.


There are two types of flows in Device Data Integration Service.

Cloud flow


Cloud flow is an integration flow that is fully managed in the cloud, from creation, design, publish, all the way to deletion. For more information, see Cloud Flows.


../_images/integration_flow_lifecycle1.png

Remote flow


Remote flow is an integration flow that is created and can be managed in the cloud, and needs to be exported to be deployed and run on-premise. For more information, see Remote Flows.


../_images/remote_flow_lifecycle1.png

Integration Template


An integration template is a pre-designed integration flow that can be used when creating flows. There are three types of templates.

  • Public Templates: Public templates are integration templates that are created by the system. Users under all OUs can access these templates but cannot edit or delete them.
  • Enterprise Templates: Enterprise templates are integration templates that are created, and can be edited or deleted, by the OU admin. All users under the OU the template belongs to can access, but cannot edit or delete, these templates.
  • Private Templates: Private templates are integration templates that are created, and can be edited or deleted, by users. All users under the OU the template belongs to can access as well as edit and delete these templates.


You can view and use integration template in Device Data Integration > Integration Template. For more information, see Create from Template.

Node


A node is a basic element in an integration flow. Each node represents one single business logic action. You can use built-in EnOS-managed nodes that are designed to connect, access, and work with your data. For more information, see Nodes Overview.

Message


A message transfers data between nodes. Each node has input and output messages, where the input message is the input of the node and the output message is the node-processed or unprocessed input message that is relayed to the downstream nodes or other EnOS services.

Msg and Metadata


A message contains msg and metadata. Msg is the payload of the message, and the metadata is a list of additional attribute information in the form of key-value pairs. Key is not case sensitive, value needs to be case sensitive.