Configuration Guide

10.3

Back Next

Hub Server Properties

You configure the

Hub Server

properties in the

cmxserver.properties

file.

The

cmxserver.properties

file is in the following directory:

MDM Hub installation directory

>/hub/server/resources

Hub Server Environment Properties

The following properties set the location of the Hub Server and connection details for the application server and the database:

cmx.home: Installation directory of the
Hub Server
. This property is set during the
Hub Server
installation.
cmx.appserver.hostname: Name of the EJB cluster to which you want to deploy the
MDM Hub
. Specify host names of the cluster servers in the following format:
<host_name>.<domain>.com
For more information about deploying the
Hub Server
in a clustered environment, see the
Multidomain MDM Installation Guide
.
cmx.appserver.jnlp.protocol: Required to launch the Hub Console only in a cloud deployment. Must be added manually. Communication protocol to use with the Java Network Launch Protocol (JNLP) file that launches the MDM Hub Console in a cloud deployment. Valid values are
HTTP
or
HTTPS
.
cmx.appserver.naming.protocol: Naming protocol for the application server type. The default values are
iiop
for Websphere,
jnp
for JBoss 5,
remote
for JBoss 7, and
t3
for WebLogic. This property is set during the
Hub Server
installation.
cmx.appserver.rmi.port: Application server port. The default values are
2809
for Websphere,
7001
for WebLogic,
1099
for JBoss 5, and
4447
for JBoss 7. For more information about deploying the
Hub Server
in a clustered environment, see the
Multidomain MDM Installation Guide
.
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
Hub Server
installation.
cmx.server.attachment.temp.ttl_minutes: Number of minutes after a file is created in the TEMP storage before it expires. Set to
0
to prevent files from expiring. Default is
60
.
cmx.server.masterdatabase.type: Type of the
MDM Hub Master Database
. This property can have one of the following values:
DB2
,
Oracle
, or
MSSQL
. This property is set during the
Hub Server
installation.
cmx.server.masterdatabase.schemaname: Required for the IBM DB2 environments only. Use the property to specify the name of the
MDM Hub Master Database
when the name is other than
cmx_system
. Default is
cmx_system
.
cookie-secure: Secures
Data Director
session cookies. To enable secure IDD session cookies, uncomment the cookie-secure flag and set the value to
true
. Default is
false
.
Restart the
Hub Console
for the change to take effect.
http-only: Secures
Data Director
session cookies for HTTP only. To enable session cookies, uncomment the http-only flag and set the value to
true
. Default is
false
.
Restart the
Hub Console
for the change to take effect.
locale: Locale for the
Hub Server
and
Hub Console
. The value of this property is set when you first install the
Hub Server
.

Application Server Properties for JBoss

The Hub Server uses the following properties when the Hub Server is running in a JBoss application server:

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
Hub Server
installation.
cmx.jboss7.management.port: JBoss management port. Default is
9999
for JBoss. This property is set during the
Hub Server
installation.
cmx.jboss7.security.enabled: Enables JBoss EJB security. Set to
true
to enable JBoss EJB security. Set to
false
to disable JBoss EJB security. Default is
true
. For information about configuring JBoss security, see the
Multidomain MDM Installation Guide
.
cmx.server.ejb3: For JBoss 7 only. Set to
true
to enable application server EJB3 lookup. Default is
false
. This property is set during the
Hub Server
installation.
ejb-client-version: Optional. Must be added manually. Specifies the EJB client version. If you do not want to use the default JBoss EJB client, use
ejb-client-version
to specify a different EJB client. For information about configuring an EJB client for the
Hub Console
, see the
Multidomain MDM Installation Guide
.
jboss.cluster: For JBoss 7 only. Specifies whether EJB servers are clustered for the Hub Server. Set to
true
to enable EJB clustering. Set to
false
if you do not have clustered EJB servers. Default is
false
.

Application Server Properties for WebSphere

