Search

Configuration Guide

Configuration Guide

10.3

Back Next

Process Server Properties

Process Server Properties

When you configure

Process Servers

, you can specify properties.

The following table describes the properties that you can specify:

Property	Description
Server	Host or machine name of the application server on which you deployed Informatica MDM Hub Process Server .
Port	HTTP or HTTPS port of the application server on which you deployed the Process Server .
Enable Cleanse Operations	Determines whether to use the Process Server for cleansing data. Select the check box to use the Process Server for cleansing data. Clear the check box if you do not want to use the Process Server for cleansing data. If an Operational Reference Store has multiple associated Process Servers , you can enhance performance by configuring each Process Server as either a match-only or a cleanse-only server. Use this option in conjunction with the Enable Match Processing check box to implement this configuration.
Threads for Cleanse Operations	Number of threads to use for cleanse, match, and tokenize operations. The default is 1. Thread counts can be changed without a Process Server restart. Consider the following factors when you set the thread count property: Number of processor cores available on the machine. Set the number of threads to the number of processor cores available on the machine for cleanse operations. For example, set the number of threads for a dual-core machine to two threads, and set the number of threads for a single quad-core to four threads. Set the number of threads to four times the number of processor cores available on the machine for batch operations. For example, set the number of threads for a dual-core machine to eight threads, and set the number of threads for a single quad-core to 16 threads. Remote database connection. If you use a remote database, set the threads for cleanse operations to a number that is slightly higher than the number of processor cores, so that the wait of one thread is used by another thread. Setting the number of threads slightly higher accounts for latency that might occur with a remote database. Process memory requirements. If you run a memory-intensive process, restrict the total memory allocated to all cleanse operation threads that run under the JVM to 1 GB. If you set this to any illegal values (such as a negative number, 0, a character, or a string), then it will automatically reset to the default value (1). After migration to a later MDM Hub version, you must change the thread count or default values are used.
Cleanse Mode	Mode that the Process Server uses for cleansing data. Batch Only . The Process Server handles only cleanse requests that come from batch jobs. The cleanse functions are called by the mappings in the stage process. Online Only . The Process Server handles only realtime 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 . The Process Server handles both batch and online cleanse requests.
Enable Match Processing	Determines whether to use the Process Server for matching data. Select the check box to use the Process Server for matching data. Clear the check box if you do not want to use the Process Server for matching data. If an Operational Reference Store has multiple associated Process Servers , you can enhance performance by configuring each Process Server as either a match-only or a cleanse-only server. Use this option in conjunction with the Enable Cleanse Operations check box to implementation this configuration.
Match Mode	Mode that the Process Server uses for matching data. Batch Only . The Process Server participates in matching only when the request comes from batch jobs. Online Only . The Process Server participates in matching only for realtime requests. Requests for realtime matching come from searchMatch SIF API calls, searchQuery API, and IDD extended search. Both . The Process Server participates in matching for batch and online requests.
Offline	The MDM Hub determines whether the Process Server is online or offline. Enabling or disabling the Offline property does not change the state of the Process Server.
Enable Batch Processing	Specifies whether the Process Server is enabled. Enable to use the Process Server. Default is disabled.
Threads for Batch Processing	Maximum number of threads to use for a batch process. Specify a value that is equivalent to four times the number of CPU cores on the system on which the Process Server is deployed. Default is 20.
CPU Rating	Specifies the relative CPU performance of the machines in the cleanse server pool. This value is used when deciding how to distribute work during distributed job processing. If all of the machines are the same, this number should remain set to the default (1). However, if one machine’s CPU were twice as powerful as the others, for example, consider setting this rating to 2.
Enable Search Processing	Indicates whether to enable search on the Process Server. Select the check box to enable search, or clear the check box to disable search.
Enable Secured Connection (HTTPS)	Indicates whether to use the HTTPS protocol to communicate with the Process Server. Select the check box to use the HTTPS protocol, or clear the check box to use the HTTP protocol. If you select to use the HTTPS protocol, you must specify the HTTPS port of the application server.
Enable ZooKeeper	Indicates whether to use the Process Server as the ZooKeeper server. If you want to use search, select the check box. In a multiple-host deployment, if you plan to enable ZooKeeper on this Process Server, enable search too.
ZooKeeper ID	Unique ID for the ZooKeeper server. Use any number from 1 to 255 as the ID.
ZooKeeper Client Port	Port number on which ZooKeeper server listens for client connections.
ZooKeeper Leader Port	Reserved for future use. Use 0 as the ZooKeeper leader port.
ZooKeeper Follower Port	Reserved for future use. Use 0 as the ZooKeeper follower port.
ZooKeeper Data Directory	Absolute path for the ZooKeeper to store the in-memory snapshots of the data and the transactional log of updates to the database. For optimal performance, use a directory in a drive that other processes do not share. Ensure that you use a valid directory because the Hub Console does not validate the directory when you save the Process Server.

Configure Process Servers for Data Cleansing

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.