Real Time Information Director User Documentation

RTID Metadata Language
Hewlett-Packard Company 76 529618-002
Enriching a Delsert Transaction
In the case of a Delsert, where all previous records related to a document are deleted and
replaced with data from an incoming document, you can use enrichments to validate or
supply data missing from the input document. This type of enrichment is called inbound
enrichment and includes enhancements like address cleansing, filling in schedule lines
missing from an order, and looking up the internal ID of a customer (when the inbound
document contains the customer’s name). An inbound enrichment is applied just after the
Director parses the inbound XML document.
In connection with a Delsert, you can also incorporate system keys and partition IDs,
aggregate data elements, or apply business rules to aggregated data; such enrichments are
categorized as top-down or bottom-up and are applied after any inbound enrichment.
Top-down enrichment operates from the highest hierarchical level of the document
downward; that is, enrichments of the parent record are invoked before enrichments of
child records. Bottom-up enrichment operates on the more detailed data related to the
document; enrichments of the child records are invoked before enrichments of the parent
record.
Enriching a Query Transaction
In the case of a Query, the most likely inbound enrichment is a standard one, looking up
internal IDs that correspond to external IDs. For this purpose, you use the Mapper and
related classes. Outbound enrichments are applied after the data is read from the
database but before the query response is sent to the requesting application; such
enrichments include mapping internal IDs to external ones for inclusion in the outbound
XML. An example of a custom outbound enrichment might be to exclude expired
records from the query response.
Enriching an Upsert Transaction
The enrichments you might specify for an Upsert, in which new records are added or new
information is added to existing records, are similar to enrichments for a Delsert, except
that you don’t need to request keys or partition IDs for existing records. Custom top-
down or bottom-up enrichments might include logic to mark superseded records for
deletion, setting expiration dates for existing records, or merging elements from obsolete
records with values in incoming records. Top-down and bottom-up enrichments are
applied after the incoming data is merged with the existing data, so both the older and the
newer data are available to the enrichment logic.
Enriching a Subscription
The enrichments you might specify for a subscription, in which a predefined query is
triggered by a specified database change, are the same as for a query.