Informatica Master Data Management
Multidomain MDM creates and maintains master data, which is a collection of core entities along with their attributes and their values that are critical to a business.
Objects Extracted
You can use the Informatica MDM resource to extract metadata from the following assets in an Informatica MDM data source:
- •Business entities
- •Business entity views
- •Staging tables
- •Landing tables
- •Relationships
- •Base objects
- •Cross reference tables
- •Attribute information of all business entities
You can view lineage for the following assets in the Catalog:
- •Landing tables and staging tables
- •Staging tables and cross reference tables
- •Cross reference tables and base objects
- •Base objects and business entities
Note: Enterprise Data Catalog version 10.4.1 supports Multidomain MDM version 10.4.0 or later.
Prerequisites
- •Register the Operational Reference Store (ORS) on the Informatica MDM Hub Console.
- •Configure the Informatica Data Director (IDD) application on the ORS using the Informatica Data Director Configuration Manager.
Basic Information
The General tab includes the following basic information about the resource:
Information | Description |
---|
Name | The name of the resource. |
Description | The description of the resource. |
Resource type | The type of the resource. |
Execute On | You can choose to execute on the default catalog server or offline. |
Resource Connection Properties
The General tab includes the following properties:
Property | Description |
---|
SSL Enabled | Indicates whether the MDM Provisioning tool uses SSL. |
Provisioning Host | Enter the host name to connect to the MDM Provisioning tool. |
Provisioning Port | Enter the port number of the MDM Provisioning tool. |
Provisioning Login User Name | Enter the user name to connect to the MDM Provisioning tool. |
Provisioning Login Password | Enter the password to connect to the MDM Provisioning tool. |
Database ID | Enter the database ID of the schema registered on the Informatica MDM Hub Console. Note: The database ID of the schema must be in lowercase. |
The Metadata Load Settings tab includes the following properties:
Property | Description |
---|
Enable Source Metadata | Extracts metadata from the data source. |
Memory | Specifies the memory required to run the scanner job. Select one of the following values based on the data set size imported: Note: For more information about the memory values, see the Tuning Enterprise Data Catalog Performance article on How To-Library Articles tab in the Informatica Doc Portal |
Custom Options | JVM parameters that you can set to configure scanner container. Use the following arguments to configure the parameters: - - -Dscannerloglevel=<DEBUG/INFO/ERROR>. Changes the log level of scanner to values, such as DEBUG, ERROR, or INFO. Default value is INFO.
- - -Dscanner.container.core=<No. of core>. Increases the core for the scanner container. The value should be a number.
- - -Dscanner.yarn.app.environment=<key=value>. Key pair value that you need to set in the Yarn environment. Use a comma to separate the key pair value.
- - -Dscanner.pmem.enabled.container.memory.jvm.memory.ratio=<1.0/2.0>. Increases the scanner container memory when pmem is enabled. The default value is 1.
|
Track Data Source Changes | View metadata source change notifications in Enterprise Data Catalog. |
Viewing Detailed Lineage between Informatica MDM and Informatica Platform Resources
To view the detailed lineage between Informatica MDM and Informatica Platform resources for data quality, and data integration mappings, perform the following steps:
- 1. Create and run an Informatica MDM resource.
- 2. Create an Informatica Platform resource, and enable Detailed Lineage for the resource.
- 3. Run the Informatica Platform resource.
- 4. Use the Connection Assignment option to configure the MDM and Informatica Platform resources as destination or target data sources. For more information about assigning connections, see the Managing Connections topic.
Note: Verify that the resource scan status of both the resources is complete before performing connection assignment.