Create catalog sources in Metadata Command Center

Step 1. Register a catalog source

1Log in to Informatica Intelligent Cloud Services.
The My Services page appears.
2Click Metadata Command Center.
The following image shows the Metadata Command Center box on the My Services page:

The Metadata Command Center home page appears.
3Click New.
4Select Catalog Source from the list of asset types.
5Select Amazon Redshift from the list of catalog source types.
The following image shows the Amazon Redshift catalog source:
6Click Create.
The New Catalog Source page opens.
The following image shows the Registration tab on the New Catalog Source page:

7In the General Information section, enter a name and an optional description for the catalog source.
Note: You can rename a catalog source after you create it, but to apply the change to all associated objects you must rerun the metadata extraction job.
8In the Connection Information area, select the connection that you created in Administrator.
9Click Connection Properties to expand and view the connection properties for the selected connection.
10Click Test Connection to test your connection to the source system.
11Click Next.

Step 2. Configure capabilities

Configure metadata extraction

1In the Connection and Runtime area, choose a serverless runtime environment or the Secure Agent group where you want to run catalog source jobs.
Note: Serverless runtime environment options are available if the catalog source works with a serverless runtime environment.
2Choose to retain or delete objects that are deleted from the source system in the catalog using the Metadata Change Option.
• - Retain. Retains objects that are deleted from the source system in the catalog. If you update or add a filter, the catalog retains objects extracted from the previous job and extracts additional objects that match the current filter. Objects deleted from the source system are not deleted from the catalog. Enrichments added on deleted objects and relationships are retained.
• - Delete. Deletes metadata from the catalog based on objects deleted from the source system and changes you make to the filter. Enrichments added on deleted objects and relationships are also permanently lost. Objects renamed in the source system are removed and recreated in the catalog.
Note: You can also change the configured metadata change option when you run a catalog source.
3In the Filters area, define one or more filter conditions to apply for metadata extraction:
1. aSelect Filter conditions.
2. b From the Include or Exclude metadata list, choose to include or exclude metadata based on the filter parameters.
3. cFrom the Object type list, select Tables, Views, External tables, or Stored procedures depending on the object that you want to extract metadata from. Select All to extract metadata from all objects.
4. dEnter the object location as the filter value.
Filters can contain the following wildcards:
• ▪ Question mark. Represents a single character.
• ▪ Asterisk. Represents multiple characters or empty text.
For object hierarchies, use a dot as a separator. When you enter values for filters, enclose them in double quotes if you use a space or a dot in a single segment.
The following image shows the filter condition options:

4To define an additional filter with an OR condition, click the Add icon.
The following image shows a filter that includes metadata from all objects in schemas with names that start with Schema and excludes metadata from all tables with names that start with table followed by one additional character in the Schema1 schema.

5Optional. In the Configuration Parameters area, enter properties to override default content values and job parameters. Click Show Advanced to view all configuration parameters.
The following table describes the properties that you enter for Catalog Source Configuration options:

Parameter	Description
Default variables values	Specify a default value for variables used in the programmable objects.
MetaTables Include Filter	Advanced parameter. When you process PL/SQL statements, Metadata Command Center does not read tables or view content by default. If you want to use the content, for example, to process dynamic SQL statements, use the MetaTables Include Filter parameter. This parameter prompts the database for the required metadata. Verify that the user has SELECT permissions for metatables. Note: Don't use this option to specify filters for tables that you want to include or exclude during the metadata extraction run.

6Optional. In the Configuration Parameters area, enter additional settings.
The following table describes the property that you enter for additional settings:
Note: The Additional Settings section appears when you click Show Advanced.

Property	Description
Expert Parameters	Enter additional configuration options to be passed at runtime. Required if you need to troubleshoot the catalog source job. Caution: Use expert parameters when it is recommended by Informatica Global Customer Support.

7Configure additional capabilities for the catalog source by clicking on the tabs.

Configure data profiling and quality

1Click the Data Profiling and Quality tab.
2Expand Data Profiling and select Enable Data Profiling.
3In the Connection and Runtime area, choose the Secure Agent group where you want to run catalog source jobs.
4Optionally, specify data profiling filters to run the profile on a subset of the metadata that you extract.
1. aSelect Yes to view filter options.
2. bFrom the Include/Exclude list, choose to include or exclude metadata.
3. cFrom the Object type list, select Schema.
4. dEnter a value to specify the object location.
Examples:
• ▪ You extracted metadata of all tables and views from a schema and now you want to run a profile on a specific table or view from the schema. Select Schema from the Object type option and then enter the schema name followed by the table name or view name in the input field. For example, Schema_Name.TABLE_NAME or Schema_Name.VIEW_NAME
• ▪ You extracted metadata from multiple schemas and now you want to run a profile on a specific schema. Select Schema from the Object type option and then enter the schema name in the input field.
To include or exclude multiple objects, click the Add icon to add filters with the OR condition.
5In the Parameters area, configure the parameters.
The following table describes the parameters that you can enter:

