Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Sizing and Platform Requirements
  9. Application Components
  10. IDD Security Configuration
  11. Data Security
  12. Example Role-Based Security Configuration
  13. Data Masking
  14. Siperian BPM Workflow Engine
  15. Locale Codes
  16. Troubleshooting
  17. Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Subject Areas

Subject Areas

The
subject area
is a core organizing concept for an Informatica Data Director application.
Other terms or concepts that are related to, or similar to, the subject area include: business object, and hierarchical entity. Informatica Data Director uses the subject area definition to determine how to treat each foreign key relationship in an Operational Reference Store (ORS).
The Hub Store maintains detailed metadata about tables and relationships defined in an ORS. This metadata includes relationships between base object tables that can represent:
  • References to lookup tables
  • Links between a parent and related child data
  • Associative links between tables - not representing an ownership relationship.
The Hub Store provides some of the metadata that allows Informatica Data Director to understand how relationships should be treated. For example, the base object lookup indicator tells Informatica Data Director when to treat a related table as a lookup with a
pre-populated
dropdown list that users see in an Informatica Data Director application.
For other relationships, an Informatica Data Director application might require additional information to correctly understand the relationships - whether they should be interpreted as relationships among tables in a subject area, or relationships between subject areas. The Informatica Data Director Configuration Manager is used to specify this additional relationship information for Informatica Data Director applications. You cannot use aliases for a subject area that is based on a Hierarchy Manager relationship.
A subject area represents a collection of data that should be treated as a unit from a business perspective. A subject area has:
  • A single root record in a base object
  • Some number of child and grandchild records (through one:many and many:many relationships).

0 COMMENTS

We’d like to hear from you!