The Hub Server uses the following properties when the Hub Server is running in a WebSphere application server:

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.appserver.password: Password of the WebSphere administrator. This property becomes available when WebSphere administrative security is enabled.
cmx.appserver.username: User name of the WebSphere administrator. This property becomes available when WebSphere administrative security is enabled.
cmx.appserver.soap.connector.port: For WebSphere only. SOAP connector port. Default value is 8880 for WebSphere. For more information about deploying the Hub Server in a clustered environment, see the
Multidomain MDM Installation Guide
for WebSphere.
cmx.websphere.security.enabled: Specifies if WebSphere security is enabled. Set to
true
or
yes
to enable WebSphere administrative security. Default is
no
. For information about enabling WebSphere administrative security, see the
Multidomain MDM Upgrade Guide
.
cmx.websphere.security.sas.config.name: For WebSphere only. Custom name of the sas.client.props file. Use for environments that use secure EJB lookups.
Default is
sas.client.props
cmx.websphere.security.sas.config.url: For WebSphere only. Location of the sas.client.props file. Use for environments that use secure EJB lookups.
Default is
https://yourdomain.com:9443/cmx/filesx/Security/Websphere/sas.client.props
.
cmx.websphere.security.ssl.config.name: For WebSphere only. Custom name of the ssl.client.props file. For environments that use secure EJB lookups.
Default is
ssl.client.props
cmx.websphere.security.ssl.config.url: For WebSphere only. Location of the ssl.client.props file. Use for environments that use secure EJB lookups.
Default is
https://yourdomain.com:9443/cmx/filesx/Security/Websphere/ssl.client.props
.
was.jms.log.dir: Optional. Must be added manually. For WebSphere only. Specifies the location of the log directory for SIB, which is a WebSphere resource.
was.jms.permanent_store.dir: Optional. Must be added manually. For WebSphere only. Specifies the location of the permanent store directory for SIB, which is a WebSphere resource.
was.jms.temp_store.dir: Optional. Must be added manually. For WebSphere only. Specifies the location of the temporary store directory for SIB, which is a WebSphere resource.

Database Properties

The following properties can be set for databases:

cmx.server.loadWorker.max.joins.optimization: Optional. Must be added manually. For IBM DB2 only. Specifies the maximum number of joins used in a query. Set to
20
when queries, with more than 12 lookup tables in a load job, take an excessively long time to run in DB2. Default is
30
.

General Properties

The following properties set the location of the Hub Server and the behavior of the Hub Server processes:

