Metadata Manager

Effective in version 10.1, you can create universal resources to extract metadata from some metadata sources for which Metadata Manager does not package a model. For example, you can create a universal resource to extract metadata from an Apache Hadoop Hive Server, QlikView, or Talend metadata source.

To extract metadata from these sources, you first create an XConnect that represents the metadata source type. The XConnect includes the model for the metadata source. You then create one or more resources that are based on the model. The universal resources that you create behave like packaged resources in Metadata Manager.

For more information about universal resources, see the "Universal Resources" chapter in the Informatica 10.1 Metadata Manager Administrator Guide.

Incremental Loading for Oracle and Teradata Resources

Effective in version 10.1, you can enable incremental loading for Oracle resources and for Teradata resources. An incremental load causes Metadata Manager to load recent changes to the metadata instead of loading complete metadata. Incremental loading reduces the amount of time it takes to load the resource.

To enable incremental loading for an Oracle resource or for a Teradata resource, enable Incremental load option in the resource configuration properties. This option is disabled by default.

For more information about incremental loading for Oracle and Teradata resources, see the "Database Management Resources" chapter in the Informatica 10.1 Metadata Manager Administrator Guide.

Hiding Resources in the Summary View

Effective in version 10.1, you can prevent a resource and its child objects from being displayed in the summary view of data lineage diagrams. To hide a resource, enable the Hide in Summary Lineage option on the Properties page of the resource configuration properties. This option is available for all resource types. It is disabled by default.

You can hide objects such as staging databases from data lineage diagrams. If you want to view the hidden objects, you can switch from the summary view to the detail view through the task bar.

For more information about the summary view of data lineage diagrams, see the "Working with Data Lineage" chapter in the Informatica 10.1 Metadata Manager User Guide.

Creating an SQL Server Integration Services Resource from Multiple Package Files

Effective in version 10.1, you can create a Microsoft SQL Server Integration Services resource that extracts metadata from packages in separate package (.dtsx) files. The package files must be in the same directory.

To create a resource that extracts metadata from packages in different package files, specify the directory that contains the package files in the Directory resource configuration property.

For more information about creating and configuring Microsoft SQL Server Integration Services resources, see the "Database Management Resources" chapter in the Informatica 10.1.1 Metadata Manager Administrator Guide.

Metadata Manager Command Line Programs

Effective in version 10.1, Metadata Manager has a new command line program. The mmXConPluginUtil command line program generates the image mapping information or the plug-in for a universal XConnect.

Command Name	Description
generateImageMapping	Generates the image mapping information for a universal XConnect.
generatePlugin	Generates the plug-in for a universal XConnect.

For more information about the mmXConPluginUtil command line program, see the "mmXConPluginUtil" chapter in the Informatica 10.1 Metadata Manager Command Reference.

Application Properties

Effective in version 10.1 you can configure new application properties in the Metadata Manager imm.properties file. This feature is also available in 9.6.1 HotFix 4. It is not available in 10.0.

The following table describes new Metadata Manager application properties in imm.properties:

Property	Description
xconnect.custom.failLoadOnErrorCount	Maximum number of errors that the Metadata Manager Service can encounter before the custom resource load fails.
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.

For more information about the imm.properties file, see the "Metadata Manager Properties Files" appendix in the Informatica 10.1 Metadata Manager Administrator Guide.

Migrate Business Glossary Audit Trail History and Links to Technical Metadata

Effective in version 10.1, you can migrate audit trail history and links to technical metadata when you export business glossaries. You can import the audit trail history and links in the Analyst tool.

This feature is also available in 9.6.1 HotFix 4. It is not available in 10.0.

For more information, see the Informatica 10.1 Upgrading from Version 9.5.1 Guide.