Integrated DB2-Powered Infosphere Warehouse and MDM System – F15

Integrated DB2-powered InfoSphere Warehouse and MDM System – F15

Eberhard Hechler IBM Boeblingen R&D Lab & IBM Singapore

Session Code: 2132 Fri, May 18th, 2012 (10:30-11:30 AM) | Platform: DB2 for LUW

Abstract: This session will highlight first experiences of integrating a DB2-powered InfoSphere Warehouse with InfoSphere MDM Server to allow execution of hybrid e-business applications that consist of operational transactions combined with real-time BI analytics. By using MQTs and DB2-based federation techniques, we will show how data redundancy can be reduced. This will be achieved by leveraging a subset of key master data domain records persisted in the DB2 data store of the MDM Server as DB2-based star schema dimensions of some sample data marts. The presentation will provide first experience and best practices of building such an integrated system by concentrating on one of IBM’s DB2-based InfoSphere Warehouse Packs.

• Understand key implementation techniques to derive an integrated DB2- powered InfoSphere Warehouse and MDM system. • Understand how MQTs and DB2-based federation can be used to reduce data redundancy. • Look at an implementation example using one of the DB2-based InfoSphere Warehouse Packs. • Dive into a sample DB2-based star schema implementation by using PARTY and CAMPAIGN master data records as star schema dimensions. • Map IBM’s InfoSphere MDM Server and InfoSphere Warehouse product offerings to the integrated platform.

1 Click to edit Master title style

Disclaimer

• THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF ANY AGREEMENT OR LICENSE GOVERNING THE USE OF IBM PRODUCTS AND/OR SOFTWARE.

• IBM, the IBM logo, ibm.com, WebSphere, Information Management, InfoSphere, and Master Data Management Server, Information Server, Lombardi, Sterling Commerce, Cast Iron, Unica, SPSS, Cognos Business Viewpoint, Traceability Server are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml

• Other company, product, or service names may be trademarks or service marks of others. Click to edit Master title style

5 key Bullet Points

• Understand key implementation techniques to derive an integrated DB2-powered InfoSphere Warehouse and MDM system. • Understand how MQTs and DB2-based federation can be used to reduce data redundancy. • Look at an implementation example using one of the DB2-based InfoSphere Warehouse Packs. • Dive into a sample DB2-based star schema implementation by using PARTY and CAMPAIGN master data records as star schema dimensions. • Map IBM’s InfoSphere MDM Server and InfoSphere Warehouse product offerings to the integrated platform. Click to edit Master title style

Agenda

• Introduction

• InfoSphere Master Data Management (MDM) recap

• DB2-powered InfoSphere Warehouse – Data Models

• InfoSphere Warehouse and MDM integration points • Example implementation • Model Mapping • Methods Click to edit Master title style Motivation for Information-centric Integration Capabilities – Initial Integration Focus Area

• All integration capabilities are viewed from an Information Management and specifically an InfoSphere product stack perspective • Accelerate infrastructure product deployment and time to value by making available integration assets that complement the IM and InfoSphere product stack • Simplify infrastructure usage patterns through pre-integration; ensure consistent usage and deployment patterns • Increase consumability, ease-of-use, and confidence in coexistence and integration capabilities; decrease project execution risk • Initial focus is on „Customer Care & Insight“ solutions, driven by • Customer engagements and requirements • Positive feedback from customers Leads to improved integration capabilities between • Operational MDM • as a transactional hub to deliver a single version of the truth of customer master data • Data Warehouse • to deliver actionable insight into the customer base

The focus of this presentation is on integration of an MDM operational system with a traditional DW environment. The objective of delivering integration assets and value is to accelerate infrastructure product deployment and time to value.

The initial focus is limited to Customer Care and Insight scenarios. Click to edit Master title style

Agenda

• Introduction

• InfoSphere Master Data Management (MDM) recap

• DB2-powered InfoSphere Warehouse – Data Models

• InfoSphere Warehouse and MDM integration points • Example implementation • Model Mapping • Methods Click to edit Master title style IBM MDM Product Portfolio Some new Features in recent Product Releases