cmx.outbound.bypass.multixref.insystem: Optional. Must be set manually. Set to
true
to bypass the creation of messages on the Hub Server when a SIF API updates a base object with multiple cross-reference records. Default is
false
.
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.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.working_files.location: Location of the cleanse job working files.
MDM Hub
uses this property during the
Hub Server
initialization routine. This property is set during the
Hub Server
installation. Do not modify this property. For information about integrating cleanse engines, see the
Multidomain MDM Cleanse Adapter Guide
.
cmx.server.encryptionMethod: Optional. Must be added manually. Set to
SSL
to enable SSL encryption.
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.met.max_send_size: Maximum file size, in bytes, that the
Repository Manager
can send. Default is
9000000
.
cmx.server.met.promotion_snapshot: Optional. Must be added manually. Set to
true
to enable generation of
.meta
files. Set to
false
to disable generation of
.meta
files. Default is
true
.
cmx.server.multi_data_set_schema: Optional. Must be added manually. Set to
true
to enable message trigger XML messages to contain the parent record and all corresponding child records. Set to
false
to disable message trigger XML messages to contain the parent record and all corresponding child records. Default is
false
.
cmx.server.poller.monitor.interval: Number of seconds between polls to all servers. Set to
0
to disable server polling. Default is
30
.
cmx.server.selective.bvt.enabled: Optional. Must be added manually. Specifies that the MDM Hub only applies BVT calculation to fields that are part of the SIF request. Set to
true
so that the MDM Hub updates only the fields specified in a SIF request. Default is
false
.
cmx.server.validateServerCertificate: Optional. Must be added manually. Set to
false
to turn off server certificate validation. Default is
true
.
cmx.web.console.session.download.timeout: Specifies the amount of time in minutes that you want to allow for launching the Hub Console after user authentication. Default is
5
. The Java Network Launch Protocol (JNLP) resources that the Hub Console requires must download within the specified time. If the JNLP resources fail to download within the specified time, users must reauthenticate to download the JNLP resources.
com.informatica.mdm.message.queue.max.bytes.threshold: Optional. Must be added manually. Specifies a maximum limit, in bytes, for messages sent to the message queue. If a message exceeds the specified size, the message will not be sent and the message status is set to Failed.
<connection factory name>.qcf.password: Optional. Must be added manually. Configures the
MDM Hub
to use the password set in the application server to configure JMS security.
<connection factory name>.qcf.username: Optional. Must be added manually. Configures the
MDM Hub
to use the user name set in the application server to configure JMS security. For more information about securing message queues, see "Configuring JMS Security".
databaseId.password: Optional. Must be added manually. Specifies the encrypted password to use with Password Encryption tool. For more information about using the Password Encryption tool, see the
Multidomain MDM Resource Kit Guide
.
databaseId.username: Optional. Must be added manually. Specifies user name to use with Password Encryption tool. For more information about using the Password Encryption tool, see the
Multidomain MDM Resource Kit Guide
.
encryption.plugin.jar: Path and file name of the data encryption JAR file. For information about configuring data encryption for the
Hub Server
, see Step 3. Configure Data Encryption for the Hub Server.
jnlp.initial-heap-size: Initial heap size in megabytes for Java Web Start for JVM. Default is
128m
.
You can change the initial heap size if the
Hub Console
JVM runs out of memory. The optimal initial heap size depends on the memory and processing power of the client machine.
jnlp.max-heap-size: Maximum heap size in megabytes for Java Web Start for JVM. Default is
512m
.
You can change the max heap size if the
Hub Console
JVM runs out of memory. The optimal initial heap size depends on the memory and processing power of the client machine.
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.
searchQuery.buildBvtTemp.MaxRowCount: Optional. Must be added manually. Specifies the maximum number of records the GetOneHop API uses during BVT calculation. Default is
5000
. For more information about GetOneHop, see the
Multidomain MDM Services Integration Framework Guide
.
sif.api.hm.flyover.max.record.count: Optional. Must be added manually. Sets the maximum record count to limit the number of relationship records that the Hierarchy View relationship table displays. Default is
10000
.
After you update the server properties, you must validate the schema and then redeploy the
Data Director
application. For information about Hierarchy View relationship table records, see the
Multidomain MDM Data Director Implementation Guide
.
sif.jvm.heap.size: Optional. Must be added manually. Sets the default heap size, in megabytes, for APIs. Default is
256
.
sif.search.result.query.temptableTimeToLive.seconds: Optional. Must be added manually. For GetOneHop. Specifies the number of seconds data in temporary tables exist during a search query. Default is
30
. For more information about GetOneHop, see the
Multidomain MDM Services Integration Framework Guide
.
sip.hm.entity.font.size: Optional. Must be added manually. Sets the font size in
Hierarchy Manager
. Values can range from
6
to
100
. For information about setting
Hierarchy Manager
properties, see the
Multidomain MDM Data Steward Guide
.
sip.hm.entity.max.width: Optional. Must be added manually. Sets the maximum entity box width in
Hierarchy Manager
. Values can range from
20
to
5000
. For information about setting
Hierarchy Manager
properties, see the
Multidomain MDM Data Steward Guide
.
sip.lookup.dropdown.limit: Number of entries that appear in a menu in the Data Manager tool and the Merge Manager tool. This property does not have a minimum or maximum limit. Default is
100
.

Batch Process Properties

The following properties affect batch processes:

