Table of Contents


  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Data Encryption Restrictions

Data Encryption Restrictions

When you configure data encryption for base object columns, data is stored in an encrypted form. You can use the encrypted data through
Data Director
. You cannot use the
Hub Console
tools such as the
Data Manager
or the
Merge Manager
to add or edit data to encrypted columns.
If you want to perform match jobs, ensure that the match rule does not include match columns with encrypted data. Match jobs require plain text data to generate match keys. Also, you cannot use wildcard characters and literal values in search queries.
A database in the
that has encrypted data cannot store calls from a SOAP user-interface that are not encrypted.
If you need to use SOAP calls to insert data into an encrypted column, the data must be pre-encrypted as SOAP calls do not encrypt data. If a SOAP call retrieves data from an encrypted column, the data is returned in an encrypted form. You cannot use encrypted columns for SOAP calls.


We’d like to hear from you!