Metadata Manager: A Developer’s

PerspectiveJamie Toth

UPMC Health PlanPittsburgh Informatica Users Group

Metadata Manager: Resource Catalog Configured, schedulable automatic data pulls catalog objects (tables,

mappings, etc.) from resources (Oracle, Informatica, etc.) Object cataloging does not require programmer intervention. End to End Object cataloging requires configuration of all databases,

targets, and sources called by connections and used in Power Center. Manual cataloging is supported.

Resource Catalog Import Availability (9.1)

Interface Tabs Permissions. Manage permissions on resources and metadata

objects in the Metadata Manager warehouse Load. Create and load resources to load metadata into the Metadata

Manager warehouse. Use the Load tab to monitor and schedule resource loads, purge metadata from the Metadata Manager warehouse, and manage the search index.

Model. Create and edit custom models, add custom attributes to packaged and custom models, and import and export custom models.

Browse. Browse and search the metadata catalog, manage business glossaries, and run data lineage analysis.

Load process Runs workflows and sessions in the background, and loads

information into the repository created for metadata manager. Can take a lengthy amount of time on large, cluttered database schemas

and Power Center folders. Can be monitored through Workflow Monitor.

Power Center Folders can be configured individually or in groups. Full end to end process documentation will require linking of Power

Center folders and database schemas associated with connections within the workflows.

Data profiling on a database would be enabled in these configuration settings.

Oracle Database with Custom SQL Modeling

Browse / Impact Analysis

Data Profiling

Search

End to End Lineage

Lineage as Documentation Image exports for visual elements. Excel / PDF export of metadata. Requires little intervention on the part of developers.

Advantages of Metadata Manager Comprehensive Search Capabilities. Overall data lineage across folders, and to information imported from

outside of Informatica. List of upstream and downstream impacts eliminates the need for

repository queries and guesswork. Shows complexity of environment in a visual way. Helps identify redundant and conflicting processes.

Gives analysts a way to evaluate data lineage without looking at mappings.

Assists in creating a basis of documentation.