Services Integration Framework Guide

10.4 HotFix 3
- 10.5
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 3
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

Appendix B: Frequently Asked Questions

How can I perform exact matches on fuzzy base objects?: To perform exact matches on fuzzy base objects, manually add the following property to the
<MDM Hub Installation Directory>\hub\cleanse\resources\cmxcleanse.properties
file:

cmx.server.match.exact_match_fuzzy_bo_api=1

Restart the application server after setting the
cmx.server.match.exact_match_fuzzy_bo_api
property.
Where can I find the debug log file for SIF requests?: You can find the
cmxserver.log
file in the following directory:

<MDM Hub Installation Directory>\hub\server\log
How can I change the processing time periods of SIF search requests?: You can add the following properties to the
<MDM Hub Installation Directory>\hub\cleanse\resources\cmxserver.properties
file to change the processing time periods of the SIF search requests:

Properties
Description
Default

sif.search.result.refresh.interval.seconds
Specifies the time interval to run the cleanup process for cached search requests.
The cleanup process also cleans the temporary tables that the unmerge process creates.

1 second

sif.search.result.query.timeToLive.seconds
Specifies the number of seconds for an unused search request to remain cached.
After the specified time period, the cleanup process removes the cached search requests.

900 seconds

sif.search.result.drop.batch.record.count
Specifies the number of cached search requests to process.
The number of searches that you specify are fetched until all the expired searches are processed.

200 searches

sif.search.result.drop.batch.interval.milliseconds
Specifies the number of milliseconds to wait after processing each batch of search results.
Use the
sif.search.result.drop.batch.interval.millisecond
property to insert a delay after processing each batch of search results.

0 milliseconds

cmx.server.match.max_time_searcher
Specifies the maximum time period for a search request to run.
If a search request does not complete within the specified time period, the search stops.

99999999 seconds
How to optimize the performance of a SearchMatch request?: Multi-threaded range processing:
Use multiple parallel threads to process the search ranges. By default, multi-threaded range processing is disabled. Set the following property to
true
in the
<MDM Hub Installation Directory>\hub\cleanse\resources\cmxcleanse.properties
file:
cmx.server.match.searcher.database.worker.multithreaded

Change the number of threads to use to process a SearchMatch request. Set the following property in the
<MDM Hub Installation Directory>\hub\cleanse\resources\cmxcleanse.properties
file:
cmx.server.match.searcher_thread_count

Set to 1 to use one thread for the SearchMatch API. Restart the application server after you set the
cmx.server.match.searcher_thread_count
property.

Fine-tuning the DBFILTERED feature:
By default, DBFILTERED is invoked when the SearchMatch record has only one SSA_KEY for fuzzy match key column. Set the following DBFILTERED threshold property in the
<MDM Hub Installation Directory>\hub\cleanse\resources\cmxcleanse.properties
file:
cmx.server.match.searcher.dbfiltered.max.key.size
The DBFILTERED feature is invoked when the SearchMatch record has a SSA_KEY that is less than or equal to the value of the
cmx.server.match.searcher.dbfiltered.max.key.size
property.
Specify the resultset size in number of rows: Set the following property to an optimal value in the
<MDM Hub Installation Directory>\hub\cleanse\resources\cmxcleanse.properties
file:
cmx.server.match.searcher.resultset.size

Routinely determine if the match key tables that are associated with base objects need to be reorganized. Reorganize match key tables based on their primary key column, SSA_KEY.

Properties	Description	Default
sif.search.result.refresh.interval.seconds	Specifies the time interval to run the cleanup process for cached search requests. The cleanup process also cleans the temporary tables that the unmerge process creates.	1 second
sif.search.result.query.timeToLive.seconds	Specifies the number of seconds for an unused search request to remain cached. After the specified time period, the cleanup process removes the cached search requests.	900 seconds
sif.search.result.drop.batch.record.count	Specifies the number of cached search requests to process. The number of searches that you specify are fetched until all the expired searches are processed.	200 searches
sif.search.result.drop.batch.interval.milliseconds	Specifies the number of milliseconds to wait after processing each batch of search results. Use the sif.search.result.drop.batch.interval.millisecond property to insert a delay after processing each batch of search results.	0 milliseconds
cmx.server.match.max_time_searcher	Specifies the maximum time period for a search request to run. If a search request does not complete within the specified time period, the search stops.	99999999 seconds

Rename Saved Search

Table of Contents

Services Integration Framework Guide

Services Integration Framework Guide

Appendix B: Frequently Asked Questions

Appendix B: Frequently Asked Questions