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: Glossary

Cleanse Requests

Cleanse Requests

All requests for cleansing are issued by batch APIs.
The batch APIs package a cleanse request as an XML payload and send it to a
Process Server
. When the
Process Server
receives a request, it parses the XML and invokes the appropriate code:
Mode Type
Description
Online operations
The result is packaged as an XML response and sent back through an HTTP POST connection.
Batch jobs
The
Process Server
pulls the data to be processed into a flat file, processes it, and then uses a bulk loader to write the data back.
  • The bulk loader for Oracle is the SQL*Loader utility.
  • The bulk loader for
    IBM DB2
    is the
    IBM DB2
    Load utility.
  • The bulk loader for
    Microsoft SQL Server
    uses the Java database connectivity driver.
The
Process Server
is multi-threaded so that each instance can process multiple requests concurrently. The default timeout for batch requests to a
Process Server
is one year, and the default timeout for online requests is one minute.
When running a stage or match job, if more than one
Process Server
is registered, and if the total number of records to be staged or matched is more than 500, and then the job will get distributed in parallel among the available
Process Servers
.

0 COMMENTS

We’d like to hear from you!