Real Time Information Director User Documentation

RTID Extensibility
Hewlett-Packard Company 16 529618 - 001
To add internal to external mappings, first declare the Mapper object that defines
the mapping table and the mapping columns. Then add an enrichment to the
EnrichedRecord object used in RelatedRecords (or a subclass of RelatedRecords)
that calls the Mapper.map() method.
3.
Compile the Java source file, as described in “Compiling Metadata.” Modify any
test files, if needed. For example, if you add internal to external mappings,
change the input file to use the external names instead of internal names.
4.
Test the metadata using the Dispatch driver. Resolve any MetadataInconsistency
exceptions that are reported, using the detailed error message. After the testing is
completed, deploy the updated Java class files to the RTID runtime environment.
See “Deploying Metadata” for deployment steps.
Updating the SQL Schema
If you have to update the SQL schema, for instance to change a column name, a primary
key, or a data type, you will have to check and possibly update your metadata.
1. If you have changed the name of a table column that is mapped to an IDoc
element, you must update the Java object definition of the metadata element to
specify the new column name.
2. If you have changed primary keys, you might need to change the links in your
content metadata. See the RTID Metadata Language module for information
about links.
3. After you have edited the Java source files to modify the metadata, you must
compile the source files, test, and deploy the updated Java classes to the runtime
environment. Refer to the instructions in “Compiling Metadata” and “Deploying
Metadata.”
The Director includes mechanisms to recognize a database schema change, re-query the
schema, and recompile the prepared statements that use the modified table. You can also
use the Management Client or interface to request the Director to reload the schema for a
specified table. The syntax for the command is described in the RTID Management
module.
Here is the recommended approach for performing an online database change and
reloading the related metadata:
1. Set the processing mode for any source system affected by the database change to
CLOSED_DEFER, as described in the RTID Management module. This
precaution prevents contention between production data feeds and requests from
the Director to change the database. CLOSED_DEFER mode saves inbound
documents in a folder for later processing. The SaveDirectory property in the
Director properties file specifies the folder name.
2. Make the actual database changes.