Parameter	Description
Modes of Run	Determine the type of data that you want the data profiling task to collect. Choose one of the following options: - Keep signatures only. Collects only aggregate information such as data types, average, standard deviation, and patterns. - Keep signatures and values. Collects both signatures and data values.
Profiling Scope	Determine whether you want to run data profiling only on the changes made to the source system or on the entire source system. Choose one of the following options: - Incremental. Includes only source metadata that is changed or updated since the last profile run. - Full. Includes the entire metadata that is extracted based on the filters applied for extraction.
Sampling Type	Determine the sample rows on which you want to run the data profiling task. Choose one of the following options: - All Rows. Runs data profiling on all rows in the metadata. - Limit N Rows. Runs data profiling on a limited number of rows. - Random N Rows. Runs data quality on the selected number of random rows.
No of rows to limit	Required if you select Limit N Rows in Sampling Type. Specify the number of rows on which you want to run data profiling.
No of random rows to limit	Required if you select Random N Rows in Sampling Type. Specify the number of random rows on which you want to run data profiling.
S3 Bucket Name	The path to the Amazon S3 bucket that is used to store staging data.
Maximum Precision of String Fields	The maximum precision value for profiles on string data type. You can set a maximum precision value of 255 characters. Default is 50.
Text Qualifier	The character that defines string boundaries. If you select a quote character, profiling ignores delimiters within the quotes. Select a qualifier from the list. Default is Double Quote.

6Expand Data Quality and select Enable Data Quality.
Note: You can click Use Data Profiling Parameters to use the same parameters as in the Data Profiling section.
7In the Connection and Runtime area, choose the Secure Agent group where you want to run catalog source jobs.
8In the Parameters area, configure the parameters.
The following table describes the properties that you can enter:

Parameter	Description
Data Quality Automation	Enable the option to automatically create or update rule occurrences for data elements in the catalog source. Choose one of the following options: - Apply on Data Elements linked with Business Dataset. Creates rule occurrences for all data elements that are linked with business data sets in the catalog source. - Apply on all Data Elements. Creates rule occurrences for all data elements in the catalog source.
Cache Result	Specify how you want to preview rule occurrence results. Select Agent Cache if you want to generate a cache file in the runtime environment and to preview the cached results faster in subsequent data preview runs. The results are cached for seven days by default after the first run in the runtime environment. Select No Cache if you don't want to cache the preview results and view the live results.
Run Rule Occurrence Frequency	Specify whether you want to run data quality rules based on the frequency defined for the rule occurrence in Data Governance and Catalog.
Sampling Type	Determine the sample rows on which you want to run the data quality task. Choose one of the following options: - All Rows. Runs data quality on all rows in the metadata. - Limit N Rows. Runs data quality on a limited number of rows. - Random N Rows. Runs data quality on the selected number of random rows.
No of rows to limit	Required if you select Limit N Rows in Sampling Type. Specify the number of rows on which you want to run data quality.
No of random rows to limit	Required if you select Random N Rows in Sampling Type. Specify the number of random rows on which you want to run data quality.
S3 Bucket Name	The path to the Amazon S3 bucket that is used to store staging data.
Maximum Precision of String Fields	The maximum precision value for profiles on string data type. You can set a maximum precision value of 255 characters. Default is 50.
Text Qualifier	The character that defines string boundaries. If you select a quote character, data quality ignores delimiters within the quotes. Select a qualifier from the list. Default is Double Quote.

9To enable the data observability capability, expand Data Observability and select Enable Data Observability.

Configure data classification

1Click the Data Classification tab.
2Select Enable Data Classification.
3Choose one or both of the following options:
• - Generated Data Classifications. CLAIRE automatically generates data classifications for the data elements.
• - Data Classification Rules. Choose from predefined or custom data classifications.
1. 1Click Add Data Classification. The following image shows the Select Data Classifications dialog box:

2. 2Select the data classifications that you want to use.
3. 3Click OK.

Configure relationship discovery

• •Import a relationship inference model. For more information about importing a relationship inference model, see Import a relationship inference model.
• •Enable data profiling on the Data Profiling and Quality tab, and select Keep Signatures and Values as the run mode in the Parameters section. These configurations enable you to retain values of the columns in the profiling results and discover relationships.

1Click the Relationship Discovery tab.
2Select Enable Relationship Discovery.
3In the Column Similarity area, select the Relationship Inference Model.
Note: The relationship inference models that you imported appear in the Relationship Inference Model field.
4In the Joinable Tables Relationship area, specify the Containment Score Threshold to identify joinable table relationships within the catalog source. This score is an indicator of the data overlap between any two given columns which determines whether the tables are joinable.
Note: A higher score means that the objects have more overlapping data and a lower score means lesser overlapping data between the two objects. A containment score threshold lower than 0.4 might result in a large number of false positives.

Configure glossary associations

1Click the Glossary Association tab.
2Select Enable Glossary Association.
3Select Enable auto-acceptance to automatically accept glossary association recommendations.
Note: If disabled, you must manually accept glossary association recommendations.
4Specify the Confidence Score Threshold for Auto-Acceptance to set a threshold limit based on which the glossary association capability automatically accepts the recommended glossary terms.
Note: Specify a percentage from 80 to 100. If the score is higher than the specified limit, the glossary association capability automatically assigns a matching glossary term to the data element.
5Optional. Choose to ignore specific parts of data elements when making recommendations. Select Yes and enter prefix and suffix keyword values as needed.
Click Select to enter a keyword. You can enter multiple unique prefix and suffix keywords. Keyword values are case insensitive.
6Optional. Choose specific top-level business glossary assets to associate with technical assets. Selecting a top-level asset selects its child assets as well. Select Top-level Glossary Assets and specify the assets on the Select Assets page.
7Click Next.
The Associations page appears.

Step 3. Associate stakeholders and asset groups

1To associate users or user groups as stakeholders with technical assets extracted from the catalog source, perform the following steps:
1. aOn the Associations page, click Stakeholders.
2. bSelect Assign Stakeholders.
3. c Select a stakeholder role.
4. dClick Select to add users and user groups from the stakeholder role as stakeholders for the technical assets.
The Add Users & User Groups dialog box displays a list of users and user groups assigned to the selected stakeholder role.

5. eSelect one or more users or user groups to assign as stakeholders for the technical assets, and click OK.
Only the selected users and user groups belonging to the specified stakeholder role are granted the permissions to technical assets.
6. fTo assign users or user groups from another stakeholder role, click Add and then repeat the steps.
2To assign asset groups to technical assets extracted from the catalog source, perform the following steps:
1. aOn the Associations page, click Asset Groups.
2. bSelect Assign Asset Groups.
3. cClick Select.
The Select Asset Groups dialog box displays the list of asset groups.
If you enabled an access policy that includes an asset group, you can only view assets that belong to that asset group.
3Select the asset groups to which you want to assign technical assets extracted from the catalog source, and click OK.

4Choose to save and run the job or to schedule a recurring job.
• - To save and run the job, click Save and then Run.
• - To schedule a recurring job, click Next to open the Schedule page.

Step 4. Run or schedule the job

Run the job manually

Run the job on a schedule

• •You create schedules for both incremental metadata extraction and full metadata extraction, but schedule the incremental extraction to run before the first full metadata extraction job.
• •You create schedules for both incremental metadata extraction and full metadata extraction, but delete the full metadata extraction schedule before its first run.

1. 1On the Schedule tab, select Run on Schedule.
The Schedule configuration page opens.
2. 2Click the checkbox corresponding to each capability that you want to include in the schedule.
3. 3Enter the start date, time zone, and the interval at which you want to run the job.
4. 4You can manage additional schedules using the following options:
• - To create a new schedule, click the Add button.
• - To delete a schedule, click the Delete button.
• - To enable or disable a schedule, click the Enable Schedule toggle button.
Note: You can create a maximum of one schedule per capability that you enable. If you purged a catalog source or did not run the metadata extraction job, the catalog source job runs metadata extraction before running other scheduled capabilities.
5. 5Click Save to save the schedule.

Monitor job status

Step 5. Assign reference catalog source connections to endpoint catalog source objects

1On the Configure page, select the Lineage tab and then select the Assign Connections tab.
The Assign Connections panel displays a list of assigned and unassigned connections along with details for each connection.
2Select the connection to the reference source system and click Assign.
The connection name appears prefixed to the reference catalog source name on the Hierarchy tab of your catalog source in Data Governance and Catalog.
The Assign Connection dialog box appears with a list of objects of the endpoint catalog sources.
3Select one or more objects from the endpoint catalog sources and click Assign.
You can connect to the following referenced source systems:
• - Informatica Intelligent Cloud Services.
• - dbt
• - AWS Glue
• - Informatica PowerCenter
The referenced catalog source must belong to the Database class type.