Design Guide

10.5 HotFix 2
- 10.5 HotFix 3
- 10.5 HotFix 1
- 10.5
- 10.2 HotFix 1
- 10.2
- 10.1
- 10.0 HotFix 1
- 10.0

Back Next

Implementing a System

This step implements the parsed rules by running the MDM-RE Table Loader to:

extract and denormalize data from the User Source Tables

create triggers on the User Source Tables (for synchronized systems)

apply transform rules

generate keys

mass load the IDT and its associated IDXs.

To implement a System, select

System

Load IDT

. You will be prompted for the name of the Table Loader Definition to execute.

Refer to the

OPERATIONS guide, MDM-RE Table Loader chapter

for detailed information about the Table Loader.

Loading a System

To un-implement a System

A System can be

unimplemented

if required. This process deletes the database objects that were created when the system was implemented. It will delete the following:

IDTs

IDXs

Persistent-IDs

Forced Link/Unlink rules

IDLs

triggers

transactions stored in the Synchronizer’s Transaction Table

un-implement

a System, select

System

Refresh

un-implement/refresh

only Persistent-ID clusters, select

System

Refresh

Select the specific object

For more information on Persistent-IDs, refer to the

Persistent-ID

chapter in this guide.

un-implement/refresh

only Forced Link/Unlink rules, select

System

Refresh

Select the specific object

The existing rules are moved to a flat file before the system deletes them. These rules can be re-used at a later stage. If you want to load these rules again, specify the PID definition to which the Forced Link/Unlink rules should be associated and the file containing the rules. The Delimiter field should be left empty.

For more information on how to load the Forced Link/Unlink rules, refer to the

MDM-RE Operations

guide.

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal