Real Time Information Director User Documentation

RTID Metadata Language
Hewlett-Packard Company 39 529618-002
Segmented Tables
A RecordSegment can actually refer to more than one table:
• Tables can be horizontally segmented, so that different columns of the same entity
are stored in different tables.
• The same entities may be represented in different tables, having different primary
keys for mapping or lookup purposes.
• Each such segmented record is identified in the content metadata as a
SplitRecord.
If the metadata specifies that a value must be stored in a specified column, the value is
stored in whichever segmented table(s) have a column by that name. Don’t use the same
name, in various child or segment tables, to refer to different entities in the IDoc!
You can move columns between different tables, or remove columns altogether, without
changing the format metadata, because the Director depends not only on the metadata but
also on the database schema, which the Director reads dynamically.
ParentElement
The ParentElement class maps an element to a column in the parent table.
ParentElement has the following parameters:
• String tagName. This parameter is the XML tag to be mapped.
• String columnName. This parameter identifies the database column.
It is possible for this specification to ambiguous. The Director uses the following rules
for mapping the data:
• If the element occurs in multiple child segments, the specified column gets the
value specified in the first child segment that contains the element.
• When an IDoc is assembled in response to a query or in the context of a
subscription, the element, as stored in the parent segment, is propagated to all
siblings.
Thus, it is best to use ParentElement only when the value of the specified element will be
the same for child segments.
Here is the constructor for the ParentElement class:
public ParentElement(String tagName, String columnName)