Skip to main content Skip to complementary content

Manage the Current Configuration

The Configuration is an extremely important concept. It is the scope for many operations, including lineage analysis, search, Version management, etc. In this way, what would otherwise be an overload of information (everything in the repository) is instead well managed according to the Configuration of metadata one is interested in analyzing or working with. The name Configuration comes from the concept of "Version & Configuration Management" where a Configurations a collocation of particular version of Models.

A valid Configuration consists of a collection of Model Versions, mapping Versions, glossaries and stitchings. The model versions relate to data stores and data processes that have been harvested into TDC .

A Configuration may be understood as any of the following:

  • Repository workspace - a collection of Repository Objects to be analyzed together (search, browse, reports, etc.) as a technical scope, or business area under the same access permission scope.
  • Enterprise architecture - a collection of data store Models (ODS, data staging areas, data warehouses, data marts, etc.) and data process Models (ETL/DI, and BI) connected together through data flow stitching.
  • Design workflow - a collection of conceptual, logical and physical Models connected (semantically stitched) together through semantic mappings modeling the design process.

A Configuration will have one or more Configuration Versions. Configuration Versions may be understood each as a different collection of versions of Repository Objects. In this way, one can define several Configuration Versions, each containing various Versions of the Repository Objects. As a result, one may perform.

  • Historical analysis using Configuration Versions containing older Versions of Models which were deployed at some time in the past
  • What-if analysis using Configuration Versions containing the Versions of Models which may be deployed in the future.

When using the TDC UI, as you are now, you will always be working with one configuration (version) at a time. Because of this feature of this user interface TDC also provides additional MANAGE > Repository features. Creating configurations and version management of existing configurations (including publishing) may only be accomplished using the MANAGE > Repository feature.

Explore Further

Assign a group to a configuration

Groups may be assigned to a particular configuration. In this way, any users who are associated with that group are provided with the default (published) (or the latest if no version is published) configuration version.

The checkbox is part of the group definition .

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!