Real Time Information Director User Documentation

RTID Metadata Language
Hewlett-Packard Company 49 529618-002
To specify an aliased document, you create a class that has a unique name and extends
AliasedDocumentDefinition.
You implement a constructor for your aliased document. This constructor calls the
superclass with the following parameters:
• IDocSegment idocSegment. This parameter contains the format metadata for the
document.
• String baseDocumentName. This parameter gives the name of the document on
which aliased document is based. For example, a special form of ORDERS05
would use ORDERS05 as its base document.
• Update and query options. See “Update and Query Options for Document
Definitions.”
Example:
In the following example, an AliasedDocumentDefintion defines the mapping of an
ORDERS05 document for Fusion North America. This class extends
AliasedDocumentDefinition. The IDocSegment tag is “ZORDREXT.”
The call to the superclass constructor passes the format metadata and the name of the
base document, which is ORDERS05.
package com.hp.rtsc.documents;
import com.hp.rtsc.metadata.*;
import com.hp.rtsc.metadata.format.*;
import java.sql.SQLException;
// Metadata class to define an ORDERS05 IDoc for Fusion North America
public class IhubOrders05FusionAM extends AliasedDocumentDefinition {
…
private static final IDocSegment idocSegment =
new IDocSegment("ZORDREXT", "SALES_ORDER", new Segment[] {
IDOC.HEADER,
new Segment("E1EDK01", new TagDefinition[] {
…
// Metadata Constructor:
public IhubOrders05FusionAM()
throws MetadataInconsistency, SQLException {
super(idocSegment, "ORDERS05");
}
}
Substitute Documents
A substitute document definition lets you replace an existing base document dynamically,
without having to shut down NonStop WLS. Use substitute documents when you want to
make corrections or changes to format metadata and deploy the changes without
interrupting a running system.