Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

Enable Search by Rules

Enable Search by Rules

When you enable a match rule set for Enable Search by Rules, you reserve that particular match rule set for use with the
SearchMatch
API. To use an Enable Search by Rules match rule set, the
SearchMatch
MatchType must be
NONE
and you must specify the match rule set in the
SearchMatch
request. If you use Enable Search by Rules then the MDM Hub only uses fuzzy matches.
You might want to perform a search with some empty fields. When SearchMatch performs a search using an Enable Search by Rules match rule set, it ignores empty fields provided by the search request. This prevents the exclusion of relevant records from the search results.
For more information about
SearchMatch
, see the
Multidomain MDM Services Integration Framework Guide
.
If you enable the optional Hub Server property to perform exact matches on fuzzy base objects, it affects match rules. The MDM Hub does not return matches if you use the same source columns for both exact and fuzzy matching. To avoid this problem, you must disable the
cmx.server.match.exact_match_fuzzy_bo_api
property in the cmxserver.properties file. For more information about the Hub Server properties, see the
Multidomain MDM Configuration Guide
.

0 COMMENTS

We’d like to hear from you!