Skip to main content Skip to complementary content

Manage a Configuration

Once you have a configuration, you may manage the configuration. In particular, you may identify the contents of the configuration, add and remove contents, configure the import of models, stitch models together and review versions, import logs and responsibilities.

Steps

  1. Sign in as a user with at least the Metadata Management capability object role assignment on the folder where the configuration will go.
  2. Either
    • Go to MANAGE > Repository and pick a configuration (and optionally a version) and right-click and select Switch to the configuration
    • Or if you are already signed into that configuration, go to MANAGE > Configuration.

Example

Sign in as Administrator .

Go to MANAGE > Configuration.

Click Adjustments .

Go to the Import Setup tab and Import Options tab to configure this model for import .

Go to the Responsibilities tab to define permissions and associate roles .

Go to the Log tab to inspect import logs .

Go to the Connections tab to stitch models together for data flow lineag e.

Explorer Further

Build a Configuration

Once you have a configuration that is complete, with connection definitions resolved, you may Build the configuration. This action allows users to perform lineage and impact analysis with the configuration, as well as semantic definition and usage reporting. It is required before any of that analysis may be made accurately in that configuration versions.

Configuration Update/Build means:

  • Update the configuration with default versions (or latest if there is no default) of each model of that configuration
  • Build that version of that Configuration. Note, it does not create a new version.

Steps

  1. Sign in as a user with at least the Metadata Management capability object role assignment on the Configuration you are in.
  2. Go to the MANAGE > Configuration in the banner.
  3. Click the Update and Build button.

Example

Sign in as a user with at least the Metadata Management capability object role assignment on the configuration.

Go to MANAGE > Configuration and click the Update and Build button.

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 presented with only that configuration and its published version, by default. They may choose other configurations and versions if they have permissions to those or are a member of a groups that is not assigned to a configuration..

Publish a Configuration

A configuration may 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.

One may publish a configuration version, or make it the default in the UI. In this way, a configuration may be used by an administrator of TDC to ensure the completeness and correctness of what is visible to business users and how all users search and analyze within the full complexity of TDC .

Steps

  1. Sign in as a user with at least the Metadata Management capability object role assignment on the folder where the configuration will go.
  2. Go to MANAGE > Repository.
Information note

Be sure the Repository Panel is filtered to enable showing of versions .

  1. Expand the configuration to show versions.
Information note

Be sure the Repository Panel is filtered to show the content versions.

  1. Right click on the configuration version in the Repository Panel and select Publish .

See publish a version .

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!