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 2
  • All Products

Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 9.5.1

Upgrading from Version 9.5.1

Back Next

Configure Process Servers for Search

Configure Process Servers for Search

When you configure search with Elasticsearch, enable search on all the Process Server instances. Use the Process Server tool in the Hub Console and the
cmxcleanse.properties
 file to configure the Process Server properties for search.
  1. In the Hub Console of a node, start the Process Server tool.
  2. Click
    Write Lock
    Acquire Lock
    .
  3. In the right pane of the Process Server tool, click the
    Add Process Server
     button.
    The
    Add/Edit Process Server
     dialog box appears.
  4. Set the following properties of a Process Server for search:
    Property
    Description
    Enable Search Processing
    Indicates whether to enable search on the Process Server.
    Ensure that you select the option to enable search.
    Enable ZooKeeper
    Indicates whether to use the Process Server as the ZooKeeper server for the search configuration with Solr.
    For search with Elasticsearch, ensure that you clear the option to disable ZooKeeper.
  5. Click
    OK
    , and then click
    Save
    .
  6. Edit the
    cmxcleanse.properties
     file.
    The
    cmxcleanse.properties
     file in the following location:
    <MDM Hub Installation Directory>\hub\cleanse\resources
    1. 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
      .
      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.
    2. Remove the following properties that are configured for search with Solr:
      • solr.allowAdminConsole
      • zookeeper.tickTime
      • pingSolrOnStartup
  7. Save the
    cmxcleanse.properties
     file.
  8. Restart the application server.
0 COMMENTS
We’d like to hear from you!