Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.3 HotFix 3
  • All Products

Table of Contents

Search

  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

Configuration Guide

Configuration Guide

Back Next

Configuring Data Load

Configuring Data Load

You can configure the data load process to use an intermediate file or to directly load data into the database for the tokenization and match process. You can configure properties in the
cmxcleanse.properties
 file to specify the method of data load and the batch size. The default is direct load.
To change the default behavior, add data load properties to the
cmxcleanse.properties
 files. The
cmxcleanse.properties
 file is in the following directory:
On Windows.
<
MDM Hub installation directory
>\hub\cleanse\resources
On UNIX.
<
MDM Hub installation directory
>/hub/cleanse/resources
The following table describes the data load properties for tokenization and matching:
Properties
Description
cmx.server.tokenize.file_load
Specifies whether to use an intermediate file to load data into the database for tokenization. Set to
true
 to use an intermediate file to load data. Set to
false
 for direct data load. Default is
true
 for Oracle and IBM DB2 environments. Default is
false
 for Microsoft SQL Server environments.
Use of intermediate files to load data is not applicable to Microsoft SQL Server.
cmx.server.tokenize.loader_batch_size
Maximum number of insert statements to send to the database during direct load. Default is
1000
.
cmx.server.match.file_load
Specifies whether to use an intermediate file to load data into the database for matching. Set to
true
 to use an intermediate file to load data. Set to
false
 for direct data load. Default is
true
 for Oracle and IBM DB2 environments. Default is
false
 for Microsoft SQL Server environments and IBM DB2 environments configured for external match.
Use of intermediate files to load data is not applicable to Microsoft SQL Server.
cmx.server.match.loader_batch_size
Maximum number of insert statements to send to the database during direct load. Default is
1000
.
0 COMMENTS
We’d like to hear from you!