|
In a distributed environment, data transfer is the major part of the communication between the Central Server and the Distributed Mediation Server. Distributed Mediation Server collects configuration-related information from the devices in the network and stores it in a database and this information is communicated to the Central Server on a periodic basis. Distributed Mediation Server packages this information in the form of Data Object and sends it to the Central Server through the communication framework. Also client requests are communicated to the Distributed Mediation Server by the Central Server.
The data that is transferred between the Central Server and the Distributed
Mediation Server is, by default, in the form of XML elements. The user
might want to transfer data that are not XML elements. In this case, the
data could be a simple data type, such as string or a complex data type.
To transfer of user data in a form other than XML, DataObject
class is used.
Data Object is the modeled object used during the data transfer between the Central Server and the Distributed Mediation Server and vice versa. Based on the necessity, one can set an XML element or any serialized object in the Data Object to transfer their data through existing Central Server-Distributed Mediation Server communication framework. In addition, priority of the data, data type, etc of the data can be set in the Data Object. You can set your own properties in the Data Object. The only prerequisite for using this data type is that the object that is to be transferred should be in a serialized form. The serialized fields of this class are
dataType: This field specifies the type of data that the Data Object will hold. The value is an integer to identify the data type as "0" (Object) or "1" (Element).
regionID: This field specifies the ID of the Distributed Mediation Server to which this Data Object is associated with.
dataPriority:
This field specifies the priority which
is attached with the data. The communication framework will use this priority
while processing the data. The value is an integer as specified in the
interface DataPriorityID
.
data: This field holds the data that need to be transferred. The data will be a byte array.
notificationType: This field indicates the module from which the data was received. The value is an integer uniquely identifying the module.
userProps: This field holds any user-specific properties that need to be transferred along with the data. For example, security information for the data can be sent using this field. The value will be of type Properties.
dataID: This field returns the Data ID of the DataObject. The Data ID contains the buffer from which the DataObject is received and a number specific to the DataObject.
The subsequent topics describe how the transfer of framework data and user-specific data can be customized:
|