cmx.server.datalayer.cleanse.working_files.location
Installation directory of the
Process Server
files. This property is set during the
Process Server
installation. For information about integrating cleanse engines, see the
Multidomain MDM Cleanse Adapter Guide
.
cmx.server.datalayer.cleanse.working_files
Specifies whether the temporary files created during cleanse jobs are stored or not. You can use the temporary files for troubleshooting or auditing purposes. Set to
FALSE
to delete the temporary working files. Set to
KEEP
to store the temporary working files. Default is
KEEP
. For information about integrating cleanse engines, see the
Multidomain MDM Cleanse Adapter Guide
.
cmx.server.datalayer.cleanse.execution
Specifies where the cleanse jobs run. Set to
LOCAL
to run cleanse jobs on the application server. Set to
DATABASE
to run cleanse jobs on the database server. Default is
LOCAL
. For information about integrating cleanse engines, see the
Multidomain MDM Cleanse Adapter Guide
.
cmx.home
Installation directory of the
Process Server
. This property is set during the
Process Server
installation.
cmx.appserver.type
Type of application server. This property can have one of the following values:
JBoss
,
WebSphere
, or
WebLogic
. This property is set during the
Process Server
installation.
cmx.appserver.version
Version of JBoss on application server. This property can have one of the following values:
5
or
7
. This property is set during the
Process Server
installation.
cmx.appserver.soap.connector.port
For WebSphere only. SOAP connector port. Default value is
8880
for WebSphere.
cmx.websphere.security.enabled
Specifies if WebSphere security is enabled. Set to
true
or
yes
to enable WebSphere administrative security. Default value is
No
.
cmx.jboss7.management.port
JBoss management port. Default is
9990
for JBoss. This property is set during the Process Server installation.
cmx.server.load.nonsmos.sourcesystem.enddate.like.smos
Sets the relationship end-date of a system that is not a State Management Override System (SMOS) to be the same as that of an SMOS. Set to
true
to enable the relationship end-date to be the same as an SMOS.
cmx.server.match.lwm
Optional. Must be added manually. Enables the lightweight matching feature, which uses SSA-NAME3. Default is
false
.
Use this parameter with the
cmx.server.match.lwm_param
and
cmx.server.match.stats
properties.
cmx.server.match.lwm_param
Optional. Must be added manually. Requires that the
cmx.server.match.lwm
property is set to
Y
or
ONLY
. Add the SSA-NAME3 controls in the following format:
LWM=Y LWM_FIELDS=<field1>,<weight1>[,...,<fieldn>,<weightn>] LWM_LIMIT=<Reject>[,<Accept>]
cmx.server.match.stats
Optional. Must be added manually. Requires that the
cmx.server.match.lwm
property is set to
Y
or
ONLY
.
cmx.server.match.server_encoding
Configures encoding for match processing. Set to
1
to enable encoding for match processing. Default is
0
.
cmx.server.match.max_records_per_ranger_node
Number of records per match ranger node. More records per match uses more memory. The optimal number of records for each match depends on the memory and processing power available to the
Process Server
. Default is
3000
.
cmx.server.match.max_return_records_searcher
Sets a limit on the number of candidate records that are scored for a search thread during a fuzzy search operation. Must be added manually. Default is
-1
.
Set the property when the fuzzy search operations are time sensitive or CPU intensive. The MDM Hub considers the value of the
GETLIST Limit
property for the Operational Reference Store (ORS) to determine when a search thread stops. You configure the
GETLIST Limit
property by using the Databases tool in the Hub Console.
If you set a value for the
cmx.server.match.max_return_records_searcher
property, the fuzzy search operations might complete faster. The search threads stop when one of the following conditions is met:
The number of candidate records that are scored reach the value set for the
cmx.server.match.max_return_records_searcher
property.
The number of matched records reach the value set for the
GETLIST Limit
property.
If you do not set the property or use the default value of
-1
, the fuzzy search operations ignore the
cmx.server.match.max_return_records_searcher
property and are based on the
GETLIST Limit
property. The search threads stop when one of the following conditions is met:
The number of matched records reach the value set for the
GETLIST Limit
property.
No candidate records are left to score.
cmx.ss.engine
Required if you want to use the Elasticsearch engine for search. Manually add the property and set to
es
.
cmx.ss.enabled
Indicates whether to enable search.
In a new installation, the default is
true
. When upgrading, if this property is set, the value remains set to the pre-upgrade value. If this property is not set, the default is
false
.
JBoss 6.4.0 only. When you enable search in an environment that uses JBoss 6.4.0, you must set
cmx.server.match.file_load
to
false
. This setting forces the Process Server to use the JDBC uploader instead of native database utilities for matches.
cleanse.library.addressDoctor.property.SetConfigFile
Informatica Address Verification
configuration file path. For example,
C:/infamdm/Hub/cleanse/resources/AddressDoctor/5/SetConfig.xml
. For information about integrating cleanse engines, see the
Multidomain MDM Cleanse Adapter Guide
.
cleanse.library.addressDoctor.property.ParametersFile
Informatica Address Verification
parameters file path. For example,
C:/infamdm/Hub/cleanse/resources/AddressDoctor/5/Parameters.xml
.
cleanse.library.addressDoctor.property.DefaultCorrectionType
Informatica Address Verification
correction type, which must be set to
PARAMETERS_DEFAULT
.
cleanse.library.trilliumDir.property.config.file.1
Trillium Director cleanse library configuration file 1 file path. For example,
C:/infamdm/Hub/cleanse/resources/Trillium/samples/director/td_default_config_Global.txt
. For information about integrating cleanse engines, see the
Multidomain MDM Cleanse Adapter Guide
.
cleanse.library.trilliumDir.property.config.file.2
Trillium Director cleanse library configuration file 2 file path. For example,
C:/infamdm/Hub/cleanse/resources/Trillium/samples/director/td11_default_config_US_detail.txt
.
cleanse.library.trilliumDir.property.config.file.3
Trillium Director cleanse library configuration file 3 file path. For example,
C:/infamdm/Hub/cleanse/resources/Trillium/samples/director/td11_default_config_US_summary.txt
.
cleanse.library.trilliumDir11.property.config.file.1
Trillium Director 11 cleanse library configuration file 1 file path. For example,
C:/infamdm/Hub/cleanse/resources/TrilliumDirector11/samples/director/td11_default_config_Global.txt
. For information about integrating cleanse engines, see the
Multidomain MDM Cleanse Adapter Guide
.
cleanse.library.trilliumDir11.property.config.file.2
Trillium Director 11 cleanse library configuration file 2 file path. For example,
C:/infamdm/Hub/cleanse/resources/TrilliumDirector11/samples/director/td11_default_config_US_detail.txt
.
cleanse.library.trilliumDir11.property.config.file.3
Trillium Director 11 cleanse library configuration file 3 file path. For example,
C:/infamdm/Hub/cleanse/resources/TrilliumDirector11/samples/director/td11_default_config_US_summary.txt
.
cleanse.library.trilliumDir.property.set_maximum_retry_count
Optional. Sets the maximum number of times the
MDM Hub
attempts to connect to the Trillium server to process a record. Default is
5
. For information about increasing the number of network connection retries, see the
Multidomain MDM Cleanse Adapter Guide
.
cleanse.library.group1EntServer.property.config.file
Group1Software Enterprise Server configuration file. This property is set during the
Process Server
installation.
cleanse.library.group1CDQ.property.config.file
Group1Software CDQ Server configuration file. This property is set during the
Process Server
installation.
cleanse.library.firstLogicDirect.property.config.file
FirstLogicDirect configuration file. This property is set during the
Process Server
installation.
cmx.server.match.distributed_match
Optional. Must be added manually. Set to
1
to enable a
Process Server
for distributed cleanse and match. Set to
0
to disable a
Process Server
for distributed cleanse and match. Default is
1
.
For information about configuring multiple
Process Servers
for cleanse and match operations, see the
Multidomain MDM Installation Guide
.
cmx.server.cleanse.min_size_for_distribution
Optional. Must be added manually. Specifies the minimum size for distribution. The
MDM Hub
distributes the cleanse job if the minimum size for distribution is reached. Default is
1000
.
cmx.server.tokenize.file_load
Optional. Must be added manually. Specifies whether to use an intermediate file to load data into the database for tokenization. Set to
true
to use an intermediate file to load data. Set to
false
for direct data load. Default is
true
for Oracle and IBM DB2 environments, where using intermediate files improves performance. Default is
false
for
Microsoft SQL Server
environments.
cmx.server.tokenize.loader_batch_size
Optional. Must be added manually. Maximum number of insert statements to send to the database during direct load of the tokenization process. Default is
1000
.
cmx.server.match.file_load
Optional. Must be added manually. Specifies whether to use an intermediate file to load data into the database for matching. Set to
true
to use an intermediate file to load data. Set to
false
for direct data load. Default is
true
for Oracle and IBM DB2 environments. Default is
false
for
Microsoft SQL Server
environments and IBM DB2 environments configured for external match.
Match for BO works successfully using property
cmx.server.match.file_load=false
in
cmxcleanse.properties
when
cmx.ss.enabled=TRUE
and Solr is configured.
When the
cmx.server.match.file_load
property is set to
false
, the number of matches in the cleanse log might differ from the Batch Viewer. If the number of matches differ, refer to the number of matches listed in the Batch Viewer.
cmx.server.match.loader_batch_size
Optional. Must be added manually. Maximum number of insert statements to send to the database during direct load of the match process. Default is
1000
.
cmx.server.match.exact_match_fuzzy_bo_api
Optional. Must be added manually. Set to
1
to perform exact matches on fuzzy base objects. Set to
0
to disable exact matches on fuzzy base objects. Default is
0
.
Restart the application server for the change to take effect. For information about configuring exact matches on fuzzy base objects, see the
Multidomain MDM Services Integration Framework Guide
.
encryption.plugin.jar
cmx.server.bmg.use_longs
Optional. Must be added manually. Set to
1
to enable the
Process Server
to use long ROWID_OBJECT values. Set to
0
to disable the
Process Server
from using long ROWID_OBJECT values. Default is
0
.
cmx.server.match.threshold_to_move_range_to_hold
Optional. Must be added manually. Sets the upper limit of records that the Match Analyze job can move to the on-hold status. Default is
1000000
.
cmx.server.dbuserexit.load.PostLoadUserExit
Optional. Must be added manually to both the cmxserver.properties file and the cmxcleanse.properties file. For Oracle only. Specifies whether the MDM Hub calls a database postload user exit after the load process. Set to
true
to enable this property. Default is
false
. For information about enabling PL/SQL user exits, see the
Multidomain MDM Upgrade Guide
for your environment.
cmx.server.dbuserexit.PostLandingUserExit
Optional. Must be added manually. For Oracle only. Specifies whether
MDM Hub
calls a post-landing user exit. Set to
true
to enable this property. Default is
false
.
For information about enabling PL/SQL user exits, see the
Multidomain MDM Upgrade Guide
.
cmx.server.dbuserexit.PreStageUserExit
Optional. Must be added manually. For Oracle only. Specifies whether
MDM Hub
calls a database user exit before performing a Stage request. Set to
true
to enable this property. Default is
false
.
cmx.server.dbuserexit.PostStageUserExit
Optional. Must be added manually. For Oracle only. Specifies whether
MDM Hub
calls a database user exit after performing a Stage request. Set to
true
to enable this property. Default is
false
.
cmx.server.dbuserexit.PreMatchUserExit
Optional. Must be added manually. For Oracle only. Specifies whether
MDM Hub
calls a database user exit before performing a Match request. Set to
true
to enable this property. Default is
false
.
cmx.server.dbuserexit.PostMatchUserExit
Optional. Must be added manually. For Oracle only. Specifies whether
MDM Hub
calls a database user exit after performing a Match request. Set to
true
to enable this property. Default is
false
.
cmx.server.dbuserexit.PostMergeUserExit
Optional. Must be added manually. For Oracle only. Specifies whether
MDM Hub
calls a database user exit after performing a Merge request. Set to
true
to enable this property. Default is
false
.
cluster.flag
Optional. Must be added manually. For WebSphere only. Specifies whether clustering is enabled. Set to
true
to enable clustering. Set to
false
to disable clustering. Default is
false
.
cmx.server.cleanse.number_of_recs_batch
Optional. Must be added manually. Sets the maximum number of records for cleansing included in a batch. Default is
50
.
For information about configuring run-time behaviour in the
Process Server
, see the
Multidomain MDM Cleanse Adapter Guide
.
cmx.server.match.searcher_search_level
Optional. Must be added manually. Sets the search level for the Extended Search in
Data Director
. Value can be
Narrow
,
Typical
,
Exhaustive
, or
Extreme
. Default is
Narrow
.
After you update the server properties, you must validate the schema and then redeploy the
Data Director
application. For information about search levels, see
Search Levels. For information about configuring Extended Search, see the
Multidomain MDM Data Director Implementation Guide
.
cmx.server.match.searcher.database.worker.multithreaded
Optional. Must be added manually. When set to true, multiple parallel threads are used to process the search ranges and optimize the performance of the SearchMatch API. By default, multi-threaded range processing is disabled.
If you set the
cmx.server.match.searcher.database.worker.multithreaded
property, ensure that you also set the thread count by configuring the
cmx.server.match.searcher_thread_count
property.
cmx.server.match.searcher.dbfiltered.max.key.size
Optional. Specifies the DBFILTERED threshold to optimize the performance of the SearchMatch API. The DBFILETRED 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.
cmx.server.match.searcher.resultset.size
Specifies the resultset size of a SearchMatch database query.
cmx.server.match.searcher_thread_count
Optional. Must be added manually. Configures the thread count for the SearchMatch API. Default is
1
. Set to
1
to use one thread for the SearchMatch API.
If you set the
cmx.server.match.searcher_thread_count
property to a value other than the default value, ensure that you set the
cmx.server.match.searcher.database.worker.multithreaded
property to
true
.
For information on optimizing performance of the SearchMatch API, see the following H2Ls on the Informatica My Support Portal:
ex.max.conn.per.host
Sets the maximum number of Elasticsearch nodes that you want to connect to the host. Set to the number of Elasticsearch cluster nodes on the host.
ex.max.threads
Sets the maximum number of threads that you want the Apache asynchronous non-blocking receiver to use for each node in the Elasticsearch cluster. Default is
1
.
Change the value only when suggested by Informatica Global Customer Support.
Manually add the property. Indicates whether you can access the Solr Administration User Interface (Admin UI). Use the Solr Admin UI to view the configuration details, run queries, and analyze search data. Set to true to enable access to the Solr Admin UI. Set to false or remove the property to disable access to the Solr Admin UI.
Optional. Length of a single tick, in milliseconds. ZooKeeper uses tick as the basic time unit to regulate timeouts. Default is 2000. Increase the time based on your requirement and the performance of the machine on which ZooKeeper is enabled.
search.provisioning.maxshards
Optional. Maximum number of shards to create for each Solr collection on a single node when you index the search data. For optimal performance, create one shard for each collection on each node. Default is 1.
pingSolrOnStartup
Required if you use WebSphere and not applicable for JBoss and WebLogic. Must be added manually. Indicates whether to create Solr collections when you start the application server after you configure search. Set to true to create collections.
search.provisioning.numshards
Optional. Number of shards to create on your Solr environment. The value depends on the maximum number of shards and the total number of nodes. For example, if the maximum number of shards is 1 and the number of nodes is 3, you can create 3 shards. Default is the total number of Process Servers on which you enable search.
search.provisioning.numreplicas
Optional. Number of copies of the search engine (Solr or Elasticsearch) documents that you want to create on different nodes. Use the replication factor to create multiple copies of the documents in the shards of different nodes. You require multiple copies of the documents to achieve high availability if one or more nodes shut down unexpectedly. For example, if the replication factor is 2, you get two copies of the documents in two nodes. For Solr, the default is 1. For Elasticsearch, the default is 0.
facet.infacount
Optional. Applicable to the Solr search engine only. Number of search results for each shard that the search functionality uses to facet the results. The search functionality uses the results based on the rank of the results in the descending order. For example, if you have 3 shards and specify 2000 as the count, the search functionality facets 6000 search results. If you specify 0 or do not specify any value, the search functionality facets all the results. Default is 1000.
MAX_INITIAL_RESULT_SIZE_TO_CONSIDER
Optional. Manually add the property. Total number of search results to display in the
Data Director
application. The recommended maximum value is 250. Default is 130. Any value higher than 130 affects the performance of the
Data Director
application.
mdm.smartsearch.cache.ttl
Optional. Manually add the property. Number of milliseconds for the cached search results of a Search Business Entity web service request to survive before the cached results expire. Default is 60000.
min_rec_for_multithreading
Minimum batch size for the MDM Hub to apply multi-threaded batch operations to a batch job. Applies to the following types of batch job: Automerge, Unmerge, Load, Initially Index Smart Search Data, Stage, Distributed Match, and the tokenization process. Default is 1000.
mq.data.change.monitor.thread.start
In a multinode environment, specifies whether there is message queue polling for individual nodes. To disable message queue polling, set to
false
. Default is
true
on all Java virtual machines where an MDM Hub EAR file is deployed.
ssl.keyStore
Required if you use the HTTPS port of the application server to configure the Process Server. Manually add the property. Absolute path and file name of the keystore file.
ssl.keyStore.password
Required if you use the HTTPS port of the application server to configure the Process Server. Manually add the property. Plain text password for the keystore file.
ssl.trustStore
Required if you use the HTTPS port of the application server to configure the Process Server. Manually add the property. Absolute path and file name of the truststore file.
ssl.trustStore.password
Required if you use the HTTPS port of the application server to configure the Process Server. Manually add the property. Plain text password for the truststore file.
cmx.websphere.security.ssl.config.url
Required if you use the HTTPS port of the application server to configure the Process Server. For WebSphere only. Manually add the property. Absolute path of the
ssl.client.props
file with the file name.
cmx.outbound.bypass.multixref.insystem
Optional. Must be set manually. Set to
true
to bypass the creation of messages on the Process Server when a batch job updates a base object with multiple cross-reference records. Default is
false
.
cmx.server.stage.sqlldr.charset
Optional. If you upload data by using SQL*Loader and the uploaded data is corrupted, set this property to the character set that matches your data, for example, AL32UTF8. When you run a stage job, the stage job generates a control file for SQL*Loader with the specified character set. You can then reload the data. Default is
UTF8
.
cmx.server.stripDML.blockSize
Number of records that the MDM Hub processes in each block. Default is
100
.
cmx.server.stripDML.noOfThreadsForDelete
Number of threads that the MDM Hub uses to delete records from the match key tables. Default is
30
.
cmx.server.stripDML.noOfThreadsForInsert
Number of threads that the MDM Hub uses to insert records into the match key tables. Default is
50
.
cmx.server.stripDML.noOfThreadsForUpdate
Number of threads that the MDM Hub uses to update records in the match key tables. Default is
30
.
cmx.server.stripDML.useDeleteInsertLock
Optional. Must be set manually. Set to
true
to ensure MDM Hub runs tokenization during a match job or a tokenization API call on a base object with a large number of records. Default is
false
.
cmx.server.stripDML.useUpdate
Optional. Must be set manually. For IBM DB2 only. Set to
true
to improve performance in IBM DB2 environments during retokenization. Default is
false
.
