Informatica MDM Multidomain Edition (Version 1) Unclaimed Life Insurance Data Management Solution Guide

Informatica MDM Multidomain Edition (Version 1) Unclaimed Life Insurance Data Management Solution Guide

Informatica MDM Multidomain Edition Unclaimed Life Insurance Data Management Solution Guide Version 1 May 2014 Copyright (c) 2014 Informatica Corporation. All rights reserved. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents Pending. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013 (1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing. Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright Sun Microsystems. All rights reserved. Copyright RSA Security Inc. All Rights Reserved. Copyright Ordinal Technology Corp. All rights reserved.copyright Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright Meta Integration Technology, Inc. All rights reserved. Copyright Intalio. All rights reserved. Copyright Oracle. All rights reserved. Copyright Adobe Systems Incorporated. All rights reserved. Copyright DataArt, Inc. All rights reserved. Copyright ComponentSource. All rights reserved. Copyright Microsoft Corporation. All rights reserved. Copyright Rogue Wave Software, Inc. All rights reserved. Copyright Teradata Corporation. All rights reserved. Copyright Yahoo! Inc. All rights reserved. Copyright Glyph & Cog, LLC. All rights reserved. Copyright Thinkmap, Inc. All rights reserved. Copyright Clearpace Software Limited. All rights reserved. Copyright Information Builders, Inc. All rights reserved. Copyright OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rights reserved. Copyright International Organization for Standardization 1986. All rights reserved. Copyright ejtechnologies GmbH. All rights reserved. Copyright Jaspersoft Corporation. All rights reserved. Copyright is International Business Machines Corporation. All rights reserved. Copyright yworks GmbH. All rights reserved. Copyright Lucent Technologies. All rights reserved. Copyright (c) University of Toronto. All rights reserved. Copyright Daniel Veillard. All rights reserved. Copyright Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright MicroQuill Software Publishing, Inc. All rights reserved. Copyright PassMark Software Pty Ltd. All rights reserved. Copyright LogiXML, Inc. All rights reserved. Copyright 2003-2010 Lorenzi Davide, All rights reserved. Copyright Red Hat, Inc. All rights reserved. Copyright The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright EMC Corporation. All rights reserved. Copyright Flexera Software. All rights reserved. Copyright Jinfonet Software. All rights reserved. Copyright Apple Inc. All rights reserved. Copyright Telerik Inc. All rights reserved. Copyright BEA Systems. All rights reserved. Copyright PDFlib GmbH. All rights reserved. Copyright Orientation in Objects GmbH. All rights reserved. Copyright Tanuki Software, Ltd. All rights reserved. Copyright Ricebridge. All rights reserved. Copyright Sencha, Inc. All rights reserved. This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and/or other software which is licensed under various versions of the Apache License (the "License"). You may obtain a copy of these Licenses at http://www.apache.org/licenses/. Unless required by applicable law or agreed to in writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses. This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of the GNU Lesser General Public License Agreement, which may be found at http:// www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University, Copyright ( ) 1993-2006, all rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of this software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html. This product includes Curl software which is Copyright 1996-2013, Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. The product includes software copyright 2001-2005 ( ) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://www.dom4j.org/ license.html. The product includes software copyright 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://dojotoolkit.org/license. This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html. This product includes software copyright 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http:// www.gnu.org/software/ kawa/software-license.html. This product includes OSSP UUID software which is Copyright 2002 Ralf S. Engelschall, Copyright 2002 The OSSP Project Copyright 2002 Cable & Wireless Deutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php. This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are subject to terms available at http:/ /www.boost.org/license_1_0.txt. This product includes software copyright 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at http:// www.pcre.org/license.txt. This product includes software copyright 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http:// www.eclipse.org/org/documents/epl-v10.php and at http://www.eclipse.org/org/documents/edl-v10.php. This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?license, http:// www.stlport.org/doc/ license.html, http:// asm.ow2.org/license.html, http://www.cryptix.org/license.txt, http://hsqldb.org/web/hsqllicense.html, http:// httpunit.sourceforge.net/doc/ license.html, http://jung.sourceforge.net/license.txt, http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/

license.html, http://www.libssh2.org, http://slf4j.org/license.html, http://www.sente.ch/software/opensourcelicense.html, http://fusesource.com/downloads/licenseagreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/licence.html; http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/license.txt; http://jotm.objectweb.org/bsd_license.html;. http://www.w3.org/consortium/legal/ 2002/copyright-software-20021231; http://www.slf4j.org/license.html; http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/license.html; http:// forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/software/tcltk/license.html, http:// www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/iodbc/wiki/iodbc/license; http:// www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/index.html; http://www.net-snmp.org/about/ license.html; http://www.openmdx.org/#faq; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt; http://www.schneier.com/blowfish.html; http:// www.jmock.org/license.html; http://xsom.java.net; http://benalman.com/about/license/; https://github.com/createjs/easeljs/blob/master/src/easeljs/display/bitmap.js; http://www.h2database.com/html/license.html#summary; http://jsoncpp.sourceforge.net/license; http://jdbc.postgresql.org/license.html; http:// protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto; https://github.com/rantav/hector/blob/master/license; http://web.mit.edu/kerberos/krb5- current/doc/mitk5license.html; http://jibx.sourceforge.net/jibx-license.html; and https://github.com/lyokato/libgeohash/blob/master/license. This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and Distribution License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code License Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php), the new BSD License (http://opensource.org/ licenses/bsd-3-clause), the MIT License (http://www.opensource.org/licenses/mit-license.php), the Artistic License (http://www.opensource.org/licenses/artisticlicense-1.0) and the Initial Developer s Public License Version 1.0 (http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/). This product includes software copyright 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For further information please visit http://www.extreme.indiana.edu/. This product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject to terms of the MIT license. This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775; 6,640,226; 6,789,096; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422; 7,676,516; 7,720,842; 7,721,270; 7,774,791; 8,065,266; 8,150,803; 8,166,048; 8,166,071; 8,200,622; 8,224,873; 8,271,477; 8,327,419; 8,386,435; 8,392,460; 8,453,159; 8,458,230; and RE44,478, International Patents and other Patents Pending. DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice. NOTICES This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software Corporation ("DataDirect") which are subject to the following terms and conditions: 1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. 2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. Part Number: MDM-DUG-10000-0001

Table of Contents Preface.... iv Informatica Resources.... iv Informatica My Support Portal.... iv Informatica Documentation.... iv Informatica Web Site.... iv Informatica How-To Library.... iv Informatica Knowledge Base.... v Informatica Support YouTube Channel.... v Informatica Marketplace.... v Informatica Velocity.... v Informatica Global Customer Support.... v Chapter 1: Introduction to Unclaimed Life Insurance Data Management Solution.... 1 Unclaimed Life Insurance Data Management Solution Overview.... 1 Users of Unclaimed Life Insurance Data Management Solution.... 2 Architecture - Informatica Components.... 2 Data Transfer Process.... 4 Chapter 2: Configuration.... 6 Configuration Overview.... 6 Prerequisites.... 7 Solution Package Components.... 7 Import Metadata Changelist into the Repository Manager.... 8 Add Custom Java Cleanse Library.... 8 Add Custom MDM Hub User Exits.... 9 Import Application Components into Informatica Data Director.... 9 Import Data Integration Mappings into the Developer Tool.... 9 Perform Post-Import Tasks.... 10 Deploy Composite Services.... 10 Chapter 3: Solution Components.... 11 Source Systems.... 11 MDM Hub Components.... 12 Base Objects.... 12 Lookup Tables.... 12 Landing Tables.... 13 Custom Tables.... 14 Staging Tables.... 15 Packages.... 17 Table of Contents i

Trust Value Settings.... 17 Data Cleansing and Standardization.... 18 MDM Hub User Exits.... 19 Match and Merge of Data.... 20 Hierarchy Management.... 21 External Match for TPA.... 22 Inbound Mappings.... 22 Map_DMF_DIM_Landing_Party_DM.... 22 Map_IDI_DIM_Landing_Party_DM.... 23 Map_Insurance_DIM_Landing_Agreement.... 25 Map_Insurance_DIM_Landing_Party_DM.... 26 Map_Insurance_DIM_Landing_Party_Role_Agreement.... 27 Map_Insurance_DIM_Landing_Postal_Address.... 27 Map_PA_DIM_Landing_Agreement.... 29 Map_PA_DIM_Landing_Party_DM.... 29 Map_PA_DIM_Landing_Party_Role_Agreement.... 30 Map_PA_DIM_Landing_Postal_Address.... 31 Map_TPA_Party_Party_DM_EMI.... 33 Outbound Mappings.... 34 Decedent Information Update.... 34 Error and Validation Reports.... 35 Map_Party_DM_EMO_TPA_Party_Output.... 35 Composite Services.... 35 Informatica Data Director User Interface.... 36 Hierarchy Configuration in Informatica Data Director... 36 Subject Area - Person.... 37 Subject Area - Address.... 37 Subject Area - Auto.... 38 Subject Area - Life.... 39 Subject Area - Property.... 39 Custom Tasks and Workflows.... 40 Chapter 4: Data Load Workflows.... 41 Initial Load Process.... 41 SSA Death Master File Incremental Load Process - Add.... 42 SSA Death Master File Incremental Load Process - Update.... 43 SSA Death Master File Incremental Load Process - Delete.... 44 TPA/Policy Admin/Customer Master Incremental Load Process - Add.... 45 TPA/Policy Admin/Customer Master Incremental Load Process - Update.... 45 Chapter 5: Reference Information.... 47 Additional Resources.... 47 ii Table of Contents

Index.... 48 Table of Contents iii

Preface The Unclaimed Life Insurance Data Management Solution Guide explains how insurance companies can get information about deceased people and identify beneficiaries. An administrator can use the information in this guide to configure the Unclaimed Life Insurance Data Management Solution. This guide assumes that you are familiar with Informatica MDM Multidomain Edition. Informatica Resources Informatica My Support Portal As an Informatica customer, you can access the Informatica My Support Portal at http://mysupport.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, Informatica Product Documentation, and access to the Informatica user community. Informatica Documentation The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at infa_documentation@informatica.com. We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments. The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to Product Documentation from http://mysupport.informatica.com. Informatica Web Site You can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services. Informatica How-To Library As an Informatica customer, you can access the Informatica How-To Library at http://mysupport.informatica.com. The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide iv

solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks. Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at http://mysupport.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through email at KB_Feedback@informatica.com. Informatica Support YouTube Channel You can access the Informatica Support YouTube channel at http://www.youtube.com/user/infasupport. The Informatica Support YouTube channel includes videos about solutions that guide you through performing specific tasks. If you have questions, comments, or ideas about the Informatica Support YouTube channel, contact the Support YouTube team through email at supportvideos@informatica.com or send a tweet to @INFASupport. Informatica Marketplace The Informatica Marketplace is a forum where developers and partners can share solutions that augment, extend, or enhance data integration implementations. By leveraging any of the hundreds of solutions available on the Marketplace, you can improve your productivity and speed up time to implementation on your projects. You can access Informatica Marketplace at http://www.informaticamarketplace.com. Informatica Velocity You can access Informatica Velocity at http://mysupport.informatica.com. Developed from the real-world experience of hundreds of data management projects, Informatica Velocity represents the collective knowledge of our consultants who have worked with organizations from around the world to plan, develop, deploy, and maintain successful data management solutions. If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at ips@informatica.com. Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at http://mysupport.informatica.com. The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at http://www.informatica.com/us/services-and-training/support-services/global-support-centers/. Preface v

C H A P T E R 1 Introduction to Unclaimed Life Insurance Data Management Solution This chapter includes the following topics: Unclaimed Life Insurance Data Management Solution Overview, 1 Users of Unclaimed Life Insurance Data Management Solution, 2 Architecture - Informatica Components, 2 Data Transfer Process, 4 Unclaimed Life Insurance Data Management Solution Overview The Unclaimed Life Insurance Benefits Act of 2011 requires insurance companies to identify beneficiaries of deceased people and to settle all insurance claims. The Unclaimed Life Insurance Data Management Solution (the Solution) integrates Informatica services and Informatica MDM Multidomain Edition to ensure compliance with the act. Insurance companies can use the Solution to extract information about deceased people from source systems, such as Social Security Administration (SSA) Death Master File (DMF), and load into the MDM Hub. The Solution uses a Data Integration Service to extract this information. Batch jobs within the MDM Hub match the incoming records with the records in the MDM Hub. The records that are not merged automatically are sent to a data steward. After a data steward approves the merge, the MDM Hub publishes records of deceased people through the outbound mappings and Java Message Service. The Policy Administration system or any other target system can use the following methods to get records with updated decedent information: Near real-time data transfer The target system subscribes to a queue to get notifications when Java Message Service publishes records with updated decedent information to the queue. Real-time data transfer The target system uses composite services to look up records with updated decedent information. 1

Batch data transfer The target system uses batch transfer to load the file with updated decedent information into their database. When target systems get records with updated decedent information, the insurance company must identify the beneficiaries of the deceased people and settle all claims. Users of Unclaimed Life Insurance Data Management Solution Users of Unclaimed Life Insurance Data Management Solution (the Solution) include insurance organizations, governments, law enforcement agencies, and medical hospitals. The following users can use the Soluiton to identify beneficiaries, verify death, and prevent identity fraud: Insurance and pension fund organizations Insurance and pension fund organizations can use the Death Master File to identify the beneficiaries of a deceased person. After identifying the beneficiaries, the organizations can contact the beneficiaries and settle the claims. Law enforcement agencies As part of investigations, law enforcement agencies and investigative firms can use the Death Master File to verify the death of a person. Governments To identify deceased people and prevent identity fraud, state governments, local governments, and security firms can compare the Death Master File with financial, credit, payment, and other applications. Medical hospitals Medical hospitals, researchers, and medical treatment programs can use the Death Master File to track former patients and study subjects. Architecture - Informatica Components The Unclaimed Life Insurance Data Management Solution (the Solution) uses the Informatica services, Informatica Developer, and Informatica MDM Multidomain Edition to transfer information about deceased people from source systems to target systems. The following image shows the Informatica components that the Solution uses: 2 Chapter 1: Introduction to Unclaimed Life Insurance Data Management Solution

The following text explains the Informatica components that the Solution uses: Informatica Administrator An administrator uses Informatica Administrator to create the Model Repository Service and Data Integration Service. An administrator might also configure Informatica Developer to connect to the model repository. Informatica Developer Informatica Developer (the Developer tool) connects to the model repository through the Model Repository Service. An administrator of the MDM Hub uses the Developer tool to import inbound and outbound mappings and change the mappings as required. Application Services The Informatica services access the domain configuration repository to maintain connections and metadata for the domain. Data Integration Service The Data Integration Service establishes integration between the MDM Hub and different source systems. Model Repository Service MDM Hub The Model Repository Service enables the Developer tool to connect to the model repository. The Data Integration Service establishes integration between the different source systems and the MDM Hub. Informatica Data Director A data steward uses Informatica Data Director to approve or reject requests to merge records. Informatica Address Doctor The Solution uses Informatica Address Doctor to standardize addresses in the incoming records. Architecture - Informatica Components 3

Informatica ActiveVOS You can use Informatica ActiveVOS to build internal workflows in the MDM Hub. The Solution starts a workflow when a data steward approves or rejects a merge request. You can use ActiveVOS to build this workflow. However, it is not required to use ActiveVOS to configure the Solution. Hub Server The Hub Server is a J2EE application that you must deploy on an application server. The Hub Server processes data within the Hub Store and integrates the MDM Hub with external applications. The Hub Server is the run-time component that manages core and common services for the MDM Hub. Hub Store The Hub Store stores and consolidates business data for the MDM Hub. The Hub Store consists of the MDM Hub Master Database and Operational Reference Store. Data Transfer Process The Unclaimed Life Insurance Data Management Solution (the Solution) reads decedent information from various source systems and sends the updated decedent information to the downstream systems. The following image shows the data flow from source systems to target systems: The Data Integration Service establishes integration between the different source systems and the MDM Hub. The following is the high-level process about how the Solution transfers data from source systems to target systems: 1. When you run the required inbound dataflow script, the inbound mappings extract information about deceased people from source systems, such as the SSA DMF, and loads it into the MDM Hub. 2. Stage jobs within MDM Hub use cleanse functions and Informatica Address Doctor to clean and standardize incoming records. 4 Chapter 1: Introduction to Unclaimed Life Insurance Data Management Solution

3. Match and merge jobs use multiple match rules to match incoming records with the records in the MDM Hub. 4. If the MDM Hub cannot automatically merge records, it creates tasks for a data steward. 5. A data steward approves or rejects merge records through Informatica Data Director. 6. When you run the required outbound dataflow script, the outbound mappings write merged records to a file and publish an error report and a validation report. 7. Java Message Service publishes automatically merged records to a queue. 8. The target systems can access records with updated decedent information. Data Transfer Process 5

C H A P T E R 2 Configuration This chapter includes the following topics: Configuration Overview, 6 Prerequisites, 7 Solution Package Components, 7 Import Metadata Changelist into the Repository Manager, 8 Add Custom Java Cleanse Library, 8 Add Custom MDM Hub User Exits, 9 Import Application Components into Informatica Data Director, 9 Import Data Integration Mappings into the Developer Tool, 9 Perform Post-Import Tasks, 10 Deploy Composite Services, 10 Configuration Overview To configure Unclaimed Life Insurance Data Management Solution, perform the following tasks: 1. Import metadata changelist or promote metadata changelist. 2. Add custom Java cleanse library. 3. Add custom MDM Hub user exits. 4. Import application components into Informatica Data Director. 5. Import data integration mappings into the Developer tool. 6. Configure inbound and outbound mappings. 7. Test inbound and outbound mappings. 8. Configure inbound and outbound dataflow scripts. 9. Deploy composite services. 6

Prerequisites Before you configure Unclaimed Life Insurance Data Management Solution, perform the following tasks: 1. Install and configure Informatica 9.5.0. Create a Data Integration Service and a Model Repository Service. Configure the Developer tool to connect to the Model Repository. 2. Install Informatica MDM Multidomain Edition 9.7.0. 3. If you have not created an Operational Reference Store (ORS), create an ORS after you install the database. After you create the ORS, import the seed into the ORS. The seed contains the initial metadata, such as REPOS tables, and other objects that the MDM Hub requires in the Hub Store. 4. Install Informatica MDM Multidomain Edition Resource Kit 9.7.0. 5. Configure the MDM Hub to use Address Doctor Cleanse Engine. 6. Optionally, configure the MDM Hub to use Informatica ActiveVOS workflow. Solution Package Components The Unclaimed Life Insurance Data Management Solution Accelerator (the Solution) is available as a ZIP file on Informatica Marketplace. Download the Solution from the following URL and extract the files: https://community.informatica.com/solutions/informatica_unclaimed_life_insurance_data_mgmt After you extract the files, the top level folder is MDM Solution that contains the following folders: Custom IDD The following folders are available inside the Custom folder: Cleanse Function Contains the CLEANSE.jar file that you must add to cleanse and standardize data coming from different source systems. Hub User Exit Contains the DIM971.jar file Siperian version and DIMVOS.jar file ActiveVOS version. You must add one of these files to the MDM Hub. Use the ActiveVOS version if you have integrated ActiveVOS with Informatica MDM Multidomain Edition. The jar file contains user exits that validate incoming records from different source systems. Web_App Contains the DIMService.zip file that includes the searchparty and getparty composite services. Use these services from a target system to search for postal addresses and insurance policies of parties stored in the MDM Hub. Contains the InfaDIMasterHub.zip that you must import through Informatica Data Director. The ZIP file contains the components to set up the application for a data steward. Met Export Contains the DIM_MET_EXPORT_06032014_HF1.change.xml file that you must import to get MDM Hub metadata. The MDM Hub metadata includes components, such as landing tables, user exits, lookup tables, staging tables, base objects, and match/merge rules. Prerequisites 7

Integration The Mercury DI folder is available inside the Integration folder. The Mercury DI folder contains the DIM_HF1_03032014.xml file that you must import through the Developer tool to configure the inbound and outbound data integration mappings. The following folders are available inside the Mercury DI folder: Sample Files Scripts Contains sample error files, source files, outbound files, and validation files. Contains scripts for the inbound and outbound data flows. You can change these scripts as required. Import Metadata Changelist into the Repository Manager You must apply the MDM Hub metadata changelist for Unclaimed Life Insurance Data Management Solution in your target environment. The MDM Hub metadata includes components, such as landing tables, user exits, lookup tables, staging tables, base objects, and match/merge rules. Metadata import works for all type of databases that the MDM Hub supports. 1. In the Hub Console, click Repository Manager. 2. Click the Import tab or the Promote tab. 3. Click the button next to the Source field. The Open Repository dialog box appears. 4. Click File Repository. 5. Browse to find the DIM_MET_EXPORT_06032014_HF1.change.xml metadata file available inside the <InstallDirectory>\MDM Solution\Met Export folder. 6. Select all the schema components or changed schema components and apply the changes. Add Custom Java Cleanse Library Multiple custom cleanse functions are available with Unclaimed Life Insurance Data Management Solution. These functions cleanse and standardize the data coming from different source systems. 1. In the Hub Console, under Model, click Cleanse Functions. 2. Click Cleanse Functions > Add Java Library. 3. Browse to find the Cleanse.jar file available inside the <InstallDirectory>\MDM Solution\Custom \Cleanse Function folder. 4. Enter a name and description for the library. 8 Chapter 2: Configuration

Add Custom MDM Hub User Exits The user exits available with Unclaimed Life Insurance Data Management Solution validate incoming records for add, update, and delete requests. 1. In the Hub Console, under Utilities, click User Object Registry and click Add. 2. Enter a description for the user exit. 3. Browse to find the DIM971.jar file available inside the <InstallDirectory>\MDM Solution\Custom\Hub User Exit\Siperian folder or the DIMVOS.jar file available inside the <InstallDirectory>\MDM Solution\Custom\Hub User Exit\ActiveVOS folder. Use DIMVOS.jar if you have integrated ActiveVOS with Informatica MDM Multidomain Edition. 4. Restart the application server. Import Application Components into Informatica Data Director When you load decedent information from different source systems into the MDM Hub, the match and merge job creates tasks for a data steward. A data steward uses Informatica Data Director to approve or reject these tasks. To set up the application for a data steward, import the application components into the Informatica Data Director. 1. Start Informatica Data Director Configuration Manager. Use the following URL: https://hostname:port/bdd/config 2. Click Import Complete IDD Application (ZIP) and browse to find the InfaDIMasterHub.zip file available inside the <InstallDirectory>\MDM Solution\IDD folder. 3. Under Bind Logical ORS, select the ORS from the list. You must select the ORS that you created when you installed MDM Multidomain Edition. 4. Click Save. 5. See the validation results and resolve any errors. Import Data Integration Mappings into the Developer Tool The inbound mappings populate data into the landing tables from files coming from different source systems. The outbound mappings publish records with updated decedent information, and create an error report and a validation report. 1. In the Informatica Developer, click File > Import. 2. Under Informatica, select Import Object Metadata File, and click Next. 3. Browse to find the DIM_HF1_03032014.xml file available inside the <InstallDirectory>\MDM Solution \Integration\Mercury DI folder, and click Next. Add Custom MDM Hub User Exits 9

4. Select the components from the source and select the target project where you want to import the objects. 5. Click Next and Finish. Perform Post-Import Tasks After you import mappings, change inbound and outbound mappings, and change the inbound and outbound dataflow scripts as required. 1. In the Developer tool, open the inbound data integration mapping objects and specify the path of the source files. 2. Open the outbound data integration mapping objects and specify the path where you want the mappings to create the output files. 3. Specify the appropriate database connection properties for the source and target database objects. 4. Save the changes. 5. Test and run the individual mappings and resolve any errors. 6. Use the Developer tool to deploy the DIM_App application to the Data Integration Service. The application is available in the DIM_HF1_03032014.xml file. 7. Change the scripts for inbound and outbound data workflows as required. Deploy Composite Services Target systems can use searchparty and getparty composite services to look up parties, postal addresses, and insurance policies that are stored in the MDM Hub. 1. In the DIMService.zip file available inside the <InstallDirectory>\MDM Solution\Custom\Web_App folder, change the files inside the Config folder as required. 2. Run the Build.xml file from the command line. The command generates a WAR file based on the changes you made to the configuration files. 3. Deploy the WAR file on the application server. 4. After you deploy the WAR file on the application server, use the following URL to get the WSDL: http://{hostname}:{port}/dimcompositeservice/mdmdimservice?wsdl 10 Chapter 2: Configuration

C H A P T E R 3 Solution Components This chapter includes the following topics: Source Systems, 11 MDM Hub Components, 12 Hierarchy Management, 21 External Match for TPA, 22 Inbound Mappings, 22 Outbound Mappings, 34 Composite Services, 35 Informatica Data Director User Interface, 36 Hierarchy Configuration in Informatica Data Director, 36 Custom Tasks and Workflows, 40 Source Systems Source systems are systems that send decedent information to the MDM Hub. Unclaimed Life Insurance Data Management Solution (the Solution) integrates with the following source systems: Customer Master System A system that contains customer master data. Internal Decedent Information System An internal system that sends decedent information. Lookup System System that stores standard lookup values, such as gender, prefix, and title. Policy Admin System a system that contains information about insurance policy holders. SSA System Social Security Administrator system that sends the Death Master File. Social Security Administration is a standard system that stores decedent information of people with Social Security numbers. The other systems are representation of systems that send decedent information to the MDM Hub. You can integrate other systems that contain decedent information with the Solution. 11

MDM Hub Components MDM Hub components process incoming records from different source systems and send records with updated decedent information to the downstream systems. The following MDM Hub components are included with this solution: Base objects Lookup tables Landing tables Custom tables Staging tables Packages and queries Trust settings Data cleansing and standardization User exits Match and merge of data Base Objects The match and merge job in the MDM Hub updates the relevant base objects to store consolidated data. The following base objects are available for Unclaimed Life Insurance Data Management Solution: C_BO_AGRMNT Stores details about insurance agreements. C_BO_PRTY_DM Stores party personal information, such as first name, last name, prefix, death date, and gender. C_BO_PSTL_ADDR Stores postal addresses. C_BR_PRTY_PSTL_ADDR Stores information about the relationship between party and postal address. In addition, it stores information about the type of postal address and the usage type of postal address. C_BR_PRTY_RLE_AGRMNT Stores information about the relationship between party and agreement. In addition, it stores information about the role and sub role of a person in an insurance agreement. Lookup Tables The MDM Hub processes need party information, such as gender, prefix name, country, and state, to process data. The lookup base tables store this information. The following lookup base tables are available for Unclaimed Life Insurance Data Management Solution: C_BT_AGRMT_TYP Stores information about the type of insurance agreement. 12 Chapter 3: Solution Components

C_BT_CNTRY Stores information about the country. C_BT_FLG Stores information about the flag. C_BT_GNDR Stores information about the gender. C_BT_PRFX_NM Stores information about the prefix name. C_BT_PRTY_RLE_AGRMNT Stores information about the role of a person in an insurance agreement. C_BT_PRTY_SUB_RLE_AGRMNT Stores information about the sub role of a person in an insurance agreement. C_BT_PRTY_TYP Stores information about the type of party. C_BT_PSTL_ADDR_TYP Stores information about the type of the postal address. C_BT_PSTL_ADDR_USG_TYP Stores information about the usage type of the postal address. C_BT_PSTL_ADDR_VLDTN_STS Stores information about the validation status of the postal address. C_BT_SFX_NM Stores information about the suffix name. C_BT_STATE Stores information about the state. Landing Tables Landing tables derive their structure from the base objects. A single landing table stores data from all source systems for a particular entity. Each landing table has a column Source System that distinguishes between data from different source systems. The following landing tables are available for this solution: C_L_AGRMNT Landing table to stores details about insurance agreements from all source systems. C_L_LKP_ADDR_USG_TYP Stores information about usage type of the postal address sent from the Lookup source system. C_L_LKP_ADDR_VLDTN_STS Stores information about the validation status of the postal address sent from the Lookup source system. C_L_LKP_AGRMNT_TYP Stores information about the type of insurance agreement, such as auto, life, or property, sent from the Lookup source system. MDM Hub Components 13

C_L_LKP_CNTRY Stores information about the country sent from the Lookup source system. C_L_LKP_FLG Stores information about the flag sent from the Lookup source system. C_L_LKP_GNDR Stores information about the gender sent from the Lookup source system. C_L_LKP_PRFX_NM Stores information about the prefix name sent from the Lookup source system. C_L_LKP_PRTY_RLE_AGRMNT Stores information about the role of a person in an insurance agreement sent from the Lookup source system. C_L_LKP_PRTY_SBRL_AGRMNT Stores information about the sub role of a person in an insurance agreement sent from the Lookup source system. C_L_LKP_PRTY_TYP Stores information about the party type sent from the Lookup source system. C_L_LKP_PSTL_ADDR_TYP Stores information about the address type sent from the Lookup source system. C_L_LKP_SFX_NM Stores information about the suffix name sent from the Lookup source system. C_L_LKP_STATE Stores information about the state. C_L_PRTY_DM Landing table to store party information from all source systems. C_L_PRTY_PSTL_ADDR Landing table to store the relationship between party and postal address. C_L_PRTY_RLE_AGRMNT Landing table to store the relationship between party and agreement. This table also stores the role and sub role of a party. C_L_PSTL_ADDR Landing table to store postal address from all source systems. Custom Tables Custom tables store information about error records, new records, and custom tasks that the MDM Hub processes create for a data steward. The following custom tables are available for Unclaimed Life Insurance Data Management Solution: C_L_CUSTOM_TASK Stores information about the custom tasks that the MDM Hub processes create for a data steward. 14 Chapter 3: Solution Components

C_L_ERR Stores all records that had errors. C_L_NEW_RCDS Stores all records that do not exist in the MDM Hub. C_L_LST_PBLSHD Stores information about the batch process names and the date on which the processes published the file with updated decedent information. Staging Tables Staging tables stage data before the MDM Hub processes process the staged data and update the base object records. The following staging tables are available for Unclaimed Life Insurance Data Management Solution: C_S_CM_AGRMNT Stores the details of insurance agreements sent from the Custom Master source system. C_S_CM_PRTY_DM Stores personal information, such as first name, last name, prefix, death date, and gender, sent from the Custom Master source system. C_S_CM_PRTY_PSTL_ADDR Stores information about the type of postal address and the usage type of postal address sent from the Customer Master source system. In addition, it stores information about the relationship between party and postal address. C_S_CM_PRTY_RLE_AGRMNT Stores information about the role and sub role of a person in an insurance agreement sent from the Customer Master source system. In addition, it stores information about the relationship between party and agreement. C_S_CM_PSTL_ADDR Stores the postal addresses sent from the Customer Master source system. C_S_IDI_PRTY_DM Stores personal information, such as first name, last name, prefix, death date, and gender, sent from the Internal Decedent Information source system. C_S_IDI_PRTY_PSTL_ADDR Stores information about the type of postal address and the usage type of postal address sent from the Internal Decedent Information source system. In addition, it stores information about the relationship between party and postal address. C_S_IDI_PSTL_ADDR Stores the postal addresses sent from the Internal Decedent Information source system. C_S_LKP_ADDR_USG_TYP Stores information about the usage type of postal addresses sent from the Lookup source system. C_S_LKP_ADDR_VLDTN_STS Stores information about the validation status of postal addresses sent from the Lookup source system. MDM Hub Components 15

C_S_LKP_AGRMNT_TYP Stores information about the type of insurance agreement sent from the Lookup source system. C_S_LKP_CNTRY Stores country code and country description sent from the Lookup source system. C_S_LKP_FLG Stores information about the flag sent from the Lookup source system. C_S_LKP_GNDR Stores information about the gender sent from the Lookup source system. C_S_LKP_PRFX_NM Stores information about the prefix name sent from the Lookup source system. C_S_LKP_PRTY_RLE_AGRMNT Stores information about the role of a person in an insurance agreement sent from the Lookup source system. C_S_LKP_PRTY_SBRL_AGRMNT Stores information about the sub role of a person in an insurance agreement sent from the Lookup source system. C_S_LKP_PRTY_TYP Stores information about the party type sent from the Lookup source system. C_S_LKP_PSTL_ADDR_TYP Stores information about the type of postal address sent from the Lookup source system. C_S_LKP_SFX_NM Stores information about the suffix name sent from the Lookup source system. C_S_LKP_STATE Stores information about the state sent from the Lookup source system. C_S_PA_AGRMNT Stores the details of insurance agreements sent from the Policy Admin source system. C_S_PA_PRTY_DM Stores personal information, such as first name, last name, prefix, death date, and gender, sent from the Policy Admin source system. C_S_PA_PRTY_PSTL_ADDR Stores information about the type of postal address and the usage type of postal address sent from the Policy Admin source system. In addition, it stores information about the relationship between party and postal address. C_S_PA_PRTY_RLE_AGRMNT Stores information about the role of a person in an insurance agreement sent from the Policy Admin source system. In addition, it stores information about the relationship between party and agreement. C_S_PA_PSTL_ADDR Stores the postal addresses sent from the Policy Admin source system. 16 Chapter 3: Solution Components

C_S_SSA_PRTY_DM Packages Stores personal information, such as first name, last name, prefix, death date, and gender, sent from the Social Security Administration source system. To complete the processing of data, MDM Hub processes need data from different tables. Packages contain the relevant queries that get the required data for processing. The MDM Hub processes use the following packages to get data: Data integration packages Hierarchy management packages Informatica Data Director packages MQ packages Services packages Trust Value Settings Different trust settings are assigned to the death information attributes. Trust for Death Date, Death Indicator, and External Match Indicator The following table shows the trust setting for death date, death indicator, and external match indicator attributes: Source System Maximum Minimum Customer Master 60 60 Interna Decedent Information 90 90 Policy Admin 60 60 SSA 90 90 SYS0 100 100 The Decay, Duration, and Graph values for the preceding trusts are 12, Month, and Linear. Trust for Death Source Flag The following table shows the trust setting for the death source flag: Source System Maximum Minimum Customer Master 90 90 Interna Decedent Information 60 60 Policy Admin 90 90 MDM Hub Components 17