cmx.server.automerge.block_size: Block size for the automerge batch process. Default is
250
.
cmx.server.automerge.threads_per_job: Number of threads for the automerge batch process. The recommended maximum value to enter is
n
-1
, where n
is the number of CPUs available to the
Hub Server
. Default is
1
.
cmx.server.batch.acceptunmatchedrecordsasunique.block_size: Maximum number of records to process in each block for the Accept Non-Matched Records as Unique batch job. Default is
250
.
cmx.server.batch.acceptunmatchedrecordsasunique.threads_per_job: Number of threads that the MDM Hub uses to process the Accept Non-Matched Records as Unique batch job. Default is
20
.
cmx.server.batch.batchunmerge.block_size: Block size for the batch unmerge process. Default is
250
.
cmx.server.batch.load.block_size: Maximum number of records to process in each block for the load job. Default is
250
.
cmx.server.batch.recalculate.block_size: Maximum number of records to process in each block for the recalculate BVT and revalidate jobs. Default is
250
.
cmx.server.batch.threads_per_job: Number of threads that the
MDM Hub
uses to process the load, recalculate BVT, and revalidate batch jobs except automerge batch jobs. Also specifies the number of threads that the
MDM Hub
uses for the batch unmerge process.; The recommended maximum value to enter is
n
-1
, where n
is the number of CPUs available to the
Hub Server
. Default is
10
.
cmx.server.jobControl.noOfDays: Optional. Must be added manually. Number of days of history to process for a batch group job log in the Batch Group tool in the Hub Console. Default is
-1
, which indicates that a log includes all history details.
cmx.server.strp_clean.execution_mode: Optional. Must be added manually. Configures the scope of operation of the background cleanup process on the match key table.
Specify one of the following values for the scope of operation:
ALL. Deletes match tokens that have
invalid_ind=1
from all the match key tables on all the registered Operational Reference Stores.
CONFIGURED_ORS. Deletes match tokens that have
invalid_ind=1
from all the match key tables on the Operational Reference Stores that you specify. If you set the scope of operation to
CONFIGURED_ORS
, add the
cmx.server.strp_clean.ors
property to the
cmxserver.properties
file.
CONFIGURED_STRP. Deletes match tokens that have
invalid_ind=1
from the match key tables of specific base objects in specific Operational Reference Stores. If you set the scope of operation to
CONFIGURED_STRP
, add the
cmx.server.strp_clean.strp
property to the
cmxserver.properties
file.
cmx.server.strp_clean.ors: Optional. Must be added manually. Specifies the names of the Operational Reference Stores on which the background cleanup process must run to delete match tokens that are not valid. For example, to delete match tokens that have
invalid_ind=1
from all the match key tables in cmx_ors1 and cmx_ors2, add
cmx.server.strp_clean.ors=cmx_ors1,cmx_ors2
.
cmx.server.strp_clean.strp: Optional. Must be added manually. Specifies the Operational Reference Store and base object combinations for which the background cleanup process must run to clean up match key tables. For example, to delete match tokens that have
invalid_ind=1
from the match key tables for BO1 in cmx_ors1 and BO2 in cmx_ors2, add
cmx.server.strp_clean.strp=cmx_ors1.C_BO1,cmx_ors2.C_BO2
.
cmx.server.strp_clean.delete_records_count: Optional. Must be added manually. Specifies the number of records to clean up from the match key table.
cmx.server.strp_clean.retry_sec: Optional. Must be added manually. Specifies the time duration in seconds for which you want the MDM Hub to search for records with match tokens that are not valid in the match key table. Default is
60
.
cmx.server.strp_clean.threads_count: Optional. Must be added manually. Specifies the number of threads that the MDM Hub uses when it searches for records with match tokens that are not valid in the match key table. Default is
20
.
mq.data.change.threads: Number of threads to use to process JMS messages during the publish process. Default is
1
.
mq.data.change.batch.size: Number of JMS messages to process in each batch for the publish process. Default is
500
.
mq.data.change.timeout: Amount of time in seconds that is allowed to process the JMS messages. Default is
120
.

Security Manager Properties

The following properties affect the Security Manager:

cmx.server.clock.tick_interval: Number of milliseconds for 1 clock tick. Default is
60000
.
cmx.server.provider.userprofile.cacheable: Specifies if data can be cached. Caching data helps improve performance. Set to
true
to enable data caching. Set to
false
to disable data caching. Default is
true
.
cmx.server.provider.userprofile.expiration: Number of milliseconds that cached data survives before it expires. Default is
60000
.
cmx.server.provider.userprofile.lifespan: Number of milliseconds that cached data survives before it expires. Default is
60000
.
cmx.server.sam.cache.resources.refresh_interval: Number of clock ticks between intervals when the Security Access Manager (SAM) resource data is reloaded from the database. Default is
5
. For information about changing the refresh interval, see the
Multidomain MDM Security Guide
. To specify the number of milliseconds for 1 clock tick, use the
cmx.server.clock.tick_interval
property.
cmx.server.sam.cache.user_profile.refresh_interval: Number of clock ticks between intervals when the SAM resource data for a user profile is reloaded from the database. Default is
30
. To specify the number of milliseconds for 1 clock tick, use the
cmx.server.clock.tick_interval
property.

