Real Time Information Director User Documentation

starting metadata class definitions in c:\rtid\chin\com after you install the Director on the
workstation.
You must define metadata (or use predefined metadata) for the following types of documents to be
received or generated by the Director:
Incoming documents that add or update records in the data store●
Documents to be assembled and sent to subscribing applications●
Documents to be returned in response to queries●
Incoming documents that express queries also have metadata, but the Director generates that
metadata automatically from the metadata for the corresponding insert/update document or query
response.
Depending on your solution, you'll need one or two types of metadata. Content metadata is
required for any solution; it defines the structure of each XML document and the organization of
your data store. Format metadata describes the required mapping of any new or changed IDocs to
fields and records in the data store; if your solution doesn't use IDocs, you won't use format
metadata. If your solution uses HL7 messages or some other non-XML message format, you'll
need an EAI tool to transform each message to an XML document that matches a class in the
content metadata.
You can specify various kinds of data enrichments in your metadata. For example, you can specify
partitioning requirements, add foreign keys to a record, or aggregate data elements in child records
to populate a field in the parent record. You can also incorporate solution-specific logic into your
metadata by creating your own enrichments, using Java.
For information about customizing metadata to meet specific requirements, see the document
entitled RTID Extensibility. For detailed information about defining metadata, see the document
entitled RTID Metadata Language.
Indicate security policies and auditing requirements. When defining a document in your metadata,
you may include information for security and auditing. For example, if a document is required to
be secure or audited, you identify the person (the consumer) to whom the data applies and the
person (the agent) who is either requesting or modifying the data. For secure documents, you
specify the security policy; for audited documents, you specify what data must be recorded. For
more information, see the document entitled RTID Security and Auditing.
4.
Create subscriptions for interested applications, if your solution requires subscriptions. For this
task, you can use any text editor or XML editor. Every message format named in a subscription
must be defined in the metadata.
As a starting point, copy the canned subscription file provided with the Subscription module.
5.