MDM - Siperian Info

Master Your Data, Master Your Business

Informatica MDM is designed to make your master data management (MDM) initiative successful. Its flexible multidomain MDM technology and unique trust framework enable rapid deployments and extensibility across the enterprise. With a proven track record of success in tackling any data-driven business problem in any industry, Informatica MDM maximizes business value by delivering comprehensive, unified, open, and economical MDM on a single platform.

1. Maximize account penetration in MDM by improving cross-sell and up-sell offers with a single or an extended customer view.

2. Easily comply with regulatory initiatives in MDM by improving the tracking, transparency, and auditing of financial data.

3. Make decisions around MDM more confidently across the global enterprise through increased accuracy, reliability, and timeliness of business-critical data.

The new version of Business Data Director significantly improves the overall productivity of business users by allowing them to customize the look and feel of the application to suit their preferences. Other new enhancements include Business Data Director's ability to integrate with external applications and provide "custom action" capabilities, which allow users to extend the data to other applications. Using advanced data federation features, line of business users can see critical transactional data within Business Data Director that enables them to perform more complex, real-time business processes such as order to cash and cross-sell and up-sell of additional products to existing customers.

There are different component of Informatica MDM Siperian HUB mentioned below.

1. MRM
2. BDD
3. HR
4. Console Manager.
5. SIF

Start up of informatica Siperian HUB :-

1. Make sure Oracle services are started on your virtual/Hosted machine.
2. Open command window and enter the following commands to start the JBOSS application server
3. CD C:\Jboss*\bin
4. Run bat –b 0.0.0.0
5. Open the informatica MDM multidomain Edition Console, by opening internet explorer and go to http://infa-server : 8080/cmx and click the launch button on the page.
6. Login with user name and Password
7. Select the target database [TR_LAB].

Define Data Model

1. Create target base table object. [Ex ADDRESS table]
2. Enable History while creating staging table.
3. Define the relation ship of base table object with other base table base object [It’s like you define the schema for base object.]
4. There could be multiple source system for same base table object [like SALES and CRM]
5. Define target data model.
6. Metadata manager option helps in importing a data model from outside Informatica HUB. It can come from 3rd party vendor tool.
7. Naming convention should be correct for all the Landing, Staging and Target tables to maintain the metadata relation.
8. “Contains Full Dataset” Property related with Delta detection while loading in landing table.

WORKSHOP MENU [Configuration -> Metadata manager]

There are 2 types of schema in MDM Hub which is

1. System schema: - we do not create these; it got created at the time of installation of the siperian].
2. ORS schema [we use these schema]

Metadata manager is different than metadata from powercenter.

For importing any table from metadata manager, first we need to validate the ORS schema[database] then after you will be able to import table from different ORS.

Some Random Info about Siperian Process :-

1. Define the trust level.
2. Dynamic CELL LEVEL Survivorship.
3. IDD is how we consume the clean records from MDM Hub or create message queues.
4. We can use stored procedure or ETL to populate the landing table.
5. ETL must truncate the landing table before loading the landing table.
6. Duplicate records in the landing table will be rejected during the staging process. (REJECT/RAW tables)
7. There should be provision of auditing data lineage.
8. Base table = Normal Columns + System generated columns.
9. Data Model Elements
10. Provide functionality for matching and merging data. There are different tables which got created in the the HUB which helps in merging and matching records ex.  OPL, MTCH, MGE, HREF, XREF tables
11. Built in Lineage (Cross-Ref tables) and history.
12. Support trust and validations rules.
13. Supports matching and merging.
14. ROWID_OBJECT is automatically generated and managed. [Port of base table]
15. Each base object has underlying cross-reference (XREF) table and it is created and managed by the system. Purpose is to cross reference with other base tables.
16. XREF is link between source key and base Object Key.
17. All the system tables start with C_REPO*.

About Staging Table

1. Intermediate work table.
2. Belongs to specific source system.
3. Staging table columns are a selected subset of user-defined columns in base object.
4. Staging table automatically has following columns
• Last_update_Date
• Source key
• SRC_ROWID
5. Staging table will have only one source and one target.
6.  Staging table has reject table. It can also have history table.

Relationship type: - you can create only virtual relationship. It can be one to many or many to many. (In many to many type relations, you need to create a intersection point)

Look Up: - When loading happens from staging to target base object table. Then Look up process also starts parallel. In other words look up in siperian  is a translation of source’s primary or foreign key value into the corresponding base object value. This specifies the relationship between two different base objects. Siperian look up is different than informatica powercenter lookup. Hub system automatically handles look ups for primary key on base objects records, by using the base object’s X-REF. if no value is found, then the new ROWID_OBJECT value will be generated.

ROW_ID :- System generate their own row_id and connect it to the primary key which is coming from the source system and store this relationship in the XREF table (can have multiple records from different source system with some ROW_ID object[Logically both records will be same])

About Siperian:- Siperian acquired  DELLOF, and then Informatica acquired Siperian.

 

 

Rohit..........