• IBM MDM Server v9.0.1 • Importing physical data models into the workbench • Optimized and Transparent SQL (OTS)

• Workbench subtype support IBM® Initiate® IBM® InfoSphere™ Master Data MDM Server Service® Physical master Virtual master registry repository of customer, • IBM Initiate Master Data Service v9.5 for delivering single, account, network & trusted versions of product data for the • Data Trust master data Governance business to consume & their relationships Single View as services Common ® • IBM Initiate Composer IBM InfoSphere™ Components IBM® InfoSphere™ Identity Insight MDM Server for PIM • MDM Powered Solutions Analytical capabilities Authors, enriches and to discover where maintains product and threat & fraud exists other master data for a to enable immediate 360 degree view • IBM InfoSphere MDM Server for PIM v9 action • User Interface Generator • Global Data Synchronization • MDM Workbench enhancements

This chart lists some new features that were made available in recent IBM MDM products. Click to edit Master title style IBM MDM Product Portfolio Mastering Data Domains

• Customers typically

start with a central Relationship

domain & deployment Location Account Product Location Account Customer CUSTOMER to PRODUCT CUSTOMERto pattern Single view of Single view of PARTY PRODUCT • Success with first MDM domain brings more Functions Unified demand from CUSTOMER to ACCOUNT PRODUCT to LOCATION business requiring Relationship Platform, Relationship Processes & additional domains Tools • IBM has pre-packaged Location Customer Product Customer Account Product functionality Master Single view of covering multiple ACCOUNT LOCATION record domains Relationship ACCOUNT to LOCATION ACCOUNT to

The core master data domains are party and product, complemented by account and location. The chart highlight the evolutionary approach of any MDM journey in terms of starting with a chosen subset of available master data domains and adding additional ones as it is required by the line of business. Click to edit Master title style IBM Initiate Master Data Service Functional Overview

• Data Stewardship • Inspect and resolve data quality issues • Visualize and manage relationships • Master Data Engine • Highly accurate and flexible matching and searching across multiple data domains • Load, match and link master data in hours • Flexible and Extensible DB2 Data Model • Model party domain in a user defined manner • Employ data models that are built and optimized specifically for master data management • MDM Powered Solutions Framework • Streamline creating MDM-powered solutions for end users • Integration • Integrate with multiple real-time and batch options • Deliver trusted master data to downstream data warehouse, analytics and BI systems • Message-based support (HL7, JMS, MQ Series)

With IBM Initiate Master Data Service, IBM enable fast deployments of a “System- of-Reference” style MDM system. This style of MDM deployment builds upon a DB2-based “thin” data model, that allows quick integration with multiple transactional systems and delivers trusted master data to downstream systems, such as data warehouse systems, or analytics and BI systems. Click to edit Master title style IBM InfoSphere MDM Server Functional Overview

• Premier Multi-domain, Multi-function • Comprehensive and extensible Party, Account Product domain coverage (data models, services) • Stand-alone and Cross-domain Use Cases • Advance tooling to tailor existing domains and create purpose-built new domains • SOA Library – 700+ pre-packaged services • Significant out of the box product functionality • Composite creation • Reduces total cost of ownership • All types of MDM implementations • Small entry-level index to strategic centralized hub • Grow as required leveraging existing functionality • Wide range of integration scenarios • Lower risk and reduce time/cost to implement • Performance/scalability, Robustness • Proven in large enterprise deployments

IBM InfoSphere MDM Server is the premier multi-domain and multi-function MDM system, which comes along with a library of more than 700 pre-defined and pre-packed master data services. It supports all types of MDM implementations, including a full transactional hub style MDM system. Click to edit Master title style IBM InfoSphere MDM Server for PIM Functional Overview InfoSphere MDM Server for PIMPIM • Collaborative Authoring Processes Collaborative Authoring • Workflows for Collaborative Tasks • Data Synchronization • Imports and Exports with Deltas & Versioning • Job Scheduler Business Process workflow • Authoring UI

