When you configure the Oracle Business Intelligence catalog source, you define the settings for the metadata extraction capability.
The metadata extraction capability extracts source metadata from external source systems. You can also configure other capabilities that the catalog source includes.
You can save the catalog source configuration at any point after you enter the connection information. After you save the catalog source, you can choose to run the catalog source job. To run the job once, click Run. To run metadata extraction and other capabilities on a recurring schedule, configure schedules on the Schedule tab.
Configure metadata extraction
When you configure the Oracle Business Intelligence catalog source, you choose a runtime environment and enter configuration parameters for 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:
aSelect Yes to view filter options.
bFrom the Include Metadata list, select Include Metadata to include metadata based on the filter parameters.
cFrom the object type list, select Objects.
dEnter the filter values.
Filters can contain the following wildcards:
▪ Question mark. Represents a single character.
▪ Asterisk. Represents multiple characters or empty text.
For path hierarchies, use the '/' separator. Filters are case-sensitive. To extract metadata from My Folders, the path in the filter value must start with: /User Folders/My Folders/
The following image shows the filter condition options:
eTo define an additional filter with an OR condition, click the Add icon.
The following image shows that the filter includes metadata from all objects named CustomerReport located across folders in the specified Oracle Business Intelligence repository:
4In the Configuration Parameters area, enter configuration parameters.
The following table describes the properties that you can enter:
Property
Description
Variable Values File
The absolute path to the Oracle Business Intelligence Repository RPD variable values file located on the Secure Agent machine. The file contains a list of RPD variable values in the following format: key=value
Data Sources File
The absolute path to the data sources XML file located on the Secure Agent machine. The file defines the Oracle Business Intelligence Publisher data source connections.
Optimize for Large Models
Choose whether you want to optimize metadata import for large files.
Select one of the following options:
- True. Optimizes the import of metadata for large Oracle Business Intelligence repository models.
- False. Imports metadata of the entire repository model. This might result in a high consumption of memory.
If you select True, Metadata Command Center doesn't import metadata for the following assets:
- Foreign keys
- Joins
- Relationships
- Logical foreign keys
In addition, Metadata Command Center doesn't store expression tree objects with lineage links.
Incremental Import
To configure how you want to extract metadata, select one of the following options:
- True. Extracts only the metadata that changed since the last metadata extraction job.
- False. Extracts the complete metadata.
Worker Threads
The number of worker threads to process metadata asynchronously. You can leave the value empty or enter a positive integer. If you don’t enter a value, Metadata Command Center computes and assigns a value between 1 and 6 based on the JVM architecture and the number of available CPU cores on the Secure Agent machine.
Default values are between 1 and 6. If you enter an invalid value, Metadata Command Center shows a warning and uses the value 1. If your machine has more memory, you can specify a higher value to process more metadata asynchronously.
Note:
Specifying a higher value might impact performance of the system.
Trust Store File
The path to the Oracle Business Intelligence SSL trust store file.
Enter the location of the directory on the Secure Agent machine where you copied the trust store file.
For example, <Informatica Secure Agent installation directory>:\<FolderName>\<truststorefilename.jks>
Trust Store Password
The password to access the contents of the trust store file.
Miscellaneous Options
Enter values for additional extraction runtime options in the following format:
-key <value>
Start each value with a hyphen followed by parameters. Separate multiple values with a space.
5Configure additional capabilities for the catalog source by clicking on the tabs.
Configure data classification
Enable the data classification capability to identify and organize data into relevant categories based on the functional meaning of the data.
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.
1Click Add Data Classification. The Select Data Classifications dialog box appears.
2Select the data classifications that you want to use.
3Click OK.
Configure glossary association
Enable the glossary association capability to associate glossary terms with technical assets, or to get recommendations for glossary terms that you can manually associate with technical assets in Data Governance and Catalog.
Metadata Command Center considers all published business terms in the glossary while making recommendations to associate your technical assets.
1Click the Glossary Association tab.
2Select Enable Glossary Association.
3Select Enable auto-acceptance to automatically 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.
5Select Enable Below-threshold Recommendations to receive glossary association recommendations below the auto-acceptance threshold. If you enable auto-acceptance, you can enable below-threshold recommendations to receive glossary recommendations below the auto-acceptance threshold.
6Specify the Confidence Score Threshold for Recommendations to set a threshold based on which the glossary association capability makes recommendations
If you enable auto-acceptance, specify a percentage from 80 to the selected auto-acceptance threshold. You can accept or reject the recommended glossary terms that fall within this range in Data Governance and Catalog.
If you disable auto-acceptance, specify a percentage from 80 to 100 inclusive.
7Choose to automatically assign business names and descriptions to technical assets. You can then choose to retain existing assignments and only assign business names and descriptions to assets that don't have assignments, or allow overwrite of existing assignments.
By default, existing assignments are retained.
8Optional. 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.
9Optional. 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.
10Optional. Choose to use abbreviations and synonym definitions from lookup tables for accurate glossary association. Select Yes to enable, and then click Select to upload a lookup table.