Oracle Database User Exits

The following properties can be used with Oracle databases. To use the properties, add the properties to both the cmxserver.properties file and the cmxcleanse.properties file.

cmx.server.dbuserexit.load.PostLoadUserExit: Optional. 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.put.PostLoadUserExit: Optional. Specifies whether MDM Hub calls a database user exit after performing a Put request. Set to true to enable this property. Default is false.
cmx.server.dbuserexit.PostMergeUserExit: Optional. Specifies whether MDM Hub calls a database user exit after performing a Merge request or an Automerge batch. Set to true to enable this property. Default is false.
cmx.server.dbuserexit.PreUnmergeUserExit: Optional. Specifies whether MDM Hub calls a database user exit before performing an Unmerge request or an Unmerge batch. Set to true to enable this property. Default is false.
cmx.server.dbuserexit.PostUnmergeUserExit: Optional. Specifies whether MDM Hub calls a database user exit after performing an Unmerge request or an Unmerge batch. Set to true to enable this property. Default is false.
cmx.server.dbuserexit.PreUserMergeAssigment: Optional. Specifies whether MDM Hub calls a database user exit before assigning unmerged records for review. Set to true to enable this property. Default is false.
cmx.server.dbuserexit.AssignTask: Optional. Specifies whether MDM Hub calls a database user exit before assigning tasks to users. Set to true to enable this property. Default is false.
cmx.server.dbuserexit.GetAssignableUserForTask: Optional. Specifies whether MDM Hub calls a database user exit before assigning tasks to users. Set to true to enable this property. Default is false.

Data Director General Properties

The following properties affect the behavior of

Data Director

After you update any of the following server properties, you must validate the schema and then redeploy the IDD application.