• Business User Interface for Authoring & Search NPI Catalog Mgt Multi-Commerce • User and Role Security MDM Custom-Built Domains • Granular Access privileges to enforce complete and accurate data Product Location Supplier Others • User & Role Security • Attribute Level Security • Flexible DB2-based Data Model • Product Catalogs, Category Hierarchies, Attributes, Relationships

IBM InfoSphere MDM Server for PIM is specifically design for collaborative authoring processes and MDM systems with a strong need for data synchronization scenarios. It consists of a very flexible DB2-based data model around products, product catalogs, category hierarchies, attributes, and relationships. Click to edit Master title style IBM MDM Product Portfolio Product Roadmap Drivers1

• Optimized engines MDM Portfolio • Best in class fit for purpose engines • Interoperability MDM Server MDM Server Initiate MDS • Packaged integration between For PIM offerings (e.g., New: Initiate MDS / MDM Server connector) • Common development framework (e.g., Eclipse-based) Interoperability Components • Common technologies • Standardized components (New: embed Initiate Match and Link in MDM Server) Common Technologies • Value-add integration1 (pre-built integration) with InfoSphere portfolio, e.g. • InfoSphere Information Server • InfoSphere Change Data InfoSphere Portfolio Integration Capture (CDC) • Cognos BI • Discovery • FileNet 1) See disclaimer on forward looking statements at the beginning of this presentation

This charts illsutrates IBM’s MDM product portfolio roadmap with regard to focus areas such as delivering a unified and optimized MDM engine with interoperability characteristics, leveraging common technologies, and delivering value-added, pre- built integration. Click to edit Master title style IBM InfoSphere MDM Server DB2-based Data Model – PARTY Example

This chart illustrates a small subset of the DB2-based data model, namely the PARTY example. This will be used further along in the presentation to demonstrate mapping between MDM and DW schemas. The InfoSphere MDM Server is an additional, new source system that complements existing data sources. This new source system is a relational database underlying the InfoSphere MDM Server. The source database model is an out-of-package MDM data model. Click to edit Master title style

Agenda

• Introduction

• InfoSphere Master Data Management (MDM) recap

• DB2-powered InfoSphere Warehouse – Data Models

• InfoSphere Warehouse and MDM integration points • Example implementation • Model Mapping • Methods

The following 5 charts describe some of the DW platform characteristics that have been used as an example to demonstrate the integration between the MDM and DW environments. In some customer projects, the provided data models of the IWH Packs need to be customized to reflect specific customer requirements. These customization and adjustments can be one of the following or even a combination: - Reduction of the data model scope by eliminating certain data objects or a reduction of the KPIs that need to be taken into consideration - Customization of existing data objects, e.g. adding attributes to existing data objects - Adding new objects that are for instance driven by new business requirements, new business measures or KPIs that need to be added to the required reporting InfoSphere Data Architect (IDA) can be used for this task. This adjustments and customization of the underlying data model will result in customization of the provided data model mapping and InfoSphere FastTrack/DataStage (FT/DS) transformation logic Click to edit Master title style The IBM InfoSphere Warehouse Packs Overview – Implementation Example1

• Set of pre-built, consolidated data structures and supporting components: • IBM InfoSphere Warehouse Pack for Customer Insight • IBM InfoSphere Warehouse Pack for Market & Campaign Insight • IBM InfoSphere Warehouse Pack for Supply Chain Insight • Applicable to any Smart Analytics System or Warehouse deployment • Derived from IBM’s industry models and years of successful client engagements across multiple industry sectors • Providing structured and deployable business content to calibrate and accelerate warehouse deployment around Customer, Market and Campaign, and Supply Chain Insight! • Content of the IBM InfoSphere Warehouse Packs • Physical Data Model • Sample physical DB structures • Sample Cognos Reports • Documentation providing guidance on deploying the Pack technical assets to Metadata Server, and guidance on the deployment/customization of this offering • Detailed guidelines on ETL and staging area provisioning • Consulting Services are available to support every aspect of the development life-cycle 1) See disclaimer on forward looking statements at the beginning of this presentation Click to edit Master title style IBM IWH Pack for Customer Insight Overview

