Table of Contents

Search

  1. Preface
  2. Introduction to Informatica MDM - Customer 360
  3. Before You Install
  4. Installing MDM - Customer 360
  5. After You Install
  6. Business Processes for Customer Management
  7. Customizing Customer 360
  8. Upgrading Customer 360
  9. Troubleshooting

Installation and Configuration Guide

Installation and Configuration Guide

Migrating to the Data Model Based on the Party Table

Migrating to the Data Model Based on the Party Table

Customer 360
versions 10.2 HotFix 2 and later use the data model based on the Party table. If you upgraded to 10.2 HotFix 2 or use
Customer 360
version 10.2 HotFix 1 or 10.2, then
Customer 360
uses the data model based on the Party Role table. You can now migrate from the data model based on the Party Role table to the data model based on the Party table.
If you do not want to migrate to the data model based on the Party table, you can continue to use the data model based on the Party Role table.
  1. Promote the
    update_foreign_keys.change.xml
    change list.
  2. Validate the
    Customer 360
    Operational Reference Store.
  3. Update foreign keys and recalculate the best version of truth for the records.
  4. Validate the
    Customer 360
    Operational Reference Store.
  5. Promote the
    party_updates.change.xml
    change list.
  6. Validate the
    Customer 360
    Operational Reference Store.
  7. If you extended the data model, import the data model extensions.
  8. Reindex the data.
  9. Deploy the updated
    Customer 360
    components.
  10. Reconfigure the values for the Full Name row in the Hierarchy Manager.
  11. Remove the post-merge user exit.
  12. Delete the shards and the ZooKeeper data directory.

0 COMMENTS

We’d like to hear from you!