Determination of Channel Attributes

Use

Before you create a channel in the Data Orchestration Engine (DOE), you must decide the attributes of this channel. The following table provides a description of the channel attributes that you must determine for a channel.

Attribute

Description

Channel type

  • Inbound channel

    The DOE only receives messages from the receivers subscribed to the channel.

  • Outbound channel

    The DOE only sends messages to the receivers subscribed to the channel.

  • Both

    This is a bi-directional channel in which DOE accepts and sends messages to the receivers.

Invocation Mode

  • Synchronous

    In this mode, when the receiver synchronizes with the DOE, the data is exchanged with the device.

    You can use this option if the receiver is connected with the DOE for a long duration of time.

  • Asynchronous

    In this mode, the DOE stores the data for each receiver in a queue. When the receiver synchronizes with the DOE, the data in the queue is exchanged with the receiver.

    You can use this option if the receiver connects to the DOE only for short durations of time. Moreover, during runtime, the administrator must extract data for the receiver.

Registration relevant

This option determines whether or not the receiver that is subscribed to this channel must register with the DOE before exchanging data.

You must implement a mechanism that allows the receivers to register with the DOE. Registration does not happen through the channel.

The DOE registers the receiver with the registration parameters that are chosen in the Mobile RMM.

Handler Name

You must implement a handler depending on the type of channel. an inbound channel should implement the IF_INBOUND_CHANNEL interface and an outbound channel should implement the IF_OUTBOUND_CHANNEL interface.

QoS (Quality of Service)

If this option is selected for the inbound channel, the DOE ensures an ordered and guaranteed processing of data. It also ensures that the data is processed only once.

Flow Definition Blueprint

You can determine whether or not to use the flow definition blueprint as an attribute to the channel handler definitions.

The DOE provides the MMW_FLOW_INBOUND_CLIENT_BV flow definition blueprint that you can use for implementing a channel. This flow blueprint specifies the processing to be performed on the data in a data object on receiving a message through the inbound handler.

To learn more about the services and methods called by this flow definition blueprint, refer to Available Flow Blueprints

Example

If you want to create an RSS channel, the attributes that you can define in the DOE are:

Attribute

Value

Channel type

Outbound channel

The DOE only sends messages to the receivers.

Invocation Mode

Asynchronous

Registration relevant

No