case.insensitive.search: If set to
true
, you can enable the case insensitiveness attribute for individual columns in the base object, which enables case insensitive query search in
Data Director
. A new index is created for each column on which this setting is enabled. As index management has its own performance overhead, use this property with caution. Default is
false
.
cmx.bdd.redirect_to_login_after_logout: Optional. Must be added manually. For Google SSO authentication in
Data Director
only. Set to
true
to configure
Data Director
to return to the login screen when you log out. Set to
false
to configure
Data Director
to redirect to the default logout screen when you log out. Default is
false
.
cmx.bdd.server.traffic.compression_enabled: Specifies if
Data Director
server traffic compression is enabled. Compressing traffic helps improve performance. Set to
true
to enable compression. Set to
false
to disable compression. Default is
true
.
cmx.dataview.enabled: When MDM administrators implement the subject area model, IDD users use the
Data
tab to search, edit, and manage records. This option specifies whether the
Data
tab and related elements appear in IDD applications.
In a new installation, the default is
false
. 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
true
.
When
cmx.dataview.enabled=true
, the following user interface elements appear in IDD applications:
New
tab, which opens the
New
window with subject areas
Data
tab with the following temporary interfaces:
Data workspace tab with subject area record views to edit and manage records
Search tabs with search queries and search query results
Task tabs to manage tasks
Links to the
Data
view from menus on other views
Custom tabs, if configured
When the
cmx.dataview.enabled
and
cmx.e360.view.enabled
property are set to
true
, and you want to enable the Cross-reference view, the History view, and the Matching Records view related to the Data Director with subject areas, set the
cmx.e360.match_xref.view.enabled
property to
false
.
If a MDM administrator implements the Entity 360 framework,
Data Director
users use the
Search
box to find records and entity tabs to edit and manage master data. In this case, you can hide the
Data
tab and related elements to avoid confusing users with similar functionality. For example, if you set
cmx.e360.view.enabled=true
, set
cmx.dataview.enabled=false
.
cmx.bdd.enable_url_authentication: Optional. Must be added manually. Enables authentication for URLs in
Data Director
. When enabled, when users log in, they pass their user name and password to the URL in
Data Director
. Set to
true
to enable authentication. Set to
false
to turn off authentication. Default is
false
.
cmx.bdd.password_blowfish_encrypted: Optional. Must be added manually. Enables Blowfish encryption for user passwords when authentication is enabled for URLs in
Data Director
. When enabled, passwords are not exposed in the URL in
Data Director
. Set to
true
to enable encryption. Set to
false
to turn off encryption. Default is
false
.
cmx.display.deployed.invalid.met.app: When the metadata for an Operational Reference Store is not valid,
Data Director
does not display the list of deployed applications. Applications that use a different, valid Operational Reference Store are also unavailable. To show the list of deployed applications, add this property and set it to
true
.
cmx.e360.view.enabled: When MDM administrators implement the Entity 360 framework, IDD users use the
Search
box to find records and a entity tabs to edit and manage records. 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
.
When
cmx.e360.view.enabled=true
, the following user interface elements appear in the
Data Director
applications:
New
tab, which opens the
New
window with business entities
Task Manager
tab to manage tasks
Search
tab with search results
Entity tabs to edit and manage business entity records. Entity tabs appear when you add a new business entity record or open a business entity record from search results. The label on the tab is dynamic, based on the action that opens the workspace.
Links to the
Business Entity
view from menus on other views
Custom tabs, if configured
cmx.dataview.taskmanager.enabled: Optional. Applicable only if the
cmx.e360.view.enabled
property is set to
false
. Indicates whether to display the Task Manager in a
Data Director
application that uses subject areas. Set to
true
to display the Task Manager. Default is
false
.
If the
cmx.dataview.taskmanager.enabled
is set to
false
and you do not create a Home page in the Provisioning tool for a Data Director application, the application displays the legacy Start page.
cmx.e360.match_xref.view.enabled: Specifies whether to enable the Cross-reference view and the Matching Records view for the Data Director with business entities. To enable the views, set to
true
. Default is
true
.
When the
cmx.dataview.enabled
and
cmx.e360.view.enabled
property are set to
true
, and you want to enable the Cross-reference view, the History view, and the Matching Records view related to the Data Director with subject areas, set the
cmx.e360.match_xref.view.enabled
property to
false
.
cmx.server.override_orstitle: Optional. Must be added manually. Specifies a preferred default title for current tasks when you log in to
Data Director
. Set the
cmx.server.override_orstitle
property to a preferred title in the
cmxserver.properties
file.; For example, if you set the property to
All Subject Areas
, the title appears as
Tasks for All Subject Areas
onscreen.
cmx.file.allowed_file_extensions: Lists the extensions of files that you can attach to a record or task in the Data Director application. By default, you can attach .pdf and .jpg files. When you specify multiple extensions, separate each value by a comma.
For example,
cmx.file.allowed_file_extensions=pdf,jpg,png,txt,zip,exe
.
cmx.file.max_file_size_mb: Specifies the size limit of files that you can attach in the Data Director application.
Data Director applications that use the subject area data model have a static size limit of 20 MB. If you specify a size limit greater than 20 MB, Data Director applications that use the subject area data model uphold the static size limit of 20 MB. Data Director applications that use the business entity data model uphold the size limit defined in the
cmx.file.max_file_size_mb
property.

Data Director Search Properties

The following properties affect the behavior of search in

