Metadata Manager
- Metadata Manager 10.5
- All Products
Property
| Description
|
---|---|
Catalog_Import_Batch_Size
| Number of elements that Metadata Manager processes in one batch when you import metadata for a custom resource from an XML file. Increase this value if errors occur during XML import. Specify any positive integer value. Default is 5000.
|
ElementFetch.ParamSize
| Number of elements that Metadata Manager processes to calculate the impact summary. You can specify any value greater than zero. Decrease the value if errors occur during impact summary calculation. Default is 10,000.
|
ETL_Task_Run_Status_Poll_Interval
| Interval, in seconds, in which the Metadata Manager Service writes ETL task run statistics to the mm.log file. Increase this value to write fewer messages to the log file. Specify any positive integer value. Default is 5.
|
GatherStatistics
| Gathers statistics after loading resources if set to yes. You can gather statistics when the Metadata Manager repository is on any relational database.
Gathering statistics improves performance of linking and catalog operations such as browse and lineage. However, there might be an increase in the time taken to load resources.
Default is Yes.
If the Metadata Manager repository is on IBM DB2 and GatherStatistics is set to yes, ensure that the IBM DB2 user has execute permissions on SYSPROC.ADMIN_CMD and SYSPROC.REBIND_ROUTINE_PACKAGE.
|
Hide_Empty_Uneditable_Properties
| Hides empty and uneditable property values in all Metadata Manager perspectives when set to the default value. Default is Y.
|
ImpactSummary.MaxObjects
| The maximum number of objects to appear in the impact summary user interface. You can specify any non-negative integer value. If you specify zero, all objects appear in the impact summary user interface. Default is 150.
When you export the impact summary results, the value of the ImpactSummary.MaxObjects property does not apply and all objects are exported.
|
indexing.mergeFactor
| Controls the number of metadata objects to store in memory before merging them into the index. Increase the default value to improve indexing performance for Metadata Manager. Default is 100.
If you set the value too high for your environment, a Java exception might occur due to too many open files.
|
indexing.ramBufferSize
| Determines the amount of memory used to buffer metadata objects before they are merged into the index. Increase the default value to improve indexing performance for Metadata Manager. Default is 256 MB.
If you set the value too high for your environment, the following error might occur:
|
Load.OracleOptimizerDynamicSampling
| Sets the Oracle session parameter OPTIMIZER_DYNAMIC_SAMPLING on the PowerCenter sessions that load to a Metadata Manager repository on Oracle.
Enter one of the following values:
Contact your Oracle database administrator to get the appropriate value for your environment.
Default is -1.
To use this option, Cost Based Optimization (CBO) must be enabled on the Oracle instance.
|
mail.from.defaultEmailId
| Email address used as the default sender address when a user does not have an email address in the system. If you do not set this property, and the user profile does not contain an email address, the user cannot send email from Metadata Manager.
|
Missing_Links_Report_Limit
| Limits the maximum number of missing links you want to export. Default is 64000.
|
Miti_Client_Version
| Current version of the Metadata Manager Agent client used by Metadata Manager. The Metadata Manager Agent that you use to load resources must match this version.
|
MitiValidationLevel
| Specifies the level of consistency check to perform while loading business intelligence and data modeling resources.
Enter one of the following values:
Default is NONE.
|
Publish.MaxObjects
| Maximum number of objects to include in the export file when you export custom and business name properties for a resource, logical group, or metadata object. Default is 200.
When you increase this limit, the Metadata Manager Service consumes additional memory in direct proportion to the value that you specify. Therefore, Metadata Manager performance can decrease.
|
SAP_MAX_TABLES
| Maximum number of tables Metadata Manager retrieves from SAP R/3 when you configure the components to extract from SAP R/3. SAP R/3 sources contain many tables. Use this setting to increase Metadata Manager performance when it retrieves application components, packages, and tables from SAP R/3.
|
search.allow.constant.score
| Enables Metadata Manager to rewrite wildcard search queries in a more efficient form if required. If you enable this property, Metadata Manager does not rank some wildcard searches correctly. Enable this property if you run wildcard searches that can match large numbers of search terms, you have increased search.max.clause.count, and the machine does not have enough memory to further increase search.max.clause.count. Default is false.
|
search.max.clause.count
| Maximum number of search terms that Metadata Manager can use in a contains, starts with, or wildcard search. For example, if you search for "cat*," Metadata Manager might create a query to find the terms "category" or "catalog" or "cat." If the number of search terms exceeds this limit, Metadata Manager cannot run the search. Default is 1024.
Increase this limit if you run wildcard searches that can produce large numbers of search terms. If you increase this limit, the Metadata Manager service might consume large amounts of memory when you run a search.
|
search.max.docs
| Maximum number of search results that Metadata Manager displays for a catalog search. Decrease the default value to improve search performance for Metadata Manager. Default is 1000.
If you set the value too high for your environment, the following error might occur:
|
Session.timeOut
| Duration after which the cookie expires.
When you log in to Metadata Manager, the Informatica Service Manager creates a cookie that it uses to authenticate your user name in Metadata Manager. If you access Metadata Manager again before the cookie expires, the Service Manager uses the authentication information in the cookie to log you in to Metadata Manager.
You can set a value from 30 through 43,200 minutes.
|
shortcut.classes
| Lists the classes that are shortcuts. When you add a shortcut class to this list of classes, children of that shortcut appear in the Catalog tree.
|
Show_Synthetic_Dates_In_Basic_Section
| Displays the synthetic dates in the Basic or Advanced section of the class properties, in all Metadata Manager perspectives.
Enter one of the following values:
After you set this value, you cannot change the display location of these properties in the user interface.
For a class, Source Creation Date, Source Update Date, MM Creation Date, and MM Update Date properties are referred as the synthetic date properties.
Default is N.
|
UseCustomStopWords
| Determines which list of common words that Metadata Manager ignores in a search. If you set this property to true, Metadata Manager uses the custom list in the stopwords.txt file. If you set this property to false, Metadata Manager uses the default list of common words to ignore in a search. Default is false.
|
xconnect.custom.failLoadOnErrorCount
| Maximum number of errors that the Metadata Manager Service can encounter before the custom resource load fails. Specify any positive integer value.
Default is 18,000.
|
xconnect.io.print.batch.errors
| Number of errors that the Metadata Manager Service writes to the in memory cache and to the mm.log file in one batch when you load a custom resource. Increase this value to reduce the time it takes for the Metadata Manager Service to log the errors. Specify any positive integer value.
Default is 100.
|