Real Time Information Director User Documentation

RTID Extensibility
Hewlett-Packard Company 11 529618 - 001
2. Let’s assume that the top tag is different from the base definition’s top tag. Then
edit Orders05EXT.java, and change the class definition to extend
AliasedDocumentDefinition instead of BaseDocumentDefinition.
3. Change the top-level tag to ORDERS05EXT as shown below:
private static final IDocSegment idocSegment =
new IDocSegment("ORDERS05EXT", "SALES_ORDER", new Segment[] {
IDOC.HEADER,
. . .
}
4. Remove the definition of the content metadata (DocumentRecord).
5. Instead of calling the superclass constructor with the documentRecord, call it with
idocSegment and the name of the base document that contains the content
metadata, for example:
super(idocSegment, "ORDERS05");
6. Compile the Orders05EXT.java source file, as described in “Compiling
Metadata.”
7. Test the metadata, and deploy the updated Java class file to the RTID runtime
environment. See “Deploying Metadata” for deployment steps.
To test inbound IDocs, use the Dispatch or Disassemble standalone program. To
test outbound IDocs, use the Dispatch standalone program. To test both inbound
and outbound IDocs, use the Reselect or Dispatch program. See “Testing the
Metadata” for information about syntax. Test with both base document sample
IDocs (ORDERS05) and with the new alias sample IDocs (ORDERS05EXT).
8. If the output from Dispatch or Reselect shows that inbound data and outbound
data sometimes vary in their format, you might need to use formatters to do data
conversions. See “Converting Data Representations,” below, for a discussion of
this topic.
Creating Metadata for a Variant Document
The steps for creating a variant document definition are the same as those enumerated in
“Creating Metadata for an Aliased Document,” except that
• Instead of extending AliasedDocumentDefinition, your new class must extend
VariantDocumentDefinition.
• The call to the superclass has an extra parameter, as described in the RTID
Metadata Language module.