Receiver Meta Model
Use
Any system that can connect to Data Orchestration Engine (DOE) is called a receiver. To enable different receivers, such as a mobile device or an external system, to connect to DOE, receivers have been categorized and each category is defined based on a specific set of attributes. The Receiver Meta Model (RMM) allows you to define this set of attributes based on which you can create receivers/devices in DOE. Therefore, a receiver/device in DOE is defined as a collection of attributes.
The attributes of a receiver meta model can be grouped into:
-
Attributes that you can customize
-
Attributes that you cannot customize
Attributes that you can Customize
|
Attribute Group |
Description |
|
Configuration |
Contains SAP defined and user defined attributes, such as installation ID, position ID, and so on. These are used to generate receivers, define distribution rules, and assign subscriptions. |
|
Administration |
Contains the attributes that administrators define for the ease of distribution of data objects and monitoring the general performance of the system. These are similar to tags and labels assigned to the messages of GMail. |
|
Data Object Association |
Provides information about the data objects that are associated with the RMM. The data object node attributes are mapped to RMM attributes to allow mass creation of devices. |
Attributes that you cannot customize
|
Attribute Group |
Description |
|
Standard |
Contains the most important attributes for a device, such as Receiver ID, Receiver category, Receiver state, and so on. These attributes as such are read-only. However, values can be specified for these attributes. |
|
Category |
Contains attributes specific to a category (group of receivers), such as receiver type, database ID, user ID, installed software components, receiver framework, client communication framework, and so on. Some of these attributes may have multiple values. For example, a receiver can have multiple users and several software components installed on it. Only the basis group can modify these attributes. |
After you define and activate an RMM, the database tables required to store the various attributes and their values are generated. This set of tables is called the receiver store. These tables are populated with values only when the you create devices.