Real Time Information Director User Documentation

RTID Metadata Language
Hewlett-Packard Company 3 529618-002
Introduction to Director Metadata
To create a real-time solution using the Real Time Information Director (called Director
for short in the rest of this document), you don’t necessarily have to write any custom
code. What you do have to do is create metadata describing the business documents your
solution requires. Specifically, you define
• Insert or update documents (inbound, source system or client to Director)
• Responses to queries (outbound, Director to client)
You don’t have to define the format of a query. The Director does so automatically for
every inbound document you define.
Note: In subscription processing, a predefined query is triggered by a database change.
Thus, a document delivered to a client as the result of a subscription is just one case of
response to a query. You don’t have to specify the query, but you do have to specify the
triggering event. For details, see the document entitled RTID Subscriptions.
A document definition is expressed as a set of nested Java new statements. The actual
input and output documents are in Extended Markup Language (XML).
For specific vertical industries, like supply-chain and healthcare, HP provides a starting
data model and corresponding metadata. For your solution, you can start with the
metadata provided and make changes and additions as required by your business.
This document describes the syntax you will use to express metadata. Another
document, entitled RTID Metadata Extensibility, describes how to deploy and test the
metadata you have created.
Many examples in this document are from a supply-chain (RTSC) solution. Some are
from an Electronic Health Record (EHR) solution. But most of the information is
applicable to any industry. The exception to this statement is that, if your solution
doesn’t use SAP IDocs, you can skip the entire discussion of format metadata.