Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Sending and Receiving Data : Adapter Application Data

Adapter Application Data
An adapter works with two kinds of data, application data and metadata. This chapter discusses application data. Metadata are discussed in Chapter 6, Metadata.
Application Data Overview
Adapters need an in-memory data structure to represent complex, hierarchical information that can be sent over a network. There are two options:
MData subclasses (MInstance, MSequence, MUnion) are restricted by metadata information.
MTree is a generic structure for complex hierarchical data. There is no constraint of content based on metadata.
MInstance, MSequence, MUnion
The Adapter SDK provides several subclasses of MData to represent complex hierarchical information:
MInstance. The MInstance class allows hierarchical data representation based on a predefined class description (metadata information). This metadata information is provided in the repository. The MApp application manager encapsulates the metadata information so it can be used during MInstance creation.
MSequence. Class for encapsulating lists of data.
MUnion. Class for encapsulating data specified in the repository as a union. Unions have a name and contain one or more unionMember association lists. Each unionMember association list has a name and a class. Union and union member elements may have extended properties.
In this manual, MInstance refers to one of these composite objects. In most cases, custom adapters send MInstance objects.
In SDK 5.x and later, an MInstance can be published without additional modification. The SDK serializes the MInstance when you pass it to a publisher’s send() method.
MTree
In addition to the MData subclasses, which are always constrained by metadata, SDK also supports an MTree format.
An MTree is a data structure that can be sent over a network. When sending an MData subclass to the transport, the SDK serializes it to create an MTree. When the data arrives, it is in MTree format.
Application Data Message Format
When a publisher endpoint sends data over the wire, the data must be marshalled to include message format information.
When sending an MInstance, the SDK performs the serialization and you need not be concerned about the message format. See Sending MInstance Data.
The message format contains information about the transport (TIBCO Rendezvous or TIBCO Enterprise Message Service) and the wire format (aeRvMsg, rvMsg, aeXml). The following message formats are supported.
Table 20 Message Formats
rvMsg using TIBCO Rendezvous transport
aeRvMsg using TIBCO Rendezvous transport
aeXml message using TIBCO Rendezvous transport
aeXml message using JMS transport

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved