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, delete, or deprecate objects that are deleted from the source system in the catalog with 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.
- - Deprecate. The lifecycle of objects imported into the catalog moves to Obsolete based on objects deleted from the source system and changes you make to the filter. This does not impact enrichments added on deprecated objects and relationships. Objects renamed in the source system are removed and recreated in the catalog. When you run the catalog source job again for other capabilities such as data classification, relationship discovery, or glossary association, the job doesn't consider obsolete objects. Obsolete objects remain in the catalog until they are purged when you run a Purge Obsolete Objects job on the Explore page.
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 to metadata extraction.
- aSelect Yes to view filter options.
- bFrom the Include/Exclude list, choose to include or exclude metadata based on the filter parameters.
- cFrom the Object type list, select Script Path.
- dEnter the script path as the filter value.
Filter values can contain the following wildcard characters:
- - Asterisk. Represents multiple characters or empty text.
- - Question mark. Represents a single character.
The following image shows the Filter conditions options:
If the scripts root directory path is /users/opt/input, use the following examples to create filter conditions:
- - To include or exclude metadata from the script named script1.sql located in the path /users/opt/input/folder1/, enter: folder1/script1.sql
- - To include or exclude metadata from all scripts with SQL extension stored in the path /users/opt/input/folder1/, enter: folder1/*.sql
- - To include or exclude metadata from all scripts stored in the path /users/opt/input/, enter: *
- - To include or exclude metadata from all scripts with SQL extension and names that start with 'script' followed by a single character, stored in the path /users/opt/input/folder1/, enter folder1/script?.sql.
- - To include or exclude metadata from the script named script1.sql located in a directory with a name that starts with 'folder1' followed by zero or more characters, enter: folder1*/script1.sql
- - To include or exclude metadata from all scripts with SQL extensions from folder2 as well as any subfolders within folder2, enter: folder1/folder2/**/*.sql
- - To include or exclude metadata from all scripts from folder2 as well as any subfolders within folder2, enter: folder1/folder2/*, folder1/folder2/, or folder1/folder2
4Optionally, in the Configuration Parameters area, enter properties to override default context values and job parameters.
Note:
Click
Show Advanced to view all configuration parameters.
The following table describes the properties that you enter for Catalog Source Configuration Options:
Property | Description |
|---|---|
Scripts Root Directory Path | Path to the remote SQL script root directory. |
Default Database | Default database for SQL script processing. |
Default Schema | Default schema for SQL script processing. |
MetaTables Include Filter | Advanced parameter. Use this parameter if you want Metadata Command Center to read the content from tables or views when processing dynamic SQL statements. |
The following table describes the property that you can 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. |
5Click Next.
The Associations page appears.