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, 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 for metadata extraction:
1. aSelect Yes to view filter options.
2. bFrom the Include or Exclude metadata list, choose to include or exclude metadata based on the filter parameters.
3. cFrom the Object type list, select All Types.
4. dEnter a value to specify the object location.
Filters can contain the following wildcards:
• ▪ Question mark. Represents a single character.
• ▪ Asterisk. Represents multiple characters or empty text.
• ▪ Double asterisk. Represents any number of segments with any number of characters.
The following image shows the filter condition options:

For path hierarchies, use the '/' separator. When you enter values for filters, enclose them in double quotes if the value includes an asterisk or spaces before or after a string value. Filters are not case-sensitive.
Use the following format when you enter values for filters: Project/FolderPath/ObjectType:ObjectName
Where:
• - Project is a project name in the ODI Studio.
• - FolderPath is the path to a folder in the ODI Studio.
• - ObjectType:ObjectName contains the type of object and the object name. The object type can be a package, scenario, mapping, or a procedure. Scenario is a special object type which can be inside a package, mapping, or a procedure.
Use the following object types in the filter:
• - Scen – Scenario
• - Map - Mapping
• - Pack - Package
• - Proc - Procedure
• - Any - to match mappings, packages, or procedures.
Examples:
• - To include or exclude metadata from the 'pack1' package in the 'Project/FolderPath/' path, enter Project/FolderPath/Pack:pack1.
• - To include or exclude metadata from the 'v1' version of 'scen1' scenario in the 'pack1' package, enter Project/FolderPath/Pack:pack1/Scen:scen1 v1.
• - To include or exclude metadata from all scenarios in the 'pack1' package, enter Project/FolderPath/Pack:pack1/Scen:*.
• - To include or exclude metadata from all scenarios in 'pack1' packages across all projects, enter Pack:pack1 or **/Pack:pack1/Scen:*.
• - To include or exclude metadata from the 'v1' version of all 'scen1' scenarios across all packages, mappings, and procedures, enter Scen:scen1 v1 or **/Any:*/Scen:scen1 v1.
• - To include or exclude metadata from all scenarios in the 'Package1' package, enter Package1/**.
• - To include or exclude metadata from all objects in the 'Directory' folder, enter */Directory/Any:*.
• - To include or exclude metadata from all objects in the 'Directory' folder as well as any subfolders within the 'Directory' folder, enter */Directory/**.
4In the Configuration Parameters area, enter properties to override default context and variable values.
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
Context Override	Enter a value to override the Default Context used by Agents property that you configure in the Oracle Data Integrator source.
Default Variable Values	Specify default values for the variables used in programmable objects in the form of key-value pairs. Use sections in the form of [section name] before you specify a variable. Example: [Global] GLOBAL.Variable = 'val' PROJECT.Variable = 25 ["ScenarioName version"] GLOBAL.Variable = 'text' PROJECT.Variable = 36

You can evaluate Java BeanShell scripts to resolve text and process SQL scripts. If the evaluation breaks due to missing values, you can provide default values for the variables in the form of key-value pairs in the Default Variable Values property.
Consider the following guidelines when you specify default variable values:
• - To use a variable for all scenarios, specify [Global] as the first segment and define the value of the global variable under the [Global] section.
• - The syntax for global variables is GLOBAL.variable_name.
• - To use a variable for a specific scenario, define the value of the variable under that scenario section.
• - Define the full scenario name in quotes. Include the name of the scenario and the version of the scenario separated by a space.
Example: "ScenarioName version"
• - Include the project name and the name of the variable separated by a dot.
Example: PROJECT.Variable
• - The value of the variable must meet the standard syntax of default variables.
Example: PROJECT.Variable = 25
5Optional. 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.

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

Configure lineage discovery

1Click the Lineage Discovery tab.
2Select Enable Lineage Discovery.
3In the Filters area, define one or more filter conditions to apply for lineage discovery.
To define filters, you can choose to select catalog source types, asset groups, or enter a catalog source name or search from a list of catalog sources.
1. aSelect Yes to view filter options.
2. bFrom the Include/Exclude list, choose to include or exclude catalog sources for lineage discovery based on the filter parameters.
3. cFrom the filter type list, select catalog source type, catalog source name, or asset group.
4. dIn the filter value field, select the required catalog source types, or click the Search button and select catalog sources or asset groups.
Filters can contain the asterisk wildcard to represent multiple characters or empty text.
The filter options appear.
Examples:
• ▪ To include or exclude all Oracle catalog sources, select Catalog Source Type as the filter type and select Oracle in the filter value field.
• ▪ To include or exclude the 'Oracle_Retail' catalog source, select Catalog Source Name as the filter type and search for the catalog source or enter Oracle_Retail in the filter value field.
• ▪ To include or exclude all catalog sources with names that start with 'Oracle', select Catalog Source Name as the filter type and search for the catalog source or enter Oracle* in the filter value field.
• ▪ To include or exclude all catalog sources with names that end with 'Retail', select Catalog Source Name as the filter type and search for the catalog source or enter *Retail in the filter value field.
• ▪ To include or exclude all catalog sources with names that contain 'Ret', select Catalog Source Name as the filter type and search for the catalog source or enter *Ret* in the filter value field.
• ▪ To include or exclude all catalog sources that are part of the 'Financial Group' asset group, select Asset Group as the filter type and search Financial Group in the filter value field.
Note:
You can't add more than one include or exclude filter for the same filter type.
5. eOptionally, to define an additional filter with an AND condition, click the Add icon.
For more information about lineage discovery, see Lineage discovery.