InfoSphere Warehouse Pack for Customer Insight 8.2 • Physical data model (.dbm file) • Customer profiling • Customer profitability • Sample physical DB structures (.ddl files) • Dimensional warehouse (SOR) • 15 tables • Datamart structures • 4 fact tables plus reference data • Sample Cognos reports (.xml files) • Cognos framework manager model • Documentation (.pdf files) Click to edit Master title style DB2 – IWH Pack for Customer Insight • A set of 20+ predefined Cognos Reports is supplied with the ISW Pack for Customer Insight • Intended to give examples of the type of reporting capable with this Model

Customer Insight

Communications Analysis Customer Activity and Complaints Customer Survey Response by Age Group Customer Survey Response by Socio Economic Group Customer Survey Response Details Customer Transaction Analysis Profiling Customer Listing Product Sales Analysis Profit by Socio Economic Group and Product Type Top Performers by Income Top Performers by Volume Transaction Listing Volume Sales by Channel Volume Sales by Customer Age Group

Profitability Analysis Average Income and Profit Customer Profitability - Europe Customer Customer Profitability - North America Profitability Income and Profit – Actual vs Budget by Year Renewals Analysis – Individual Renewals Analysis – Organization Periodic Analysis Current Quarter v Same Quarter Last Year (Individual) Current Quarter v Same Quarter Last Year (Organization) This Year to date vs Last year to date (Organization) Year on Year Profitability Comparison (Individual) Year on Year Profitability Comparison (Organization) Click to edit Master title style Integrated DB2-powered Warehouse and InfoSphere MDM Platform The larger Picture – Examples of Integration Areas

• Build integrated MDM and BI/Warehousing schema to allow execution of new and emerging hybrid workloads • Demand for operational transactions combined with real-time advanced analytics • Demand to exploit KPIs and analytical insight within real-time operational transactions • Reduce data redundancy between master data records persisted in InfoSphere MDM Server data store and the InfoSphere Warehouse SOR • Materialize master data domain records only once within combined schema • Leverage MDM master data domain records for warehouse and data mart schemas • Enable low-latency to real-time synchronization from InfoSphere MDM Server to InfoSphere Warehouse SOR and derived data mart(s) • Allow „write-back“ of analytical insight from BI/Warehousing schema to MDM Server for insight to be leveraged by operational usage scenarios • Analytical insight that is relevant for managed master data domains • Analytical insight that is derived through • Standard reporting and dashboarding • Analytical engines, e.g. SPSS Click to edit Master title style The overall Information Mangement Landscape Focus on InfoSphere Warehouse Packs

• Over time the intention is to expand the Packs principle to the broader IM landscape • Initial technology focus for InfoSphere Warehouse Packs Design Model - Physical Data Model Customer Insight - Cognos FM Model

Concerned with knowing all relevant info about our current Cognos customers Master InfoSphere Market & Campaign Insight Information Warehouse Hub/MDM Concerned with knowing the details of the overall market and Server how to acquire new customers SPSS Supply Chain Insight Information Server Concerned with understanding all of the relevant aspects of the suppliers to the Business

SOURCE SYSTEMS, Smart Analytics System DATA MARTS, SILOS COMMON METADATA Click to edit Master title style

Agenda

• Introduction

• InfoSphere Master Data Management (MDM) recap

• DB2-powered InfoSphere Warehouse – Data Models

• InfoSphere Warehouse and MDM integration points • Example implementation • Model Mapping • Methods Click to edit Master title style InfoSphere MDM and Data Warehouse Integration Initial Focus Area

• Integration for improved Customer Insight • Provides deployment acceleration and enablement • Serves as a generic and cross-Industry, InfoSphere-centric integrated value • Serves as an enabler for specific Industry solutions focusing on customer insight • Provides pre-packaged, pre-tested integration value • Initial focus is on integration of operational MDM with analytical BI/Data Warehousing with focus on InfoSphere Warehouse Packs