Data Director

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.
es.index.refresh.interval: Sets the interval, in seconds, for Elasticsearch to commit the changes to the data after an Initially Index Smart Search Data batch job is run. The data is available for search after this time interval. Default is
30
.
This property impacts the high indexing volume encountered during initial indexing. Change the value only when suggested by Informatica Global Customer Support.
cmx.server.batch.smartsearch.initial.block_size: Maximum number of records that the Initially Index Smart Search Data batch job can process in each block. Default is 250. When you index a large data set, increase the number of records. The recommended maximum value is 1000.
cmx.server.match.max_time_searcher: Optional. Must be added manually. Specifies the maximum duration allowed for a search to run. Default is
99999999
seconds.
cmx.server.remove_duplicates_in_search_query_results: Specifies if duplicate records appear in the search query results. Set to
true
to show duplicate records in search query results. Set to
false
to hide duplicate records in search query results. Default is
false
.
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
.
cmx.ss.dirtyIndex.disable: Required in a cloud deployment if you use the Solr search engine. Must be added manually. Allows the Batch Viewer tool to start and prevents the warning icon that indicates an outdated index from being displayed in the Batch Viewer tool. Before you start the Batch Viewer tool in a cloud deployment, set to
true
. Default is
false
.
If you use the Elasticsearch search engine, you must set the property to
false
.
search.provisioning.numshards: Optional. Number of shards to create on your Elasticsearch 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 Hub Servers.
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.
sif.search.result.drop.batch.interval.milliseconds: Optional. Must be added manually. Specifies the interval, in milliseconds, that the SearchResultManager daemon pauses after each batch of search results cleansing is processed. Default is
0
.
sif.search.result.drop.batch.record.count: Optional. Must be added manually. Specifies the number of cached searches that the SearchResultManager daemon cleans up at one time. Default is
200
.
sif.search.result.query.timeToLive.seconds: Optional. Must be added manually. Specifies the number of seconds that an unused query remains cached. Default is
900
.
sif.search.result.refresh.interval.seconds: Optional. Must be added manually. Specifies the interval, in seconds, the SearchResultManager daemon pauses after running the cleanup process for cached searches. Default is
1
. For information about configuring SIF Search APIs, see the
Multidomain MDM Services Integration Framework Guide
.
ssl.keyStore: Required if you use the HTTPS port of the application server to configure the Hub 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 Hub 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 Hub 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 Hub Server. Manually add the property. Plain text password for the truststore file.

Data Director Task and Workflow Properties

The following properties affect tasks and review process workflows:

activevos.merge.workflow.service.name: You must specify the name of the MDM service calls to Informatica ActiveVOS. By default, this property is not defined. If the property is not defined, an automatic merge task is not created.
activeos.workflow.startup.timeout.seconds: Number of seconds to wait for Informatica ActiveVOS to create a task and return a task ID. Default is
10
.
cmx.e360.BPMProcess.view.enabled: Optional. Must be added manually.
Indicates whether to display the workflow diagram associated with the tasks in the Task Manager for the users with the ActiveVOS abAdmin role assigned. Set to
true
to display the workflow diagram. Default is
false
.
cmx.e360.BPMProcess.view.autologout.seconds: Optional. Must be added manually.
Number of seconds for an ActiveVOS session to remain active when you access the workflow diagram in the Task Manager. The session ends after the specified time period. Default is
30
.
cmx.server.task.grouppotentialmergebyruleid: Optional. Must be added manually. Specifies that a manual match task that generates multiple matches creates multiple task entries with the same ROWID. Set to
false
to create one task for each match entry. Default is
true
.
sip.task.assignment.interval: Number of minutes between automatic task assignments. Set to
0
to disable automatic task assignments. Default is
0
.
sip.task.assignment.start.delay: The time in minutes that automatic task assignment waits to start after the MDM Hub initializes. If you do not configure a delay, an error can occur when a user creates tasks. Default is
10
minutes.
sip.task.digest.interval: Number of hours between task notifications. Set to
0
to disable task notifications. Default is
0
.
sip.task.maximum.assignment: Number of tasks automatically assigned to each user when automatic task assignment is enabled. Default is
25
.
task.creation.batch.size: Optional. Must be added manually. Sets the maximum number of records to process for each match table for each iteration of the automatic tasks assignment process. Default is
1000
.
For information about configuring merge task properties, see the
Multidomain MDM Business Process Manager Adapter SDK Implementation Guide
.
task.creation.maximum: Optional. Must be added manually. Sets the maximum number of tasks that the
MDM Hub
creates for each match table. Default is
50
. If the number of tasks exceeds this value, then no more merge tasks for records in the match table can be created until the number of tasks associated with the match table are closed.

Siperian Workflow Engine Mail Server Properties

