Real Time Information Director User Documentation

RTID Extensibility
Hewlett-Packard Company 19 529618 - 001
Replacing Existing Format Metadata
The Director also supports dynamic replacement of existing metadata for Base, Aliased
and Variant documents:
• Dynamically deploying an Aliased document definition automatically replaces the
previous Aliased document definition for the same IDoc.
• Dynamically deploying a Variant document definition automatically replaces the
previous Variant document definition of the same IDoc.
• To replace a Base document definition, you define a Substitute document, as
described in “Creating Metadata for a Substitute Document,” below.
In all these cases, the dynamically deployed document definition updates the Director
format metadata, which deals with XML tags, but not the Director content metadata,
which deals with SQL tables. Aliased, variant, and substitute documents use the content
metadata of the corresponding Base document, including database resources like
prepared statements.
Replacing Existing Content Metadata
The Director also supports replacement of content metadata for a native document or an
IDoc.
To replace a native document definition, you create a new class that specifies the same
top-level tag as the old class. Then you compile, test, and deploy the class. Java does not
delete the old class, but the Director begins to use the new one.
To replace the content metadata for an existing IDoc, you create a new base document: a
new class that specifies the same top-level tag as the base document you are replacing.
After you deploy the new class, Aliased and Variant documents that referred to the old
base document will automatically use the new one.
Creating Metadata for a Substitute Document
To replace only the format metadata of a base document, follow these steps to create a
substitute document definition:
1. Open the source file that contains the current metadata for the document type. For
example, if you were updating the metadata for the ORDERS05 document, you
would open the com\hp\rtsc\documents\Orders05.java file.
2. Save the file with a new name. For example, save the file Orders05.java with the
new name Orders05v1.java, where v1 means version 1. Also, change the class