The RKM role is to perform
customized reverse engineering for a model. The RKM is in charge of connecting
to the application or metadata provider then transforming and writing the
resulting metadata into Oracle Data Integrator's repository. The metadata is
written temporarily into the SNP_REV_xx tables. The RKM then calls the Oracle
Data Integrator API to read from these tables and write to Oracle Data
Integrator's metadata tables of the work repository in incremental update mode.
This is illustrated below:
Reverse-engineering
Knowledge Modules
A typical RKM follows these steps:
1.
Cleans up the SNP_REV_xx tables from
previous executions using the OdiReverseResetTable tool.
2.
Retrieves sub models, datastores,
columns, unique keys, foreign keys, conditions from the metadata provider to
SNP_REV_SUB_MODEL, SNP_REV_TABLE, SNP_REV_COL, SNP_REV_KEY, SNP_REV_KEY_COL,
SNP_REV_JOIN, SNP_REV_JOIN_COL, SNP_REV_COND tables.
3.
Updates the model in the work
repository by calling the OdiReverseSetMetaData tool.
No comments:
Post a Comment