Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.3 HotFix 1
  • All Products

Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Configuration Guide

Configuration Guide

Back Next

Configure the Hub Server Properties

Configure the Hub Server Properties

You must configure all the Hub Server instances to enable search. Use the Hub Server tool in the Hub Console and the
cmxserver.properties
 file to configure the Hub Server properties for search.
  1. Use a text editor to open the
    cmxserver.properties
     file in the following location:
    <MDM Hub Installation Directory>\hub\server\resources\cmxserver.properties
  2. Configure the following properties for search:
    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
    The dirty index flags are not applicable to Elasticsearch. You must set the value to
    true
     to disable the use of dirty index for Elasticsearch. Default is
    false
    .
    This property is applicable to the Solr search engine and will be deprecated. For the Solr search engine, the property is set to
    false
     to ensure that the Batch Viewer does not stop responding.
    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.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
    .
    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.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.
    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.enrichcopager.thread_pool
    Manually add the property. Sets the number of threads the EnrichCoPager property uses from the thread pool to perform parallel ReadCO operations. Default is 30. If you set the number of threads to 1, the property is disabled.
    cmx.server.enrichcopager.min_rec_for_multithreading
    Sets the minimum number of records to return before the EnrichCoPager property uses multithreading. Default is 2.
    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.
After you update the Hub Server properties, you must validate the Operational Reference Store (ORS), and restart the Hub Console.
0 COMMENTS
We’d like to hear from you!