Data Director Implementation Guide

10.4 HotFix 1
- 10.5 HotFix 3
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4
- 10.3 HotFix 3
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

Step 1. Create the IDD Application

Create the IDD application in the IDD Configuration Manager.

For IDD instances that span multiple ORS databases that is you can create subject areas from different ORSes, but the subject area child for a subject area should be from the same ORS; create the individual subject areas for each ORS separately (in separate IDD applications).

Export the configuration.

Integrate the individual XML configuration files by merging them to create a multi-ORS IDD instance.

Consider the following configuration issues:

Consideration	Description
Application Source System	The most important property defined at the IDD application level is the source system that an IDD application uses for tracking updates made within the IDD application itself (such as edits made by IDD application users in a Data View). By default, the Admin system is used. Using the Systems and Trust tool in the Hub Console you can create an application source system. To configure the trust on BO columns for another system, you must create a dummy staging table and map it to the IDD source system. Regardless of which IDD application source system you use, it needs to be configured to have the highest level of trust to guarantee that the changes applied by IDD application users override any other contributing values and end up in the BVT (master record). If this is not the case, the results of an update will be very confusing to IDD application users.
HM Configuration	If you are planning to use the IDD HM functionality, you need to define the HM profile (using the Hierarchies tool in the Hub Console) that will be used for configuring the IDD Hierarchy Manager functionality. The HM configuration needs to be specified up front to ensure that the subject area definitions are consistent with the HM Entity definitions.

Consideration

Description

Application Source System

The most important property defined at the IDD application level is the source system that an IDD application uses for tracking updates made within the IDD application itself (such as edits made by IDD application users in a Data View).

By default, the Admin system is used. Using the Systems and Trust tool in the Hub Console you can create an application source system. To configure the trust on BO columns for another system, you must create a dummy staging table and map it to the IDD source system.

Regardless of which IDD application source system you use, it needs to be configured to have the highest level of trust to guarantee that the changes applied by IDD application users override any other contributing values and end up in the BVT (master record). If this is not the case, the results of an update will be very confusing to IDD application users.

HM Configuration

If you are planning to use the IDD HM functionality, you need to define the HM profile (using the Hierarchies tool in the Hub Console) that will be used for configuring the IDD Hierarchy Manager functionality.

The HM configuration needs to be specified up front to ensure that the subject area definitions are consistent with the HM Entity definitions.

Rename Saved Search

Table of Contents

Data Director Implementation Guide

Data Director Implementation Guide

Step 1. Create the IDD Application

Step 1. Create the IDD Application