• Provides integration value, content and assets on top of IM product stack Following list describes the initial integration scope • Data model mapping between InfoSphere MDM Server and IWH Pack for Customer Insight – other IWH Packs under consideration • InfoSphere DataStage transformation jobs and skeletons • Analytical models to deliver customer insight • Set of Cognos BI reports • InfoSphere Blueprint Director models to define & manage the end-to-end information flow

This charts lists the integration related value, content, and assets. The core asset is the data model mapping between the InfoSphere MDM Server data model and the data warehouse data model. Click to edit Master title style InfoSphere Data Architect (IDA) Create initial Mappings

This chart illustrates a small example of the data model mapping as it can be done with InfoSphere Data Architect (IDA). This chart also depicts where the mapping of objects between MDM and the data warehouse is possible and meaningful. There may actually be quite a number of objects within the MDM data model that cannot and should not be mapped to the data warehouse schema. Further refinement and customization of the data model mapping has to be done, even if no data model adjustments are performed on either system: MDM Server and the data warehouse side. For instance, further data model mappings have to be performed between the S_CODE table and the TYPE, CODE, and LOOKUP tables of the MDM Server that are relevant form a customer insight perspective. 23 Click to edit Master title style MDM Server v8.5 Data Model Mapping

• MDM data model • MCIP data model (staging) • MCIP data model (SOR)

• CONTACT • S_CUSTOMER • CUSTOMER •Has CONT_ID (PK) •Has S_CST_ID (PK) •Has CST_ID (PK) •Contains link to type: either •Contains CST_NUM, •Contains CUST_NUM, PSN_ID, ORG or PERSON PSN_REFR_NUM, HH_ID, ORG_ID HH_REFR_NUM, • IDENTIFIER ORG_REFR_NUM • EMPLOYEE •Contains CONT_ID (FK) •Has EMPE_ID (PK) • S_EMPLOYEE •Contains EMPE_NUM, PSN_ID, • ORG •Has S_EMPE_ID (PK) ORG_ID •Contains CONT_ID (PK, FK) •Contains EMPE_NUM, PSN_REFR_NUM, • HOUSEHOLD • PERSON ORG_REFR_NUM •Has HH_ID (PK) •Contains CONT_ID (PK, FK) •Contains HH_REFR_NUM, • S_HOUSEHOLD • SUSPECT •Has S_HH_ID (PK) • ORGANIZATION •Contains CONT_ID (FK) •Contains HH_REFR_NUM •Has ORG_ID (PK) •Contains ORG_REFR_NUM • S_ORGANIZATION •Contains NUM_OF_CUST, •Has S_ORG_ID (PK) NUM_OF EMP •Contains ORG_REF_NUM •Contains NUM_OF_CUST, • PERSON NUM_OF_EMP •Has PSN_ID (PK) •Contains HH_ID • S_PERSON •Contains dependent children •Has S_PSN_ID (PK) and adults •Contains PSN_REFR_NUM, HH_REFR_NUM •Contains dependent children and adults

This charts illustrates the relationship between the key PARTY-related objects in the InfoSphere MDM Server and the correspondi For instance, the PERSON object in the MDM data model is mapped to the S_PERSON object in the data warehouse staging area. Click to edit Master title style Tooling Infrastructure

• Perform initial data mapping in InfoSphere Data Architect (IDA) • Annotations for transformation logic • Create detailed mapping in InfoSphere Fast Track • Transformation logic • Mapping to non-business data • Develop ETL jobs in InfoSphere DataStage jobs • Complex transformation logic • Develop/enhance Analytical models and BI reports for Customer Insight Pack • Blueprint Director models for end-to end information flow

In order to use the data model mapping for the required customization of InfoSphere DataStage (DS) transformation jobs, the data model mapping will be deployed on InfoSphere FastTrack (FT). FT can also be used to perform any required mapping customization. For this, the MSL file has to be imported into FT. Following is the methodology to import the IDA MSL file into FT:

