Configuration Guide

10.4 HotFix 3
- 10.5 HotFix 2
- 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

Process Server Properties

Identifies the server and port for the selected

Process Server

. The other properties control the behavior of the Process Server, such as which types of processes the server handles and the number of threads to use.

You can enable or disable the following types of processes on the

Process Server

Cleanse operations

Fuzzy match and query search processes

Load and merge batch processes

Elasticsearch processes

Best practice

: Keep it simple. Enable all the operations and processes on all the

Process Servers

. If performance becomes an issue, you can decide how to distribute the workload among the servers. For example, if you have a heavy cleanse workload, you might configure one

Process Server

for online cleanse operations and a different one for batch cleanse operations. If batch jobs for cleanse and match run at the same time, consider running the jobs on different

Process Servers

If you change the properties, restart the

Process Server

. The exception is thread counts, which do not require a restart. The following table describes the properties that you can specify:

Property	Description
Server	IP address or the fully qualified host name of the application server on which you deployed this Process Server . Do not use localhost as the host name.
Port	HTTP or HTTPS port of the application server on which you deployed this Process Server .
Cleanse Operations	Indicates whether this Process Server handles cleanse operations. Default is true. Use the Cleanse Mode option to specify whether this server handles batch jobs, real-time cleanse requests, or both.
Batch Threads for Cleanse and Fuzzy Match	Number of threads to use for cleanse, tokenize, and match batch jobs. Default is 1. Best practices : When you are using fuzzy match or address verification, enable one thread per CPU. For example, on a quad-core machine, set this value to 4. When you are not using fuzzy match or address verification, and most of the data cleansing involves strings, enable four threads per CPU. For example, on a quad-core machine, set this value to 16. When you are running the Process Server on a separate machine from the Operational Reference Store , add one additional thread to accommodate latency that might occur with a remote database. If you run a memory-intensive process, restrict the total memory allocated to all these threads in the JVM to 1 GB.
Cleanse Mode	Specifies the types of cleanse operations that this Process Server handles. Batch Only . Handles only cleanse requests that come from batch jobs. The cleanse functions are called by the mappings in the stage process. Online Only . Handles only real-time cleanse requests. Requests come from cleanse functions that are called implicitly by the CleansePut SIF API or that are configured explicitly in the IDD Subject Area Cleanse Function. Both . Handles both batch and online cleanse requests.
Fuzzy Match and Query Search Processing	Indicates whether this Process Server handles fuzzy match. Default is true. Use the Match Mode option to specify whether this server handles batch jobs, real-time match requests, or both.
Match Mode	Specifies the types of fuzzy match processing that this Process Server handles. Batch Only . Participates in matching only when the request comes from batch jobs. Online Only . Participates in matching only for real-time requests. Requests for real-time matching come from searchMatch SIF API calls and IDD extended search. Both . Participates in matching for batch and online requests.
Offline	Status of this Process Server . Selecting or clearing the check box does not change the state of the Process Server .
Load and Merge Batch Processing	Indicates whether this Process Server handles data load batch jobs and merge batch jobs. Default is false.
Threads for Load and Merge	Maximum number of threads to use for data load batch jobs and automerge batch jobs. Best practice : Enable four threads per CPU on the machine. For example, on a quad-core machine, set a value of 16. Default is 20.
CPU Rating	Specifies the relative CPU performance of the machines in the cleanse server pool. Best practice : If the performance of the machines that run the Process Servers are similar, keep the default value of 1. If this Process Server machine has double the performance of the other machines, set this value to 2.
Elasticsearch Processing	Indicates whether this Process Server handles the Initially Index Smart Search Data batch job. This batch job creates indexes for all the values of the searchable fields in a business entity.
Secured Connection (HTTPS)	Indicates whether this Process Server uses the HTTPS protocol. If selected, ensure that the Port option is set to an HTTPS port number.

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

Process Server Properties

Process Server Properties