Real Time Information Director User Documentation

RTID Metadata Language
Hewlett-Packard Company 60 529618-002
public VirtualColumn (String columnNames)
Example:
The following metadata comes from the branch library example. In this case, the input
document supplies the RETURNBRANCHID and RETURNEDDATE. CARDID is
obtained from another record. The inbound enrichment ReturnItemEnrichment uses
these columns for processing but does not store them in the Item record.
Library.itemRecord.enrich(new Enrichment[] {
new VirtualColumn("RETURNBRANCHID RETURNEDDATE CARDID"),
new ReturnItemEnrichment()
});
DeleteRows
The DeleteRows enrichment causes the Director to delete existing records from the table
where this enrichment is specified.
This option is valid only in document definitions that use the UPSERT option. As part of
an Upsert, the Director selects existing records from the database. Then it merges the
existing records with the incoming data. After the merge operation, SQL updates and
inserts occur; at this point, if the metadata specifies DeleteRows, the Director deletes the
existing rows from the table.
DeleteRows uses the default constructor. In other words, just specify new DeleteRows() in
the content metadata.
If you specify DeleteRows in a document definition that uses DELSERT or INSERT, a
MetadataInconsistency exception occurs.
More Metadata Examples
The next several pages give examples of how to use enrichments and other metadata
objects to achieve data-store integration and to enhance document processing.
Examples: Enriching Input Data
When inserting or updating data, the Director usually directly inserts values present in the
inbound document into the data store. However, sometimes the Director needs to derive
values to insert. An important example is the need to assign a unique ID to an entity, such
as a customer, to correlate related records in the data store.