When you use the Siperian workflow engine, the following properties affect the behavior of the mail server that is used for task notifications:

mail.smtp.auth: Determines whether the specified mail server requires authentication for outgoing messages. If you use the
MDM Hub
mail server, set mail.smtp.auth to
true
. Default is
false
.
For information about configuring task notification emails, see the
Multidomain MDM Data Director Implementation Guide
.
mail.smtp.host: Name of the mail server for task notification emails. After you update the server properties, you must validate the schema and then redeploy the
Data Director
application. For information about configuring task notification emails, see the
Multidomain MDM Data Director Implementation Guide
.
mail.smtp.password: Password for the specified mail.smtp.user. If mail.smtp.auth is
true
, set a value for mail.smtp.password. For information about configuring task notification emails, see the
Multidomain MDM Data Director Implementation Guide
.
mail.smtp.port: Port number of the mail server. Default is
25
. For information about configuring task notification emails, see the
Multidomain MDM Data Director Implementation Guide
.
mail.smtp.sender: Specifies the email address of the task notification email sender. For information about configuring task notification emails, see the
Multidomain MDM Data Director Implementation Guide
.
mail.smtp.user: User name for the outgoing mail server. If mail.smtp.auth is
true
, set a value for mail.smtp.user. For information about configuring task notification emails, see the
Multidomain MDM Data Director Implementation Guide
.

Password Hashing and Custom Hashing Properties

The following properties affect password hashing and custom hashing algorithms:

password.security.hash.algo: Determines the hashing algorithm (ALGO_NAME) that is used to encrypt passwords in the MDM Hub. This property is set during the
Hub Server
installation. Set to
SHA3
to use the SHA3 hashing algorithm. Set to any other name, without special characters or spaces, for a custom hashing algorithm.
For more information about configuring hashing algorithms, see the
Multidomain MDM Security Guide
.
password.security.hash.algo.<ALGO_NAME>.class: Contains the underlying implementation class of the hashing algorithm specified in the
password.security.hash.algo
property. This property is set during the
Hub Server
installation.
password.security.hash.algo.property.<param-name>: Optional. Specifies any custom property of a configured hashing algorithm. By default, specifies the size property of the SHA3 hashing algorithm. Set to one of the following values:
224
,
256
,
384
, or
512
. Default is
512
.
com.informatica.mdm.security.certificate.provider.class: Set to
com.siperian.sam.security.certificate.PKIUtilDeafultImpl
for the default certificate provider in the MDM Hub. This property is set during the
Hub Server
installation.
informatica.security.unique.id: Customer hashing key that is used for password hashing. Informatica recommends to use a hashing key that contains a sequence of up to 32 hexadecimal characters with no delimiters. For more information about using a customer hashing key, see the
Multidomain MDM Security Guide
.
Protect the secrecy of your customer hashing key. If the value of the customer hashing key is lost, you must reset all passwords.

Security Configuration Utility Properties

To use the security configuration utility, set the following properties:

mdm.mail.server.host: Set to the SMTP server host of the email client that is used by the MDM administrator. For example,
smtp.gmail.com
. If you reset a password, the security configuration utility sends a new temporary password to the associated email address of the user account.
mdm.mail.server.port: Set to the port that is used by the email client that is used by the MDM administrator.
mdm.mail.server.user: Set to the email address of the MDM administrator. For example,
MDM_Hub_admin@gmail.com
.
mdm.mail.server.password: Enter the password for the email address of MDM administrator.
mdm.mail.server.smtpauth: Set to
true
to enable SMTP authentication. Required to connect to Gmail SMTP server.
mdm.mail.server.ttls: Set to
true
to enable TTLS authentication. Required to connect to Gmail SMTP server.

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

Hub Server Properties

Hub Server Properties

Hub Server Environment Properties

Application Server Properties for JBoss

Application Server Properties for WebSphere

Database Properties

General Properties

Batch Process Properties

Security Manager Properties

Oracle Database User Exits

Data Director General Properties

Data Director Search Properties

Data Director Task and Workflow Properties

Siperian Workflow Engine Mail Server Properties

Password Hashing and Custom Hashing Properties

Security Configuration Utility Properties