- Export an MSL file to CSV - Import the DBM model into the InfoSphere Metadata Server - Import the CSV mapping into FastTrack

Once the data model mapping is imported into FT, the provided DS transformation jobs can now be customized and adjusted to reflect the data model changes and adaptations that were done on the MDM Server and the IWH Packs. Click to edit Master title style InfoSphere FastTrack (FT) Define Mapping Specifications

• Define transformation logic, selection criteria, lookups, populate non-business tables etc.

This is a screen shot of the InfoSPhere FastTrack (FT) tool regarding the definition of the mapping specifications. Click to edit Master title style PARTY-related Mapping – detailed View

InfoSphere MDM Server IWH Pack for MCI • MDM CONTACT (PARTY) can • In MCIP, there is no „general“ CONTACT be (PARTY) object • PERSON • S_PERSON can be • ORG • S_EMPLOYEE • IDENTIFIER further specifies a) Link to „internal“ ORG type in CDORGTP CONTACT e.g. via passport_id, b) Link to S_EMPLOYEE in the context of a CONTRACT via „emp“ type in company_id, driver_license_id, CDCONTRACTROLETP (as not all S_EMPLOYEES ... of an S_ORGANIZATION may manage an S_AGREEMENT) • S_CUSTOMER a) MDM PARTY is S_CUSTOMER if CONTRACT exists in MDM b) S_CUSTOMER can also be an S_ORGANIZATION

IDENTIFIER CONTACT S_PERSON S_ORGANIZATION (PARTY)

PERSON ORG S_EMPLOYEE S_CUSTOMER

This chart illustrates the different structures of the PARTY-related objects and the corresponding mapping between the Master Data and the Data Warehouse side. Click to edit Master title style PARTY-related Mapping – detailed View

IDENTIFIER contains addtl. credentials, e.g. IDENTIFIER S_PERSON can play a role passport, driver license S_PERSON as S_CUSTOMER and/or ... S_EMPLOYEE cont_id ...... psn_refr_num ...

CONTACT CONTACT is either PERSON or ORG cont_id • S_PERSON is S_CUSTOMER, if S_CUSTOMER cst_num and ... CONTRACT exists in MDM psn_refr_num • S_CUSTOMER can be identical person_org_code CHAR(1) column to S_ORG or S_PERSON ...... determine PERSON cst_num or ORG ... psn_refr_num PERSON org_refr_num ... cont_id ... S_CUSTOMER can be an S_ORG empe_num and psn_refr_num S_EMPLOYEE identical Defines PERSON ... CONTACTREL to ORG relationship empe_num ...... from_cont_id psn_refr_num to_cont_id org_refr_num ...... Link to Can be internal internal ORG ORG or external ORG S_ORGANIZATION via CDORGTP cont_id ...... org_refr_num ...

This figure provides further details regarding the mapping of the InfoSphere MDM Server to the Data Warehouse staging areas regarding the S_CONTRACT-related and S_PARTY-related mappings. Detailed view of the S_PARTY-related mapping. Click to edit Master title style CONTRACT-related Mapping – detailed View

CONTRACT S_AGREEMENT contract_id ...... agreement_tp_cd agrm_tp ...... product_id pd_num ... Mapping of PRODUCT via CONTRACT table ... agrm_refr_num ... CONTRACTCOMPONENT cst_num ... contract_id CONTRACTCOMPONENT empe_num ... mapped to S_AGREEMENT PARTY could also be an ... contr_component_id S_EMPLOYEE if ORG with ... „internal“ type exists in MDM S_EMPLOYEE CONTRACTROLE MDM PARTY mapped to CONTRACT, identifying PARTY ...... as S_CUSTOMER via „cust“ empe_num Type in CDCONTRACTROLETP contr_component_id ... cont_id contr_role_tp_cd MDM PARTY mapped to S_CUSTOMER ... CONTRACT, identifying PARTY Identified cont_id in MDM will be as S_EMPLOYEE via „emp“ taken as S_CUSTOMER because Type in CDCONTRACTROLETP of existence of ... CDCONTRACTROLETP CONTRACTCOMPONENT cst_num and PRODUCT in CONTRACT ...... contr_role_tp_cd CDAGREEMENTTP ... S_PRODUCT ...... agreement_tp_cd pd_num ......

