Skip to main content

Managing configurations

A configuration is an environment or workspace where you connect imported models to each other to build a global schema of the enterprise information system.

You have been assigned an object role with at least the Metadata Viewing capability.

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 imported into Talend Data Catalog.

A configuration may be understood as any of the following:
  • Repository workspace is 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 is 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 is a collection of conceptual, logical and physical models connected (semantically stitched) together through semantic mappings modeling the design process.

A configuration may have one or more versions. Configuration versions may be understood each as a different collection of versions of repository objects. You can define several configuration versions, each containing various versions of the repository objects.

As a result, you can 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.

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!