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.7.1

Upgrading from Version 9.7.1

Configure the Hub Server for Search

Configure the Hub Server for Search

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.dirtyIndex.disable
    Applicable to the Solr search engine and will be deprecated. Set to
    true
    for Elasticsearch. Default is
    false
    .
    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.
    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!