This figure provides further details regarding the mapping of the InfoSphere MDM Server to the Data Warehouse staging areas regarding the S_CONTRACT-related and S_PARTY-related mappings. It is a detailed view of the S_CONTRACT-related mapping. Click to edit Master title style InfoSphere MDM and Data Warehouse Integration InfoSphere Blueprint Director – Content & Integration

• Integrate InfoSphere Blueprint Director with focus on Warehouse Packs • Blueprint director model for IWH Packs based on new content and integration scope

The IBM InfoSphere Blueprint Director provides a possibility to depict the overall integration architecture. It also allows further customization and adaptation regarding the concrete customer IT infrastructure. Click to edit Master title style InfoSphere MDM and Data Warehouse Integration InfoSphere Blueprint Director – Analytics

The IBM InfoSphere Blueprint Director provides a possibility to depict the overall integration architecture. It also allows further customization and adaptation regarding the concrete customer IT infrastructure. This chart is a screen shot of the Analytics component. Click to edit Master title style InfoSphere MDM and Data Warehouse Integration InfoSphere Blueprint Director – Party Segmentation

This chart contains further details on the PARTY (for instance: customer) segmentation. Click to edit Master title style Integrated Warehouse and MDM Platform Integrated System-of-Record – Example Schema

Master Data Management Services

CRUD Requests | Business Services | Admin Services Master Data may be persisted within other systems, depending on MDM deployment style „Materialized“ Master Data Domain Representation Relational Data Model

Transformation Customer Product Account Aggregation

Federation Integrated (incl. master data) SOR

System of MQTs Bi-directional Replication & Synchronization Record (virtual | real)

• Bi-directional replication and synchronization is based • „Materialized“ master data domain on InfoSphere Information Server and InfoSphere CDC representation will be used as part of • Includes required transformation and data quality integrated SOR improvement, data cleansing, ... • Federation may be used to build SOR, • Includes federation to include master data records from incl. Data sources ouside MDM domain „materialized“ master data domain representation • Allows real-time access to master data from BI analytical • MQTs can be entirely materialzed or applications virtual, or a combination

This is a very high-level Architecture Overview Diagram (AOD) on further more in-depth integration options between the MDM and the Data Warehouse components. It also illustrates the usage of DB2 functions. Click to edit Master title style

5 key Bullet Points

• Understand key implementation techniques to derive an integrated DB2-powered InfoSphere Warehouse and MDM system. • Understand how MQTs and DB2-based federation can be used to reduce data redundancy. • Look at an implementation example using one of the DB2-based InfoSphere Warehouse Packs. • Dive into a sample DB2-based star schema implementation by using PARTY and CAMPAIGN master data records as star schema dimensions. • Map IBM’s InfoSphere MDM Server and InfoSphere Warehouse product offerings to the integrated platform. Click to edit Master title style Your Feedback, Questions, and Comments are highly welcome

Thank you! Eberhard Hechler IBM Boeblingen R&D Lab & IBM Singapore [email protected] Session 2132 Integrated DB2-powered InfoSphere Warehouse and MDM System

Biography: Eberhard Hechler, SCITA, Executive IT Architect, joined the IBM Boeblingen R&D Lab in 1983. After a 2,5 year international assignment to the IBM Kingston Lab in New York, he has worked in software development, performance optimization and benchmarking, and solution architecture and design. Since 1992, his focus is on DB2 and Information Management. His main expertise includes the areas of DB2 on LUW, information integration, MDM and DB2-based Data Warehousing. He is a member of the IBM Academy of Technology, the IBM Asset Architecture Board, and the IBM InfoSphere Architecture Board. He co-authored the following books: (1) Enterprise Master Data Management, 2008, Pearson plc, and (2) The Art of Enterprise Information Architecture, 2010, Pearson plc.