Prepare the Data Catalog physical data layer for MicroStrategy stitching

Before you can stitch data objects to the assets in Collibra Data Intelligence Cloud, you must prepare the Data Catalog physical data layer to create assets and the database > schema > table > column hierarchy.

If you set the useCollibraSystemName property to true in your lineage harvester configuration file, you also have to create a System asset. For more information, see Automatic stitching.

Important In the global assignment of each asset type included in the MicroStrategy operating model, ensure that none of the characteristics that are in the operating model have a maximum cardinality of “0”. If the maximum cardinality is set to “0” for any such characteristics, ingestion will fail.

Prerequisites

Steps

  1. Create a System asset:
    Note Carry out this step only if you have set the useCollibraSystemName property to true in your lineage harvester configuration file.
    1. Open the product for which you want to create an asset (for example, Business Glossary).
    2. On the main toolbar, click .
      The Create dialog box appears.
    3. On the Assets tab, click System.
      The Create Asset dialog box appears.
    4. Enter the required information.
      FieldDescription
      Type

      The asset type of the asset that you are creating.

      Domain

      The domain to which the asset will belong.

      Tip Ensure that the domain type of the selected domain is assigned to the selected asset type.

      Name

      A name to identify the asset.

      Tip 

      You can simultaneously create multiple assets.
      To do so, after typing the name, press Enter, and then type the next name. Depending on the settings, asset names may need to be unique in their domain. If you enter a name that already exists, it appears in the strike-through style.

    5. Click Create.
      A message stating that one or more assets are created appears in the upper-right corner of the page.
  2. Register a database as data source. You can register a database or an SQL directory as data source.
    After registration, the assets of the following asset types are created in Data Catalog:
    • Schema
    • Table
    • Column
    Tip The full name of your Schema asset must match the exact name of the schema in the data source that you register in the configuration file.
  3. Create a Database asset:
    Tip The full name of your Database asset must match the exact name of the database or project, in case of Google BigQuery, that you register in the configuration file.
    1. Open the product for which you want to create an asset (for example, Business Glossary).
    2. On the main toolbar, click .
      The Create dialog box appears.
    3. On the Assets tab, click Database.
      The Create Asset dialog box appears.
    4. Enter the required information.
      FieldDescription
      Type

      The asset type of the asset that you are creating.

      Domain

      The domain to which the asset will belong.

      Tip Ensure that the domain type of the selected domain is assigned to the selected asset type.

      Name

      A name to identify the asset.

      Tip 

      You can simultaneously create multiple assets.
      To do so, after typing the name, press Enter, and then type the next name. Depending on the settings, asset names may need to be unique in their domain. If you enter a name that already exists, it appears in the strike-through style.

    5. Click Create.
      A message stating that one or more assets are created appears in the upper-right corner of the page.
  4. Create a relation between the System asset and the Database asset using the "Technology Asset groups / is grouped by Technology Asset" relation type.
    1. In the tab pane, click Add Characteristic.
      The Add a characteristic dialog box appears.
    2. Click Relations.
    3. Search for and click groups Technology asset.
      The Add groups Technology asset dialog box appears.
    4. Enter the required information.
      OptionDescription
      Assets

      The name of the database.

      Filter suggested assets by organization

      Option to filter the suggestions based on selected communities and domains.

      If this option is selected, the organization tree appears. You can then filter and select domains and communities.

      Start dateOptionally enter the date on which the relation between the assets becomes applicable. Leave this field empty to create a permanent relation.
      End dateOptionally enter the date on which the relation between the assets is no longer applicable. Leave this field empty to create a permanent relation.
    5. Click Save.
  5. Create a relation between the Database asset and the Schema asset using the "Technology Asset has / belongs to Schema" relation type.
    1. In the tab pane, click Add Characteristic.
      The Add a characteristic dialog box appears.
    2. Click Relations.
    3. Search for and click has schema.
      The Add has schema dialog box appears.
    4. Enter the required information.
      OptionDescription
      Assets

      The name of the schema.

      Filter suggested assets by organization

      Option to filter the suggestions based on selected communities and domains.

      If this option is selected, the organization tree appears. You can then filter and select domains and communities.

      Start dateOptionally enter the date on which the relation between the assets becomes applicable. Leave this field empty to create a permanent relation.
      End dateOptionally enter the date on which the relation between the assets is no longer applicable. Leave this field empty to create a permanent relation.
    5. Click Save.

What's next?

If you haven't created a configuration file yet, you are now required to create it.

If you created the configuration file and prepared the physical data layer, you can run the lineage harvester to start the technical lineage process.

When the technical lineage process is finished, you can go to the asset page of a MicroStrategy Report or MicroStrategy Data Attribute asset and view the technical lineage.

The lineage harvester also uses scheduled jobs to automate the technical lineage process.