Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Appendix A: Sizing and Platform Requirements
  9. Appendix B: Application Components
  10. Appendix C: IDD Security Configuration
  11. Appendix D: Data Security
  12. Appendix E: Example Role-Based Security Configuration
  13. Appendix F: Data Masking
  14. Appendix G: Siperian BPM Workflow Engine
  15. Appendix H: Locale Codes
  16. Appendix I: Troubleshooting
  17. Appendix J: Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Cleanse Match Server

Cleanse Match Server

The Cleanse Match Server run-time component is a servlet that handles cleanse requests. This servlet is deployed in an application server environment. The servlet contains two server components:
  • a cleanse server that handles data cleansing operations
  • a match server that handles match operations
The Cleanse Match Server is multi-threaded so that each instance can process multiple requests concurrently. It can be deployed on a variety of application servers.
The Cleanse Match Server interfaces with any of the supported cleanse engines, such as the Trillium Director cleanse engine. The Cleanse Match Server and the cleanse engine work to standardize the data. This standardization works closely with the Informatica Consolidation Engine (formerly referred to as the Merge Engine) to optimize the data for consolidation.

0 COMMENTS

We’d like to hear from you!