Real Time Information Director User Documentation

RTID Metadata Language
Hewlett-Packard Company 20 529618-002
SQL Keys
The Director queries the SQL schema to discover the following information about each
table that a document uses:
• The key fields for each table
• The name of each field
• The datatype of each field
• The scale and precision of each field
• The default value of each field
• Whether a field allows nulls
The leverage gained from the SQL schema greatly reduces the amount of metadata that
you need to specify for individual documents.
Native Document Format
The Director can receive native documents as input or deliver them to clients in response
to queries or subscriptions.
For information about the native document format, see the document called RTID
Message Format and Programmatic Interfaces.
Note: If you’re reading this document sequentially and your solution does not require
IDocs, you can now skip to “Enriching the Data.”
Format Metadata and SAP Intermediate Documents
Unlike native documents, which require only content metadata, IDocs require both
content and format metadata. The reason is that, whereas the structure of a native
document corresponds to the structure of the data store (with XML segments
corresponding to database records, and XML elements corresponding to columns with the
same names as the XML tags), the relation between data items in an IDoc and fields and
records in the data store is not predictable. For instance, an element of an IDoc might be
stored in a database column with a different name, or the place to store some data
element might be determined by the value of the element.